Re: error trying to compile anything
Hi there, Uao!!! you are quick. Thank you for respoding. I have attached the output file if someone can have look at it. Thanx again BiLo -- Original Message -- [EMAIL PROTECTED] wrote: Hello there, I tried to search in the archive for this but no result. I am sure that it is a configuration problem but I don't know were to start. The problem: As soon I start the ./configure I get the error: cpp0.ece - Entry point not found. on the top of the error bar, in the windows I get: The procedure entry point getrlimit could not be located in the dynamic link library cygwin1.dll. This means that you have an older cygwin1.dll somewhere in your path. use cygcheck -r -s -v and send the output to the list or examine it by yourself. The program is looking for the gcc in the /usr/local/lib and it generate the eror in the shell: configure: error: installation or configuration problem: C compiler cannot create executables.. this is quite strange - what is the value of your CC environment variable ? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Re: error trying to compile anything
[EMAIL PROTECTED] wrote: Hi there, Uao!!! you are quick. Thank you for respoding. I have attached the output file if someone can have look at it. Well, I don't see the attachment :) Thanx again BiLo -- Original Message -- [EMAIL PROTECTED] wrote: Hello there, I tried to search in the archive for this but no result. I am sure that it is a configuration problem but I don't know were to start. The problem: As soon I start the ./configure I get the error: cpp0.ece - Entry point not found. on the top of the error bar, in the windows I get: The procedure entry point getrlimit could not be located in the dynamic link library cygwin1.dll. This means that you have an older cygwin1.dll somewhere in your path. use cygcheck -r -s -v and send the output to the list or examine it by yourself. The program is looking for the gcc in the /usr/local/lib and it generate the eror in the shell: configure: error: installation or configuration problem: C compiler cannot create executables.. this is quite strange - what is the value of your CC environment variable ? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: error trying to compile anything
Ops..the output file.. I have enclosed the file now Thanx again BiLo -- Original Message -- [EMAIL PROTECTED] wrote: Hello there, I tried to search in the archive for this but no result. I am sure that it is a configuration problem but I don't know were to start. The problem: As soon I start the ./configure I get the error: cpp0.ece - Entry point not found. on the top of the error bar, in the windows I get: The procedure entry point getrlimit could not be located in the dynamic link library cygwin1.dll. This means that you have an older cygwin1.dll somewhere in your path. use cygcheck -r -s -v and send the output to the list or examine it by yourself. The program is looking for the gcc in the /usr/local/lib and it generate the eror in the shell: configure: error: installation or configuration problem: C compiler cannot create executables.. this is quite strange - what is the value of your CC environment variable ? Cygnus Win95/NT Configuration Diagnostics Current System Time: Wed Jan 16 15:15:48 2002 Windows 2000 Professional Ver 5.0 build 2195 Path: D:\CYG\usr\local\bin D:\CYG\bin D:\CYG\bin c:\WINNT\system32 c:\WINNT c:\WINNT\System32\Wbem D:\CYG\home\pino\bin SysDir: C:\WINNT\System32 WinDir: C:\WINNT HOME = `D:\CYG\home\pino' MAKE_MODE = `unix' PWD = `/home/nmap-2.54BETA30' USER = `pino' ALLUSERSPROFILE = `C:\Documents and Settings\All Users' APPDATA = `C:\Documents and Settings\pino\Application Data' BASH_ENV = `/home/pino/.bashrc' COMMONPROGRAMFILES = `C:\Program Files\Common Files' COMPUTERNAME = `2KBOX' COMSPEC = `C:\WINNT\system32\cmd.exe' HOMEDRIVE = `C:' HOMEPATH = `\' HOSTNAME = `2KBOX' HOSTTYPE = `i686' LOGONSERVER = `\\2KBOX' LS_COLORS = `' LS_OPTIONS = `-s -F -T 0 --color=yes' MACHTYPE = `i686-pc-cygwin' NUMBER_OF_PROCESSORS = `1' OLDPWD = `/home/nmap-2.54BETA30/mswin32' OS2LIBPATH = `C:\WINNT\system32\os2\dll;' OS = `Windows_NT' OSTYPE = `cygwin' PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH' PROCESSOR_ARCHITECTURE = `x86' PROCESSOR_IDENTIFIER = `x86 Family 6 Model 8 Stepping 3, GenuineIntel' PROCESSOR_LEVEL = `6' PROCESSOR_REVISION = `0803' PROGRAMFILES = `C:\Program Files' PROMPT = `$P$G' PS1 = `\[\033]0;\w\007 \033[32m\]\u@\h \[\033[33m\w\033[0m\] $ ' SHELL = `/bin/bash' SHLVL = `1' SYSTEMDRIVE = `C:' SYSTEMROOT = `C:\WINNT' TEMP = `c:\DOCUME~1\pino\LOCALS~1\Temp' TERM = `cygwin' TMP = `c:\DOCUME~1\pino\LOCALS~1\Temp' USERDOMAIN = `2KBOX' USERPROFILE = `C:\Documents and Settings\pino' WINDIR = `C:\WINNT' _ = `/usr/bin/cygcheck' 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 = 0x0022 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/ (default) = `D:\CYG' flags = 0x0002 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/usr/bin (default) = `D:/CYG/bin' flags = 0x0002 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/usr/lib (default) = `D:/CYG/lib' flags = 0x0002 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup 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 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\01 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\02 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\03 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\04 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\05 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\06 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\07 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\08 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\09 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0A HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0B HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0C HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0D HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0E HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0F HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\10 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\11 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\12
Re: Re: error trying to compile anything
[EMAIL PROTECTED] wrote: Ops..the output file.. I have enclosed the file now Thanx again BiLo -- Original Message -- [EMAIL PROTECTED] wrote: Hello there, I tried to search in the archive for this but no result. I am sure that it is a configuration problem but I don't know were to start. The problem: As soon I start the ./configure I get the error: cpp0.ece - Entry point not found. on the top of the error bar, in the windows I get: The procedure entry point getrlimit could not be located in the dynamic link library cygwin1.dll. This means that you have an older cygwin1.dll somewhere in your path. use cygcheck -r -s -v and send the output to the list or examine it by yourself. The program is looking for the gcc in the /usr/local/lib and it generate the eror in the shell: configure: error: installation or configuration problem: C compiler cannot create executables.. this is quite strange - what is the value of your CC environment variable ? Cygnus Win95/NT Configuration Diagnostics Current System Time: Wed Jan 16 15:15:48 2002 Windows 2000 Professional Ver 5.0 build 2195 Path: D:\CYG\usr\local\bin D:\CYG\bin D:\CYG\bin c:\WINNT\system32 c:\WINNT c:\WINNT\System32\Wbem D:\CYG\home\pino\bin Better move the first path entry D:\CYG\usr\local\bin after the D:\CYG\bin entries. The lines below that you, or someone else or something else has installed some cygwin linked executables. The real problem is they put it in the wrong place. Never use C:\WINNT\ to store the cygwin1.dll. Found: C:\WINNT\cat.exe -- REMOVE THIS ONE! Found: D:\CYG\bin\cat.exe Warning: C:\WINNT\cat.exe hides D:\CYG\bin\cat.exe Found: C:\WINNT\ls.exe -- REMOVE THIS ONE! Found: D:\CYG\bin\ls.exe Warning: C:\WINNT\ls.exe hides D:\CYG\bin\ls.exe REMOVE THIS! It highly not recommended to store cygwin1.dll in this location, not to mention that there are two different copies of cygwin1.dll on you system. Up to and including the latest release 1.3.6-6 two copies of cygwin1.dll could hardly coexist without trouble. 792k 2000/02/15 C:\WINNT\cygwin1.dll - os=4.0 img=1.0 sys=4.0 cygwin1.dll v0.0 ts=1999/8/3 13:02 Cygwin DLL version info: DLL version: 2.1.0 DLL epoch: 19 DLL bad signal mask: 19005 DLL old termios: 5 API major: 0 API minor: 14 Shared data: 2 DLL identifier: cygwin Mount registry: 2 Cygnus registry name: Cygnus Solutions Cygwin registry name: Cygwin Program options name: Program Options Cygwin mount registry name: mounts v2 Build date: Tue Aug 3 16:02:08 1999 Snapshot date: 1999-08-01-23:55-EST Shared id: cygwinS2 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Re: error trying to compile anything
Yes...It works.. Thank you m8 I was using the ls in the winnt because when I am in the win prompt then I always get confused with dir and ls. But now it works Thank you Pavel. BiLo -- Original Message -- [EMAIL PROTECTED] wrote: Ops..the output file.. I have enclosed the file now Thanx again BiLo -- Original Message -- [EMAIL PROTECTED] wrote: Hello there, I tried to search in the archive for this but no result. I am sure that it is a configuration problem but I don't know were to start. The problem: As soon I start the ./configure I get the error: cpp0.ece - Entry point not found. on the top of the error bar, in the windows I get: The procedure entry point getrlimit could not be located in the dynamic link library cygwin1.dll. This means that you have an older cygwin1.dll somewhere in your path. use cygcheck -r -s -v and send the output to the list or examine it by yourself. The program is looking for the gcc in the /usr/local/lib and it generate the eror in the shell: configure: error: installation or configuration problem: C compiler cannot create executables.. this is quite strange - what is the value of your CC environment variable ? Cygnus Win95/NT Configuration Diagnostics Current System Time: Wed Jan 16 15:15:48 2002 Windows 2000 Professional Ver 5.0 build 2195 Path:D:\CYG\usr\local\bin D:\CYG\bin D:\CYG\bin c:\WINNT\system32 c:\WINNT c:\WINNT\System32\Wbem D:\CYG\home\pino\bin Better move the first path entry D:\CYG\usr\local\bin after the D:\CYG\bin entries. The lines below that you, or someone else or something else has installed some cygwin linked executables. The real problem is they put it in the wrong place. Never use C:\WINNT\ to store the cygwin1.dll. Found: C:\WINNT\cat.exe -- REMOVE THIS ONE! Found: D:\CYG\bin\cat.exe Warning: C:\WINNT\cat.exe hides D:\CYG\bin\cat.exe Found: C:\WINNT\ls.exe -- REMOVE THIS ONE! Found: D:\CYG\bin\ls.exe Warning: C:\WINNT\ls.exe hides D:\CYG\bin\ls.exe REMOVE THIS! It highly not recommended to store cygwin1.dll in this location, not to mention that there are two different copies of cygwin1.dll on you system. Up to and including the latest release 1.3.6-6 two copies of cygwin1.dll could hardly coexist without trouble. 792k 2000/02/15 C:\WINNT\cygwin1.dll - os=4.0 img=1.0 sys=4.0 cygwin1.dll v0.0 ts=1999/8/3 13:02 Cygwin DLL version info: DLL version: 2.1.0 DLL epoch: 19 DLL bad signal mask: 19005 DLL old termios: 5 API major: 0 API minor: 14 Shared data: 2 DLL identifier: cygwin Mount registry: 2 Cygnus registry name: Cygnus Solutions Cygwin registry name: Cygwin Program options name: Program Options Cygwin mount registry name: mounts v2 Build date: Tue Aug 3 16:02:08 1999 Snapshot date: 1999-08-01-23:55-EST Shared id: cygwinS2 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Re: Re: error trying to compile anything
[EMAIL PROTECTED] wrote: Yes...It works.. Thank you m8 np :) I was using the ls in the winnt because when I am in the win prompt then I always get confused with dir and ls. You can use all the cygwin utilities from the command prompt just by adding the cygwin bin directory in your PATH. You can do this by editing autoexec.bat if you are on Win9x or by setting it from Control Panel - System - Advanced tab on WinNT,2k and XP. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: error trying to compile anything
[EMAIL PROTECTED] schrieb: The lines below that you, or someone else or something else has installed some cygwin linked executables. The real problem is they put it in the wrong place. Never use C:\WINNT\ to store the cygwin1.dll. Warning: C:\WINNT\ls.exe hides D:\CYG\bin\ls.exe REMOVE THIS! It highly not recommended to store cygwin1.dll in this location, not to mention that there are two different copies of cygwin1.dll on you system. Up to and including the latest release 1.3.6-6 two copies of cygwin1.dll could hardly coexist without trouble. what about real versioning of the cygwin.dll finally? perl did the half-baked thing (perl56.dll), though I heavily voted for the real thing that times. cygwin also (cygwin1.dll). why not cygwin-$(version).dll = cygwin-1.1.6.dll this is not FAT16 anymore. we have w95/98/ME and NT systems only. all support long filenames. duplicate dll's will be gone. microsoft dll hell will be past tense. -- Reini Urban http://atelier.akbild.ac.at/ (soon) http://xarch.tu-graz.ac.at/home/rurban/ (big) http://tv.mur.at/ (kulturelles) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: error trying to compile anything
At 06:24 PM 1/16/2002, Reini Urban wrote: [EMAIL PROTECTED] schrieb: The lines below that you, or someone else or something else has installed some cygwin linked executables. The real problem is they put it in the wrong place. Never use C:\WINNT\ to store the cygwin1.dll. Warning: C:\WINNT\ls.exe hides D:\CYG\bin\ls.exe REMOVE THIS! It highly not recommended to store cygwin1.dll in this location, not to mention that there are two different copies of cygwin1.dll on you system. Up to and including the latest release 1.3.6-6 two copies of cygwin1.dll could hardly coexist without trouble. what about real versioning of the cygwin.dll finally? perl did the half-baked thing (perl56.dll), though I heavily voted for the real thing that times. cygwin also (cygwin1.dll). why not cygwin-$(version).dll = cygwin-1.1.6.dll this is not FAT16 anymore. we have w95/98/ME and NT systems only. all support long filenames. duplicate dll's will be gone. microsoft dll hell will be past tense. The issue is not as simple as just DLL names. Of course, if you want to show us all your dandy solution, provide a patch and it will be thoughtfully reviewed. Larry Hall [EMAIL PROTECTED] RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: error trying to compile anything
Reini: what about real versioning of the cygwin.dll finally? perl did the half-baked thing (perl56.dll), though I heavily voted for the real thing that times. cygwin also (cygwin1.dll). why not cygwin-$(version).dll = cygwin-1.1.6.dll this is not FAT16 anymore. we have w95/98/ME and NT systems only. all support long filenames. duplicate dll's will be gone. microsoft dll hell will be past tense. Larry Hall (RFK Partners, Inc) schrieb: The issue is not as simple as just DLL names. Of course, if you want to show us all your dandy solution, provide a patch and it will be thoughtfully reviewed. is this list about politics (software design) or patches (software implementation) only? of course dll names are just part of the game. but an important one, which bit microsoft heavily AFAIK. cygwin does support softlinks, so we should use them. the implementation is trivial, but there should be consense. -- Reini Urban http://atelier.akbild.ac.at/ (soon) http://xarch.tu-graz.ac.at/home/rurban/ (big) http://tv.mur.at/ (kulturelles) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: error trying to compile anything
Okay people: 0) short filenames is NOT the reason for cygwin1.dll. It is called that because it is the 1st stable backward compatible DLL. Everything compiled against any version of cygwin1.dll in the past will work with any newer version without relinking (but not vice versa). For instance: a) build foo.exe while cygwin1.dll(1.3.1) is on your system foo.exe will work with cygwin1.dll(1.3.2, 1.3.3, 1.3.4, 1.4.0, etc) WITHOUT recompiling. b) However, if you build foo.exe while cygwin1.dll(1.3.1) is on your system, you should NOT expect that it will work if you revert your cygwin1.dll to an EARLIER version, such as 1.3.0, 1.1.8, etc. When a) is no longer true, then we will bump the DLL name to cygwin2.dll. 1) cygwin supports symlinks -- but microsoft does not. And it is the Microsoft Windows Runtime Loader that must search out and load the DLLs into memory. Therefore, you cannot have cygwin-1.1.3.dll - cygwin-1.1.6.dll and expect programs that want cygwin-1.1.3.dll to work. Therefore you must have actual copies of every cygwin-x.y.z dll on your system that is needed by some executable. Symlinks not allowed. 2) If you have multiple cygwin dlls on a system, then they must all use different named shared memory areas (otherwise bad things will happen). This means that foo.exe (depends on cygwin-1.1.3.dll) and bar.exe (depends on cygwin-1.1.4.dll) can't communicate very well. 3) With strongly versioned DLLs, you can't fix bugs. If cygwin-1.1.4.dll has a bug, then everything compiled against it will have that bug. When cygwin-1.1.5.dll comes out, you'll have to recompile all of those applications to take advantage of the bug fix. Unix gets around this by having a MAJOR_VERSION (libfoo.so.X) and all the strongly versioned development links are just pointers to that (libfoo.so.X.Y.Z - libfoo.so.X). On windows, we can't really do that (see point #1 above). So, you might as well be linking everything statically -- because you lose the ability to slipstream bugfixes. See the DLL naming thread in the cygwin-apps mailing list archive from 1.5years ago for more information. Reini, you don't know as much about real versioning as you think. Check the libtool mailing list and documentation for info on version strings, (c - a) numbering, and backward compatibility. --Chuck Reini Urban wrote: Reini: what about real versioning of the cygwin.dll finally? perl did the half-baked thing (perl56.dll), though I heavily voted for the real thing that times. cygwin also (cygwin1.dll). why not cygwin-$(version).dll = cygwin-1.1.6.dll this is not FAT16 anymore. we have w95/98/ME and NT systems only. all support long filenames. duplicate dll's will be gone. microsoft dll hell will be past tense. Larry Hall (RFK Partners, Inc) schrieb: The issue is not as simple as just DLL names. Of course, if you want to show us all your dandy solution, provide a patch and it will be thoughtfully reviewed. is this list about politics (software design) or patches (software implementation) only? of course dll names are just part of the game. but an important one, which bit microsoft heavily AFAIK. cygwin does support softlinks, so we should use them. the implementation is trivial, but there should be consense. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: error trying to compile anything
Robert Collins schrieb: From: Reini Urban [EMAIL PROTECTED] cygwin does support softlinks, so we should use them. sorry about the confusion. I mixed copies (aka cygwin file hardlinks) with softlinks. to stay zynical I meant those links which you create by $ ln /bin/cygwin-1.1.1.6.dll /bin/cygwin1.dll and not those by $ ln -s /bin/cygwin-1.1.1.6.dll /bin/cygwin1.dll which is of course not trivial :) There can be only one, multiple strong version hardly linked into apps is wrong and I'll keep my mouth shut. But .dll's are loaded by the win32 (on 95) and the Native API (NT). Cygwin symlinks are _not_ supported by those OS's, so symlinking is not an option. the implementation is trivial, but there should be consense. Implementation is non trivial (IMO). Here are some potential implementations: 1) For win95, produce a kernel VXD that patches the CreateProcess call to interpret symlinks. 2) For winNT, create a kernel thunk to do the same. 3) Create an NT service/device driver that creates an NT Reparse point, and returns the correct cygwin1.dll canonical location. hardlinks aren't good enough, they can't go across file systems. 4) Create replacement assembly stub for gcc to use when linking against cygwin1.dll that will interpret symlinks and then at runtime fix up the symbols that should have resolved to cygwin1.dll, to resolve against a dynamically opened cygwin1.dll. Note that this will have to execute before any .dll startup code. Now, if you still think it's trivial, I'll be happy to review your (trivial) patch to implement that. -- Reini Urban http://atelier.akbild.ac.at/ (soon) http://xarch.tu-graz.ac.at/home/rurban/ (big) http://tv.mur.at/ (kulturelles) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: error trying to compile anything
- Original Message - From: Reini Urban [EMAIL PROTECTED] Sent: Thursday, January 17, 2002 1:00 PM Subject: Re: error trying to compile anything Robert Collins schrieb: From: Reini Urban [EMAIL PROTECTED] cygwin does support softlinks, so we should use them. sorry about the confusion. I mixed copies (aka cygwin file hardlinks) with softlinks. to stay zynical I meant those links which you create by $ ln /bin/cygwin-1.1.1.6.dll /bin/cygwin1.dll Which (on NTFS) are _real_ hardlinks. They are _not_ copies. and not those by $ ln -s /bin/cygwin-1.1.1.6.dll /bin/cygwin1.dll which is of course not trivial :) There can be only one, multiple strong version hardly linked into apps is wrong and I'll keep my mouth shut. I don't know what you mean here. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
