[openbeos] Re: cannot build R5KernelStaticLibrary (please reply to this mail, not the previous one)

  • From: "Waldemar Kornewald" <Waldemar.Kornewald@xxxxxx>
  • To: <openbeos@xxxxxxxxxxxxx>
  • Date: Wed, 3 Sep 2003 18:08:25 +0200

> On 2003-09-02 at 02:19:45 [+0200], Ingo Weinhold wrote:
> >
> > On 2003-09-01 at 18:50:36 [+0200], Waldemar Kornewald wrote:
> > > The original mail was sent using the wrong email account, so here it
is a
> > > second time:
> > >
> > > Hi,
> > > some minutes ago I added libkernelppp.a to the build. It is the base
for
> > > all
> > > PPP modules (no, PPP is not finished yet ;).
> > > The problem is that it is not linked after all objects are compiled
> > > (cpp.cpp
> > > is an exception here and I do not know how to add it to the build
> > > correctly
> > > (I could add the files directly, but why should we have multiple
cpp.cpp
> > > files?)).
> > >
> > > Could somebody please help me? Ingo? :)
> >
> > I would, but currently updating my tree fails (`Write failed: Broken
pipe').
> > Your Jamfile (not yet visible via anonymous CVS, but in the CVS mail
:-),
> > looks quite OK at the first glance; I would replace the LOCATE_SOURCE by
a
> > SEARCH_SOURCE, but I wouldn't completely rule out, that it might work as
is
> > (though SEARCH_SOURCE is correct here).
>
> OK, apparently that was the problem. I fixed that and added
> `src/tests/kits/net/ppp' to the build.

Unfortunately this did not help. I forgot to commit the jamfile in
tests/kits/net.
The source files are compiled, but jam does not even try to link them.
When using "StaticLibrary" instead of R5KernelStaticLibrary the objects are
not linked, either.

I suppose there is some problem with creating static libraries for R5 in
general (the kernel's static libraries are linked without any problems).
Maybe Jamrules needs a fix?

Waldemar


Other related posts: