From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] -cc checking wrong
Date: Mon, 8 May 2006 11:12:54 -0400 [thread overview]
Message-ID: <20060508151254.GA10640@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <87d5epnec3.fsf@Janik.cz>
On Mon, May 08, 2006 at 09:52:12AM +0200, Pavel Jan?k wrote:
> From: "Jim C. Brown" <jma5@umd.edu>
> Date: Sun, 7 May 2006 20:34:11 -0400
>
> > The right thing to do might be to check if the first arg is ccache,
> > and if so check for both ccache and the 2nd compiler. Especially if
> > ccache is the only compiler that requires arguments be passed to it
> > in --cc or CC=
>
> This is also wrong - you can use "distcc ccache gcc" as your compiler...
Hmm.
Maybe make the check into a function, and if the first arg is distcc or ccache,
check that the first arg is -x and then call the function recursively with the
remaining args. Else just check if the compiler exists.
> --
> Pavel Jan?k
>
> Sounds like a "bug waiting to be implemented" ;)
> -- Rik van Riel in linux-kernel
>
>
> _______________________________________________
> 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.
next prev parent reply other threads:[~2006-05-08 15:12 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 [this message]
2006-05-08 18:53 ` Pavel Janík
2006-05-08 19:08 ` Jim C. Brown
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=20060508151254.GA10640@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 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.