Ralf,
So here's my basic problem. GCC, Binutils and GLIBC don't really agree about
PIC nature of code. GCC seems to default to PIC unless you say -no-pic, but
even then doesn't remove the -KPIC flag to the assembler. GLIBC requires the
PIC symbol to be defined otherwise it uses non-pic assembly code which won't
compile with the -KPIC flag to the assembler (there are also a bunch of
linux/glibc compatiblity issues we won't get into right now).
So my questions is - should GCC by default generate non-pic code or should it
generate PIC code by default? If it generate PIC by default it needs to define
PIC and __PIC__ ... but this will cause problems when building a static version
of GLIBC (even though it's really a PIC version).
I would want to do the following - gcc by default doesn't build PIC code, fix
the -KPIC flag to be passed only when generating PIC code, and make a few minor
changes to GLIBC to allow all this to happen.
Comments?
Cheers
Tim
> On Tue, Mar 07, 2000 at 06:48:37PM +0000, Tim Wilkinson wrote:
>
> > I'm in the process of re-integrating the latest GCC, Binutils and Glibc
> > releases for a Linux/Mips machine (namely a Cobalt Cube). It would
> > appear that this hasn't been done for a while since things don't seem to
> > play nice right now. I'd like to know who else is working on this
> > little project so I can avoid duplicating effort - and I have a tonne of
> > questions regarding the "right" way to do various things.
>
> > If anyone working on similar stuff (you know who you are) can email me
> > on or off these lists I'd appreciate it.
>
> Just start asking me. While I don't know how current code work I've written
> most of what Cobalt's stuff is based on and also worked as a consultant for
> Cobalt for some time, so I should have answer to many of your questions.
>
> I'd like to ask you to also cc everything to [EMAIL PROTECTED],
> [EMAIL PROTECTED] and [EMAIL PROTECTED] For the latter
> list you'll need to be subscribed for posting vi [EMAIL PROTECTED]
> This are the lists which most of the Linux/MIPS developers are using;
> some of them will definately be interested in your work.
>
> > And of course I'd ultimately like to get this back into the various
> > source trees.
>
> Indeed. I should have done this myself ages ago.
>
> Greetings from Brazil,
>
> Ralf
--
Tim Wilkinson Tel: (510) 527-4025 ext 12
Transvirtual Technologies, Inc., Fax: (510) 559-3287
Berkeley, CA, USA. Email: [EMAIL PROTECTED]
