In message 9 May Musus Umbra <[EMAIL PROTECTED]> wrote: > On Thursday 08 May 2008, Ed Avis wrote: > > Francis Devereux wrote: > > >This is just a guess, but maybe something is trying to execute > > >/etc/ allegrorc and you need to grant execute permissions on > > More likely, to read it, and you need chmod a+r /etc/allegrorc. > > FWIW, I'm using Fedora8 here (i386 bit) and (presumably) the same > packages as Terry (4.2.2-7). My /etc/allegrorc looks like this: > -rw-r--r-- 1 root root 15080 2008-01-22 10:35 /etc/allegrorc > and is part of the allegro-4.2.2-7 package. > > If your /etc/allegrorc exists, try (as root): > chmod 644 /etc/allegrorc
OK, I made sure that was all the same...no improvement :-( > > If it doesn't exist, something is weird ;) > > Oh - you mentioned turning SELinux off - did you reboot after making > that change? I don't think I had, but have done so since, and still no change. I have just removed the Allegro and Allegro-devel packages and re-installed, and everything is unchanged. I have had a snoop at the config.log generated when I successfully built RPCemu rev121, and that refers to finding /usr/bin/allegro-config. No such entry exists when in the config.log for rev127, and further examination of the config.log files reveals that my path (on my new system) is bare bones, i.e. it doesn't include /usr/bin, /usr/local/bin and others that were set on my old system. So edited my path and logged in again and ran ./configure and all's well. So there you go. When setting up the new system I had forgotten to set my path variable properly...although one would expect that the basic defaults would have included these paths. Now to see how RPCemu performs on the 64 bit system. Thanks for all the help. Cheers, -- Regards, Terry Duell _______________________________________________ Rpcemu mailing list [email protected] http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
