public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@novell.com>
To: <gcc-patches@gcc.gnu.org>
Cc: <binutils@sources.redhat.com>
Subject: Re: libiberty addition (for binutils): unlink_if_ordinary
Date: Wed, 02 Mar 2005 08:46:00 -0000	[thread overview]
Message-ID: <s2257d6a.087@emea1-mh.id2.novell.com> (raw)

>>> Hans-Peter Nilsson <hp@bitrange.com> 02.03.05 01:11:44 >>>
>On Wed, 26 Jan 2005, Jan Beulich wrote:
>> libiberty/
>> 2005-01-26  Jan Beulich  <jbeulich@novell.com>
>>
>> 	* Makefile.in (CFILES): Add unlink-if-ordinary.c
>> 	(REQUIRED_OFILES): Add unlink-if-ordinary.o.
>> 	Add dependencies and rule for unlink-if-ordinary.o.
>> 	* unlink-if-ordinary.c: New.
>
>This caused a GCC warning regression: 2 new warnings for lstat
>not being declared (once when compiled for host
>i686-pc-linux-gnu, once for target cris-axis-elf).  I suggest
>the usual configure hoops be added.

Hmm, I can't see such when building binutils on i686-pc-linux-gnu. And
the logic to deal with lstat availability was taken from elsewhere in
binutils, too.

Jan

             reply	other threads:[~2005-03-02  8:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-02  8:46 Jan Beulich [this message]
     [not found] <s1f74c78.013@emea1-mh.id2.novell.com>
2005-03-01  1:32 ` DJ Delorie
     [not found] <s21b15e2.073@emea1-mh.id2.novell.com>
2005-02-22 18:36 ` DJ Delorie
  -- strict thread matches above, loose matches on Subject: below --
2005-02-22 18:29 Jan Beulich
     [not found] <s21a0df3.067@emea1-mh.id2.novell.com>
2005-02-21 21:50 ` DJ Delorie
2005-02-21 19:45 Jan Beulich
2005-01-26  7:53 Jan Beulich
2005-03-02  0:12 ` Hans-Peter Nilsson

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=s2257d6a.087@emea1-mh.id2.novell.com \
    --to=jbeulich@novell.com \
    --cc=binutils@sources.redhat.com \
    --cc=gcc-patches@gcc.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 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).