Setting timezone in UserBuildConfig no longer works

[haiqu]

$ jam -q install-haiku build/jam/UserBuildConfig: line 19: parse error at keyword : warning: unknown rule /boot/system/data/timezones/Australia/Melbourne

Build system is BeOS 5.1d0

[stippi]

Did you really open a bug report for a syntax error you made in your own UserBuildConfig? Please at least post the respective lines.

[haiqu]

I may be dumb, Stippi, but I'm not stupid. To be stupid AND dumb you'd have to be brilliant...

# Add symlink/file (timezone and keymap settings) to the image. AddSymlinkToHaikuImage home config settings

: /boot/system/data/timezones/Australia/Melbourne : timezone ;

AddFilesToHaikuImage home config settings : <keymap>American : Key_map ;

[haiqu]

Woops, I don't remember commenting that out. Invalid, please close again.

[haiqu]

Naah, wait a minute. That's just Trac's crappy quoting problem. It looks like this:

# Add symlink/file (timezone and keymap settings) to the image.
AddSymlinkToHaikuImage home config settings
	: /boot/system/data/timezones/Australia/Melbourne : timezone ;
AddFilesToHaikuImage home config settings : <keymap>American : Key_map ;

VALID.

[stippi]

This is how it looks for me:

# overwrite default timezone and keymap
AddSymlinkToHaikuImage home config settings
	: /boot/system/data/timezones/Europe/Berlin : timezone ;

AddFilesToHaikuImage home config settings : <keymap>German : Key_map ;

And that certainly works. Can you please show your entire UserBuildConfig, specifically line 19?

[mmlr]

Your syntax error obviously starts at the lines above those as jam tries to use the symlink target path as a rule. You probably miss a closing ";" on a line above those.

[bonefish]

If jam reports a syntax error in your UserBuildConfig, it's a syntax error in your UserBuildConfig and not a build system problem. My guess is you missed a ";" or "}" (respectively the delimiting spaces) earlier in the file. At any rate adding the time zone symlink works.

[haiqu]

Thanks Michael. The problem was indeed a missing semicolon above that point. I'm used to build tools that report on the line in which the error occurs, I guess jam isn't able to be that exact.

[stippi]

Multiple points:

• It was obvious from the beginning that the error must be in your UserBuildConfig, see my very first comment.
• Your insisting and inability to provide sufficient info has dragged this out much longer than necessary. It costs us all time, as you no doubt know.
• Even build tools like GCC will choke on the next statement if you forget a semicolon. If you forget it in a header after the last class declaration, it will even choke in a different file (the file where you include the header...)
• Next time you encounter a bug that has a very high likeliness of being on your side, please double check everything before reporting it. And yes, a reported syntax error in a file you created yourself does count as very likely to be an error on your side. ;-)
• Remember that we are an open source project where you want us to code and fix real issues, instead of spending our limited spare time on invalid bug reports.