public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>
Cc: binutils@sourceware.org
Subject: Re: Add support for ld-elf.so.hints on FreeBSD and DragonFly - Fourth  try
Date: Tue, 11 Apr 2006 13:12:00 -0000	[thread overview]
Message-ID: <443B869E.20705@redhat.com> (raw)
In-Reply-To: <200603212223.28315@enterprise.flameeyes.is-a-geek.org>

Hi Diego,

> Okay, new version of the patch, this time it includes an almost verbatim copy 
> of the elf-hints header file from FreeBSD as elf-hints-local.h, that is 
> included if the elf-hints.h file is not present in the system already, so 
> that it works when building non systems not using FreeBSD's or DragonFly's 
> libc,but still defaults to system's headers if they are present, so that if 
> they change the signature it works fine anyway.
> This should solve the license issues, too.

Thanks - I have checked your patch in together with this ChangeLog entry.

Cheers
   Nick

ld/ChangeLog
2006-04-11  Diego Petteno <flameeyes@gentoo.org>

         * emultempl/elf32.em: Add support for elf-hints.h on FreeBSD
	and Dragonfly targets.
	* configure.in (AC_CHECK_HEADERS): Add elf-hints.h.
	* Makefile.am (HFILES): Add elf-hints-local.h.
	* elf-hints-local.h: New file.
	* Makefile.in: Regenerate.
	* configure: Regenerate.

      parent reply	other threads:[~2006-04-11 10:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-21 22:52 Diego 'Flameeyes' Pettenò
2006-03-21 23:59 ` Mike Frysinger
2006-04-11 13:12 ` Nick Clifton [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=443B869E.20705@redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=flameeyes@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).