From: DJ Delorie <dj@redhat.com>
To: binutils@sources.redhat.com, gdb-patches@sources.redhat.com,
cygwin@sources.redhat.com, newlib@sources.redhat.com
Subject: [merge] build-libiberty patch merged from gcc
Date: Wed, 28 Nov 2001 12:03:00 -0000 [thread overview]
Message-ID: <200111282001.fASK1St14784@greed.delorie.com> (raw)
Message-ID: <20011128120300.pZKOe00aMpJA8Ok0k6dvGGk19ILinLlEj0Oc5kLP0FU@z> (raw)
I merged the top-level and libiberty parts of this patch from gcc:
http://gcc.gnu.org/ml/gcc-patches/2001-11/msg01611.html
If you configure a build where build!=host, you will now see a
top-level build directory named after the build system, with a
libiberty build in it. This libiberty is suitable for programs which
must run on the build machine. To add support for this to your
project, there are two options. The above patch demonstrates how to
detect the build!=host case with configure. This older patch
demonstrates how to do it with just a Makefile change:
http://gcc.gnu.org/ml/gcc-patches/2001-07/msg00608.html
If you encounter any problems with the build-libiberty changes, please
let me know.
Thanks,
DJ
next reply other threads:[~2001-11-28 12:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-17 20:43 DJ Delorie [this message]
2001-11-28 12:03 ` DJ Delorie
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=200111282001.fASK1St14784@greed.delorie.com \
--to=dj@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=cygwin@sources.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=newlib@sources.redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox