This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libgcc/66809] stage 1 build failure in libgcc on sparc-sun-solaris2.10
- From: "subscribe at teskor dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 09 Apr 2018 16:50:31 +0000
- Subject: [Bug libgcc/66809] stage 1 build failure in libgcc on sparc-sun-solaris2.10
- Auto-submitted: auto-generated
- References: <bug-66809-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66809
Michael Teske <subscribe at teskor dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |subscribe at teskor dot de
--- Comment #5 from Michael Teske <subscribe at teskor dot de> ---
Why not add the directory to the RPATH of the created binaries? I ended up
doing it manually afterwards by using the rpath utility from
https://blogs.oracle.com/solaris/changing-elf-runpaths-code-included-v2 , but
it could be easily done during linking. Are there any reasons against doing it?