Any news on possibly getting a useable UWIN perl release for win64???? I've
been asking for months. Please?!?!?!?

Thanks, Bear

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Bear Limvere
Sent: Thursday, June 06, 2013 7:58 AM
To: 'Glenn Fowler'
Cc: [email protected]
Subject: Re: [uwin-users] UWIN 64 - perl and groff install fails on Windows7

Any progress on getting perl and groff re-packaged for Winders 7 64-bit?

This morning am getting a "CGIWrap Error: Real UID could not be changed!"
error on the website.

I do REALLY miss having perl to run some of the parts of my business.

Thanks, Bear
-------------------------------------------
Bear Limvere - Woodturner, Artist, Musician http://www.BearLimvere.com/
http://www.StandingPeopleDesigns.com/ -
https://www.facebook.com/StandingPeopleDesigns
"You give but little when you give of your possessions.
 It is when you give of yourself that you truly give."
 ~Kahlil Gibran
Mitakuye Oyasin -- We are all RELATED! 


-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Glenn Fowler
Sent: Thursday, April 25, 2013 12:14 PM
To: [email protected]; [email protected]
Cc: [email protected]
Subject: Re: [uwin-users] UWIN 64 - perl and groff install fails on Windows7


On Thu, 25 Apr 2013 19:39:40 +0200 Simon Toedt wrote:
> On Thu, Apr 25, 2013 at 4:24 PM, Bear Limvere 
> <[email protected]> wrote:
> >>> When I tried to install either uwin-groff.2008-11-15.win32.i386 or 
> >>> uwin-perl-58.2005-11-04.win32.i386, I get an open command prompt 
> >>> with the message "cannot find UWIN registry keys"

the installation registry was reorganized a few years back the intention was
to keep it backwards compatible but that obvisouly didn't work

we'll repackage groff and and updated perl 32 bit for next week

> Is there still anyone left who didn't abandon UWIN? The UWIN lists are 
> pretty much like a desert when I compare it to the hundreds of posting 
> I get from the Cygwin lists

a bunch of non-cygwin code and packages need #ifdef CYGWIN and that
generates a lot of traffic

also, while cygwin was/is busy posting about how hard it would be to get 64
bit native executables working we implemented it 2 years ago on uwin with
transparent access between uwin*32 and uwin*64 bit processes and files and
via the virtual /32/ and /64/ mounts we also managed to tame the microsoft
penchant for adding a new api for the cross product of
        file/registry X ucs16/utf X 32bit/64bit

for the past year or so we have been concentrating on performance in the
face of heavy process load -- the internal test scripts we have regularly
crashed uwin and cygwin -- getting uwin through that has been a chore

we're also in the process of thread-safing many of the libast apis and
that's another time-consuming activity that thankfully is nearing conclusion

_______________________________________________
uwin-users mailing list
[email protected]
http://lists.research.att.com/mailman/listinfo/uwin-users


_______________________________________________
uwin-users mailing list
[email protected]
http://lists.research.att.com/mailman/listinfo/uwin-users


_______________________________________________
uwin-users mailing list
[email protected]
http://lists.research.att.com/mailman/listinfo/uwin-users

Reply via email to