| To: | scsh-users@scsh.net |
|---|---|
| Subject: | Re: 0.6.5 compilation problem with gcc 4.0.3 |
| From: | sqweek <sqweek@gmail.com> |
| Date: | Thu, 1 Jun 2006 11:08:48 +0800 |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=lnEHCbLNjJjmihko081xZNtydgDCGQptwA0LACAyCOeJoUp6k/G+lPL7+ogVkO4WW338QW/hDeIh4cTZT/Dtt3n6S0TDInSPPT8PQdaPOGe0Q/KJnLVXdn7kYaQ8eZejMqCX60DsYKS1JANamrC9FK/WFevkp5xmZ6fiqDsafmI= |
| List-id: | <scsh-users.list-id.scsh.net> |
On 01/06/06, Martin Gasbichler <gasbichl@informatik.uni-tuebingen.de> wrote: sqweek <sqweek@gmail.com> writes: > I moved the write_integer prototype outside the ps_write_integer > function body and it went and compile happily. Best guess is that gcc > is misinterpreting the intent of the static keyword in this context as > a persistant variable instead of a symbol local to the compilation > unit? This problem has been fixed in the latest version of scsh (0.6.7). It's available from <http://www.scsh.net>. Argh, I should check this kind of thing. Sorry for the line noise. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Next by Date: | Report from R6RS Editors Committee, Mitchell Wand |
|---|---|
| Next by Thread: | Report from R6RS Editors Committee, Mitchell Wand |
| Indexes: | [Date] [Thread] [Top] [All Lists] |