This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See crosstool-NG for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Wed, Jun 13, 2012 at 10:02 AM, Thomas De Schampheleire <patrickdepinguin@gmail.com> wrote: > Hi, > > On Fri, Jun 8, 2012 at 2:16 PM, Thomas De Schampheleire > <patrickdepinguin@gmail.com> wrote: >> [Please keep me in CC] >> >> Hi, >> >> I'm experiencing trouble with cloog in crosstool-ng 1.15.2, and I >> didn't have problems before with 1.13.4. I'm using the same >> configuration. >> >> Note: the machine on which I have these problems is running CentOS >> 5.8, which does not contain the most recent packages of anything. But >> note also that the same machine was used before (1.13.4) without >> problems. >> >> The first problem was this: >> >> [EXTRA] ? ?Building CLooG/ppl >> [ALL ?] ? ?make[3]: Entering directory >> `/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/powerpc-unknown-linux-gnu/build/build-cloog-ppl-host-x86_64-build_unknown-linux-gnu' >> [ALL ?] ? ?cd /repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9 >> && /bin/sh /repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9/autoconf/missing >> --run aclocal-1.9 -I m4 >> >> [ALL ?] ? ?aclocal: couldn't open directory `m4': No such file or directory >> [ERROR] ? ?make[3]: *** >> [/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/src/cloog-ppl-0.15.9/aclocal.m4] >> Error 1 >> [ALL ?] ? ?make[3]: Leaving directory >> `/repo/central/jenkins/workspace/buildroot-eglibc-toolchain/output/build/build-toolchain/.build/powerpc-unknown-linux-gnu/build/build-cloog-ppl-host-x86_64-build_unknown-linux-gnu' >> >> The m4 directory is indeed not present in cloog-ppl so it shouldn't be >> referenced anyway. >> I could fix this problem by changing the cloog Makefile.in and >> Makefile.am so that the m4 directory is not included (remove >> ACLOCAL_AMFLAGS setting). > > So I tracked down the first problem (assuming the second is a > consequence of the first). > > In previous crosstool-ng versions (1.14), the cloog sources were not > patched. In the current version, configure and configure.in are > changed. This triggers the cloog Makefile to call the folllowing line: > autoconf/missing --run aclocal-1.9 -I m4 > > When aclocal-1.9 is not present on the system, all is fine. The script > returns with a simple warning saying that aclocal-1.9 isn't installed > and that you only need it if you changed configure.in. This comes from > the following lines in autoconf/missing: > > # If it does not exist, or fails to run (possibly an outdated version), > # try to emulate it. > case "$1" in > ?aclocal*) > ? ?echo 1>&2 "\ > WARNING: \`$1' is $msg. ?You should only need it if > ? ? ? ? you modified \`acinclude.m4' or \`${configure_ac}'. ?You might want > ? ? ? ? to install the \`Automake' and \`Perl' packages. ?Grab them from > ? ? ? ? any GNU archive site." > ? ?touch aclocal.m4 > ? ?;; > > > When aclocal-1.9 is present, it actually runs it, with parameter -I > m4' as instructed by the cloog package. However, the m4 directory > doesn't exist and aclocal chokes on it. According to me this is a > problem in the cloog package that should be fixed. > > But, I'm troubled by the fact that I haven't found reports about this > anywhere. Do none of you have aclocal-1.9 installed? > > What is the best solution here? > > One thing that works is make sure that aclocal.m4 is more recent than > the patched configure files (by touching it) so that the missing > script isn't called. This works in the current case because the > patching of configure doesn't have impact on the aclocal.m4 file. It > may not be a generic fix in case configure is patched with more > impact, but it works (I tried). > > What do you think? Any input is welcome... > Yann, any input? -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |