public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Chris Morgan <chmorgan@gmail.com>
To: crossgcc@sourceware.org
Subject: CLooG build error
Date: Wed, 25 Jan 2012 22:07:00 -0000	[thread overview]
Message-ID: <CAAPegz0en7mBTuo_qQxuyBfQab8PpL9iiBhuwYpyc-_b0GbwUQ@mail.gmail.com> (raw)
In-Reply-To: <CAAPegz20kka=E=vZ11UB9F8JNFyWpX6NDyzo38K7G1SnVo9a+g@mail.gmail.com>

Using latest hg, barebones configuration arm cpu:

...
[CFG  ]                 /*-----------------------------------------------*
[CFG  ]                  *           CLooG configuration is OK           *
[CFG  ]                  *-----------------------------------------------*/
[CFG  ]    It appears that your system is OK to start CLooG
compilation. You need
[CFG  ]    now to type "make". After compilation, you should check
CLooG by typing
[CFG  ]    "make check". If no problem occur, you can type "make uninstall" if
[CFG  ]    you are upgrading an old version. Lastly type "make
install" to install
[CFG  ]    CLooG on your system (log as root if necessary).
[EXTRA]    Building CLooG/ppl
[DEBUG]    ==> Executing: 'make' '-j2' 'libcloog.la'
[ALL  ]    make[1]: Entering directory
`/home/cmorgan/ct-ng-install/bin/.build/arm-unknown-eabi/build/build-cloog-ppl'
[ALL  ]    /bin/bash ./libtool  --tag=CC   --mode=compile
x86_64-build_unknown-linux-gnu-gcc -DHAVE_CONFIG_H -I.
-I/home/cmorgan/ct-ng-install/bin/.build/src/cloog-ppl-0.15.10
-I./include/cloog -I./include
-I/home/cmorgan/ct-ng-install/bin/.build/src/cloog-ppl-0.15.10/include
 -I/home/cmorgan/ct-ng-install/bin/.build/arm-unknown-eabi/build/static/include
-I/home/cmorgan/ct-ng-install/bin/.build/arm-unknown-eabi/build/static/include
 -Wall -fomit-frame-pointer -pipe  -MT block.lo -MD -MP -MF
.deps/block.Tpo -c -o block.lo `test -f 'source/block.c' || echo
'/home/cmorgan/ct-ng-install/bin/.build/src/cloog-ppl-0.15.10/'`source/block.c
[ALL  ]    /bin/bash ./libtool  --tag=CC   --mode=compile
x86_64-build_unknown-linux-gnu-gcc -DHAVE_CONFIG_H -I.
-I/home/cmorgan/ct-ng-install/bin/.build/src/cloog-ppl-0.15.10
-I./include/cloog -I./include
-I/home/cmorgan/ct-ng-install/bin/.build/src/cloog-ppl-0.15.10/include
 -I/home/cmorgan/ct-ng-install/bin/.build/arm-unknown-eabi/build/static/include
-I/home/cmorgan/ct-ng-install/bin/.build/arm-unknown-eabi/build/static/include
 -Wall -fomit-frame-pointer -pipe  -MT loop.lo -MD -MP -MF
.deps/loop.Tpo -c -o loop.lo `test -f 'source/loop.c' || echo
'/home/cmorgan/ct-ng-install/bin/.build/src/cloog-ppl-0.15.10/'`source/loop.c
[ALL  ]    mv -f .deps/loop.Tpo .deps/loop.Plo
[ALL  ]    mv -f .deps/block.Tpo .deps/block.Plo
[ALL  ]    mv: mv: cannot stat `.deps/loop.Tpo': No such file or directory
[ERROR]    make[1]: *** [loop.lo] Error 1
[ALL  ]    make[1]: *** Waiting for unfinished jobs....
[ALL  ]    cannot stat `.deps/block.Tpo': No such file or directory
[ERROR]    make[1]: *** [block.lo] Error 1
[ALL  ]    make[1]: Leaving directory
`/home/cmorgan/ct-ng-install/bin/.build/arm-unknown-eabi/build/build-cloog-ppl'
[ERROR]
[ERROR]  >>
[ERROR]  >>  Build failed in step 'Installing CLooG/ppl'
[ERROR]  >>        called in step '(top-level)'
[ERROR]  >>
[ERROR]  >>  Error happened in: CT_DoExecLog[scripts/functions@172]
[ERROR]  >>        called from:
do_cloog[scripts/build/companion_libs/cloog.sh@61]
[ERROR]  >>        called from: main[scripts/crosstool-NG.sh@597]
[ERROR]  >>
[ERROR]  >>  For more info on this error, look at the file: 'build.log'
[ERROR]  >>  There is a list of known issues, some with workarounds, in:
[ERROR]  >>
'/home/cmorgan/ct-ng-install/share/doc/crosstool-ng/ct-ng.hg@default-188d58cfe7cf/B
- Known issues.txt'
[ERROR]
[ERROR]  (elapsed: 146:14.54)
...

Dependency issue in cloog? Anyone else seeing this?

Chris

--
For unsubscribe information see http://sourceware.org/lists.html#faq

       reply	other threads:[~2012-01-25 22:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAAPegz3+cnkhtdzA1MO8caoH-MXAT6GjPDd6g7cUQ5Moetk2kg@mail.gmail.com>
     [not found] ` <CAAPegz20kka=E=vZ11UB9F8JNFyWpX6NDyzo38K7G1SnVo9a+g@mail.gmail.com>
2012-01-25 22:07   ` Chris Morgan [this message]
2012-01-26 15:41     ` Johannes Stezenbach
2012-01-26 15:46       ` Chris Morgan
2012-01-26 16:28         ` Johannes Stezenbach
2012-01-26 21:24           ` Chris Morgan
2012-01-27  0:03             ` Benoît Thébaudeau
2012-01-27 10:56               ` Johannes Stezenbach
2012-01-27 12:02                 ` Benoît Thébaudeau
2012-01-27 17:18                   ` Chris Morgan
2012-01-27 20:10                     ` Benoît Thébaudeau
2012-01-27 20:06                   ` Chris Morgan
2012-01-27 20:11                     ` Benoît Thébaudeau
2012-01-27 20:15                       ` Chris Morgan
2012-01-27 17:15                 ` Chris Morgan
2012-01-28 23:07       ` Yann E. MORIN
2012-01-29 10:10         ` Johannes Stezenbach
2012-01-29 10:53           ` Yann E. MORIN
2012-01-30 21:16             ` Chris Morgan
     [not found] <5c2d9079-5714-4600-829c-08365856a158@zose-store-12>
2012-01-28 22:41 ` Benoît Thébaudeau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAAPegz0en7mBTuo_qQxuyBfQab8PpL9iiBhuwYpyc-_b0GbwUQ@mail.gmail.com \
    --to=chmorgan@gmail.com \
    --cc=crossgcc@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).