stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Sebor <se...@roguewave.com>
Subject Re: Next Darwin/Mac OS X Porting Problem...
Date Wed, 14 Mar 2007 16:55:55 GMT
Eric Lemings wrote:
> Yep that fixed it.  Opened up STDCXX-356 so you can track it.

Thanks! I've checked in your patch (although I forgot your
attribution -- sorry about that).

Martin

> 
> Brad.
> 
>> -----Original Message-----
>> From: Martin Sebor [mailto:sebor@roguewave.com] 
>> Sent: Tuesday, March 13, 2007 8:34 PM
>> To: stdcxx-dev@incubator.apache.org
>> Subject: Re: Next Darwin/Mac OS X Porting Problem...
>>
>> Eric Lemings wrote:
>>>  
>>> The util/localedef.cpp source file fails to compile.
>>>
>>> ...
>>> gcc runall.o cmdopt.o output.o util.o exec.o display.o -o exec 
>>> -L./stdcxx/lib -lstd -lsupc++ -lgcc_eh -lm
>>> gcc -c -I./stdcxx/include/ansi -D_RWSTDDEBUG    -D_RWSTD_USE_CONFIG
>>> -I./stdcxx/include -I./stdcxx/include -I./stdcxx/include/loc
>>                                          ^^^^^^^^^^^^^^^^^^^^^^
>>
>> This is the problem. You don't want ./stdcxx/include/loc
>> in the search path.
>>
>> I was going to continue with: "Look at one of our build
>> logs for an example of the correct command line:
>> http://people.apache.org/~sebor/stdcxx/results/redhat_as-5.0-e
>> m64t-gcc-32b-4.1.1-11s-log.gz.txt"
>> but I see we have -I$(TOPDIR)/include/loc there for the
>> utilities as well, and always have! It should be just
>> a matter of taking it out. Can you open a new issue for
>> this?
>>
>> Martin
>>
>>


Mime
View raw message