* obsolete files
@ 1999-07-16 19:02 Mark E.
0 siblings, 0 replies; 6+ messages in thread
From: Mark E. @ 1999-07-16 19:02 UTC (permalink / raw)
To: binutils
Hi group,
I retrieved binutils from CVS late yesterday. I believe it contains some
files that are out of date. Specifically:
bfd/makefile.dos
libiberty/makefile.dos
gas/config/go32.cfg
The configure.bat files are also obsolote and can be removed.
---
Mark Elbrecht, snowball3@bigfoot.com
http://snowball.frogspace.net/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: obsolete files
1999-07-20 3:40 ` Eli Zaretskii
@ 1999-07-20 9:20 ` Ian Lance Taylor
0 siblings, 0 replies; 6+ messages in thread
From: Ian Lance Taylor @ 1999-07-20 9:20 UTC (permalink / raw)
To: eliz; +Cc: binutils, snowball3, robert.hoehne
Date: Tue, 20 Jul 1999 06:39:57 -0400 (EDT)
From: Eli Zaretskii <eliz@delorie.com>
Perhaps the necessary changes for
configure.bat simply didn't reach you somehow.
Or I messed up checking them in.
Ian
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: obsolete files
1999-07-18 18:51 ` Ian Lance Taylor
@ 1999-07-20 3:40 ` Eli Zaretskii
1999-07-20 9:20 ` Ian Lance Taylor
0 siblings, 1 reply; 6+ messages in thread
From: Eli Zaretskii @ 1999-07-20 3:40 UTC (permalink / raw)
To: Ian Lance Taylor; +Cc: binutils, snowball3, robert.hoehne
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: obsolete files
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
1 sibling, 1 reply; 6+ messages in thread
From: Ian Lance Taylor @ 1999-07-18 18:51 UTC (permalink / raw)
To: eliz; +Cc: binutils, snowball3, robert.hoehne
Date: Sun, 18 Jul 1999 06:18:57 -0400 (EDT)
From: Eli Zaretskii <eliz@delorie.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?
Ian
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: obsolete files
1999-07-18 3:19 Eli Zaretskii
@ 1999-07-18 6:20 ` Mark E.
1999-07-18 18:51 ` Ian Lance Taylor
1 sibling, 0 replies; 6+ messages in thread
From: Mark E. @ 1999-07-18 6:20 UTC (permalink / raw)
To: Eli Zaretskii, Robert Hoehne, binutils
>
> > The configure.bat files are also obsolete and can be removed.
>
> That's true. But instead of all those obsolete configure.bat files, a
> single configure.bat in the top-level directory should be added to the
> distribution. Without this, configuring and building Binutils with
> DJGPP tools is not for the faint of heart.
Right. What I was planning was a configure.bat that runs a script that
sets up the usual variables (PATH_SEPARATOR, etc.) which in turn
calls configure. Does this sound reasonable?
---
Mark Elbrecht, snowball3@bigfoot.com
http://snowball.frogspace.net/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: obsolete files
@ 1999-07-18 3:19 Eli Zaretskii
1999-07-18 6:20 ` Mark E.
1999-07-18 18:51 ` Ian Lance Taylor
0 siblings, 2 replies; 6+ messages in thread
From: Eli Zaretskii @ 1999-07-18 3:19 UTC (permalink / raw)
To: binutils; +Cc: Mark E., Robert Hoehne
> The configure.bat files are also obsolete and can be removed.
That's true. But instead of all those obsolete configure.bat files, a
single configure.bat in the top-level directory should be added to the
distribution. Without this, configuring and building Binutils with
DJGPP tools is not for the faint of heart.
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?
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~1999-07-20 9:20 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-07-16 19:02 obsolete files Mark E.
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
1999-07-20 9:20 ` Ian Lance Taylor
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).