[openbeos] Re: help building haiku: error ... skipped for lack of libbe.so

On 2007-04-29 at 05:40:57 [+0200], Andre Garzia <soapdog@xxxxxxx> wrote:
> Friends,
> 
> I am new here. I am running Zeta 1.21. With help from BGA, I setup
> the correct gcc and friends here. I checkout the haiku source and
> after seeing an error with jam (max actions bla bla bla) and googled
> for a solution, the solution was to build and install a newer jam, so
> I fetched the one from build tools and built and install it. I used:
> 
> svn checkout svn://svn.berlios.de/haiku/buildtools/trunk/jam jam
> 
> make
> ./jam0 install
> 
> then I moved to the haiku source folder and tried
> ./configure target=haiku
> jam
> 
> while the terminal flashed lots of nice output, I wondered about
> seeing lots of messages like:
> 
> ... skipped for lack of libbe.so
> 
> and
> 
> ... skipped for lack of libroot.so

That's actually not so nice output. It means that libbe.so/libroot.so 
couldn't be built (likely due to some error listed earlier) and that 
therefore targets depending on them can't be built.

> I know this libraries to be at /etc/develop/haiku-r1-gcc2-x86/lib and
> I have a symlink binding that haiku folder to 'current'.

Er, no idea what you are doing, but that certainly doesn't look right. The 
Haiku build is pretty self contained. If you have the required tools 
installed (mainly binutils and gcc, or when building the cross compilation 
tools a few more of the GNU tools), everything needed is in the source tree 
and everything generated in the output directory.

Have you tried following the instructions in the ReadMe, and, if that 
applies (i.e. you don't build on BeOS), the ReadMe.cross-compile?

It also might be helpful to read some resources on our website:

http://haiku-os.org/documents/dev/haiku_development_getting_started

> I've tested
> by building a hello world from Sample Code folder and it works fine.
> I never used jam before, nor did I built haiku from sources, so I
> don't know if this message is common or if I forgot to set some
> variable or something to tell jam where to look for the libraries.
> 
> Can someone please shed a clue?

If you're following the ReadMe instructions and it still doesn't work, then 
please send the output. Run jam with option "-q", so it will terminate as 
soon as it encounters an error.

CU, Ingo

Other related posts: