public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
To: Jerome Guitton <guitton@gnat.com>
Cc: Julian Brown <julian@codesourcery.com>,  binutils@sources.redhat.com
Subject: Re: Build failure on Debian testing (cross to arm-none-eabi)
Date: Fri, 22 Apr 2005 16:54:00 -0000	[thread overview]
Message-ID: <873btiycpq.fsf@codesourcery.com> (raw)
In-Reply-To: <20050422093547.GE15341@adacore.com> (Jerome Guitton's message of "Fri, 22 Apr 2005 11:35:47 +0200")

Jerome Guitton <guitton@gnat.com> writes:
> Julian Brown (julian@codesourcery.com):
>> In file included from /home/jules/binutils/src/bfd/doc/chew.c:86:
>> /home/jules/binutils/src/bfd/sysdep.h:140: error: parse error before 
>> "ftello64"
>> /home/jules/binutils/src/bfd/sysdep.h:140: warning: data definition has 
>> no type or storage class
>> /home/jules/binutils/src/bfd/sysdep.h:152: error: parse error before 
>> "off64_t"
>
> Mmmm... Sorry for this one. I am able to reproduce it on a linux
> host. I am investigating.

This reminds me ... in the past, I've had problems with binutils'
habit of generating the documentation at install time.  For instance,
in a rather complicated environment where I built the software, then
handed it over to a sysadmin for installation, and he didn't have the
same $PATH as I did, and it blew up not being able to find either
makeinfo or cc.

GCC builds the documentation as part of "make all" - this works much
better in that sort of environment, and would have caught this bug as
well.  What do people think of changing it?

zw

  reply	other threads:[~2005-04-22 16:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21 19:25 Julian Brown
2005-04-22  9:36 ` Jerome Guitton
2005-04-22 16:54   ` Zack Weinberg [this message]
2005-04-22 19:19     ` Hans-Peter Nilsson
2005-04-22 19:29       ` Zack Weinberg
2005-04-25  7:45       ` Thorsten Glaser
2005-04-25 11:40         ` Hans-Peter Nilsson
2005-04-26 18:51     ` Nick Clifton
2005-05-18 19:15       ` Build documentation in 'make all' (was Re: Build failure on Debian testing (cross to arm-none-eabi)) Zack Weinberg
2005-05-19 12:20         ` Nick Clifton
2005-04-22 13:50 ` Build failure on Debian testing (cross to arm-none-eabi) Jerome Guitton
2005-04-22 14:08   ` H. J. Lu
2005-04-22 14:59     ` Jerome Guitton

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=873btiycpq.fsf@codesourcery.com \
    --to=zack@codesourcery.com \
    --cc=binutils@sources.redhat.com \
    --cc=guitton@gnat.com \
    --cc=julian@codesourcery.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).