[openbeos-build-team] Re: Detecting libgcc
- From: "David Reid" <dreid@xxxxxxxxxxxx>
- To: <openbeos-build-team@xxxxxxxxxxxxx>
- Date: Fri, 28 Jun 2002 14:45:08 +0100
We shoudn't need -lnet.
david
----- Original Message -----
From: "Ingo Weinhold" <bonefish@xxxxxxxxxxxxxxx>
To: <openbeos-build-team@xxxxxxxxxxxxx>
Sent: Friday, June 28, 2002 4:19 PM
Subject: [openbeos-build-team] Re: Detecting libgcc
>
> > >I don't know how the move is going to happen. For Jam I'd like to
> > > use
> > a
> > >vendor branch and it's not desirable, if it would get lost.
> >
> > By the way, I already have a BeOS compatible version of the Jam 2.4
> > source code on my machine. I changed all the line breaks from CRLF
> > to
> > just LF (since it would not compile with CRLFs...they break the
> > preprocessor.) I also started making some changes to Jambase, since
> > the original one is crappy as far as BeOS support is concerned (the
> > default LINKLIBS was -lnet???)
> >
> > Therefore don't waste your time doing the same thing Ingo, I can
> > import
> > my tree and/or at least email it to you.
>
> I suspect, I made almost the same changes you did -- it wasn't really a
> big waste of time though, as it took only a couple of minutes. As
> planned, I've also implemented the rule to execute commands at parse
> time. Thus I would rather like you to send me your sources, so that I
> can incorporate the differences.
>
> Regarding the libnet thingy, I faintly remember, that there was an
> issue -- some POSIX functionality living in it or so. But that could
> have concerned an older BeOS version only or may as well be complete
> nonsense. I guess, David can say a final word about it?!
>
> CU, Ingo
>
>
>
>
Other related posts:
