In article <cahqjq4joy3+y5mnr5ktdjfd76my88feh9qdoxfw25ch9td9...@mail.gmail.com>, Robert Heaton <[email protected]> wrote:
> Autobuilder: Package "dpkg" will be built using rules at > "/home/robheaton/Downloads/gccsdk/autobuilder/cli/dpkg" > Autobuilder: Dependency libbz2-1.0 satisfied by previous successful build > Autobuilder: No match for Debian dependency "libselinux1" - ignoring > Autobuilder: Dependency zlib1g satisfied by previous successful build > Autobuilder: Package "coreutils" will be built using rules at > "/home/robheaton/Downloads/gccsdk/autobuilder/cli/coreutils" > Autobuilder: Package "dpkg" will be built using rules at > "/home/robheaton/Downloads/gccsdk/autobuilder/cli/dpkg" > Autobuilder: Dependency libbz2-1.0 satisfied by previous successful build > Autobuilder: No match for Debian dependency "libselinux1" - ignoring > Autobuilder: Dependency zlib1g satisfied by previous successful build > Autobuilder: Package "coreutils" will be built using rules at > "/home/robheaton/Downloads/gccsdk/autobuilder/cli/coreutils" > Autobuilder: Package "dpkg" will be built using rules at > "/home/robheaton/Downloads/gccsdk/autobuilder/cli/dpkg" Looks like there is a circular dependancy with coreutils and dpkg. As a temporary workaround you could 'touch autobuidler/cli/dpkg/last-success' and build coreutils and dpkg manually. You'll also need to update to r5492 of the autobuilder first. Chris. -- Email: [email protected] _______________________________________________ GCCSDK mailing list [email protected] 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
