From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: FYI: -Wunused warning in cp-namespace.c with old glibc...
Date: Wed, 30 Dec 2009 13:22:00 -0000 [thread overview]
Message-ID: <20091230132227.GA13143@caradoc.them.org> (raw)
In-Reply-To: <20091230104816.GC548@adacore.com>
On Wed, Dec 30, 2009 at 02:48:16PM +0400, Joel Brobecker wrote:
> Hello,
>
> We're still supporting some pretty old x86-linux distributions at
> AdaCore, and one of them comes with a now antiquated version of
> the glic. And unfortunately, this version of glic plays some tricks
> with strncpy, while these tricks are disabled on older glibcs
> for GCC 3.2+:
FYI, we ran into this too - we ended up dropping a newer
bits/string2.h (from RHEL4 rather than RH8/RHEL3, I believe) into our
build system. The newer one works fine with an older runtime.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-12-30 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-30 10:48 Joel Brobecker
2009-12-30 13:22 ` Daniel Jacobowitz [this message]
2010-03-24 23:26 ` Joseph S. Myers
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=20091230132227.GA13143@caradoc.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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