This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/17219] -static and -statig-libgcc aren't doing what they should.
- From: "wilson at specifixinc dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 2 Sep 2004 21:26:37 -0000
- Subject: [Bug target/17219] -static and -statig-libgcc aren't doing what they should.
- References: <20040828001516.17219.gonnetp@inf.ethz.ch>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From wilson at specifixinc dot com 2004-09-02 21:26 -------
Subject: Re: -static and -statig-libgcc aren't doing what
they should.
gonnetp at inf dot ethz dot ch wrote:
> Looking forward to seeing thins fixed :)
It will probably only be fixed if you write a patch for it.
I'd like to repeat again that using static linking on Irix6 is not a
good idea.
> The multiple versions I have here are 64 and 32 bit versions, so whatever
> I link at compile time will be the right one. The problem is that I have
You should also have mips3 and mip4 versions of the 32-bit libraries.
If I remember right, there is no mips3 64-bit library. The mips4
libraries won't work on a mips3 machine. The mips3 libraries should
work on a mips4 machine. If you have a mips4 machine, the mips3
libraries might be optional ones that aren't installed on your machine.
But if you do a normal link, against the shared libraries, you don't
have to worry about any of this stuff. The right library will always
loaded in regardless of which machine you compile on and which machine
you run on.
> to deploy a stand-alone application on a bunch of irix boxes that don't
> have a gcc > 3.0 installed...
The best solution for this problem is to use --disable-shared when
configuring gcc. You will then get only static libgcc and libstdc++
libraries. You can then link normally, and get the static versions of
gcc libraries and shared/dynamic versions of the system libraries, which
is really what you want.
GCC defaults to -mips3, so these static libgcc and libstdc++ libraries
should work everywhere.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17219