From: "Alexander Stohr" <Alexander.Stohr@gmx.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: coreutils-native-7.2-r0 dependencies not checked
Date: Tue, 28 Sep 2010 19:29:26 +0200 [thread overview]
Message-ID: <20100928172926.22160@gmx.net> (raw)
>> | make: GNUmakefile: Too many levels of symbolic links
>
>This is a known issue - please make sure you don't have simlinks in your
>TMPDIR. If you need to offload portions of your TMPDIR to another partition
>or other place, adjust the corresponding variables instead of symlinking...
>--
>Denys
Hello Denys,
Thanks for that reply.
My whole build dir got symlinked into the home dir due to disk space issues.
But there are no symlinks in the temp dir area as far as i can say.
A somewhat strange behavior. I never noticed tools stumbling across such.
My not that deeply tested, first shot, cheap cheat is that:
do_compile_prepend() {
cd ${S}
if [ -L GNUmakefile ]
then
rm -f GNUmakefile
ln -s Makefile GNUmakefile
fi
}
i've added that to the non-native recipes of the coreutils, m4 and autoconf.
lets see how far that will work for me in my setup.
the build has already flawlessly proceeded to task 181 containing the binutils-cross compilation...
regards, Alex.
PS:
later on i found those discussion mentioning three recipe names from above:
http://old.nabble.com/failing-to-make-u-boot-omap3,-Too-many-levels-of-symbolic-links-td27315933.html
--
Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief!
Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail
next reply other threads:[~2010-09-28 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 17:29 Alexander Stohr [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-09-28 15:10 coreutils-native-7.2-r0 dependencies not checked Alexander Stohr
2010-09-28 16:09 ` Denys Dmytriyenko
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=20100928172926.22160@gmx.net \
--to=alexander.stohr@gmx.de \
--cc=openembedded-devel@lists.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.