Dave Korn wrote:
Roberto, what does ldd show on the various cc1 binaries in the different
stage directories of your most recent bootstrap? I'm guessing you'll see that
the stage 2 cc1 is linked against the system libstdc++ rather than the
newly-bootstrapped one.
$ find . -name cc1
./prev-gcc
On Mon, Jan 12, 2009 at 2:25 PM, Dave Korn
wrote:
> Yep. It particularly shows up on win32 because i) all references have to
> be resolved at final link time in an executable - perhaps by reference to a
> DLL, but they can't just be left dangling to be filled in at runtime by the
> loader as th
Joseph S. Myers wrote:
> On Mon, 12 Jan 2009, Roberto Bagnara wrote:
>
>> I am not sure I understand the question (and I am not familiar with Cygwin).
>> The answer to the question "Why is there C++ in my libppl" is that libppl
>> is written in C++. The C interface to the PPL, libppl_c, is also wr
On Mon, 12 Jan 2009, Roberto Bagnara wrote:
> I am not sure I understand the question (and I am not familiar with Cygwin).
> The answer to the question "Why is there C++ in my libppl" is that libppl
> is written in C++. The C interface to the PPL, libppl_c, is also written
> in C++. Your descrip
Sebastian Pop wrote:
Q3) Why is there C++ in my libppl? Have I done something wrong to get it
there in the first place, or is it supposed to work somehow?
At the end of stage 1, I can work around the problem by manually running
the final link command, but using the (native compiler's) g++ dri