This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/17646] [4.0 Regression] xgcc links 64bit objects into a 32bit target
- From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 6 Jan 2005 22:42:19 -0000
- Subject: [Bug target/17646] [4.0 Regression] xgcc links 64bit objects into a 32bit target
- References: <20040924065857.17646.olh@suse.de>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-06 22:42 -------
(In reply to comment #17)
> I tried this:
> That appears to work. Only the binaries like cc1 end up in
> /usr/libexec/gcc/powerpc64-suse-linux/4.0.0
> This should be /usr/lib64/gcc-lib (at least thats the place where cc1 is now).
> So is just passing --libexecdir=/usr/lib64 supposed to work? Have to try it now.
> No idea what /usr/libexec is and why SuSE did never use it.
No /usr/libexec is correct for executables which are never to be executed by the user themselves.
>From BSD's hier man page:
libexec/ system daemons & system utilities (executed by other programs).
before 3.4, we did place cc1 in /usr/lib/gcc-lib/ but that was plainly wrong, this changed and now we
place the cc1 (and the related files) in /usr/libexec/gcc/ which is more correct.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17646