------- Comment #20 from imam dot toufique at intel dot com 2008-07-02 16:17 ------- (In reply to comment #19) > (In reply to comment #7) > > > >So, you are suggesting that I should remove fPIC option, correct? > > > Yes. Is there a reason why you have CFLAGS set anyways? > > 2. -fPIC has always been set in all the other gcc versions that I have > > compiled through CFLAGS. So, I did not think about this issue until you > > pointed it out. > This does not explain _why_ you used -fPIC in the first place. > IOW, why did you ever start using -fPIC? > We could just recommend to you not to use -fPIC in the CFLAGS > for configuring GCC. But from the PR history it is not clear whether > you had a good reason to use it in the first place, thus it is difficult > to know what you may be working around here for. > > Do I need to exclude -fPIC for the other platform (e.g. x86_64) builds when > > I > > build gcc 4.3.1? I have tried building 4.3.1 in SLES10 with -fPIC option , > > and > > it built OK for me. > That may well be.
well... when libstdc and other shared libs are built, are they all built position independent? the whole idea here to make sure that we must build position independent libstdc.so and other shared libs. Moreover, I have tested with the -fPIC options in 4.3.2 pre-release and the build works OK. also, I am getting an error from 'ld' that it can't find symbol '-lc' . I am not sure if this gcc related or binutils related. any ideas? Please see comment #18 for more info. thanks -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36622
