From: Robert Schwebel <r.schwebel@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Marc Kleine-Budde <mkl@pengutronix.de>
Subject: Re: [ptxdist] cross-compiling and uname
Date: Fri, 20 Jan 2012 08:38:12 +0100 [thread overview]
Message-ID: <20120120073812.GD20430@pengutronix.de> (raw)
In-Reply-To: <20120120073144.GH4854@pengutronix.de>
On Fri, Jan 20, 2012 at 08:31:44AM +0100, Michael Olbrich wrote:
> On Fri, Jan 20, 2012 at 06:30:49AM +0100, Robert Schwebel wrote:
> > On Thu, Jan 19, 2012 at 10:47:55PM +0100, Michael Olbrich wrote:
> > > we had some patches lately about configure scripts etc. using
> > > uname to detect stuff. Why don't we create a fake
> > > ../sysroot-cross/bin/uname that produces the output we would
> > > expect on the target? This way we don't have to fix all those
> > > packages and we have on less source of host system information
> > > leaking into the build.
> >
> > Are there any host tools which do also run uname? I'd prefer
> > overwriting cached variables or something like that.
>
> That's why I want to place it in sysroot-cross/bin. That's not in PATH
> for hosttools.
Hmm, I'm still not sure if this was side-effect free. However, leaving
it as it is will result in at least the same ammount of failures :-)
Marc, do you have an oppinion?
rsc
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-01-20 7:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 21:47 Michael Olbrich
2012-01-20 5:30 ` Robert Schwebel
2012-01-20 7:31 ` Michael Olbrich
2012-01-20 7:38 ` Robert Schwebel [this message]
2012-01-20 8:36 ` Marc Kleine-Budde
2012-01-20 9:09 ` Juergen Beisert
2012-01-20 9:07 ` Juergen Beisert
2012-01-21 20:15 ` Bernhard Walle
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=20120120073812.GD20430@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=mkl@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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