public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@delorie.com>
To: Ian Lance Taylor <ian@zembu.com>
Cc: binutils@sourceware.cygnus.com, snowball3@bigfoot.com,
	robert.hoehne@gmx.net
Subject: Re: obsolete files
Date: Tue, 20 Jul 1999 03:40:00 -0000	[thread overview]
Message-ID: <199907201039.GAA28595@indy.delorie.com> (raw)
In-Reply-To: <19990719015012.1463.qmail@daffy.airs.com>

  Date: 18 Jul 1999 21:50:12 -0400
  From: Ian Lance Taylor <ian@zembu.com>

>    As a matter of fact, I don't understand wasn't top-level configure.bat
>    added to the current sources, since this is the only change that
>    Robert Hoehne needed to do to build 2.8.1 with DJGPP that wasn't
>    checked into the development sources.  All the other changes are
>    already there in v2.9.1.  Why?
> 
> I'm not sure quite what you are saying.  There is a top level
> configure.bat file in binutils 2.9.1.  Is it incorrect or something?

It is very obsolete and doesn't do what has to be done to configure
Binutils for DJGPP.  The DJGPP port of Binutils runs the top-level
configure script nowadays, but configure.bat in 2.9.1 doesn't do that.
Instead, it invokes configure.bat batch files (which are also obsolete
and should IMHO be removed from the distribution) in each one of the
subdirectories.  What top-level configure.bat _should_ do is to set
several environment variables that will help the configure script to
run smoothly, and then simply invoke "sh ./configure".

When I compared the sources of Binutils 2.8.1 ported to DJGPP by
Robert Hoehne with Binutils 2.9.1, I saw that all the changes Robert
needed to do in order to build Binutils were already in 2.9.1, with
the sole exception of the top-level configure.bat that seems to remain
unchanged.  Hence my question why weren't configure.bat changes
incorporated in v2.9.1.  Perhaps the necessary changes for
configure.bat simply didn't reach you somehow.

  reply	other threads:[~1999-07-20  3:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-18  3:19 Eli Zaretskii
1999-07-18  6:20 ` Mark E.
1999-07-18 18:51 ` Ian Lance Taylor
1999-07-20  3:40   ` Eli Zaretskii [this message]
1999-07-20  9:20     ` Ian Lance Taylor
  -- strict thread matches above, loose matches on Subject: below --
1999-07-16 19:02 Mark E.

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=199907201039.GAA28595@indy.delorie.com \
    --to=eliz@delorie.com \
    --cc=binutils@sourceware.cygnus.com \
    --cc=ian@zembu.com \
    --cc=robert.hoehne@gmx.net \
    --cc=snowball3@bigfoot.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).