public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>,
	       Iain Buclaw <ibuclaw@gdcproject.org>
Cc: gdb-patches@sourceware.org, yunlian@google.com
Subject: Re: [BUILDROBOT] asprintf() no longer declared
Date: Tue, 30 Jun 2015 16:55:00 -0000	[thread overview]
Message-ID: <5592C9E6.5040202@redhat.com> (raw)
In-Reply-To: <20150630162540.GA23299@lug-owl.de>

On 06/30/2015 05:25 PM, Jan-Benedict Glaw wrote:
> On Thu, 2015-06-25 16:23:48 +0200, Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
>> On Fri, 2015-06-19 17:18:38 +0200, Iain Buclaw <ibuclaw@gdcproject.org> wrote:
>>> Belated attempt at downstreaming libiberty changes from upstream.
>>> Split it into two patches, one with dlang related changes, the other
>>> with everything else.
>>>
>>> As requested, commits have been replayed ontop of gdb rather than a
>>> straight diff between the directories.
>> [...]
>>
>> Seems there were some minor changes in libiberty which breaks code
>> generation on non-GNU systems due to missing asprintf().
>>
>>   On the AIX builder (gcc111.fsffrance.org), I see build failures in
>> Binutils since then, see ie.
>> http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=448549:
>>
>> /bin/sh ./libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I/home/jbglaw/repos/binutils_gdb/bfd -I. -I/home/jbglaw/repos/binutils_gdb/bfd -I/home/jbglaw/repos/binutils_gdb/bfd/../include  -DHAVE_cr16_elf32_vec -DHAVE_elf32_le_vec -DHAVE_elf32_be_vec -DHAVE_plugin_vec  -DBINDIR='"/home/jbglaw/build/cr16-elf/_install_/bin"'  -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Werror -I/home/jbglaw/repos/binutils_gdb/bfd/../zlib -g -O2 -MT bfd.lo -MD -MP -MF .deps/bfd.Tpo -c -o bfd.lo /home/jbglaw/repos/binutils_gdb/bfd/bfd.c
>> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I/home/jbglaw/repos/binutils_gdb/bfd -I. -I/home/jbglaw/repos/binutils_gdb/bfd -I/home/jbglaw/repos/binutils_gdb/bfd/../include -DHAVE_cr16_elf32_vec -DHAVE_elf32_le_vec -DHAVE_elf32_be_vec -DHAVE_plugin_vec -DBINDIR=\"/home/jbglaw/build/cr16-elf/_install_/bin\" -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Werror -I/home/jbglaw/repos/binutils_gdb/bfd/../zlib -g -O2 -MT bfd.lo -MD -MP -MF .deps/bfd.Tpo -c /home/jbglaw/repos/binutils_gdb/bfd/bfd.c -o bfd.o
>> /home/jbglaw/repos/binutils_gdb/bfd/bfd.c: In function 'bfd_errmsg':
>> /home/jbglaw/repos/binutils_gdb/bfd/bfd.c:543:7: error: implicit declaration of function 'asprintf' [-Werror=implicit-function-declaration]
>>        if (asprintf (&buf, _(bfd_errmsgs [error_tag]), input_bfd->filename, msg)
>>        ^
>> cc1: all warnings being treated as errors
>> make[3]: *** [bfd.lo] Error 1
>> make[3]: Leaving directory `/home/jbglaw/build/cr16-elf/build-binutils-full/bfd'
> 
> It's a few days since building GDB probably broke on all non-GNU
> platforms. Is somebody about to work on that?

TBC, this is not really Iain's fault, as his patch was
just a merge from upstream.

(It'd be good if people interested in the affected platforms
came forward and help diagnose/fix it.)

I suspect that this is what is breaking things:

--- a/include/ChangeLog
+++ b/include/ChangeLog

+2015-05-22  Yunlian Jiang  <yunlian@google.com>
+
+       * libiberty.h (asprintf): Don't declare if HAVE_DECL_ASPRINTF is
+       not defined.
+

I see here that Yunlian actually wanted this to fix the gdb build:

 https://sourceware.org/ml/gdb-patches/2015-05/msg00665.html

Iain just happened to merge the patch sooner.

Added Yunlian Jiang to CC.

I think the problem is that bfd's configure.ac is missing
an AC_CHECK_DECLS for asprintf, so that HAVE_DECL_ASPRINTF can end
up defined.

(the series mentioned at https://gcc.gnu.org/ml/gcc-patches/2015-02/msg01712.html
would address this for good all over the tree, but I never heard
from the libiberty maintainers about that idea.  Surprisingly, I notice
now that I missed converting bfd/.)

Thanks,
Pedro Alves

      parent reply	other threads:[~2015-06-30 16:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19 15:18 [PATCH v2 1/2] Sync libiberty with gcc upstream Iain Buclaw
2015-06-24 11:34 ` Pedro Alves
2015-06-24 13:52   ` Iain Buclaw
2015-06-24 13:54     ` Pedro Alves
2015-06-25 14:23 ` [BUILDROBOT] asprintf() no longer declared (was: [PATCH v2 1/2] Sync libiberty with gcc upstream) Jan-Benedict Glaw
2015-06-25 21:13   ` [BUILDROBOT] asprintf() no longer declared Sergio Durigan Junior
2015-06-30 16:25   ` [BUILDROBOT] asprintf() no longer declared (was: [PATCH v2 1/2] Sync libiberty with gcc upstream) Jan-Benedict Glaw
2015-06-30 16:42     ` [BUILDROBOT] asprintf() no longer declared Luis Machado
2015-06-30 16:55     ` Pedro Alves [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=5592C9E6.5040202@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ibuclaw@gdcproject.org \
    --cc=jbglaw@lug-owl.de \
    --cc=yunlian@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).