From: Earnie Boyd <earnie_boyd@yahoo.com>
To: ian.macey@db.com, cygwin@sourceware.cygnus.com
Subject: Re: B20.1: make doesn't work - not LF problem
Date: Tue, 06 Jun 2000 06:30:00 -0000 [thread overview]
Message-ID: <20000606132948.12931.qmail@web112.yahoomail.com> (raw)
Please visit my page for instructions on updating to version 1.1.
--- ian.macey@db.com wrote:
>
> The build of GNU make v3.77 doesn't work.
>
Make works fine. It's your setup that's wrong.
> Here's a valid makefile (between - - -s):
>
> - - -
> string = abc
>
> echo.exe:
> @echo $(string)
> - - -
>
I just tried this with make version 3.77 and I get `abc' as output.
-8<-
> PS: Here's the cygcheck -s -v -r output:
>
> Cygnus Win95/NT Configuration Diagnostics
> Current System Time: Tue Jun 6 11:42:38 2000
>
> WinNT Ver 4.0 build 1381 Service Pack 3
>
The first item in your path *must always* be the directory containing the
cygwin1.dll and executables.
> Path: .
> /e/work/bin
> ~/bin
> /progra~1/ORANT/bin
> .
> /bin
> /e/work/dev/lib
> /PROGRA~1/cygnus/bin
> /PROGRA~1/cygnus/usr/bin
> /Inprise/vbroker/bin
> /Inprise/vbroker/lib
> /progra~1/perl5/bin
> /WINNT/system32
> /WINNT
> /PROGRA~1/MSOFFICE/Office
> /Progra~1/Mts
> /Progra~1/Mi017e~1/Common/VSS/win32
> /Progra~1/toolkit
> /Progra~1/Window~1/Accessories
> /Progra~1/Mi017e~1/vc98/bin
> /Progra~1/Mi017e~1/common/MSDev98/bin
> /win32app/ADMIN/ntreskit
> /Program Files/Microsoft Visual Studio/Common/Tools/WinNT
> /Program Files/Microsoft Visual Studio/Common/MSDev98/Bin
> /Program Files/Microsoft Visual Studio/Common/Tools
> /Program Files/Microsoft Visual Studio/VC98/bin
> /e/ProgramFiles/java/jdk1.2.2/bin
>
> SysDir: C:\WINNT\System32
> WinDir: C:\WINNT
>
-8<-
>
> HKEY_CURRENT_USER\Software\Cygnus Solutions
> HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin
> HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2
> (default) = `/cygdrive'
> cygdrive flags = 0x00000020
> HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/
> (default) = `C:'
> flags = 0x00000000
> HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/c
> (default) = `c:'
> flags = 0x00000000
> HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/d
> (default) = `d:'
> flags = 0x00000000
> HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/dev/fd0
> (default) = `\\.\a:'
> flags = 0x00000000
> HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/dev/fd1
> (default) = `\\.\b:'
> flags = 0x00000000
> HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/dev/st0
> (default) = `\\.\tape0:'
> flags = 0x00000000
> HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/dev/st1
> (default) = `\\.\tape1:'
> flags = 0x00000000
> HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/e
> (default) = `e:'
> flags = 0x00000000
> HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/r
> (default) = `r:'
> flags = 0x00000000
> HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/w
> (default) = `w:'
> flags = 0x00000000
*******************************
* > HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\c
* > (default) = `c:'
* > flags = 0x00000000
*******************************
This is an invalid mount entry. You can use regedit to delete this record.
You can also try to `umount c' to see if it removes this entry.
> HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options
> HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup
You may use *regedit only* to remove this following set of registry entries.
They are not hurting your current setup but also aren't needed any longer.
************************
> HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0
> HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts
> HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\00
> (default) = `c:'
> unix = `c'
> fbinary = 0x00000000
> fsilent = 0x00000000
> fmixed = 0x00000000
> HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\01
> (default) = `w:'
> unix = `/w'
> fbinary = 0x00000000
> fsilent = 0x00000000
> fmixed = 0x00000000
> HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\02
> (default) = `r:'
> unix = `/r'
> fbinary = 0x00000000
> fsilent = 0x00000000
> fmixed = 0x00000000
> HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\03
> (default) = `e:'
> unix = `/e'
> fbinary = 0x00000000
> fsilent = 0x00000000
> fmixed = 0x00000000
> HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\04
> (default) = `\\.\tape1:'
> unix = `/dev/st1'
> fbinary = 0x00000000
> fsilent = 0x00000001
> fmixed = 0x00000000
> HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\05
> (default) = `\\.\tape0:'
> unix = `/dev/st0'
> fbinary = 0x00000000
> fsilent = 0x00000001
> HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\06
> (default) = `\\.\b:'
> unix = `/dev/fd1'
> fbinary = 0x00000000
> fsilent = 0x00000001
> HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\07
> (default) = `\\.\a:'
> unix = `/dev/fd0'
> fbinary = 0x00000000
> fsilent = 0x00000001
> HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\08
> (default) = `d:'
> unix = `/d'
> fbinary = 0x00000000
> fsilent = 0x00000000
> HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\09
> (default) = `c:'
> unix = `/c'
> fbinary = 0x00000000
> fsilent = 0x00000000
> HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0A
> (default) = `C:'
> unix = `/'
> fbinary = 0x00000000
> fsilent = 0x00000000
>
*******************
> Found: C:\PROGRA~1\cygnus\bin\bash.exe
> Found: C:\PROGRA~1\cygnus\bin\cat.exe
> Not Found: cpp (good!)
> Found: C:\PROGRA~1\cygnus\bin\find.exe
> Not Found: gcc
> Not Found: gdb
> Not Found: ld
> Found: C:\PROGRA~1\cygnus\bin\ls.exe
> Found: C:\PROGRA~1\cygnus\bin\make.exe
> Found: C:\bin\sh.exe
>
I find it interesting that you're trying to use make when you don't have the
gcc compiler set and binutils installed.
> 569k 2000/05/15 C:\PROGRA~1\cygnus\usr\bin\cygwin1.dll - os=4.0 img=1.0
> sys=4.0
> "cygwin1.dll" v0.0 ts=2000/5/15 4:48
> Use -h to see help about each section
>
>
You've mixed b20 with Version 1.1. Albeit the cygwin1.dll is backward
compatible with the binaries that use it, the object libraries that you might
use when building programs are not. If you intend to use Cygwin for
development you need to do a full upgrade.
Regards,
=====
---
Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
__Cygwin: POSIX on Windows__
Cygwin Newbies: < http://www.freeyellow.com/members5/gw32/index.html >
__Minimalist GNU for Windows__
Mingw32 List: < http://www.egroups.com/group/mingw32/ >
Mingw Home: < http://www.mingw.org/ >
__________________________________________________
Do You Yahoo!?
Yahoo! Photos -- now, 100 FREE prints!
http://photos.yahoo.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2000-06-06 6:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-06 6:30 Earnie Boyd [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-06 12:41 Earnie Boyd
2000-06-06 12:25 Earnie Boyd
2000-06-06 12:32 ` Chris Faylor
2000-06-06 14:08 ` Norman Vine
2000-06-06 11:33 Earnie Boyd
2000-06-06 11:40 ` Chris Faylor
2000-06-06 8:17 ian.macey
2000-06-06 4:01 ian.macey
2000-06-06 9:36 ` Chris Faylor
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=20000606132948.12931.qmail@web112.yahoomail.com \
--to=earnie_boyd@yahoo.com \
--cc=cygwin@sourceware.cygnus.com \
--cc=ian.macey@db.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).