Hi, does anyone have some ideas regarding my problem building haiku under zeta 1.2?
System: Zeta 1.2
GCC: the required one, 2.95.3
I used ./configure without specified target.
I want to replace my Zeta installation with the Haiku one, so I typed:
HAIKU_INSTALL_DIR=/Haiku jam -q install-haiku
$ gcc -o “generated/objects/dano/x86/release/tools/gensyscalls/gensyscallinfos” “generated/objects/dano/x86/release/tools/gensyscalls/gensyscallinfos.o” -lstdc++.r4
generated/objects/dano/x86/release/tools/gensyscalls/gensyscallinfos.o: In function ostream & operator<<<char, string_char_traits<char>, __default_alloc_template<false, 0> >(ostream &, basic_string<char, string_char_traits<char>, __default_alloc_template<false, 0> > const &)': gensyscallinfos.cpp:(.gnu.linkonce.t.__ls__H3ZcZt18string_char_traits1ZcZt24__default_alloc_template2b0i0_R7ostreamRCt12basic_string3ZX01ZX11ZX21_R7ostream+0x25): undefined reference toostream::write(char const *, long)'
collect2: ld returned 1 exit status
$
It seems I have missed a configuration installing the devtools …?
There are some special steps when installing the gcc 2.95.3 from bebits on a Zeta system - when installing the new libstdc++.r4.so you have to copy some “sdk” files as well - I’ve only done it once because I don’t use Zeta, but I remember it being a little bit more work that installing the same compiler on BeOS R5.
Make sure to read the readme that comes with the new GCC carefully and note any zeta-specific differences.
After removing the -q param, I get following error:
AddSymlinkToContainerCopyFilesScript beos/system/add-ons/kernel/drivers/dev/net/wb840
AddSymlinkToContainerCopyFilesScript beos/system/add-ons/kernel/drivers/dev/net/net_stack
…skipped kernel_x86 for lack of kernel_x86…
…skipped syscalls.S.inc for lack of gensyscalls…
…skipped <src!system!libroot!os>syscalls.o for lack of syscalls.S.inc…
…skipped libruntime_loader.a for lack of <src!system!libroot!os>syscalls.o…
…skipped runtime_loader for lack of libruntime_loader.a…
…skipped os_main.o for lack of <src!system!libroot!os>syscalls.o…
MergeObjectFromObjects1 actions too long (max 10240)!
$
I installed the gcc compiler carefully, just like the Readme says …
would the command ‘jam haiku-install’ run without installing jam from the buildtools folder? I installed jam which is linked from the ‘haiku-os.org -> getting started’ site.
$ query name='libstdc++*'
/boot/beos/etc/develop/zeta-r1-gcc2-x86/tools/sdk_/release/H-i586-pc-beos5/T-i586-pc-beos5/lib/libstdc++.a
/boot/beos/etc/develop/zeta-r1-gcc2-x86/tools/gcc-2.95.3_binutils-2.17_rel-070218/lib/gcc-lib/i586-pc-beos/2.95.3-beos-060710/libstdc++.a
/boot/beos/etc/develop/zeta-r1-gcc2-x86/tools/gcc-2.95.3_binutils-2.17_rel-070218/lib/libstdc++.a.2.10.0
/boot/beos/system/lib/libstdc++.r4.so
/boot/apps/Emulators/DosBox/lib/libstdc++.r4.so
/boot/apps/Graphics/Blender/lib/libstdc++.r4.so
/boot/home/Downloads/develop/lib/x86/libstdc++.r4.so
/boot/beos/etc/develop/zeta-r1-gcc2-x86/lib/x86/libstdc++.r4.so
/boot/beos/etc/develop/zeta-r1-gcc2-x86/tools/gcc-2.95.3_binutils-2.17_rel-070218/lib/libstdc++.r4.so
$
and the link gnupro is pointing to
$ ls -l gn*
lrwxrwxrwx 1 baron users 0 Oct 16 06:12 gnupro -> /boot/beos/etc/develop/zeta-r1-gcc2-x86/tools/gcc-2.95.3_binutils-2.17_rel-070218
$
The whole output of the failing build can be found here.
Yes it will. IIRC, Zeta (and beos max) comes with an older version of Jam which often runs into the MergeObjectsFromObjects error you saw above.
Building and installing the jam from Haiku’s buildtools or downloading it from the website (assuming it’s up-to-date) is a requirement.
Make sure when you run jam -v (or whatever the switch is to get the version) that it reports the Haiku version. Maybe you have more than one in the path?
[quote]
Yes it will. IIRC, Zeta (and beos max) comes with an older version of Jam which often runs into the MergeObjectsFromObjects error you saw above.
Building and installing the jam from Haiku’s buildtools or downloading it from the website (assuming it’s up-to-date) is a requirement.
Make sure when you run jam -v (or whatever the switch is to get the version) that it reports the Haiku version. Maybe you have more than one in the path?[/quote]
Hi, thanks, but I tried first to call jam from the shell, which explained me not to find any command like ‘jam’.
I gave Jerome ssh access to my Zeta machine and he copied the right version of libstdc++.r4.so. Afaik Zeta 'til version 1.2 didn’t ship with jam …
Nevertheless, thank for your help!
the build stopped for me because a lack of free memory. And indeed, another build was running at the same time
I hope you got it running.
Jérôme[/quote]
Hi Jerome,
I started the build again with ‘install-haiku’, it installed, but I rebootet without creating a bootfloppy. Now I’ll have to look what to do to boot it. At least I can see the KDL and the Haiku logo
I’ll keep you informed.
I tried a lot now, with makehaikubootfloppy, setting -base either to /Haiku (then, another error message appeared ‘no path to boot found’ ->not exactly the words that where shown) or only ‘makehaikubootfloppy’ -> see picture here.
No need to create a boot floppy.
All you need to do is chainload the partition - it has its own boot block - you can use bootman to do this.
I beleive you can install bootman by running “bootman” from a zeta terminal. Keep in mind, bootman will replace the contents of your MBR. If you’re currently using Grub or some other boot manager, you will probably want to configure that instead.
[quote=umccullough]No need to create a boot floppy.
All you need to do is chainload the partition - it has its own boot block - you can use bootman to do this.
I beleive you can install bootman by running “bootman” from a zeta terminal. Keep in mind, bootman will replace the contents of your MBR. If you’re currently using Grub or some other boot manager, you will probably want to configure that instead.[/quote]
Hm, that was the first I tried, it didn’t work … same error message there…
Haiku booting is currently broken for me as well for a couple of revisions this week. The safe modes do not help either.
I am booting from GRUB on a P4 with SIS chipset and Nvidia graphics, which previously worked fine. The black Haiku screen is displayed and nothing happens.
So I guess we’ll have to wait for it to be fixed or go back revision by revision to find out where it broke.
EDIT: The broken revisions were 22598-22620, try 22621 or later.
