>>I was tinkering with cross compiling the Linux kernel on Cygwin 1.7 and
>>go a new error since the last time. The kernel compression now uses some
>>more elf definitions for x86 which are in elf.h on Linux but in
>>ELFTypes.h on Cygwin 1.7. You cannot include both because there is a
>>conflict b
On Sat, Nov 28, 2009 at 10:59:08PM -0600, Stephen M. Kenton wrote:
>I was tinkering with cross compiling the Linux kernel on Cygwin 1.7 and
>go a new error since the last time. The kernel compression now uses some
>more elf definitions for x86 which are in elf.h on Linux but in
>ELFTypes.h on Cy
I was tinkering with cross compiling the Linux kernel on Cygwin 1.7 and
go a new error since the last time. The kernel compression now uses some
more elf definitions for x86 which are in elf.h on Linux but in
ELFTypes.h on Cygwin 1.7. You cannot include both because there is a
conflict between
Charles Wilson wrote:
Eliot Moss wrote:
The new termcap causes my xterm to segmentation fault.
When I back out just the termcap line of this update
in cygwin setup, xterm fires up fine.
Sigh. I think I know what the problem is. The fix is simple, but...
Some of the terminfo entries require mo
Eliot Moss wrote:
> The new termcap causes my xterm to segmentation fault.
> When I back out just the termcap line of this update
> in cygwin setup, xterm fires up fine.
Sigh. I think I know what the problem is. The fix is simple, but...
Some of the terminfo entries require more than 1KB to repre
The new termcap causes my xterm to segmentation fault.
When I back out just the termcap line of this update
in cygwin setup, xterm fires up fine.
xterm -v prints Cygwin 6.8.99.903(250), which shows
up as 250-1 in setup.
The libtermcap.a that works is labeled 20050421-1;
the new one that causes t
I got a couple of new errors since the last time cross compiled the
Linux kernel on Cygwin with 20 or so tool chains for the different
arches and compare the results to Linux
CYGWIN_NT-5.1 MediaCenterPC 1.7.0(0.212/5/3) 2009-07-24 09:59 i686 Cygwin
Linux 454util 2.6.31.5-127.fc12.x86_64 #1 SMP
On Sat, Nov 28, 2009 at 12:13 PM, Angelo Graziosi wrote:
>
> Corinna Vinschen wrote:
>>
>> Fixes a few last-minute bugs:
>
> Now, it seems that creating directories and files in some manner acquires an
> extra unexpected '+' flag. For example (from Cygwin.bat or MinTTY):
>
>
> $ echo "Not " > foo1
lemke...@t-online.de wrote:
> But I still like an answer to this:
>
>> But how do I get back a pure C locale? I also
>> want ls -l to output the old standard date format. So
>> setenv LANG C.what? C.ISO-8859-15 is kind of nice (the accented
>> chars display fine) but ls then shows the iso-type
2009/11/28 lemkemch:
> But how do I get back a pure C locale?
If by that you mean an ASCII locale: C.ASCII. (Btw, that's essentially
the same as C.ISO-8859-1, i.e. it's 8-bit not 7-bit).
> I also
> want ls -l to output the old standard date format. So
> setenv LANG C.what? C.ISO-8859-15 is kind
On Sat, 28 Nov 2009 20:23:49 +0100, I wrote:
On Sat, 28 Nov 2009 17:16:44 +0100, Marco Atzeri wrote:
--- Sab 28/11/09, lemkemch ha scritto:
> and the Cygwin console. Urxvt and xterm require an X
server.
And that I really don't like. Way too complex for my
taste for the
simple task of popp
lemke...@t-online.de wrote:
>>
>> mintty is the right tool for replacing rxvt for not X11.
>>
>> on XP I have no problem to build a file like
>> $ touch ÄÄÆÉßü
>>
>> and to have exactly the same on explorer and from
>> cmd.
>>
>
> I just gave it a try. It seemed to have solved the character
> pro
On Sat, 28 Nov 2009 17:16:44 +0100, Marco Atzeri wrote:
--- Sab 28/11/09, lemkemch ha scritto:
> and the Cygwin console. Urxvt and xterm require an X
server.
And that I really don't like. Way too complex for my
taste for the
simple task of popping up a text window.
>
mintty is the right t
On Sat, Nov 28, 2009 at 01:04:14PM -0500, Dave Steenburgh wrote:
>I "fixed" the problem. I have not updated any software nor changed
>any scripts, and yet I can no longer reproduce these behaviors. I am
>absolutely certain that there is more than one problem here, and I
>hope someone takes a clos
The terminfo0 packages contain the terminal information database that
enables proper operation of ncurses-based applications. This package,
which can be installed alongside the regular 'terminfo' ones, provides
that database using the organizational structure expected by libncurses8
and earlier (ne
The terminfo packages contain the terminal information database that
enables proper operation of ncurses-based applications. The termcap
package provides an obsolete, backwards-compatible format that
contains similar information, for a few selected terminal types.
This package provides the terminf
The terminfo0 packages contain the terminal information database that
enables proper operation of ncurses-based applications. This package,
which can be installed alongside the regular 'terminfo' ones, provides
that database using the organizational structure expected by libncurses8
and earlier (ne
The terminfo packages contain the terminal information database that
enables proper operation of ncurses-based applications. The termcap
package provides an obsolete, backwards-compatible format that
contains similar information, for a few selected terminal types.
This package provides the terminf
I "fixed" the problem. I have not updated any software nor changed
any scripts, and yet I can no longer reproduce these behaviors. I am
absolutely certain that there is more than one problem here, and I
hope someone takes a close look at my previous posts.
--
Problem reports: http://cygwin
Corinna Vinschen wrote:
Fixes a few last-minute bugs:
Now, it seems that creating directories and files in some manner
acquires an extra unexpected '+' flag. For example (from Cygwin.bat or
MinTTY):
$ echo "Not " > foo1.txt
$ echo "Not OK" > foo2.txt
$ diff -Naur foo1.txt foo2.txt > foo.
--- Sab 28/11/09, lemkemch ha scritto:
> > and the Cygwin console. Urxvt and xterm require an X
> server.
>
> And that I really don't like. Way too complex for my
> taste for the
> simple task of popping up a text window.
> >
mintty is the right tool for replacing rxvt for not X11.
on XP I ha
lemke...@t-online.de wrote:
> And that I really don't like. Way too complex for my taste for the
> simple task of popping up a text window.
Try mintty; Andy has done a great job with it. It supports unicode,
displays natively without needing a Xserver, and is (obviously) actively
maintained. The
On Fri, Nov 27, 2009 at 10:11:07PM -0600, Charles D. Russell wrote:
>
> But there is no alternative for external storage that is to be readable
> on Windows, Linux, and Mac OSX. And I use Cygwin scripts for all my
> backups and housekeeping.
Just a side note:
I don't know about Mac, but I'm
On Sat, 28 Nov 2009 07:57:52 +0100, Andy Koppe wrote:
2009/11/27 :
What am I doing wrong with my first tries of 1.7? I created in Windows
Explorer a directory Ébène and in it a file très. When I look at it
with ls in an rxvt window I don't see the accented characters but the
two utf-8 bytes.
On Nov 28 13:53, Corinna Vinschen wrote:
> Besides, we have not only to map the few
> characters you're talking about, the U+f0XX range is also used to
> map invalid UTF-8 chars.
Oh, and all control characters from 0x01 to 0x1f.
The only feasible alternative to the U+f0XX range would be one of th
Andrew Schulman schrieb:
It would be great to port Puppet to Cygwin.
Puppet's scope on a Cygwin host is going to be more limited than on Linux,
just because Cygwin's scope is limited. Puppet could easily manage
Cygwin's file and services, but managing Windows files and services would
take more
On Nov 28 05:19, Eric Blake wrote:
> According to Linda Walsh on 11/28/2009 3:24 AM:
> > Any other standards group I know of is going UTF-8. All of the
> > linux distributions I know are going UTF-8. I'd like to see Cygwin
> > go that way too.
I don't understand this one. What on earth are you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Linda Walsh on 11/28/2009 3:24 AM:
> But barring any other changes, I'd really, (like pretty please!)
> like to see them mapped to their, reserved-visual, but semantically
> impotent equivalents.
http://cygwin.com/acronyms/#PTC
Rather
# Eric Blake:...
[believes he has round trip mapping and that it is more valuable]
than user's being able to identify their files in the OS GUI or
on a linux server]
# Linda W. replies to Eric:
[points out that the current system already uses valid Unicode values
(as others have poin
29 matches
Mail list logo
