On 2007-04-12 at 00:43:30 [+0200], Euan Kirkhope <euan.kirkhope@xxxxxxxxxxxxxx> wrote: > On 11/04/07, Bryan Varner <bryan@xxxxxxxxxxxxx> wrote: > > I've had no problems following Stefano's instructions. > > > > The trick is to do the export after you switch to the root user > > (before invoking makebootable) otherwise, the environment isn't setup. > > > > At least, that's been my experience. > > > > -Bryan > > > > > > On Apr 10, 2007, at 6:25 PM, Euan Kirkhope wrote: > > > > > On 10/04/07, Euan Kirkhope <euan.kirkhope@xxxxxxxxxxxxxx> wrote: > > >> On 10/04/07, Stefano Ceccherini <stefano.ceccherini@xxxxxxxxx> wrote: > > >> > 2007/4/10, Euan Kirkhope <euan.kirkhope@xxxxxxxxxxxxxx>: > > >> > > I'm getting an error when trying to run the app "can't find > > >> > > libroot_build.so" or words to that effect. The files exist, > > >> and I > > >> > > tried copying them to /lib, and the same folder as the exe. > > >> But to no > > >> > > avail. Any ideas? And yes I probably am a noob. If I can't > > >> get it > > >> > > to work I'll probably move the haiku to the start of another > > >> drive > > >> > > anyways. > > >> > > > >> > The folder where those libraries reside needs to be included in the > > >> > LD_LIBRARY_PATH environment variable. > > >> > I usually do an 'export > > >> > LD_LIBRARY_PATH=$LD_LIBRARY_PATH:"<path_to_libroot_build.so>" ' > > >> before > > >> > calling makebootable, where <path_to_libroot_build.so> is the real > > >> > path to the libroot_build.so library, obviously :) > > >> > > > >> > > > >> Sounds like an easy fix, I'll give it a shot. Thanks! > > >> > > > > > > Still no luck keep getting: > > > ./makebootable: error while loading shared libraries: > > > libroot_build.so: cannot open shared object file: No such file or > > > directory > > > > > > Gonna give up and add another harddrive, I hope haiku likes booting > > > from /dev/hdb1 without changing the partition offset... :) > > > > > > I did some partition shuffling on my laptop which is where the haiku > source and build tools reside, and makebootable runs with out any > export, or ldconfig changes. The system I was trying to use is a > fresh ubuntu install on my desktop. I just copied makebootable, and > the libbe_build.so, and libroot_build.so over. I'll install the > source and tools, and start from scratch to see if that fixes it... Note that "configure" stores some absolute paths, that is after moving the source tree and/or the output directory you should at least run "configure" again. In case you didn't know, configure has the "--cross-tools-prefix" option, so you don't need to build the cross-compilation tools again. BTW, you can run build system tools using jam, which will automatically set up the LD_LIBRARY_PATH. E.g.: jam -q run ":<build>makebootable" /dev/the_partition CU, Ingo