[Xastir] Error upgrading from 1.7.1 to 1.9.2

Nick nwsnowboarder at verizon.net
Sun Jul 27 14:00:38 EDT 2008


Here it is


bash-3.2$ cc -v x.c    
i686-apple-darwin8-gcc-4.0.1: x.c: No such file or directory
Using built-in specs.
Target: i686-apple-darwin8
Configured with: /private/var/tmp/gcc/gcc-5363.obj~28/src/configure 
--disable-checking -enable-werror --prefix=/usr --mandir=/share/man 
--enable-languages=c,objc,c++,obj-c++ 
--program-transform-name=/^[cg][^.-]*$/s/$/-4.0/ 
--with-gxx-include-dir=/include/c++/4.0.0 --with-slibdir=/usr/lib 
--build=powerpc-apple-darwin8 --with-arch=nocona --with-tune=generic 
--program-prefix= --host=i686-apple-darwin8 --target=i686-apple-darwin8
Thread model: posix
gcc version 4.0.1 (Apple Computer, Inc. build 5363)
bash-3.2$

Gerry Creager wrote:
> Nick,
>
> Do you have the gnu compilers installed, or is it trying to use XLC? 
> please try 'cc -v x.c' and let us see the result.
>
> gerry
>
> Tom Russo wrote:
>> On Sun, Jul 27, 2008 at 10:47:22AM -0700, we recorded a 
>> bogon-computron collision of the <nwsnowboarder at verizon.net> flavor, 
>> containing:
>>> Found the config.log file, thank you Tom.
>>>
>>> Here it is:
>>>
>>> I see several potential problems under output variables, but not 
>>> sure how to resolve it.
>>
>> The problem is right here:
>>
>>> It was created by xastir configure 1.9.2, which was
>>> generated by GNU Autoconf 2.59.  Invocation command line was
>>>
>>>   $ ./configure
>>>
>> [...]
>>> configure:2229: checking for C compiler default output file name
>>> configure:2232: gcc    conftest.c  >&5
>>> /usr/bin/ld: 
>>> /usr/lib/gcc/i686-apple-darwin8/4.0.1/../../../libSystem.dylib 
>>> unknown flags (type) of section 6 (__TEXT,__literal16) in load 
>>> command 0
>>> collect2: ld returned 1 exit status
>>> configure:2235: $? = 1
>>> configure: failed program was:
>>
>> [...]
>>
>>
>> There is something wrong with your installation of the compiler, as 
>> it is
>> puking on a system dynamic library.
>>
>> I don't know anything about Mac OS X, so someone here with some 
>> experience
>> there might have to help you out.
>>
>



More information about the Xastir mailing list