All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: grub-devel@gnu.org, Robert Millan <rmh@aybabtu.com>
Subject: Cross-compilation check broken
Date: Wed, 28 Jan 2009 21:14:34 -0500	[thread overview]
Message-ID: <1233195275.2727.18.camel@dv> (raw)

Hello, Robert!

Your commit 1955 breaks my script for testing PowerPC.  That's the
script:

#!/bin/sh
set -e
CROSS_PATH=/home/proski/src/buildroot/build_powerpc/staging_dir/usr/bin
PATH=$CROSS_PATH:$PATH
./configure --with-platform=ieee1275 --target=powerpc-linux
make -j2
./grub-mkrescue --grub-mkimage=./grub-mkelfimage --pkglibdir=. grub.iso
qemu-system-ppc -nographic -cdrom grub.iso -boot d

I compile for target "powerpc-linux" and I have powerpc-linux-gcc in the
PATH.  However, I'm using native tools.  I'm not interested in running
tools in an emulator (actually, I have another script that does it).
Therefore, build and host are the same, so TARGET_CC is set to gcc.

The new check must be wrong.  TARGET_CC is used to build executables for
the target system.  It should be found using the specified target even
if the tools are compiled natively.

Actually, the original check wasn't particularly good.  Maybe we could
check if target_alias is defined?  Or maybe we could always check for
TARGET_CC?

-- 
Regards,
Pavel Roskin



             reply	other threads:[~2009-01-29  2:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-29  2:14 Pavel Roskin [this message]
2009-01-29 13:07 ` Cross-compilation check broken Robert Millan
2009-01-29 16:19   ` Pavel Roskin
2009-02-07 21:42     ` Robert Millan

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=1233195275.2727.18.camel@dv \
    --to=proski@gnu.org \
    --cc=grub-devel@gnu.org \
    --cc=rmh@aybabtu.com \
    /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.