At 07:15 PM 1/16/2002, 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.d
- 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]>
> > > cy
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.dl
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 inst
- Original Message -
From: "Reini Urban" <[EMAIL PROTECTED]>
> cygwin does support softlinks, so we should use them.
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
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
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.
>
>
[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
>
[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 i
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
[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 confi
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.
>>
>> T
[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] wrot
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 th
[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."
> o
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:
16 matches
Mail list logo