Csound Csound-dev Csound-tekno Search About

[Csnd] Csound 5.10.1 build dies with ludicrous gcc arguments

Date2009-04-02 21:47
FromJeremy Henty
Subject[Csnd] Csound 5.10.1 build dies with ludicrous gcc arguments
AttachmentsNone  

Date2009-04-02 22:04
Fromvictor
Subject[Csnd] Re: Csound 5.10.1 build dies with ludicrous gcc arguments
They are defined in SConstruct. Looks like for some reason whitespaces
were inserted. Check if SConstruct appears to be correct.
----- Original Message ----- 
From: "Jeremy Henty" 
To: "Csound" 
Sent: Thursday, April 02, 2009 9:47 PM
Subject: [Csnd] Csound 5.10.1 build dies with ludicrous gcc arguments


>
> I'm trying to upgrade from 5.09 (which built without problem) to
> 5.10.1.  The build dies almost immediately:
>
>    CONFIGURATION DECISION: Using single-precision floating point for audio 
> samples.
>    Checking for C header file stdio.h... no
>     *** Failed to compile a simple test program. The compiler is
>     *** possibly not set up correctly, or is used with invalid flags.
>     *** Check config.log to find out more about the error.
>
> In config.log:
>
>    scons: Configure: Checking for C header file stdio.h...
>    .sconf_temp/conftest_0.c <-
>      |
>      |#include 
>      |
>      |
>    gcc -o 
> .sconf_temp/conftest_0.o -c -DGNU_GETTEXT -g -fomit-frame-pointer -freorder-blocks 
>  - D L I N U X - D P I P E 
> S -DBETA -DHAVE_SOCKETS -I. -IH -I/usr/include/fltk-1.1 -I/usr/local/include 
>  -I/usr/include -I/usr/include -I/usr/X11R6/include 
> .sconf_temp/conftest_0.c
>    gcc: D: No such file or directory
>    gcc: L: No such file or directory
>    gcc: I: No such file or directory
>    gcc: N: No such file or directory
>    gcc: U: No such file or directory
>    gcc: X: No such file or directory
>    gcc: D: No such file or directory
>    gcc: P: No such file or directory
>    gcc: I: No such file or directory
>    gcc: P: No such file or directory
>    gcc: E: No such file or directory
>    gcc: S: No such file or directory
>    gcc: cannot specify -o with -c or -S with multiple files
>    scons: Configure: no
>
> Where are those insane "- D L I N U X - D P I P E S" arguments coming
> from?
>
> The system is GNU/Linux, gcc 4.1.2, glibc 2.5.1.
>
> Regards,
>
> Jeremy Henty
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
> csound" 


Date2009-04-02 22:51
FromJeremy Henty
Subject[Csnd] Re: Re: Csound 5.10.1 build dies with ludicrous gcc arguments
AttachmentsNone  

Date2009-04-02 23:22
FromAlan Peter Fitch
Subject[Csnd] Re: Re: Re: Csound 5.10.1 build dies with ludicrous gcc arguments
Jeremy Henty wrote:
> On Thu, Apr 02, 2009 at 10:04:00PM +0100, victor wrote:
>> They are defined in SConstruct. Looks like for some reason whitespaces
>> were inserted. Check if SConstruct appears to be correct.
> 
> SConstruct looks OK (and this bit is the same as in 5.09):
> 
>     if getPlatform() == 'linux':
> 	commonEnvironment.Append(CCFLAGS = "-DLINUX")
> 	commonEnvironment.Append(CPPFLAGS = '-DHAVE_SOCKETS')
> 	commonEnvironment.Append(CPPPATH = '/usr/local/include')
> 	commonEnvironment.Append(CPPPATH = '/usr/include')
> 	commonEnvironment.Append(CPPPATH = '/usr/include')
> 	commonEnvironment.Append(CPPPATH = '/usr/X11R6/include')
> 	commonEnvironment.Append(CCFLAGS = "-DPIPES")
> 	commonEnvironment.Append(LINKFLAGS = ['-Wl,-Bdynamic'])
> 
> But.. the CSound  5.09 build now dies in exactly  the same way!!!  But
> it definitely  worked the  last time I  tried it.  Could  upgrading to
> Python 2.6.1 have done this?  I note that (a) SCons.Environment.Append
> has a lot of different cases depending on the types of things, and (b)
> the bug appears to strike  CCFLAGS but not CPPPATH or CPPFLAGS.  Maybe
> the CCFLAGS key is associated to a value of a different type?
> 
> Regards,
> 
> Jeremy Henty
> 
> 

CCFLAGS and is in double quotes "", the others are in single quotes ''.
Perhaps the strings are being interpreted as Unicode (16 bit characters)
for some reason.

What's your default language?


regards
Alan



-- 
Alan Fitch

Date2009-04-02 23:31
FromAnthony Kozar
Subject[Csnd] Re: Re: Re: Csound 5.10.1 build dies with ludicrous gcc arguments
> But.. the CSound  5.09 build now dies in exactly  the same way!!!  But
> it definitely  worked the  last time I  tried it.  Could  upgrading to
> Python 2.6.1 have done this?

Probably!  The two problem flags are surrounded by double quotes "".  Python
2.6 is probably configured to treat these as Unicode strings, thus producing
two bytes for each character.  Try single quotes or read the Python docs to
figure out why this is happening.

Python 2.6 is a bridge to Python 3.0 and Csound has not been tested with it
AFAIK.

Anthony Kozar
mailing-lists-1001 AT anthonykozar DOT net
http://anthonykozar.net/

Jeremy Henty wrote on 4/2/09 5:51 PM:

> 
> On Thu, Apr 02, 2009 at 10:04:00PM +0100, victor wrote:
>> They are defined in SConstruct. Looks like for some reason whitespaces
>> were inserted. Check if SConstruct appears to be correct.
> 
> SConstruct looks OK (and this bit is the same as in 5.09):
> 
>   if getPlatform() == 'linux':
> commonEnvironment.Append(CCFLAGS = "-DLINUX")
> commonEnvironment.Append(CPPFLAGS = '-DHAVE_SOCKETS')
> commonEnvironment.Append(CPPPATH = '/usr/local/include')
> commonEnvironment.Append(CPPPATH = '/usr/include')
> commonEnvironment.Append(CPPPATH = '/usr/include')
> commonEnvironment.Append(CPPPATH = '/usr/X11R6/include')
> commonEnvironment.Append(CCFLAGS = "-DPIPES")
> commonEnvironment.Append(LINKFLAGS = ['-Wl,-Bdynamic'])
> 
> But.. the CSound  5.09 build now dies in exactly  the same way!!!  But
> it definitely  worked the  last time I  tried it.  Could  upgrading to
> Python 2.6.1 have done this?  I note that (a) SCons.Environment.Append
> has a lot of different cases depending on the types of things, and (b)
> the bug appears to strike  CCFLAGS but not CPPPATH or CPPFLAGS.  Maybe
> the CCFLAGS key is associated to a value of a different type?
> 
> Regards,
> 
> Jeremy Henty
> 
> 
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"


Date2009-04-02 23:41
FromJeremy Henty
Subject[Csnd] Re: Re: Re: Re: Csound 5.10.1 build dies with ludicrous gcc arguments
AttachmentsNone  

Date2009-04-02 23:43
FromJeremy Henty
Subject[Csnd] Re: Re: Re: Re: Csound 5.10.1 build dies with ludicrous gcc arguments
AttachmentsNone  

Date2009-04-02 23:51
FromAlan Peter Fitch
Subject[Csnd] Re: Re: Re: Re: Re: Csound 5.10.1 build dies with ludicrous gcc arguments
Jeremy Henty wrote:
> On Thu, Apr 02, 2009 at 11:22:04PM +0100, Alan Peter Fitch wrote:
> 
>> CCFLAGS and is in double quotes "", the others are in single quotes ''.
> 
> No deal: I tried changing the double quotes to single quotes and it
> still broke exactly as before.
> 
> Regards,
> 
> Jeremy Henty
> 
> 
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 

What version of scons are you using? There's this bugfix listed in the
release notes of Scons...

RELEASE 1.1.0.d20081207 - Sun, 07 Dec 2008 19:17:23 -0800

    - Fix env.Append() and env.Prepend()'s ability to add a string to
      list-like variables like $CCFLAGS under Python 2.6.

regards
Alan

-- 
Alan Fitch

Date2009-04-02 23:57
FromJeremy Henty
Subject[Csnd] Re: Re: Re: Csound 5.10.1 build dies with ludicrous gcc arguments
AttachmentsNone  

Date2009-04-03 00:06
FromJeremy Henty
Subject[Csnd] Re: Re: Re: Re: Re: Re: Csound 5.10.1 build dies with ludicrous gcc arguments
AttachmentsNone