qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] -cc checking wrong
Date: Mon, 8 May 2006 15:08:04 -0400	[thread overview]
Message-ID: <20060508190804.GA10821@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <87u080l55i.fsf@Janik.cz>

On Mon, May 08, 2006 at 08:53:29PM +0200, Pavel Jan?k wrote:
> 
>    > check that the first arg is -x
> 
> This is also incorrect.
> 
> pavel@paveljanik:/tmp> alias compiler=gcc
> pavel@paveljanik:/tmp> compiler -v
> Reading specs from /usr/lib/gcc-lib/i586-suse-linux/3.3.5/specs
> [...]
> pavel@paveljanik:/tmp> [ -x compiler ] || echo ERROR
> ERROR
> pavel@paveljanik:/tmp> 
> 
> The only correct way is to *execute* simple test.

Incidently, this is not correct either way.

$ alias compiler=gcc
$ compiler -v
Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5-20050130/specs
[...]
$ ./configure --cc=compiler
ERROR: "compiler" either does not exist or does not work

Thats with the fixed CVS that uses my other patch.

Aliases aren't suppose to pass through to shell scripts.

> -- 
> Pavel Jan?k
> 
> "With some developers it is not needed to run the code through
> obfuscator... I have inherited code which only the compiler could
> understand."      -- someone in LKML
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
> 

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.

  reply	other threads:[~2006-05-08 19:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-01  7:41 [Qemu-devel] -cc checking wrong Pavel Janík
2006-05-07 22:46 ` Pavel Janík
2006-05-08  0:18   ` Jim C. Brown
2006-05-08  0:34     ` Jim C. Brown
2006-05-08  7:52       ` Pavel Janík
2006-05-08 15:12         ` Jim C. Brown
2006-05-08 18:53           ` Pavel Janík
2006-05-08 19:08             ` Jim C. Brown [this message]
2006-05-08  0:53     ` Paul Brook
2006-05-08  1:13       ` Jim C. Brown

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=20060508190804.GA10821@jbrown.mylinuxbox.org \
    --to=jma5@umd.edu \
    --cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).