From: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
To: Eric Goforth <ewgoforth@netmcr.com>,
"cygwin@sourceware.cygnus.com" <cygwin@hotpop.com>
Subject: Re: No such file or directory
Date: Sat, 25 Mar 2000 19:44:00 -0000 [thread overview]
Message-ID: <4.3.2.20000325222901.00d398a0@pop.ma.ultranet.com> (raw)
In-Reply-To: <38DBEF82.7DF664AD@netmcr.com>
At 05:43 PM 3/24/00, Eric Goforth wrote:
>I'm trying to compile the Remind utility to work under Cygwin. I
>initially tried compiling it with the I've compiled it, and then tried
>"make install," but I'm getting a bunch of "No such file or directory"
>messages. I created a /usr/local/man and /usr/local/bin directories. I
>then tried doing another "make" and "make install." Apparently, it
>compiled correctly?
>
>In the Readme.DOS file I am told the following:
>
>3 - If you are using Turbo C to compile Remind, type:
>
> make -fmakefile.tc
>
> If you are using Microsoft C to compile Remind, type:
>
> make makefile.msc
>
>I considered trying to compile it with the -mno-cygwin option and using
>one of these other makefiles. I'm not much of a C programmer as I'm
>sure you can tell.
>
>BASH.EXE-2.02$ make
>
>*******************
>* *
>* Building REMIND *
>* *
>*******************
>
>make[1]: Nothing to be done for `all'.
>BASH.EXE-2.02$ ls
>ACKNOWLEDGEMENTS config.cache examples tests
>COPYRIGHT config.log install-sh unconfigure
>Makefile config.status man www
>README configure remind.lsm
>WINDOWS configure.in scripts
>build.tk docs src
>BASH.EXE-2.02$ make install
>
>*********************
>* *
>* Installing REMIND *
>* *
>*********************
>
>cd src; make install
>for prog in remind rem2ps ./../scripts/kall ./../scripts/rem
>./../scripts/tkremi
>nd ./../scripts/cm2rem.tcl ; do \
> /CYGNUS/CYGWIN~1/H-I586~1/BIN/install -c $prog /usr/local/bin ;
>\
>done
>/CYGNUS/CYGWIN~1/H-I586~1/BIN/install: remind: No such file or directory
>/CYGNUS/CYGWIN~1/H-I586~1/BIN/install: rem2ps: No such file or directory
>strip /usr/local/bin/remind
>strip: /usr/local/bin/remind: No such file or directory
>make[1]: [install] Error 1 (ignored)
>strip /usr/local/bin/rem2ps
>strip: /usr/local/bin/rem2ps: No such file or directory
>make[1]: [install] Error 1 (ignored)
>for man in ./../man/kall.1 ./../man/rem.1 ./../man/rem2ps.1
>./../man/remind.1 ./
>../man/tkremind.1 ./../man/cm2rem.1 ; do \
> /CYGNUS/CYGWIN~1/H-I586~1/BIN/install -c -m 644 $man
>/usr/local/man/man1
> ; \
>done
>BASH.EXE-2.02$
Looks to me like your big problem is the install program which assumes the
UNIX convention of executables without extensions (.exe). It looks for
remind and not remind.exe, which is what exists. The solution? There are
a few:
1. Check the mail archives for this problem and download an updated
install script that looks for executables with extensions (I forget
exactly who created this install script and where you can get it from
but its in the mail archives SOMEWHERE at least. It may be at one of
the "Ported Software" web sites pointed at from the Cygwin site too).
2. Check out your makefile and see if there's a simple way to add the .exe
suffix to the executable names that its looking for. Many makefiles
have a spot to define a "SUFFIX" variable that will tack on that
character sequence to the end executable names it goes looking to
install. If "SUFFIX" does not exist, altering the makefile directly
to add ".exe" to all the executable programs that its installing is
also an option, albeit a little more typing.
3. If you're building on NT, the last option is to simply remove the
".exe" from the executables built and rerun "make install". The
install will find the executables and install them properly. They
will run fine in bash, but DOS prompts/boxes will not run them, since
they always need the extension to understand that its an executable.
This is not an option for 9x as I understand it, since 9x doesn't
know about executables if there's no extension to indicate it as such.
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
118 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
(508) 560-1285 - cell phone
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~2000-03-25 19:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-24 14:41 Eric Goforth
2000-03-25 13:07 ` Terry Lincoln
2000-03-25 19:44 ` Larry Hall (RFK Partners, Inc) [this message]
2000-03-25 19:50 ` Chris Faylor
2000-03-25 20:11 ` Larry Hall (RFK Partners, Inc)
2000-03-26 9:06 ` Chris Faylor
2000-03-27 7:25 ` Larry Hall (RFK Partners, Inc)
-- strict thread matches above, loose matches on Subject: below --
2020-07-06 12:57 Billie Healy
2020-07-06 16:41 ` ASSI
2020-07-06 16:59 ` Eliot Moss
2008-06-26 9:07 pirracas77
2008-06-26 9:35 ` Dave Korn
2008-06-26 15:37 ` pirracas77
[not found] <f9dce6b30707120418yc2bea1axa699bea2d824e176@mail.gmail.com>
2007-07-12 12:38 ` Larry Hall (Cygwin)
2004-12-06 23:49 no " Kevin Smith
2002-12-13 16:03 No " ganglio
2000-03-27 6:01 Earnie Boyd
2000-03-27 7:56 ` Chris Faylor
2000-03-27 5:56 Earnie Boyd
2000-03-27 7:51 ` Chris Faylor
2000-03-26 16:11 Rick Rankin
2000-03-26 15:02 Rick Rankin
2000-03-26 15:09 ` Chris Faylor
2000-03-25 20:13 Rick Rankin
2000-03-26 9:13 ` Chris Faylor
2000-03-27 14:23 ` Michael Hirmke
2000-01-15 4:50 Slate
2000-01-15 8:00 ` Heinz-Juergen Oertel
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=4.3.2.20000325222901.00d398a0@pop.ma.ultranet.com \
--to=lhall@rfk.com \
--cc=cygwin@hotpop.com \
--cc=ewgoforth@netmcr.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).