[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-gcc-list] [avr-libc-dev] [bug #28837] using PSTR with c++ produ
From: |
Weddington, Eric |
Subject: |
Re: [avr-gcc-list] [avr-libc-dev] [bug #28837] using PSTR with c++ produces warnings |
Date: |
Wed, 2 Nov 2011 10:14:55 -0600 |
> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden On
> Behalf Of Joerg Wunsch
> Sent: Tuesday, November 01, 2011 10:08 AM
> To: address@hidden
> Cc: address@hidden
> Subject: Re: [avr-gcc-list] [avr-libc-dev] [bug #28837] using PSTR
with
> c++ produces warnings
>
>
> . use --disable-shared when configuring the gmp, mpc, and mpfr
> libraries for your new compiler
>
> (In the latter case, make sure that there are no .so libs from
> previous attempts sitting around in ${prefix}/lib.)
>
> Based on experience from previous toolchain compilations, it's also
> always a good idea to reset PATH to the minimal elements that are
> strictly needed for the compilation, like /bin/:/usr/bin, or
> /bin:/usr/bin:/usr/local/bin.
>
The above advice always worked for me. Personally I don't like messing
around with shared libraries (DLLs) unless I have to. Simplifying the
PATH also has always made building things easier. I do this in my build
scripts. A lot of build problems that I have run into seems to get fixed
quickly by fixing the PATH.
Re: [avr-gcc-list] [avr-libc-dev] [bug #28837] using PSTR with c++ produces warnings, Volker Kuhlmann, 2011/11/05