Error Building OMAP3 ROM
Rob Heaton (274) 515 posts |
Evening All, I’ve been trying to get RPCemu to build an OMAP3 ROM from the CVS source tree. As far as I know I have everything setup correctly. The build fails when it trys to build the Kernel. Can someone please take a look at my build log file to ensure I’m not doing something silly. Many thanks, Rob. |
Steve Revill (20) 1361 posts |
You clearly have a copy of the C tools, or AMU wouldn’t be running. That’s a start! Next, did you run the Obey file RiscOS.Library.InstallTools when you first installed the build environment onto the RPCemu hard drive? I’m assuming your AcornC/C++ stuff is also installed on that hard drive… Next, how are you initiating the build? You should be using RiscOS.Apps.!Builder and then selecting an appropriate environment (in this case you want the ROOL.OMAP3 environment). Build phases would normally be something like:
How does that get on? |
Rob Heaton (274) 515 posts |
Thanks for the reply Steve. Yes I did run the Obey file; RiscOS.Library.InstallTools I am using !Builder, and I am using the profile ROOL.OMAP3. I have also chosen those options in !Builder you mentioned. To setup the Build directory I extracted the Batch 1 to 6 archive, then extracted the daily OMAP archive over the top. (Was that the correct thing to do??) Rob. |
Chris Gransden (337) 1207 posts |
How did you download the source? I just followed the CVS instructions using ubuntu. Then transferred everything to rpcemu. It worked first time no problems. |
Rob Heaton (274) 515 posts |
I downloaded the daily .tar.bz2 file, and unpacked it with the UnTarBZ2 application. |
Steve Revill (20) 1361 posts |
The OMAP source archive should be everything you need to build it, aside from the C tools that you install once using the InstallTools script. The old Batch archives are just noise nowadays. Unfortunately, I think our wiki build documentation is a little out of date in that respect. I’d advise re-extracting the OMAP source archive somewhere (without any of the Batch stuff or BuildEnv stuff or any other archives) then have another spin. |
Rob Heaton (274) 515 posts |
Thanks Steve, I’ll give that a go! Some of the documentation on setting up the build folder is a little confusing! I’ll post my results here once I’ve had another go. |
Rob Heaton (274) 515 posts |
I started again today, with a new install of RPCemu. I downloaded the latest daily snapshot of the OMAP3 tree. The build failed again, this time whilst building “Messages” Error: Resources.ROOL.OMAP3.<build> should be a directory. I have uploaded the buildlog again, if anyone can give me any pointers. Build Log |
Steve Revill (20) 1361 posts |
What OS are you running on RPCemu? Also, what does:
*show Build$LocaleListNumeric
say (e.g. after a failed build)?
Finally, what is inside RiscOS.Sources.Internat.Messages.Resources.ROOL.OMAP3? |
Rob Heaton (274) 515 posts |
I’m running RISC OS 4.02 dated 10-Aug-1999. I’ll run the build again, and se what *show Build$LocaleListNumeric says. I tried going into RiscOS.Sources.Internat.Messages.Resources.ROOL.OMAP3 but the last two folders don’t exist, I can only get to RiscOS.Sources.Internat.Messages.Resources (There is no ROOL folder) Rob. |
Jeffrey Lee (213) 6048 posts |
Ah, now this one I can answer – Steve forgot to mention that you also need to do the “Export resources” step (which populates the contents of ….Messages.Resources with all the files which go into ResourceFS in the ROM image) Since the preceeding steps have presumably built OK, you should be able to avoid a full rebuild by running !Builder again on the same build tree, but with just the “Export resources”, “Make ROM”, “Install ROM”, and “Join ROM” options selected. Then for subsequent builds you’d usually only need the 3 ROM options selected (unless you’ve changed one of the files that goes into Resources, or changed a shared header that gets exported to the “RiscOS.Export” folder, etc.) |
Steve Revill (20) 1361 posts |
Well spotted. Serves me right for trying to remember the phases off the top of my head. |
Rob Heaton (274) 515 posts |
Thanks Jeffrey, I got a little further! This time I got: fatal error: structure mismatch at line 52 in macro MyDesk. This was while it was running make install_rom on module ROMFonts. Build log is below; Build Log |
Rob Heaton (274) 515 posts |
As the repeated error in the build log relates to: fonts.corpus.medium.oblique.intmetric0 I looked in the folder riscos.sources.video.render.fonts.romfonts.fonts.corpus.medium.oblique and I don’t have a file called “intmetric0” In that folder there is only a text file called “Outlines0” I assume the “intmetric0” file is missing? |
Rob Heaton (274) 515 posts |
Please ignore my last post, I wasn’t merging both sets of “Castle” & “Mixed” folders from the archive. I have corrected this and the build is running through once again. |
Rob Heaton (274) 515 posts |
I have finally got the ROM image to build! Many thanks for all the help. Rob. |
Alan Robertson (52) 420 posts |
Good to hear you’ve got it working. Does existing documentation need to be updated to reflect your ‘real world’ building exercise? If so, can I ask that you try to update it, so future developers can benefit from your experience. Sorry, if I’m sounding too much like your parents! nag, nag ,nag… |
Rob Heaton (274) 515 posts |
Hi Alan, I was thinking of updating the documentation anyway! I can’t say it will read as a Charles Dickens novel, but I’ll do my best! Rob. |