Ticket #128 (Open)Thu May 24 18:18:58 UTC 2007

Thanks for the report. TaskWindow output would be really helpful in diagnosing the problem. You could upload the TaskWindow output by saving it to a file and attaching it using the “Attachment” entry below your name and above the comment box in the “New ticket” or “Update ticket” forms (e.g. in an update to this ticket).

Help on the Web site is in the wiki. Specifically, or more help on using the bug tracker, please have a look here.

Usually, most people leave the release and milestone blank for RISC OS faults because as yet we don’t have a specific project or target that we’re working towards, against which faults can be raised. However, setting the part to “RISC OS: General” or “RISC OS: C/C++ Toolchain” (according your best guess about the nature of the fault you’re reporting) is helpful for filtering searches.

System: RO5.13
Thanks for your reply. Here-attached is the
taskwindow output from !Builder on BatchOne.

This sounds like mkdir isn’t working correctly. We have a tool called “mkdir” in the RiscOS.Library.UNIX directory which is a rough port of the UNIX mkdir command, including the “-p” switch which means create parent directories if they also don’t exist.

Some people already have a utility called mkdir installed on their system that doesn’t implement the -p switch, or they have an alias for mkdir which simply calls cdir, both of which stops our one from being run.

Check for these gotchas first.

All of those “duplicate component” ‘errors’ are actually nothing of the sort. This dates back to the days when scrbuild (the binary which is hiding behind !Builder) was only used for ROM builds and they considered having the same module in a build multiple times to be an error.

For other builds, such as disc builds, this is no longer the case; you often want to have multiple builds of a given component. We just haven’t got around to clobbering scrbuild yet.

Whatever environment I choose the error is always the same: “<Build$Dir>.BuildSys.perl.ImageName: open(.BuildSys.ImageName.SysMap) failed”.
This means that the variable $dir is not getting the right value in the perl script. Surely this is a perl problem rather than a srcbuild problem? More specifically $ENV{$envmap{uc ‘Build$Dir’}}
is not evaluating to anything. I can get a bit further in the build process by bodging in values in the perl script, but that is no panacea. I have checked that no other perls are interfering. I am still mystified, and of course cannot get anywhere with building anything. Have any other Iyonix users had the same problem? The perl is exactly as downloaded from the ROOL site.

Do you still get this error with the latest batch one archives (BBE+Sources)? I’ve taken a brand new IYONIX and installed it on there and the whole of batch one builds correctly.

Closed due to lack of reports of this ever being a problem in newer batch releases.

Same issue. Plus it’s really annoying.