Dann Corbit wrote:
> The response from the Mingw team:
> >Comment By: Earnie Boyd (earnie)
>
> Date: 2004-04-08 07:33
>
> Message:
> Logged In: YES
> user_id=15438
>
> Symbolic links to files and directories do not work on Win32
> in general. Support for symlink operation is limited to the source
Tom Lane said:
> "Dann Corbit" <[EMAIL PROTECTED]> writes:
>> The response from the Mingw team:
>
>>> Symbolic links to files and directories do not work on Win32
>>> in general. Support for symlink operation is limited to the source
>>> directory or file existing and being able to copy the source
"Dann Corbit" <[EMAIL PROTECTED]> writes:
> The response from the Mingw team:
>> Symbolic links to files and directories do not work on Win32
>> in general. Support for symlink operation is limited to the source
>> directory or file existing and being able to copy the source to the
>> destination
> -Original Message-
> From: Dann Corbit
> Sent: Wednesday, April 07, 2004 10:34 AM
> To: Tom Lane
> Cc: [EMAIL PROTECTED]
> Subject: Re: [HACKERS] Small suggestion on build script
>
>
> > -Original Message-
> > From: Tom Lane [mailto:[EMAIL
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 06, 2004 10:55 PM
> To: Dann Corbit
> Cc: [EMAIL PROTECTED]
> Subject: Re: [HACKERS] Small suggestion on build script
>
>
> "Dann Corbit" <[EMAIL PROTECT
> whilst I have, on rare occasions, observed the symlink
> failure under MingW, I've never come across the other issues
> you've mentioned (I build from cvs, instead of snapshots, but
> I can't imagine that causes these problems).
I'm running off snapshots (my bison install is badly broken),
Dann Corbit wrote:
> I would like to suggest changing the symlinks to copy commands:
> The reason is that under Mingw, I get random failures with the
> symlinks (typically all will work but one or two, but there is no
> telling which will succeed and which will fail).
configure will automatically
"Dann Corbit" <[EMAIL PROTECTED]> writes:
> I would like to suggest changing the symlinks to copy commands:
That would cause make to fail to handle update dependencies on the
linked files.
> The reason is that under Mingw, I get random failures with the symlinks
This is the worst sort of Microso
Hi Dann,
> > Which version
> > are you using?
>
> Msys version is 1.0.
Ok, probably the same I'm using (MSYS-1.0.10 and MSYS-1.0.9)
> [EMAIL PROTECTED] /u/postgresql-snapshot
> $ gcc --version
> gcc.exe (GCC) 3.3.3 (mingw special)
I'm using MinGW-3.1.0-1, which has:
gcc.exe (GCC) 3.2.3 (mi
> -Original Message-
> From: Dann Corbit
> Sent: Tuesday, April 06, 2004 5:47 PM
> To: Claudio Natoli; [EMAIL PROTECTED]
> Subject: Re: [HACKERS] Small suggestion on build script
>
>
> > -Original Message-
> > From: Claudio Natoli [mailto:[E
> -Original Message-
> From: Claudio Natoli [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 06, 2004 5:42 PM
> To: Dann Corbit; '[EMAIL PROTECTED] '
> Subject: RE: [HACKERS] Small suggestion on build script
>
>
>
> Hi Dann,
>
> whilst I ha
? Which version are you using?
Is it possible the wrong libs/include files are being referenced? Are you
sure parts of cygwin are not in your path? ...
Cheers,
Claudio
-Original Message-
From: Dann Corbit
To: [EMAIL PROTECTED]
Sent: 4/7/04 7:14 AM
Subject: [HACKERS] Small suggestion on
On Tue, 6 Apr 2004, Dann Corbit wrote:
> I would like to suggest changing the symlinks to copy commands:
>
> cp ./src/backend/port/tas/dummy.s ./src/backend/port/tas.s
> cp ./src/backend/port/dynloader/win32.c ./src/backend/port/dynloader.c
> cp ./src/backend/port/sysv_sema.c ./src/backend/port/pg
I would like to suggest changing the symlinks to copy commands:
cp ./src/backend/port/tas/dummy.s ./src/backend/port/tas.s
cp ./src/backend/port/dynloader/win32.c ./src/backend/port/dynloader.c
cp ./src/backend/port/sysv_sema.c ./src/backend/port/pg_sema.c
cp ./src/backend/port/sysv_shmem.c ./src/
14 matches
Mail list logo