This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Please review 3.4 patches

http://gcc.gnu.org/ml/gcc-patches/2004-10/msg00795.html

This last one, at least, is clearly wrong.

You're now defaulting to --enable-shared, even on systems that may not support shared libraries at all.

What's wrong with Joe's suggested solution: set LD_LIBRARY_PATH when running programs from the stage1/ or stage2/ directories?

Also, do we have a list of the patches that went in post GCC 3.4.2 that are causing problems? I want to know what we will have to take out if we have to take things out.

I am unsympathetic to the "this problem always existed because of libgcc_s.so; we just get lucky because that happens to be on the machine" argument. In practice, people do not have the problem with libgcc_s.so; they only have it with libunwind.

--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]