From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: confusing qemu-native problem
Date: Mon, 17 Aug 2009 14:28:58 +0200 [thread overview]
Message-ID: <4A894D0A.2080105@dresearch.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0908130730390.3621@juice.ott.cti.com>
Michael Smith schrieb:
> Heh, I guess there's a limit on #! line length.
>
> include/linux/binfmts.h:#define BINPRM_BUF_SIZE 128
<grrrrrr> This looks like a limit from the last millenium. </grrrrrr>
But you're rigth. This seems to be the problem.
> I guess you could try to make your build directory name a bit shorter, or
> hack up pod2man to use #!/usr/bin/env perl.
I choose to shrink my directory path names, because a short look throught the staging area should, that there are a some other scripts with the same problem.
But that's really really ugly. Especially this undetermined behaviour.
Steffen
prev parent reply other threads:[~2009-08-17 12:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AcoU52Sb18YP2SXPQq6rfJAb373LGA==>
2009-08-04 9:38 ` confusing qemu-native problem Sledz, Steffen
2009-08-04 12:29 ` Gregory Machairidis
2009-08-04 12:56 ` Steffen Sledz
2009-08-05 10:37 ` Steffen Sledz
2009-08-13 7:44 ` Steffen Sledz
2009-08-13 11:32 ` Michael Smith
2009-08-17 12:28 ` Steffen Sledz [this message]
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=4A894D0A.2080105@dresearch.de \
--to=sledz@dresearch.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.