Hallo Ashley,
Am Samstag, 15. März 2003 um 10:05 schriebst du:
> NOTE: I am not on the list. Please reply directly.
> Why does cygwin setup want to downgrade perl from 5.8 to 5.6? Is this
> intentional or accidental? The following excerpt from
> http://archive.progeny.com/cygwin/setup.ini
Gerrit P. Haase wrote:
> Hallo Ashley,
>
> Am Samstag, 15. März 2003 um 10:05 schriebst du:
>
>> NOTE: I am not on the list. Please reply directly.
>
>> Why does cygwin setup want to downgrade perl from 5.8 to 5.6? Is
>> this intentional or accidental? The following excerpt from
>
>> http://arc
I start Midnight Commander in a rxvt window. After quitting mc, the
spawned shell (bash or zsh) is not teminated - leaving a "zombie"
shell process.
This doesn't happen when mc is started in "normal" console window.
Thorsten
Newest versions of mc, rxvt, bash and zsh under Windows XP SP1
mc 4.6
Hallo Max,
>> My workaround for setup.exe's behaviour is ...
> Messy Please don't advise people to circumvent setup!
I know that, then it is better to say:
My workaround for setup.exe's behaviour is:
build & install perl-5.8 yourself from source.
Gerrit
--
=^..^=
--
Unsubscribe info:
Tim Largy wrote:
> Hi,
>
> I installed the cygwin distribution (February 14) on Windows XP and am
> having trouble with spaces my home directory "/cygwin/c/Documents and
> Settings/largy". For example, when I run the command "startx" at the
> bash prompt I get:
>
> [: and: unknown operand
> [: and:
On Sun, 16 Mar 2003, Thorsten Kampe wrote:
> I start Midnight Commander in a rxvt window. After quitting mc, the
> spawned shell (bash or zsh) is not teminated - leaving a "zombie"
> shell process.
>
> This doesn't happen when mc is started in "normal" console window.
I've noticed this already
Grok. I'll frob it tomorrow at work.
Thanks!!!
On Sat, 2003-03-15 at 01:14, Randall R Schulz wrote:
{ snip }
>
> David,
>
> If DISPLAY is set, then rxvt tries to use it and fails if it cannot
> successfully do so. If you want rxvt to operate in GDI mode, make sure
> it does not inherit a s
Hi
I am using GCC in cygwin and I want' to prorgams based on the i386-elf
format like in linux. I am having troubles building it though
I have tried
binutils:
./configure --target=i386-elf
make
make install
OK
GCC whole distribution:
./configure --target=i386-elf
make
But when building GCC I j
Steve Graham wrote:
> Hi
>
> I am using GCC in cygwin and I want' to prorgams based on the i386-elf
> format like in linux. I am having troubles building it though
>
> I have tried
>
> binutils:
> ./configure --target=i386-elf
> make
> make install
> OK
>
> GCC whole distribution:
> ./configure
Hallo mellman,
Am Freitag, 14. März 2003 um 22:46 schriebst du:
> Is there a way to dump the exact pipeline that perldoc uses?
> It says something in the man page about nroff, etc ...
> Does it use nroff or groff?
/usr/bin/nroff
From perldoc -h:
Options:
-t Display pod using pod2text ins
On Sun, Mar 16, 2003 at 11:23:47AM -, Max Bowsher wrote:
> Tim Largy wrote:
> > What are most people using as
> > their home directories, and from the multitudinous ways of setting it,
> > what is the preferred method?
>
> The Cygwin default home dir is /home/username. Did you change it
> deli
Hi All...
The attached script launches the ssh-agent (via keychain) from cygrunsrv so
that it (the ssh-agent process) survives logout. It takes no keys when it is
launched, it just creates the ssh-agent process that can stay around
forever. Then when you start a bash login shell, the keychain i
Ok, lets try that again.
I am about to write the Kernel for an operating system that I am writing and
I would like to use the GCC on cygwin, but I need to output ELF files rather
than PE. I have never tried to compile GCC before and I am having a problem
getting it to build.
I have tried going st
Hmm, to simplify it even more, there is no concept of "the entire cygwin
distribution" :-D There's only a fluid set of packages, each of which has
a version.
Igor
On Sun, 16 Mar 2003, Tim Largy wrote:
> I've answered my own question. There is no concept of versioning for the
> entire cyg
On Sunday 16 March 2003 09:02, Steve Graham wrote:
>
> I have made many google seaches and I can't find any sources on making
> cross-compilers on Cygwin, if you know of any good resouces please could
> you let me know.
>
>From the first page of a Google search:
http://www.objsw.com/CrossGCC/
Sear
I've followed the instructions on that page but i'm still getting this
problem, sorry I can't give you more information than this but I don't
really have any clue what is going wrong.
One other resource that I will hopefully have is the Book "GCC The Complete
Reference" Arther Griffith, which has
/ Igor Pechtchanski <[EMAIL PROTECTED]> wrote:
| Hmm, to simplify it even more, there is no concept of "the entire cygwin
| distribution" :-D There's only a fluid set of packages, each of which has
| a version.
So basically you can give cygwin a version number based on date or
similar, and thus y
Hi All...
I made a small patch to keychain, so that it creates an additional
pid file named ~/ssh-agent.cmd
The only difference between this and the previous version is that the file
created is ~/ssh-agent.cmd instead of ~/ssh-agent.bat so it is a bit less
obtrusive. I couldn't do a ~/.ssh-agent
> Chris,
>
> On Thu, Mar 13, 2003 at 11:57:43PM -, Chris January wrote:
> > Corinna, the cpuid results are still valid if the user doesn't
> have NT. Only
> > in the worst case scenario (i.e. a user running Windows 95/98
> on a 486) will
> > it be necessary to resort to falling back on the regi
Hello !
I am working on a caudium port (http://caudium.net)
I am meeting an issue with mainCRTStartup during the compilation
process.
ld: warning: cannot find entry symbol _mainCRTStartup; defaulting to 00401000
I wonder why ld is claiming about such flags
whereas caudium is a http server and ha
Christopher Faylor wrote:
I'm looking forward to seeing someone debug what the problem is here.
Me too.
Just to be clear: I don't know emacs. I'm not refusing to work on the
problem. I don't know how to duplicate it and I don't have the time to
track it down now if I did.
Ok, had some time to
Still talking about this, eh? Somehow I thought it had died down
before I went on my business trip.
On Fri, Mar 14, 2003 at 11:57:02AM -0600, Brian Ford wrote:
>Vanilla gcc 3.2.x is NOT ABI compatible with Cygwin's pre 3.2 gcc,
>fact. I wanted to know why this was allowed to persist given the
>s
Hi,
Welcome to another release of the Nano package, the pico clone with many
extensions, all while remaining very small indeed. (For those a little lost
at this point, its a text editor, reasonably powerful given its size and
ease of use)
This is the first release of the stable 1.2 branch - a
I've made a new snapshot of cygwin available. This is a departure from
previous snapshot in that it is built from a branch rather than from the
CVS trunk. The branch contains an accumulation of all of the fixes that
have shown up on the CVS trunk minus any new 64 bit development.
I found and fix
Brian Ford wrote:
> Vanilla gcc 3.2.x is NOT ABI compatible with Cygwin's pre 3.2 gcc, fact.
> I wanted to know why this was allowed to persist given the simple patch
> required to fix it, question. I had seen Mr. Faylor make statements
> before to the effect of: doubles in structures are not tha
On Sun, Mar 16, 2003 at 08:32:46PM -0500, Christopher Faylor wrote:
> 2) bunzip2 cygwin-2003/???.dll.bz2
cygwin-2003.dll.bz2
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://c
On Mon, Mar 17, 2003 at 12:59:21PM +1100, Danny Smith wrote:
>Brian Ford wrote:
>
>> Vanilla gcc 3.2.x is NOT ABI compatible with Cygwin's pre 3.2 gcc, fact.
>> I wanted to know why this was allowed to persist given the simple patch
>> required to fix it, question. I had seen Mr. Faylor make state
On Sun, Mar 16, 2003 at 09:01:23PM -0500, Christopher Faylor wrote:
>On Mon, Mar 17, 2003 at 12:59:21PM +1100, Danny Smith wrote:
>>Brian Ford wrote:
>>
>>> Vanilla gcc 3.2.x is NOT ABI compatible with Cygwin's pre 3.2 gcc, fact.
>>> I wanted to know why this was allowed to persist given the simple
--- Danny Smith <[EMAIL PROTECTED]> wrote: > Brian Ford wrote:
>
> > Vanilla gcc 3.2.x is NOT ABI compatible with Cygwin's pre 3.2 gcc, fact.
> > I wanted to know why this was allowed to persist given the simple patch
> > required to fix it, question. I had seen Mr. Faylor make statements
> > be
Christopher Faylor wrote:
I've made a new snapshot of cygwin available. This is a departure from
previous snapshot in that it is built from a branch rather than from the
CVS trunk. The branch contains an accumulation of all of the fixes that
have shown up on the CVS trunk minus any new 64 bit dev
On Sun, Mar 16, 2003 at 09:23:45PM -0500, Rolf Campbell wrote:
>Christopher Faylor wrote:
>>Reports of success or failure to the list, please.
>Emacs problems: all gone.
Wow. Amazing. Good to hear. Talk about shooting in the dark.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscrib
Christopher Faylor writes:
>
> I've made a new snapshot of cygwin available.
>
> Reports of success or failure to the list, please.
This seems to fix the 'long hang after control-c' problem
I reported.
Thank you !
Norman
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug
Pierre A. Humblet wrote:
I recall another problem that somebody had reported after answering "yes".
The chown command in a postinstall script had no effect. That would mean
that at, at least at that site, the program was lacking the Restore
privilege.
To test if this is a prevalent problem, a sim
33 matches
Mail list logo
