From: Tony Breeds <tony@bakeyournoodle.com>
To: Stefan Berger <stefanb@us.ibm.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
xen-devel-bounces@lists.xensource.com
Subject: Re: [PATCH] [XM-TEST] Fix xm-test suite for x86-64
Date: Tue, 31 Oct 2006 11:42:14 +1100 [thread overview]
Message-ID: <20061031004214.GK27551@bakeyournoodle.com> (raw)
In-Reply-To: <OF8CDA98FD.4FD47460-ON85257217.004F36B5-85257217.0050FF32@us.ibm.com>
On Mon, Oct 30, 2006 at 09:44:52AM -0500, Stefan Berger wrote:
> I have changed the xm-test/ramdisk/Makefile.am to look like this now. With
> this only x86-64 so far gets its own config for the uClibc.
>
> - cp configs/uClibc $(BR_SRC)/toolchain/uClibc/uClibc.config
> + if [ $(BR_ARCH) == "x86_64" ]; then \
> + cp configs/uClibc-$(BR_ARCH) \
> + $(BR_SRC)/toolchain/uClibc/uClibc.config; \
> + else \
> + cp configs/uClibc \
> + $(BR_SRC)/toolchain/uClibc/uClibc.config; \
> + fi
>
> Is this better?
Personally I prefer your original approach. Sure it creates duplicate
data files (as i386 and powerpc uClibc are the same) but it follows the
buildroot precident, and allows for changing configs based on the arch
without modifying the Makefiles.
> http://bugs.busybox.net/bug_view_advanced_page.php?bug_id=523
Bugger. I wonder what the timeframe is for the next uClibc release.
> And thanks on the hint on how to patch hping2. It works now - at least for
> x86-64.
Glad it helped.
Yours Tony
linux.conf.au http://linux.conf.au/ || http://lca2007.linux.org.au/
Jan 15-20 2007 The Australian Linux Technical Conference!
prev parent reply other threads:[~2006-10-31 0:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-27 20:35 [PATCH] [XM-TEST] Fix xm-test suite for x86-64 Stefan Berger
2006-10-28 4:34 ` Tony Breeds
2006-10-28 15:00 ` Stefan Berger
2006-10-30 3:17 ` Tony Breeds
2006-10-30 14:44 ` Stefan Berger
2006-10-31 0:42 ` Tony Breeds [this message]
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=20061031004214.GK27551@bakeyournoodle.com \
--to=tony@bakeyournoodle.com \
--cc=stefanb@us.ibm.com \
--cc=xen-devel-bounces@lists.xensource.com \
--cc=xen-devel@lists.xensource.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.