Re: Overriding stuff from OSKit libs, some random remarks, and patches

• To: Michael Hohmuth <hohmuth@innocent.com>
• Subject: Re: Overriding stuff from OSKit libs, some random remarks, and patches
• From: Alastair Reid <reid@cs.utah.edu>
• Date: Tue, 12 Oct 1999 12:30:18 -0600
• cc: oskit-users@cs.utah.edu
• In-reply-to: Your message of "12 Oct 1999 20:20:05 +0200." <7saepo4f1m.fsf@os.inf.tu-dresden.de>
• Sender: owner-oskit-users@fast.cs.utah.edu

Michael Hohmuth wrote:
> > One area where I did have trouble was convincing the linker that it
> > should actually use stuff from my library and not from the OSKit's
> > libraries.  For example, the linker liked to use osenv_irq_enable()
> > from liboskit_dev and not from my lib even though my lib was first on
> > the command line because this symbol was first used from within
> > liboskit_dev.
> 
> [snip]
> 
> So I'm back at sucking in my library's objects via kludges in header
> files...

For the sake of my sanity, I seem to have erased all details of this
kludge from my mind.

Could you use gcc's -u flag instead?

  gcc ... -u osenv_irq_enable libmichael.a liboskit_dev.a ...

or, alternatively, don't use .a files:

  gcc ... -u osenv_irq_enable michael1.o michael2.o ... liboskit_dev.a ...


--
Alastair Reid        reid@cs.utah.edu        http://www2.cs.utah.edu/~reid/

ps I'm working on a better way of specifying exactly what should be linked
   to what (a sort of "fancy linker") which should completely eliminate
   this kind of problem.

• Re: Overriding stuff from OSKit libs, some random remarks, and patches
• From: Michael Hohmuth <hohmuth@innocent.com>

• Prev: Re: Overriding stuff from OSKit libs, some random remarks, and patches
• Next: Re: No luck with Kaffe
• Index(es):
  • Main
  • Thread