Linking cc1 to external libraries

Linking cc1 to external libraries

[Alexandre Courbot]

Hi everybody,

I wandered around the doc and the Makefiles, and have found no way to add 
additional libraries to link to for cc1. I need the compiler (and only the 
compiler) to link to one library that is installed on the system (using -L 
and -l options), but at first sight it doesn't seem possible. As a workaround 
I've included my library as a part of the backend, but that quite... gruiiik.

I know this is not something really common - but do someone know of a way to 
require additional linking when building cc1? That could be useful, and if it 
isn't possible yet it wouldn't require much more than an additional Makefile 
variable that the backend programmer could override...

Alex.

Re: Linking cc1 to external libraries

[Andrew Pinski]

I would look the variable `LIBS' (located around line 693 on the 
mainline).

Thanks,
Andrew Pinski


On Thursday, Apr 17, 2003, at 08:45 US/Eastern, Alexandre Courbot wrote:

> Hi everybody,
>
> I wandered around the doc and the Makefiles, and have found no way to 
> add
> additional libraries to link to for cc1. I need the compiler (and only 
> the
> compiler) to link to one library that is installed on the system 
> (using -L
> and -l options), but at first sight it doesn't seem possible. As a 
> workaround
> I've included my library as a part of the backend, but that quite... 
> gruiiik.
>
> I know this is not something really common - but do someone know of a 
> way to
> require additional linking when building cc1? That could be useful, 
> and if it
> isn't possible yet it wouldn't require much more than an additional 
> Makefile
> variable that the backend programmer could override...
>
> Alex.
>
>
>

Re: Linking cc1 to external libraries

[Alexandre Courbot]

> I would look the variable `LIBS' (located around line 693 on the
> mainline).

I had seen it too - unfortunately, it is used not only when linking cc1, but 
also for xgcc and cpp. Of course, it wouldn't hurt much to have these linked 
to the library as well, since cc1 would be. But it's certainly not the 
cleanest way to do. In my mind, since only cc1 need this lib, it doesn't make 
sense to link the other programs with it too.

Anyway, your mail made me think again about it, and it seems that it would be 
less hassle than including the lib to the backend. The problem (or should I 
rather say feature) still remains half-open, though.

Thanks!
Alex.

Re: Linking cc1 to external libraries

[Alexandre Courbot]

> I would look the variable `LIBS' (located around line 693 on the
> mainline).

Ah, actually I don't think it would work. The backend's Makefile fragments are 
outputted before LIBS is initially set, which results in an override of any 
value you would have put in it.

Alex.

Re: Linking cc1 to external libraries

[Alexandre Courbot]

> > I would look the variable `LIBS' (located around line 693 on the
> > mainline).
>
> Ah, actually I don't think it would work. The backend's Makefile fragments
> are outputted before LIBS is initially set, which results in an override of
> any value you would have put in it.

Woops. And I forgot that when linking cc1, -lstdc++ must obviously be 
specified, otherwise there will obviously be loads of undefined references. 
So in any way, I must be able to specify additional libraries for cc1. Since 
I'm manually modifying the generated Makefile for now, I'm open to any 
suggestion! :)

Alex.