Christopher Faylor wrote:
> On Mon, Jun 02, 2008 at 06:40:27PM -0600, Eric Blake wrote:
> >According to Brian Keener on 6/2/2008 6:16 PM:
> >>Remembering I meant to check the FAQ for any extra instructions on
> >>building a debug Cygwin I checked there but still didn't find any clue.
> >
> >I think
On Mon, Jun 02, 2008 at 06:40:27PM -0600, Eric Blake wrote:
>According to Brian Keener on 6/2/2008 6:16 PM:
>>Remembering I meant to check the FAQ for any extra instructions on
>>building a debug Cygwin I checked there but still didn't find any clue.
>
>I think the difference is in the recent upgra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Brian Keener on 6/2/2008 6:16 PM:
| Remembering I meant to check the FAQ for any extra instructions on
| building a debug Cygwin I checked there but still didn't find any clue.
I think the difference is in the recent upgrade of binutils,
Remembering I meant to check the FAQ for any extra instructions on
building a debug Cygwin I checked there but still didn't find any clue.
I did though trying a few more options in google find this message from
Corinna in the archive from Feb
(http://cygwin.com/ml/cygwin/2008-02/msg00340.html)
On Sat, May 31, 2008 at 8:00 PM, Nathan Thern <[EMAIL PROTECTED]> wrote:
> Hi all-
> I just built chicken-3.2.0 on cygwin. The build went just fine, but the
> install put the runtime dlls (cygchicken-0.dll and cyguchicken-0.dll) in
> /usr/lib rather than /usr/bin. The installation did not work unti
Nathan Thern wrote:
> I've been using gcc extensively to compile scheme interpreters and to
> compile code generated by various scheme-to-C systems. Here's a simple
> check, though:
> ---
> $ echo -e '#include \nmain(){printf("Hello World\\n");}' >
> hw.c; cat hw.c; /usr/bin/gcc hw.c; ./a.exe
> #i
Dave Korn wrote:
> Only unsigned char *, isn't it?
Any kind of char *. The standard says simply "a character type" (6.5
#7), and it also says that any signed or unsigned variant of the
effective type may also alias that type.
> Looking at the mask value, it has ten bits set. Hence 1024 pos
Brian Dessent wrote on 02 June 2008 19:43:
> Dave Korn wrote:
>
>> Regardless of how well (or poorly) the
>> hash function distributes DLLS into the various buckets, there are only
>> 1024 of them, and we have many DLLs, many of which will occupy multiple
>> buckets; collisions are inevitable.
>
Brian Dessent wrote on 02 June 2008 19:49:
> again because the above violates the C aliasing rules. Making relocp a
> char * should be the right solution because char * can alias everything,
Only unsigned char *, isn't it?
cheers,
DaveK
--
Can't think of a witty .sigline today
I'm setting up cron for cygwin on 7 servers. I've done 2 servers with few
problems, however, on the 3rd on I'm running into a problem in which cron
processes do not run. I've done a bit of research and I've found the problem
to be the following in the cronbug.txt file:
/usr/sbin/cron: PID 450
Nathan Thern wrote:
> The C compiler "/usr/bin/gcc.exe" is not able to compile a simple test
> program.
Can you in fact compile a "hello world" program with gcc?
> Is this a problem with my environment, or something else?
This would be a lot easier to answer if you provided the requested
"c
The first time I tried to use cmake to configure a package I got this message:
--- TERMINAL SESSION ---
$ cmake .
-- The C compiler identification is GNU
-- Check for working C compiler: /usr/bin/gcc.exe
-- Check for working C compiler: /usr/bin/gcc.exe -- broken
CMake Error at
/usr/share/cmake-
Reini Urban wrote:
> Got it:
> - for (; (char *)&relocp->SizeOfBlock < (char *)relocs + size &&
> relocp->SizeOfBlock != 0; ((char *)relocp) += relocp->SizeOfBlock)
> + for (; (char *)&relocp->SizeOfBlock < *(char**)relocs + size &&
> relocp->SizeOfBlock != 0; (*(char**)relocp) += relocp->SizeOf
Dave Korn wrote:
> Regardless of how well (or poorly) the
> hash function distributes DLLS into the various buckets, there are only 1024
> of them, and we have many DLLs, many of which will occupy multiple buckets;
> collisions are inevitable.
First of all, I don't see where this 1024 comes from.
Reini Urban schrieb:
Brian Dessent schrieb:
Reini Urban wrote:
I thought I'll improve the rebase logic by adding some fixed base
addresses and space to certain apps
(bash, perl, python, rest) to be able to properly rebase the culprit
packages in advance.
I wanted to start with
/usr/bin/bash.
Brian Dessent wrote on 02 June 2008 18:33:
> Dave Korn wrote:
>
>> There are only 1024 possible image bases to choose from, and any DLL >=
>> 256kB in size will span several of them. Collisions are an
>> inevitability, no? I think we'll probably still have a need for rebase
>> until the whol
Dave Korn wrote:
> There are only 1024 possible image bases to choose from, and any DLL >=
> 256kB in size will span several of them. Collisions are an inevitability,
> no? I think we'll probably still have a need for rebase until the whole
> world goes 64bit and we've got room for a few more
Reini Urban wrote:
> I know.
Well then why didn't you say that so that I wouldn't have to waste my
time explaining.
> I wanted to hear some magic g++ --allow-non-ansi switch (-std=c89 or
> such for C++) or some INT2PTR macro.
The C++ parser was completely rewritten in gcc 3.4. This is one of t
Brian Dessent wrote on 02 June 2008 16:29:
> Is this really a good direction to move in? The long term plan, as I
> understood it, was to simply build everything with
> --enable-auto-image-base and avoid forever the problem of having to
> manually rebase ever.
--enable-auto-image-base isn't
On Mon, Jun 02, 2008 at 07:03:18PM +0200, Reini Urban wrote:
> Brian Dessent schrieb:
>> Reini Urban wrote:
>>> I thought I'll improve the rebase logic by adding some fixed base
>>> addresses and space to certain apps
>>> (bash, perl, python, rest) to be able to properly rebase the culprit
>>> pack
postgresql 8.1.4-2 is promoted from test to current and
8.2.5-1 is added to test via the cygwin setup.exe
mirror network.
What's new:
http://www.postgresql.org/docs/8.1/static/release-8-1-4.html
http://www.postgresql.org/docs/8.2/static/release-8-2-5.html
Before you upgrade a postgresql pack
The cygwin perl packages perl and perl_manpages have
been updated in the experimental branch to 5.10.0-4.
Click on [Exp]
This looks like to be the final 5.10.0 revision, just the rebaseall
problem is outstanding, and the cygwin-1.7 utf-8 pathname support.
Important Changes since the last per
Brian Dessent schrieb:
Reini Urban wrote:
I thought I'll improve the rebase logic by adding some fixed base
addresses and space to certain apps
(bash, perl, python, rest) to be able to properly rebase the culprit
packages in advance.
I wanted to start with
/usr/bin/bash.exe
/usr/bin/cygintl
Hello all,
I'm sure I'm probably missing some option but I was trying to do a
fresh compile for a debug version of the cygwin1.dll and got the error
mentioned in the subject. I tried do just a straight build and also
looked at the changes for dllfixdbg which appears to be where the
gnu_debugl
Reini Urban wrote:
> I thought I'll improve the rebase logic by adding some fixed base
> addresses and space to certain apps
> (bash, perl, python, rest) to be able to properly rebase the culprit
> packages in advance.
>
> I wanted to start with
> /usr/bin/bash.exe
> /usr/bin/cygintl-8.dll
>
I thought I'll improve the rebase logic by adding some fixed base
addresses and space to certain apps
(bash, perl, python, rest) to be able to properly rebase the culprit
packages in advance.
I wanted to start with
/usr/bin/bash.exe
/usr/bin/cygintl-8.dll
/usr/bin/cygiconv-2.dll
/usr/bin/c
On Mon, Jun 02, 2008 at 05:30:16PM +0530, Mani kandan wrote:
>We are migrating unix application to windows. We have converted the
>Unix samp.sh file to samp.bat for windows. While converting samp.sh
>file we have used some unix command in samp.bat file.We have installed
>SFU to support those unix
Hi,
We are migrating unix application to windows. We have converted
the Unix samp.sh file to samp.bat for windows.
While converting samp.sh file we have used some unix command in
samp.bat file.We have installed SFU to support
those unix command. We are using some cygwin exe also.We have
i
Experimental versions of the cygwin clamav packages (The Clam
AntiVirus - GPL anti-virus toolkit)
has been updated to 0.93.1rc1-1.
There is also a new seperate package clamav-db for the two big database files.
0.93.1rc1 is a maintenance release with bug fixes for issues raised
with 0.93 for exampl
29 matches
Mail list logo
