headers
glacken | 1 Nov 2008 01:03
Picon
Favicon

Re: Brand new Cygwin install on a Vista (Home Premium) machine


Karl M-2 wrote:
> 
> 
> Hi All...
> 
> I just did a fresh install of the current Cygwin 1.5 on a Vista Home
> Premium machine.
> 
> There were only a couple bumps. For OpenSSH, the ssh-host-config had to be
> run
> multiple times...it first bailed out because of the protection of the
> passwd and group
> files...next because of the protection of /var. I think it would be good
> to have it offer
> to fix these. I can submit a patch if desired.
> 
> The second issue was with vim from a cmd console window. When I run vim,
> the
> arrow keys work fine until I enter insert mode...then the arrow keys alter
> the test
> and take me out of insert mode. I've not seen this before and some
> Googling didn't
> help. Any thoughts?
> 
> Otherwise, it was a great experience. I used the latest setup.exe snapshot
> and it
> worked very well.
> 
> Thanks to all,
(Continue reading)

Permalink | Reply | 0 comments |
headers
glacken | 1 Nov 2008 01:11
Picon
Favicon

Re: Brand new Cygwin install on a Vista (Home Premium) machine


Did you install onto an AMD or an Intel machine? My install onto an Intel
machine (Vista Home Premium) resulted in a string of messages that
cygwin1.dll was the wrong version.

rg

Karl M-2 wrote:
> 
> 
> Hi All...
> 
> I just did a fresh install of the current Cygwin 1.5 on a Vista Home
> Premium machine.
> 
> There were only a couple bumps. For OpenSSH, the ssh-host-config had to be
> run
> multiple times...it first bailed out because of the protection of the
> passwd and group
> files...next because of the protection of /var. I think it would be good
> to have it offer
> to fix these. I can submit a patch if desired.
> 
> The second issue was with vim from a cmd console window. When I run vim,
> the
> arrow keys work fine until I enter insert mode...then the arrow keys alter
> the test
> and take me out of insert mode. I've not seen this before and some
> Googling didn't
> help. Any thoughts?
(Continue reading)

Permalink | Reply | 1 comment |
headers
glacken | 1 Nov 2008 01:40
Picon
Favicon

Re: Vista and cygwin1.dll


Further comments from glacken.

I had been using cygwin on a 64 bit AMD. I copied my cygwin partition from
the AMD-64 to the Intel-64 via a thumb-drive, apparently with no problems.

The fact that I get the same errors using two versions of cygwin makes me
suspect that the Intel-64 is the culprit.

The two cygwin versions are in separate partitions: each has one
cygwin1.dll, and no cygwin.dll.

rg

glacken wrote:
> 
> Vista gives a string of error messages, essentialy saying that I am using
> wrong cygwin1,dll. There are several sites that claim to fix this problem,
> but I am reluctant to use them.
> 
> Note that this problem is the same with cygwin 1.5.25.15 downloaded today,
> and with an older cygwin setup copied from my WindowsXP computer.
> 
> 

--

-- 
View this message in context: http://www.nabble.com/Vista-and-cygwin1.dll-tp20248321p20276058.html
Sent from the Cygwin list mailing list archive at Nabble.com.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Gary R. Van Sickle | 1 Nov 2008 03:53
Picon

RE: cygwin g++ strictness

> From: John Emmas
> 
> ----- Original Message -----
> From: "Peter Rosin"
> Sent: 31 October 2008 15:19
> Subject: Re: cygwin g++ strictness
> >
> > I some projects I'm involved with there's quite a bit of 
> the following:
> >
> > [...]
> >
> > int.c:6: warning: int format, int32_t arg (arg 2)
> >
> I must confess, this has been a source of irritation for me 
> too but at least it doesn't stop the build.  It does however 
> bring us back to the fundamental question - when programming 
> like this:-
> 
> int32_t i = 32;
> printf("%d", i);
> 
> is it reasonable for a programmer to assume that a type 
> declared as int32_t will be compatible with "%d" when 
> building for a 32-bit platform?

No.  The only reasonable assumption to make in a case like this is that if
you don't do it right, you'll end up doing it over.  "%d" means "int".  You
use that to print an int.  If you have something that is not an int, and you
want to print it, then you have exactly two reasonable choices:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Gary R. Van Sickle | 1 Nov 2008 05:02
Picon

RE: cygwin g++ strictness

> From: Eric Blake
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> According to John Emmas on 10/31/2008 9:35 AM:
> > question - when programming like this:-
> > 
> > int32_t i = 32;
> > printf("%d", i);
> > 
> > is it reasonable for a programmer to assume that a type declared as 
> > int32_t will be compatible with "%d" when building for a 
> 32-bit platform?
> 
> It is not portable to platforms with 16-bit int (although 
> these days, such platforms are museumware).

That, or:
- Running your car's engineware.
- Exploding an airbag into your face on detecting a collisionware.
- Recording your vital signsware.
- Pumping insulin into youware.
- Doing your laundyware
- Computerized exercise machinewear
- Microwaveware
- A billion other products with 8- and 16-bit microcontrollers in themware.

CSci doesn't begin and end with the CPU currently on our desks!
(Continue reading)

Permalink | Reply | 3 comments |
headers
David Arnstein | 1 Nov 2008 08:49
Picon
Favicon

Call "undocumented" NTDLL functions with Cygwin/gcc?

I would like to use some of the "undocumented" NTDLL functions from
within a C or C++ program. I would like to compile this program from
Cygwin's C or C++ compiler.

The functions I refer to involve Registry operations, such as 
NtQueryValueKey() and NtEnumerateValueKey(). I found some sparse
documentation here:
http://undocumented.ntinternals.net/UserMode/Undocumented%20Functions/NT%20Objects/Key/NtQueryValueKey.html

I could not find these under /usr/include. Any suggestions?
Permalink | Reply | 5 comments |
headers
Corinna Vinschen | 1 Nov 2008 10:14
Favicon

Re: Call "undocumented" NTDLL functions with Cygwin/gcc?

On Nov  1 03:49, David Arnstein wrote:
> I would like to use some of the "undocumented" NTDLL functions from
> within a C or C++ program. I would like to compile this program from
> Cygwin's C or C++ compiler.
> 
> The functions I refer to involve Registry operations, such as 
> NtQueryValueKey() and NtEnumerateValueKey(). I found some sparse
> documentation here:
> http://undocumented.ntinternals.net/UserMode/Undocumented%20Functions/NT%20Objects/Key/NtQueryValueKey.html
> 
> I could not find these under /usr/include. Any suggestions?

Many of the ntdll functions and types are defined under
/usr/include/w32api/ddk.  The definitions are not complete so expect
that you have to create your own header to define missing symbols.
Patches to extend the files in w32api (maintained by the MingW team) are
always welcome.

Corinna

--

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat
Permalink | Reply | 4 comments |
headers
Ralph Hempel | 1 Nov 2008 13:28
Favicon

Re: cygwin g++ strictness

Gary R. Van Sickle wrote:
>> From: Eric Blake

>> It is not portable to platforms with 16-bit int (although 
>> these days, such platforms are museumware).
> 
> That, or:
> - Running your car's engineware.
> - Exploding an airbag into your face on detecting a collisionware.
> - Recording your vital signsware.
> - Pumping insulin into youware.
> - Doing your laundyware
> - Computerized exercise machinewear
> - Microwaveware
> - A billion other products with 8- and 16-bit microcontrollers in themware.
> 
> CSci doesn't begin and end with the CPU currently on our desks!

Thanks for reminding everyone that GCC is used for more than building
desktop software. And to bring this around to Cygwin again, I've been
using GCC for ARM under Cygwin for a few years now to build my Lua
for the LEGO MINDSTORMS NXT.

Having been through the gauntlet porting C code from 8 to 16 to 32 bit
machines, I've been bitten by almost every possible portability bug
there is - and I agree with Gary

   Fix it the right way so that it's truly protable.

Ralph
(Continue reading)

Permalink | Reply | 2 comments |
headers
rhhardin | 1 Nov 2008 14:38
Picon

Broken Pipe message suppression?


Is there a way in bash to eliminate the printed broken pipe message?  eg.

./b.sr: line 12:  5576 Broken pipe

in the middle of the terminal output.

I'm running a January 2006 version, if that matters, under XP.
--

-- 
View this message in context: http://www.nabble.com/Broken-Pipe-message-suppression--tp20280463p20280463.html
Sent from the Cygwin list mailing list archive at Nabble.com.
Permalink | Reply | 0 comments |
headers
Mike Marchywka | 1 Nov 2008 15:05
Picon
Favicon

RE: cygwin g++ strictness


> 
>>> It is not portable to platforms with 16-bit int (although 
>>> these days, such platforms are museumware).
>> 
>> That, or:
>> - Running your car's engineware.
>> - Exploding an airbag into your face on detecting a collisionware.
>> - Recording your vital signsware.
>> - Pumping insulin into youware.
>> - Doing your laundyware
>> - Computerized exercise machinewear
>> - Microwaveware
>> - A billion other products with 8- and 16-bit microcontrollers in themware.
>>

These "resource constrained" devices are important to remember as even desktop
computers have limitations - and desktop programmers, from 
what I can see in how Flash and Acrobat function, often forget this. 

>> CSci doesn't begin and end with the CPU currently on our desks!
> 
> Thanks for reminding everyone that GCC is used for more than building
> desktop software. And to bring this around to Cygwin again, I've been
> using GCC for ARM under Cygwin for a few years now to build my Lua
> for the LEGO MINDSTORMS NXT.
> 
> Having been through the gauntlet porting C code from 8 to 16 to 32 bit
> machines, I've been bitten by almost every possible portability bug
> there is - and I agree with Gary
(Continue reading)

Permalink | Reply | 0 comments |

Gmane