mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] cross-compiling and uname
Date: Fri, 20 Jan 2012 09:36:48 +0100	[thread overview]
Message-ID: <4F1927A0.7080201@pengutronix.de> (raw)
In-Reply-To: <20120120073812.GD20430@pengutronix.de>


[-- Attachment #1.1: Type: text/plain, Size: 1981 bytes --]

On 01/20/2012 08:38 AM, Robert Schwebel wrote:
> 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?

We cannot overwrite uname, because even configure with --host and
--build uses uname:

$ strace -o log -e execve -f ./configure --host=x86_64-unknown-linux-gnu --build=x86_64-unknown-linux-gnu
$ grep uname log
1610  execve("/bin/uname", ["uname", "-m"], [/* 51 vars */]) = 0
1612  execve("/bin/uname", ["uname", "-r"], [/* 51 vars */]) = 0
1614  execve("/bin/uname", ["uname", "-s"], [/* 51 vars */]) = 0
1616  execve("/bin/uname", ["uname", "-v"], [/* 51 vars */]) = 0
1618  execve("/usr/bin/uname", ["/usr/bin/uname", "-p"], [/* 51 vars */]) = -1 ENOENT (No such file or directory)
1620  execve("/bin/uname", ["/bin/uname", "-X"], [/* 51 vars */]) = 0

Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

[-- Attachment #2: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2012-01-20  8:36 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
2012-01-20  8:36       ` Marc Kleine-Budde [this message]
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=4F1927A0.7080201@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    --cc=r.schwebel@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