From: Clemens Helfmeier <clemens@helfmeier.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Problem in configure
Date: Mon, 13 Oct 2008 08:56:39 +0200 [thread overview]
Message-ID: <20081013065639.GD2412@helfmeier.de> (raw)
In-Reply-To: <da3a2a260810121808j3daf99c7mfdabb31f0d876c70@mail.gmail.com>
Hi James,
This is a shell thing. It just ensures that the evaluation does not result in
if test = xno; then
(in case the variable is empty) and thus throw an error. with "x" it its like
this for an empty variable
if test x = xno; then
which would work fine for shells.
The x does not affect the result of the evaluation since it is on both sides of
the evaluation.
Bye,
Clemens
On Sun, Oct 12, 2008 at 09:08:09PM -0400, James Shewey wrote:
> This may be a nevermind situation. I was compiling on a 64 bit system.
> Changing the line described to if test "$grub_cv_prog_target_cc" = xno;
> then" Resulted in an error stating that neither start or _start was defined.
> This led me to the following post:
> http://bbs.archlinux.org/viewtopic.php?id=56033. This led me to try
> compiling on my 32 bit system which worked just fine.
>
> On Sun, Oct 12, 2008 at 8:29 PM, James Shewey <jdshewey@gmail.com> wrote:
>
> > I believe that line 6938, which reads:
> >
> > if test "x$grub_cv_prog_target_cc" = xno; then
> >
> > May contain an error. Perhaps this should read
> >
> > if test "$grub_cv_prog_target_cc" = xno; then
> >
> > or
> >
> > if test "$grub_cv_prog_target_cc" = no; then
> >
> > ?
> >
> > -James
> >
> >
> >
> >
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
next prev parent reply other threads:[~2008-10-13 6:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 0:29 Problem in configure James Shewey
2008-10-13 1:08 ` James Shewey
2008-10-13 6:56 ` Clemens Helfmeier [this message]
2008-10-13 7:38 ` Christian Franke
-- strict thread matches above, loose matches on Subject: below --
2008-10-13 11:33 James Shewey
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=20081013065639.GD2412@helfmeier.de \
--to=clemens@helfmeier.de \
--cc=grub-devel@gnu.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.