This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/39947] Shared libgcc getting clobbered for multilib builds
- From: "jon_y at users dot sourceforge dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 29 Apr 2009 08:37:10 -0000
- Subject: [Bug target/39947] Shared libgcc getting clobbered for multilib builds
- References: <bug-39947-17646@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #4 from jon_y at users dot sourceforge dot net 2009-04-29 08:37 -------
(In reply to comment #3)
> (In reply to comment #2)
> > The same problem will occur for all dll's (libstdc++-x,dll, libgfortran-x.dll,
> > libssp-x.dll, etc) that are built as part of gcc
> > Danny
>
> That's correct. We have to find a way to install those binaries for multilib
> builds into different locations, or we have to extend the DLL names by a target
> key.
> I would prefer here to use a different location, why not using in /bin target
> specific directories? Something like bin/dll32 and bin/dll64?
>
> Cheers,
> Kai
>
I would prefer a new naming scheme, that way, we don't need to change PATH (by
much) for the system to pick up the dlls.
btw, my libssp seems oddly placed.
<prefix>/lib/gcc/x86_64-w64-mingw32/bin/libssp-0.dll (64bit)
<prefix>/lib/gcc/x86_64-w64-mingw32/4.5.0/bin/libssp-0.dll (32bit)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39947