Re: Initial Compilation Error

Chris Bertinato <[email protected]> Sat, 26 Aug 2006 13:02:57 -0500
Newsgroups gmane.os.opendarwin.darwinports
Message-ID <[email protected]>
Excellent! Worked like a charm.

On Aug 25, 2006, at 6:39 PM, Ryan Schmidt wrote:

> On Aug 26, 2006, at 01:25, Chris Bertinato wrote:
>
>> When selfupdating I get this compilation error:
>>
>> cc -dynamiclib -L/usr/local/lib  -L/usr/lib -lcurl -lssl -lcrypto - 
>> lz darwinports.o portconf.o session.o util.o -o Darwinports.dylib - 
>> L/System/Library/Frameworks/Tcl.framework/Versions/8.4 - 
>> ltclstub8.4 -L/usr/local/lib  -L/usr/lib -lcurl -lssl -lcrypto -lz  
>> -lreadline  -lcrypto
>> /usr/bin/libtool: can't locate file for: -ltclstub8.4
>> /usr/bin/libtool: file: -ltclstub8.4 is not an object file (not  
>> allowed in a library)
>> /usr/bin/libtool: for architecture: cputype (16777234) cpusubtype  
>> (0) file: -lSystem is not an object file (not allowed in a library)
>> make[2]: *** [Darwinports.dylib] Error 1
>> make[1]: *** [all] Error 1
>> make: *** [all] Error 1
>> DEBUG: Error installing new DarwinPorts base: shell command "cd / 
>> opt/local/var/db/dports/sources/ 
>> rsync.rsync.darwinports.org_dpupdate1/base && ./configure -- 
>> prefix=/opt/local --with-install-user=root --with-install- 
>> group=admin --with-tclpackage=/Library/Tcl && make && make  
>> install" returned error 2
>>
>> I don't know whether this is relevant, but I also get a number of  
>> the same warning:
>>
>> 	In file included from util.c:37:
>> 	util.h:2:3: warning: style of line directive is a GCC extension
>> 	util.h:44:3: warning: style of line directive is a GCC extension
>> 	util.c:39:3: warning: style of line directive is a GCC extension
>>
>> I'm running Mac OS X 10.4.7(8J135) with Darwin kernel version  
>> 8.7.0.  Compiling with gcc 3.1.
>>
>> I get the same kind of errors when compiling the jpeg libraries.
>>
>> It seems as if the compiler is just mistaking an option for a  
>> filename, but I'm not sure if this is part of a more general  
>> problem.  Should I perhaps update gcc? Any help is appreciated.  
>> Cheers.
>
> Oh, goodness, yes. Why are you using gcc 3.1? You should be using  
> gcc 4.0.1 with Mac OS X 10.4.x. Install Xcode 2.4 right away, and  
> if that still leaves you compiling with gcc 3.1, use gcc_select to  
> switch to 4.0.1.
>
>