public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* configuration scripts.
@ 1997-09-08 16:54 Smith, Eric
  0 siblings, 0 replies; 3+ messages in thread
From: Smith, Eric @ 1997-09-08 16:54 UTC (permalink / raw)
  To: 'gnu-win32@cygnus.com'

To all:

Having just recently started with the GNU family of tools, hopefully
someone can provide me info on this.

I have just installed the entire cdk from Cygnus Solutions.  Following
research (and interpretation of included README to FAQ on WWW), I have
done the following additional steps.

1. Create shortcut of sh.exe in /bin.

2. Added the following to my environment:
   GCC_EXEC_PREFIX  =  C:\gnuwin32\b18\H-i386-cygwin32\lib\gcc-lib\
   PATH =
C:\gnuwin32\b18\H-i386-cygwin32\bin;C:\gnuwin32\b18\tcl\bin;...
   TCL_LIBRARY = C:/gnuwin32/b18/tcl/lib/tcl7.6
   GDBTK_LIBRARY = C:/gnuwin32/b18/share/gdbtcl

3. Created a /tmp directory.

After doing this, I have tried many times to execute configure scripts
for additional gnu tools (like gnat, hello-1.3, etc...).  The following
is the result.

bash$ ./configure: (null)

I have examined the scripts as best I can (I don't usually program shell
scripts), tried numerous parameters based on the file text, and yet I
cannot get the configuration files to generate the correct makefile from
makefile.in.

What do I still have to do to get the configuration scripts to run?

Eric M. Smith
telephone               : (423) 229-2254
profs/officevision     : XGIB003
internet -- business : erics@eastman.com
internet -- personal  : burnsun@tricon.net

Do not meddle in the affairs of wizards, for they are quick to anger.
Do not meddle in the affairs of dragons, for you are crunchy and taste
good with ketchup.

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

^ permalink raw reply	[flat|nested] 3+ messages in thread
* configuration scripts
@ 1997-09-10  1:50 Smith, Eric
  1997-09-15 18:42 ` Mikey
  0 siblings, 1 reply; 3+ messages in thread
From: Smith, Eric @ 1997-09-10  1:50 UTC (permalink / raw)
  To: 'gnu-win32@cygnus.com'

To all,

Thank you for the responses.

I have resigned myself to the long and arduous task of using Borland's
FCONVERT.EXE to convert all of my configuration scripts from ANSI to OEM
format (strip out <CR>).  For the number of files I have, this appears
to be a long task.

This closes out one problem, but makes me wonder, why do the GNU scripts
from the .tar.gz files at the main ftp site have <CR><LF> in them
instead of just <LF>.  They are identified as UNIX scripts, but appear
to have a PC flavor to them.  Since I haven't edited them ("cat
{filename} | more" instead) I can't figure out where the <CR> came from
unless it is there to start.

Eric M. Smith
telephone               : (423) 229-2254
profs/officevision     : XGIB003
internet -- business : erics@eastman.com
internet -- personal  : burnsun@tricon.net

Do not meddle in the affairs of wizards, for they are quick to anger.
Do not meddle in the affairs of dragons, for you are crunchy and taste
good with ketchup.

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~1997-09-15 18:42 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1997-09-08 16:54 configuration scripts Smith, Eric
1997-09-10  1:50 Smith, Eric
1997-09-15 18:42 ` Mikey

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).