Mail Archives: djgpp-workers/2001/09/16/03:26:55
On Sat, 15 Sep 2001, Charles Sandmann wrote:
> > Took a completely clean cvs tree (so nothing much in the bin directory).
> > When doing the make -C utils, I get the error message:
> > *** No rule to make target '../../bin/bin2h.exe', needed by '_alle'
> >
> > It looks like to me this rule is in makefile.inc (?) but it doesn't
> > see it. Can anyone else see this if bin2h is moved?
>
> This was caused by crt0.o being in upper case
Any idea how did crt0.o get renamed to upper case?
> I was surprised we were case sensitive here.
Make is case-insensitive only when LFN is off (because then things
won't work at all if we don't down-case file names and truncate them
to 8+3 limits).
Getting Make to be really insensitive to file-name letter-case
requires heavy changes in Make sources, since it uses strcmp, and
there's no clear indication whether the compared strings are file
names or parts thereof, or just strings. So I decided not to do that
after considering the issues involved.
> > Another problem - if I use the "make" excutable from the w2k site
> > that Andrew built - I get "Bad command or file name" errors, and other
> > similar problems. If I use the make.exe from Andris' site I got a few
> > weeks ago, it works. The distribution version works (but leaks selectors).
> > I then tried a copy I built from source and I see the same errors as
> > Andrew's W2K version. Build configuration problem on W2k?
I'm not sure I understand: what ``build configuration'' did you have
in mind?
> I found if I rebuilt make linked to the patched 2.03 library I get this error,
> but if I link to the original 2.03 library I don't. So, something in
> the new W2K updates (both in 2.04 cvs and 2.03) seems to cause make to
> be unhappy in some cases. Sigh.
Can you post a sample of commands or targets where you get "Bad
command or file name" messages? That might give a clue where to look
for possible causes.
Btw, I found out that if I open a DOS box on W2K and type some
innocent command, like "djtar -h", I get "Bad command or file name",
and right after that the expected results of the program's run. It
almost sounds like W2K fails to find djtar.exe (although it's on my
PATH), then ``changes its mind'' and runs it normally. This happens
only once, the first time after I boot the machine. Any ideas?
(Yes, you guessed it: my wife got a notebook with W2K Professional.)
- Raw text -