From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] cross-compiling and uname
Date: Thu, 19 Jan 2012 22:47:55 +0100 [thread overview]
Message-ID: <20120119214755.GF4854@pengutronix.de> (raw)
Hi,
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.
Michael
--
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 reply other threads:[~2012-01-19 21:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 21:47 Michael Olbrich [this message]
2012-01-20 5:30 ` Robert Schwebel
2012-01-20 7:31 ` Michael Olbrich
2012-01-20 7:38 ` Robert Schwebel
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=20120119214755.GF4854@pengutronix.de \
--to=m.olbrich@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