From: Simon Stelling <blubb@gentoo.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] -fPIC - Toolchain broken?
Date: Wed, 18 Oct 2006 17:53:28 +0200 [thread overview]
Message-ID: <45364DF8.9000803@gentoo.org> (raw)
In-Reply-To: <45364363.3010601@getdesigned.at>
Sebastian Redl wrote:
> Hi,
>
> While trying to compile OpenOffice.org, I was blocked by the inability
> to compile icu-3.4.1.
> The compilation fails on linking the third library it tries to build,
> libicui18n.so, with this message:
>
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.1/../../../../x86_64-pc-linux-gnu/bin/ld:
> warning: creating a DT_TEXTREL in object.
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.1/../../../../x86_64-pc-linux-gnu/bin/ld:
> ucol_wgt.o: relocation R_X86_64_PC32 against `compareRanges' can not be
> used when making a shared object; recompile with -fPIC
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.1/../../../../x86_64-pc-linux-gnu/bin/ld:
> final link failed: Bad value
> collect2: ld returned 1 exit status
It worked fine on my working system (CFLAGS="-O2 -march=opteron -pipe"),
but failed the same way in my development chroot (CFLAGS="-ggdb
-march=k8 -pipe").
I didn't look at the code yet, but I guess it has some #ifndef
__OPTIMIZED__. __OPTIMIZED__ is set by gcc with -O2 and above. I guess
if you switch back to your -O3 CFLAGS it will compile.
> I even manually removed the previously built libraries (libicudata.so
> and libicuuc.so) and relinked them with -fPIC, although I don't even
> know whether the flag has any influence on linking. Same error.
-fPIC only affects compilation
> I have the same problem when manually trying to compile any
> Mozilla-based application. However, most programs and libraries build
> fine - I just finished merging KOffice without any problems.
>
> So, is my toolchain screwed up? Am I doing something wrong? Is the icu
> ebuild simply broken?
I have exactly the same versions of binutils in both working and
development system and never had problems, so I'd say all is fine on
your side. We'll have to fix the ebuild I guess.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 developer
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2006-10-18 15:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 15:08 [gentoo-amd64] -fPIC - Toolchain broken? Sebastian Redl
2006-10-18 15:28 ` Hemmann, Volker Armin
2006-10-18 15:53 ` Simon Stelling [this message]
2006-10-18 16:08 ` Simon Stelling
2006-10-18 17:41 ` Sebastian Redl
2006-10-18 18:32 ` Simon Stelling
2006-10-18 21:21 ` [gentoo-amd64] " Duncan
2006-10-19 9:54 ` Sebastian Redl
2006-10-19 13:11 ` Conway S. Smith
2006-10-19 15:42 ` Simon Stelling
2006-10-19 20:43 ` Duncan
2006-10-20 9:10 ` Simon Stelling
2006-10-23 14:20 ` Kevin F. Quinn
2006-10-23 15:22 ` Duncan
2006-10-19 20:33 ` Duncan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45364DF8.9000803@gentoo.org \
--to=blubb@gentoo.org \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox