Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Dan Aizenstros <dan@vcubed.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: linux-mips@oss.sgi.com
Subject: Re: Binutils-2.10
Date: Mon, 31 Jul 2000 18:24:10 -0400	[thread overview]
Message-ID: <3985FC8A.70E449C6@vcubed.com> (raw)
In-Reply-To: Pine.GSO.3.96.1000731182751.21648Q-100000@delta.ds2.pg.gda.pl

Thanks for the help.  I was able to build binutils-2.10 after
generating the headers as you described.

The reason I expect the patch to change generated files is
because the normal make does not generate them and the files
are included in the binutils-2.10.tar.bz2 file.  They are also
in CVS.  Why are generated files in CVS or the binary distribution
if you have to generate them?

I thought all I would have to do is a ./configure; make; make install
after I applied the patches.  Maybe you could add the need to generate
files on your binutils-2.10 web page.

Dan Aizenstros
Software Engineer
V3 Semiconductor Corp.

"Maciej W. Rozycki" wrote:
> 
> On Mon, 31 Jul 2000, Dan Aizenstros wrote:
> 
> > it is a generated file so how do I generate it?  I am also
> 
>  make -C bfd headers
> 
> > wondering if changes to this file are missing from the patch
> > file.
> 
>  It's intentional.  Why would generated files be included in a patch?  It
> only makes life more difficult when applying to modified sources.
> 
> --
> +  Maciej W. Rozycki, Technical University of Gdansk, Poland   +
> +--------------------------------------------------------------+
> +        e-mail: macro@ds2.pg.gda.pl, PGP key available        +

  reply	other threads:[~2000-07-31 22:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-31 14:45 Binutils-2.10 Dan Aizenstros
2000-07-31 16:31 ` Binutils-2.10 Maciej W. Rozycki
2000-07-31 22:24   ` Dan Aizenstros [this message]
2000-08-01  8:42     ` Binutils-2.10 Maciej W. Rozycki
2000-07-31 16:34 ` Binutils-2.10 Ulf Carlsson

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=3985FC8A.70E449C6@vcubed.com \
    --to=dan@vcubed.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=macro@ds2.pg.gda.pl \
    /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