On Fri, 28 Feb 2003, Christopher Faylor wrote:
> On Fri, Feb 28, [EMAIL PROTECTED]:32:08PM -0500, Igor Pechtchanski wrote:
> >On Fri, 28 Feb 2003, Christopher Faylor wrote:
> >
> >> I wonder if regtool will just compile OOB with -mno-cygwin. Apologies
> >> if that was suggested, too.
> >
> >Nope,
On Fri, Feb 28, 2003 at 12:32:08PM -0500, Igor Pechtchanski wrote:
>On Fri, 28 Feb 2003, Christopher Faylor wrote:
>
>> I wonder if regtool will just compile OOB with -mno-cygwin. Apologies
>> if that was suggested, too.
>
>Nope, it needs getopt...
So does cygcheck. cygcheck isn't a cygwin progr
On Fri, 28 Feb 2003, Christopher Faylor wrote:
> I wonder if regtool will just compile OOB with -mno-cygwin. Apologies
> if that was suggested, too.
Nope, it needs getopt...
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_[EMA
On Fri, Feb 28, 2003 at 09:15:27AM -0800, Randall R Schulz wrote:
>At 09:05 2003-02-28, Christopher Faylor wrote:
>>On Fri, Feb 28, 2003 at 07:49:24AM -0800, Randall R Schulz wrote:
>>>At 06:47 2003-02-28, Fabrice Marchal wrote:
Max Bowsher wrote:
>No. It's a virtual directory. It's also
At 09:05 2003-02-28, Christopher Faylor wrote:
On Fri, Feb 28, 2003 at 07:49:24AM -0800, Randall R Schulz wrote:
>At 06:47 2003-02-28, Fabrice Marchal wrote:
>>Max Bowsher wrote:
>>>No. It's a virtual directory. It's also read only. Use regtool.
>>
>>Is there any other way around without install
On Fri, Feb 28, 2003 at 07:49:24AM -0800, Randall R Schulz wrote:
>At 06:47 2003-02-28, Fabrice Marchal wrote:
>>Max Bowsher wrote:
>>>No. It's a virtual directory. It's also read only. Use regtool.
>>
>>Is there any other way around without installing cygwin (I mean just
>>having cygwin1.dll of
At 06:47 2003-02-28, Fabrice Marchal wrote:
Max Bowsher wrote:
No. It's a virtual directory. It's also read only. Use regtool.
Max.
Is there any other way around without installing cygwin (I mean just having
cygwin1.dll of course) and without using regedit to do the job?
fabrice
Fabrice,
Write
Max Bowsher wrote:
Fabrice Marchal wrote:
Larry Hall (RFK Partners, Inc.) wrote:
Fabrice Marchal wrote:
Randall R Schulz wrote:
Fabrice,
It would seem that the answer is right there on the page you
referenced. You can script a change to that registry entry via the
Cygwi
Fabrice Marchal wrote:
> Larry Hall (RFK Partners, Inc.) wrote:
>
>> Fabrice Marchal wrote:
>>
>>> Randall R Schulz wrote:
>>>
Fabrice,
It would seem that the answer is right there on the page you
referenced. You can script a change to that registry entry via the
Cygwin
Larry Hall (RFK Partners, Inc.) wrote:
Fabrice Marchal wrote:
Randall R Schulz wrote:
Fabrice,
It would seem that the answer is right there on the page you
referenced. You can script a change to that registry entry via the
Cygwin regtool script. You can do this in an install or post-install
Randall R Schulz wrote:
Fabrice,
It would seem that the answer is right there on the page you
referenced. You can script a change to that registry entry via the
Cygwin regtool script. You can do this in an install or post-install
script or upon each invocation of your application, providing it
Fabrice,
It would seem that the answer is right there on the page you
referenced. You can script a change to that registry entry via the
Cygwin regtool script. You can do this in an install or post-install
script or upon each invocation of your application, providing it's
invoked via a script.
On Thu, 27 Feb 2003, Fabrice Marchal wrote:
> Hi,
> I have come accross the 384 Mb limit for allocating memory in cygwin.
> (e.g. char* pnt = new char[ long size = 500*1024*1024 ]; will not work )
>
> I have been able to modify this using the workaround documented in the
> Users Guide (http://cyg
13 matches
Mail list logo
