Also try re-running "svn up" in your project directory - sometimes the svn checkout doesn't finish properly.
You can also try "jam -q haiku-image" which will make it stop on the first failed target instead of continuing on. That might yield some clue as to what failed.
Oops, I meant you can use -d to change the output of jam (I was thinking -v from other tools)...
-d has different debug levels...
Anyhow, I'm not even sure the version of Jam on the website is up-to-date - it's probably safer to get jam from the buildtools branch, build it, and install it from there. Glad to hear downloading a new version fixed your problem though :)
You're right - I assumed... (there are probably a dozen posts here in the forums and mailing list about it) - anyhow, the old website article used to actually specify how to get it, but that's been mostly replaced with jam.zip download link now...
UPDATE: I just checked, and it appears the version for download is already up-to-date - nothing has changed since 20060813
The Linux dev tools page still explains how to get it:
I poked around the svn repository and guessed the svn command to download ... it would be nice if install instructions were included in the directory ... after making the files I followed the install instructions from the jam zip directory and am trying the jam again.
For the record - after updating my BeOS R5 system with the latest code, I too have this problem now. So, it's not your environment :)
BTW, it appears that r21484 was when the FileType-F started to fail consistently. If you were to revert to r21483, or even just revert the one mimeset.cpp that was changed there, it would probably succeed - I'll try that tonight.
I am posting from haiku rev 2159 after compiling on my system ... !!!
Awesome, welcome aboard Jim. If you can program at all, maybe you can start fixing bugs and sending patches. Building your own Haiku is the first step on the journey to being a Haiku contributor! :-D
I just updated to r23117 and ran jam -q haiku.image. the resulting image file is empty except for a home folder ( probably added when I mounted the image in BeOS ). I believe this was caused when links was added to the jamfile /haiku/trunk/build/jam/HaikuImage ( r23089 ) as the resulting image file has been empty since then.
There is no error. Jam completes as expected and reports that it is copying the files to the image, but there are no files in the resulting haiku.image file.
After remarking out the section for links in /haiku/trunk/build/jam/HaikuImage the jam completed with all the files copied to the haiku.image file. ??? This doesn't make any sense as jam must be run with a command line argument to activate the links download. Any ideas what is going on?
You should ask on the Haiku Development list or file an issue on Trac (http://dev.haiku-os.org) - Ingo would probably be able to help you track this down much better, but he doesn't read these forums AFAIK.
Comments
Re: Jam doesn't work.
Strange - what OS are you building on?
Also try re-running "svn up" in your project directory - sometimes the svn checkout doesn't finish properly.
You can also try "jam -q haiku-image" which will make it stop on the first failed target instead of continuing on. That might yield some clue as to what failed.
Re: Jam doesn't work.
I am using BeOS MAX 4.1 and have tried all these suggestions ... same issue.
Re: Jam doesn't work.
you can use -v to increase the verbosity of the jam output also...
check the jam commandline options for more info
You are using the Haiku version of Jam from the buildtools branch right?
Re: Jam doesn't work.
you can use -v to increase the verbosity of the jam output also
how ???
You are using the Haiku version of Jam from the buildtools branch right??? I downloaded Jam from the website and installed.
Success
I re-downloaded jam, and now I'm jammin!
Re: Jam doesn't work.
Oops, I meant you can use -d to change the output of jam (I was thinking -v from other tools)...
-d has different debug levels...
Anyhow, I'm not even sure the version of Jam on the website is up-to-date - it's probably safer to get jam from the buildtools branch, build it, and install it from there. Glad to hear downloading a new version fixed your problem though :)
Re: Jam doesn't work.
Where is the "buildtools branch?"
I love it when people assume too much.
It seemed to jam but in the end .....
...skipped haiku.image for lack of haiku.image-copy-files...
...failed updating 1 target(s)...
...skipped 2 target(s)...
...updated 1840 target(s)...
no haiku.image to test.
Re: Jam doesn't work.
You're right - I assumed... (there are probably a dozen posts here in the forums and mailing list about it) - anyhow, the old website article used to actually specify how to get it, but that's been mostly replaced with jam.zip download link now...
UPDATE: I just checked, and it appears the version for download is already up-to-date - nothing has changed since 20060813
The Linux dev tools page still explains how to get it:
http://haiku-os.org/documents/dev/getting_linux_developer_tools
You don't need the entire buildtools though - just buildtools/trunk/jam:
http://svn.berlios.de/viewcvs/haiku/buildtools/trunk/
You can "svn co" just that directory from the repo.
In any case, you will need to run "jam -q haiku-image" if you want it to stop on the target that failed.
Re: Jam doesn't work.
I poked around the svn repository and guessed the svn command to download ... it would be nice if install instructions were included in the directory ... after making the files I followed the install instructions from the jam zip directory and am trying the jam again.
Still won't build
Link generated/objects/haiku/x86/release/add-ons/tracker/filetype/FileType-F
XRes1 generated/objects/haiku/x86/release/add-ons/tracker/filetype/FileType-F
Chmod1 generated/objects/haiku/x86/release/add-ons/tracker/filetype/FileType-F
SetType1 generated/objects/haiku/x86/release/add-ons/tracker/filetype/FileType-F
MimeSet1 generated/objects/haiku/x86/release/add-ons/tracker/filetype/FileType-F
mimeset:
generated/objects/r5/x86/release/tools/mimeset -f "generated/objects/haiku/x86/release/add-ons/tracker/filetype/FileType-F" ;
...failed MimeSet1 generated/objects/haiku/x86/release/add-ons/tracker/filetype/FileType-F ...
...removing generated/objects/haiku/x86/release/add-ons/tracker/filetype/FileType-F
...skipped haiku.image-copy-files-dummy-beos/system/add-ons/Tracker for lack of FileType-F...
...skipped haiku.image for lack of haiku.image-copy-files...
...failed updating 1 target(s)...
...skipped 2 target(s)...
...updated 263 target(s)...
Yes I downloaded the add-ons/Tracker directory again and this is the result. I guess building Haiku just isn't for me. I'm lost.
Re: Still won't build
Interesting - that's a recent issue reported on the dev mailing list... I thought it was Linux-specific, but maybe not.
In any case, I think it will be fixed soon - as there were some discussions about what causes it as well.
http://www.freelists.org/archives/haiku-development/06-2007/msg00212.html
(looks like axel mentioned something about deleting the entire "generated" directory and jamming again from scratch)
Re: Still won't build
For the record - after updating my BeOS R5 system with the latest code, I too have this problem now. So, it's not your environment :)
BTW, it appears that r21484 was when the FileType-F started to fail consistently. If you were to revert to r21483, or even just revert the one mimeset.cpp that was changed there, it would probably succeed - I'll try that tonight.
Re: Jam doesn't work.
deleted this line from /src/add-ons/tracker/filetype/Jamfile and the jam completed.
added same vector icon as FileTypes preflet, but somehow the
resources are not added for the "Addon" target type? Ingo?
SubDir HAIKU_TOP src add-ons tracker filetype ;
SetSubDirSupportedPlatformsBeOSCompatible ;
# TODO: does not seem to work:
AddResources FileType-F : FileType.rdef ;
Addon FileType-F :
FileType.cpp
: be tracker
;
Re: Jam doesn't work.
It's possible that mmlr has even fixed the problem now in r21515 by adding a newer BMessage implementation to libbe...
Re: Jam doesn't work.
Nope, apparently it is now supposedly fixed in r21518:
https://lists.berlios.de/pipermail/haiku-commits/2007-June/013008.html
I'll check when I get home :)
works now.
I am posting from haiku rev 2159 after compiling on my system ... !!!
Re: Jam doesn't work.
dfasf
Re: Jam doesn't work.
dfasf
What is this supposed to mean?
Re: works now.
I am posting from haiku rev 2159 after compiling on my system ... !!!
Awesome, welcome aboard Jim. If you can program at all, maybe you can start fixing bugs and sending patches. Building your own Haiku is the first step on the journey to being a Haiku contributor! :-D
looks like it's broke again
oops ... my bad
The file ... adpcm.c was messed up ... replaced the file and jam worked again.
It's broken again
I just updated to r23117 and ran jam -q haiku.image. the resulting image file is empty except for a home folder ( probably added when I mounted the image in BeOS ). I believe this was caused when links was added to the jamfile /haiku/trunk/build/jam/HaikuImage ( r23089 ) as the resulting image file has been empty since then.
Re: Jam doesn't work.
So, what's the error?
Links is added as a download (wget) and unzip IIRC - so perhaps that is failing.
Re: Jam doesn't work.
There is no error. Jam completes as expected and reports that it is copying the files to the image, but there are no files in the resulting haiku.image file.
Re: Jam doesn't work.
FedoraCore 6
JAM from buildtools compiled and installed OK!
BINUTILS and GCC4 (--build-cross-tools-gcc4 x86) compiled OK!
jam -q haiku-image
...
InitScript1 generated/haiku.image-make-dirs
CreateContainerMakeDirectoriesScript1 generated/haiku.image-make-dirs
ResComp1 generated/objects/haiku/x86/common/home-config-settings-printers-preview.rsrc
rc: Error! -:2 syntax error, unexpected $undefined
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:generated/objects/linux/lib
cat "data/image_directories/home-config-settings-printers-preview.rdef" | /home/haikuos/haiku/generated/cross-tools/bin/i586-pc-haiku-gcc -E -D__HAIKU__ -DHAIKU_DISTRO_COMPATIBILITY_DEFAULT -D__INTEL__ -DARCH_x86 -DHAIKU_TARGET_PLATFORM_HAIKU -iquote . -iquote generated/objects/common -iquote generated/objects/linux/x86/common -iquote generated/objects/haiku/x86/common - | egrep -v '^#' | generated/objects/linux/x86/release/tools/rc/rc -I . -I generated/objects/common -I generated/objects/linux/x86/common -I generated/objects/haiku/x86/common --auto-names -o "generated/objects/haiku/x86/common/home-config-settings-printers-preview.rsrc" -
...failed ResComp1 generated/objects/haiku/x86/common/home-config-settings-printers-preview.rsrc ...
...skipped haiku.image-make-dirs-attributes-home-config-settings-printers-Preview for lack of home-config-settings-printers-preview.rsrc...
...skipped haiku.image-make-dirs-attributes-dummy-home/config/settings/printers/Preview for lack of haiku.image-make-dirs-attributes-home-config-settings-printers-Preview...
...skipped /haiku.image for lack of haiku.image-make-dirs...
...failed updating 1 target(s)...
...skipped 3 target(s)...
...updated 4 target(s)...
Re: Jam doesn't work.
After remarking out the section for links in /haiku/trunk/build/jam/HaikuImage the jam completed with all the files copied to the haiku.image file. ??? This doesn't make any sense as jam must be run with a command line argument to activate the links download. Any ideas what is going on?
Re: Jam doesn't work.
You should ask on the Haiku Development list or file an issue on Trac (http://dev.haiku-os.org) - Ingo would probably be able to help you track this down much better, but he doesn't read these forums AFAIK.