apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Trawick <traw...@attglobal.net>
Subject Re: [PATCH] Re: setting LDFLAGS for apr build; won't be set in apr-config; why?
Date Tue, 30 Mar 2004 15:03:12 GMT
Joe Orton wrote:
> On Tue, Mar 30, 2004 at 09:25:30AM -0500, Jeff Trawick wrote:
> 
>>here's a more concrete example
>>
>>apr HEAD
>>RHEL 3.0 for PPC
>>libtool 1.4.3 from system install
>>
>>CFLAGS="-Xcompiler -m64" LDFLAGS="-Xcompiler -m64 -Xlinker -melf64ppc" \ 
>>./configure
> 
> 
> Isn't that equivalent to the simpler CC="gcc -m64" ./configure?

I guess if setting CC to a program and options doesn't bother you it shouldn't 
bother me either ;)  seems unnatural though

One good thing to come out of this is that a certain person is going to learn 
not to ask me how to build stuff, because they suggested CC="gcc -m64" and I 
thought "gross, it should work without mixing programs and options in the same 
envvar."

>>are there some build mysteries which explain why the attached patch should 
>>not be committed?
> 
> 
> There are probably other cases where the current behaviour is desirable,
> e.g.  if you want to use some special flag to link libapr which is only
> appropriate when linking a shared library (and can't be used when
> linking programs).
> 
> The "change it and see who complains" route sounds fine :)

not unexpected :)

Mime
View raw message