Home
Reading
Searching
Subscribe
Sponsors
Statistics
Posting
Contact
Spam
Lists
Links
About
Hosting
Filtering
Features Download
Marketing
Archives
FAQ
Blog
 
Gmane
From: Keith Marshall <keithmarshall-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f <at> public.gmane.org>
Subject: Re: New binutils snapshot
Newsgroups: gmane.comp.gnu.mingw.devel
Date: Thursday 10th January 2008 21:32:31 UTC (over 9 years ago)
On Wed, 2008-01-09 at 21:20 -0500, Chris Sutcliffe wrote:
> Keith, what files were missing?

On this occasion, just these two, (identified after following the build
procedure outlined below):--

  $ cd ~/tmpdir/kit
  $ find . -type f -print
  ./ld/deffilep.c
  ./ld/deffilep.h

> I want to make sure that they are in this source tarball.

The most reliable way to ensure that is to follow the build procedure 
I described the other day, on mingw-users.  For reference, here it is
again, as I've adapted it for a crossed-native build:--

  $ rm -rf tmpdir
  $ mkdir -p tmpdir/kit
  $ cd tmpdir
  $ mkdir dist
  $ tar xf $PACKAGE_DIR/binutils-2.18.50-20071123-src.tar.gz
  $ find . -type d -name CVS -exec rm -rf {} +
  $ cd kit
  $ ../binutils-2.18.50/configure --prefix=c:/mingw  \
      --build=i686-pc-linux --host=i586-mingw32  \
      --with-gcc --with-gnu-as --with-gnu-ld  \
      --disable-nls
  $ make
  $ make prefix=`cd ../dist;pwd` install
  $ make distclean
  $ tar chf - . | ( cd ../binutils-2.18.50/; tar xf - )
  $ cd ../dist
  $ find . -type f -iname dir -exec rm -i {} +
  $ tar czhf $RELEASE_DIR/binutils-2.18.50-20071123-bin.tar.gz *
  $ cd ..
  $ tar czhf $RELEASE_DIR/binutils-2.18.50-20071123-src.tar.gz  \
      binutils-2.18.50

Note the two find commands.  The first cleans up the source tree, if the
original tarball was created for an original source tree checked out
from CVS, (as was the case for Danny's 2.17.50 release); the second
expunges any info `dir' files, which should *never* be included in any
binary distribution package; (there weren't any in this case, but it's
always a good idea to check).

It is also a good idea to run:--

  $ find . -type f -print

on the build directory, (`kit' in the above example), immediately after
the `make distclean', and review what has been left behind.  In the
2.18.50 case, there were only the two files noted above, which *should*
be distributed, but in 2.17.50 there were also several generated manpage
files, and even some configure output and log files, left behind, and
these definitely should not be distributed, so I removed them, before
merging the distcleaned build tree back into the unmodified source tree,
(the `tar chf - . | ...' command).

Regards,
Keith.


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
 
CD: 3ms