From: Christoph Kukulies <kuku@gilberto.physik.RWTH-Aachen.DE>
To: cygwin@sourceware.cygnus.com
Subject: Subject: SHELL=/bin/sh in Makefiles
Date: Thu, 29 Jul 1999 08:15:00 -0000 [thread overview]
Message-ID: <199907291515.RAA85673@gil.physik.rwth-aachen.de> (raw)
I tried to compile flex 2.5.4a under b20 (finally got it compiled).
I was surprised that even ./configure worked.
The only glitch I came across was that I got a strange
/c: Can't open /c
when I ran 'make' from within bash.
I removed the SHELL=/bin/sh statement from the Makefile and got
ahead.
What is the secret of this? I remember that I had the same problem
under b19. I have a sh.exe in C:\bin .
--
Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: Christoph Kukulies <kuku@gilberto.physik.RWTH-Aachen.DE>
To: cygwin@sourceware.cygnus.com
Subject: Subject: SHELL=/bin/sh in Makefiles
Date: Sat, 31 Jul 1999 18:34:00 -0000 [thread overview]
Message-ID: <199907291515.RAA85673@gil.physik.rwth-aachen.de> (raw)
Message-ID: <19990731183400.HwgzEexT255Ds1QuVtujvqapoTLhdF3V2zAkfKlPbDU@z> (raw)
I tried to compile flex 2.5.4a under b20 (finally got it compiled).
I was surprised that even ./configure worked.
The only glitch I came across was that I got a strange
/c: Can't open /c
when I ran 'make' from within bash.
I removed the SHELL=/bin/sh statement from the Makefile and got
ahead.
What is the secret of this? I remember that I had the same problem
under b19. I have a sh.exe in C:\bin .
--
Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~1999-07-29 8:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-29 8:15 Christoph Kukulies [this message]
1999-07-31 18:34 ` Christoph Kukulies
1999-07-30 12:51 Lamb, Ronald F.
1999-07-31 18:34 ` Lamb, Ronald F.
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=199907291515.RAA85673@gil.physik.rwth-aachen.de \
--to=kuku@gilberto.physik.rwth-aachen.de \
--cc=cygwin@sourceware.cygnus.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).