Antwort: Re: wrong compiler flag detection

[jens . rehsack]

Hi Simon,

I've seen the new release came out will I was sick and it contains the 
fix. I tried it on AIX and it works well.
Thanks for your work.

Mit freundlichen Grüßen / Best Regards

Jens Rehsack
_________________________________________

Fa. Manß & Partner

Fa. Manß & Partner
Gebäude B151
51368 Leverkusen, Deutschland

Tel:  +49 - 214 - 30 - 41 562
Fax: +49 - 214 - 30 - 31 625
E-Mail: address@hidden
Web: http://www.BayerBBS.com

Geschäftsführung: Vorsitzender Daniel Hartert   |   Arbeitsdirektor 
Norbert Fieseler
Vorsitzender des Aufsichtsrats: Klaus Kühn
Sitz der Gesellschaft: Leverkusen   |   Amtsgericht Köln, HRB 49895




Simon Josefsson <address@hidden> 
06.03.2009 18:29

An
address@hidden
Kopie
address@hidden
Thema
Re: wrong compiler flag detection






Simon Josefsson <address@hidden> writes:

> address@hidden writes:
>
>> ld: 0706-005 Cannot find or open file: diagnostics-show-option
>>         ld:fopen(): No such file or directory
>> *** Error code 255
>
> Hi!  Thanks for the report.
>
> Ouch.  Libidn checks whether -fdiagnostics-show-option is supported by
> the compiler before using it, but it seems this parameter has another
> meaning for xlc compared to gcc.  As a work around, you can build libidn
> using 'make WARN_CFLAGS=' to avoid passing these extra flags to the
> compiler.
>
> I'm not sure how to fix this cleanly.  Ideas welcome.  I'll try to think
> about it as well.

I have changed so that the many warning flags are only tested for when
using gcc.  This should solve this problem for xlc, I think.  Please
confirm that the upcoming release fixes this for you.

http://git.savannah.gnu.org/cgit/libidn.git/commit/?id=fa40eeae60b65dbb0d57ab3e24d7e33c4bff1857


Thanks,
Simon