> In message <DUB120-DS925A6587EC8ED323D07C1F0320@phx.gbl>
"Alan Buckley" <alan_baa@hotmail.com> wrote:
> > I’ve just tried to build the native RISC OS compiler on a Debian
> > system
> > and it failed with:
>
> > checking whether stripping libraries is possible... yes
> > checking if libtool supports shared libraries... no
> > checking whether to build shared libraries... no
> > checking whether to build static libraries... yes
> > /home/alanb/gccsdk/gcc4/riscos/asasm/elftoolchain/configure: line 11928:
> > syntax
> > error near unexpected token `LIBARCHIVE,'
> > /home/alanb/gccsdk/gcc4/riscos/asasm/elftoolchain/configure: line 11928:
> > ` PKG_
> > CHECK_MODULES(LIBARCHIVE, libarchive >= $REQ_LIBARCHIVE_VERSION)'
> > configure: error:
> > /home/alanb/gccsdk/gcc4/riscos/asasm/elftoolchain/configure fa
> > iled for elftoolchain
> > make[1]: *** [ronative-riscostools-built] Error 2
> > make[1]: Leaving directory `/home/alanb/gccsdk/gcc4'
> > make: *** [getenv] Error 2
> Was this a full clean build (either freshly checked out, either after a
> make clean or make distclean) ? Did you do the build for the
> cross-compiler
> with the same set of sources ?
No, I had run svn update on it a few times.
> Otherwise, I would remove all generated autotools file in the riscos/asasm
> directory with a:
> for i in riscos/asasm riscos/asasm/decaof/ riscos/asasm/elftoolchain/ ; do
> svn status --no-ignore $$i | grep "^I " | cut -b 9- | xargs rm -rf ;
> done
> and restart the build.
This didn't work. But a make clean followed by make ronative did.
It there any way to just rebuild the parts that have changed after an svn
update?
It took all morning to rebuild the ronative compilers and I'd like to try
to keep up to date with the trunk build for the cross-compiler at least
without it taking so long.
Thanks,
Alan
_______________________________________________
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
No comments:
Post a Comment