All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Baking coreutils-native-7.2-r0 fails
Date: Thu, 16 Jul 2009 14:48:43 +0200	[thread overview]
Message-ID: <h3n7jb$il3$1@ger.gmane.org> (raw)
In-Reply-To: <69E6C70090A0A14498CC98FAE5E06B6E3CF928@hiob.intern.dresearch.de>

On 16-07-09 14:10, Sledz, Steffen wrote:
> I've an interesting problem baking coreutils-native-7.2-r0 (org.openembedded.dev branch with Angstrom distro and different machines, checked e.g. with beagleboard, x86, and hipox) on some hosts:
>
> NOTE: Running task 28 of 69 (ID: 7, /home/DRESEARCH/sledz/work/openembedded/recipes/coreutils/coreutils-native_7.2.bb, do_compile)
> ERROR: function do_compile failed
> ERROR: log data follows (/home/DRESEARCH/sledz/oe/tmp.3/work/i686-linux/coreutils-native-7.2-r0/temp/log.do_compile.757)
> | NOTE: make
> | make: GNUmakefile: Too many levels of symbolic links
> | make: stat: GNUmakefile: Too many levels of symbolic links
> | make: *** No rule to make target `GNUmakefile'.  Stop.
> | FATAL: oe_runmake failed
>
> I've tried building on two different hosts: on one of them (mobil-400-300) everything works well, on the other (fsc-480-012-88) the mentioned problem occurs (logs for both are attached). Both are running openSUSE 11.1 (same patch level), same bitbake version, same OE release (last commit is c0b076183453b890a5baaf5bbd2d53061e5ecc84). I started with an empty sources dir and tmp.3 was deleted before too.
>
> I'm totally confused. What's wrong here?

Sounds like your builddir is either on nfs or contains a symlink.

regards,

Koen




  reply	other threads:[~2009-07-16 13:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-16 12:10 Baking coreutils-native-7.2-r0 fails Sledz, Steffen
2009-07-16 12:48 ` Koen Kooi [this message]
2009-07-16 13:50   ` Sledz, Steffen

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='h3n7jb$il3$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.