Stefan Bellon wrote: > 2John Tytgat wrote: ^ Whatever this was, it was a mistake. ;-)
> > Ah so I did try the right thing and no, -gnatdl does not give me the > > debug I thought it would give in this case. :-( > I suspected this. It shows the information for explicitly stated > dependencies in a file. But if your hello.adb is just the simple > procedure Hello is > begin > null; > end Hello; > then there is no gain with -gnatdl. Ok, I did some tests in the meantime and can say the following: 1) It is "just" a path lookup issue. If you copy the system ads and adb directories in your current working directory, then system.ads and other system packages you depend on in your project are found. 2) gnatmake does not work reliably yet. If you start compilation via gnatmake, you get: *gnatmake hello gcc -c } ΒΈ hello.adb gnatmake: error, unable to locate gcc So I sticked to *gcc -c hello.adb which worked and produced an o.hello ELF output. 3) gnatmake does not find its sister programs: *gnatmake hello gnatbind -x hello.ali gnatmake: error, unable to locate gnatbind Again, calling gnatbind manually works (having copied the system ali directory over into the current working directory previously): *gnatbind -x hello.ali 4) Linking with gnatlink does not work either. 5) What is puzzling me is, that in lib.gcc.arm-unknown-riscos.4/1/1.adalib.o there is only g-trasym present and nothing else. I would have expected that directory to be either fully populated with object files for the individual packages or completely empty, if the appropriate library is in place. Ok, that's for it now, have to do some work. Will take a closer look this evening if I find the time. Greetings, Stefan -- Stefan Bellon _______________________________________________ GCCSDK mailing list gcc@gccsdk.riscos.info Bugzilla: http://www.riscos.info/bugzilla/index.cgi List Info: http://www.riscos.info/mailman/listinfo/gcc Main Page: http://www.riscos.info/index.php/GCCSDK
