>From ouside, you can find beta at http://www2.research.att.com/sw/download/beta/
Regards 2011/6/17 Glenn Fowler <[email protected]> > > the first beta of uwin release 5.0 is avaiilable at > http://www.research.att.com/sw/download/beta > 5.0b includes a native 64 bit uwin (win32.i386-64) > that is fully interoperable with the 32 bit uwin (win32.i386) > > right now only { uwin-base uwin-dev } are available in 64 bit > once the beta stabilizes we will add other packages > > online uwin documentation will be updated next week > including details on new features and 32/64 bit operation > > 5.0b is beta, so don't switch over production machines without > doing compatibility testing; we expect frequent updates > for the rest of the month as feedback flows in > > the current release 5.0b version is 2011-06-16; uname -R shows > the build time down to the second -- this may come in handy > on days when we post multiple beta versions (we've had a few > of those internally this year) > > a few quick notes on 32/64 > > (1) 32 and 64 bit uwin can be installed in the same uwin root -- > the 32 and 64 bit binary files and data are in installed in > different directories; /proc and ps, from either 32 or 64 > bit processes, access the same process and system data > > (2) /usr /var /sys /msdev point to 32 bit files for 32 bit processes > and 64 bit files for 64 bit processes; there is only one copy of > non-binary files > > (3) you can override the default 32/64 mapping by prefixing any absolute > path (path that starts with /) with /32 to specify the 32 bit version > and /64 to specify the 64 bit version; non-binary paths may also be > prefixed, both prefixes simply point to the same physical file; the > 32/64 prefixes work with /reg too -- this means one way to name > 32 and 64 bit data -- no more SysWOW3264, SysNative, WoW3264Node, etc. > e.g., /32/sys/cmd is the 32 bit CMD.EXE and /64/sys/cmd is the 64 bit > try this from 32 and 64 bit ksh to see the physical (DOS path) mappings > winpath /32/sys/cmd /64/sys/cmd /32/bin/ksh /64/bin/ksh > uwin grabs the top level directories /u32 and /v32 (the name choice > speeds up the 32/64 name lookup); from a 64 bit process if /usr/bin/foo > is not found then /32/usr/bin/foo is checked > > (4) currently cc(1) is only tested with msvc for 32/64 operation; by > default the 32 bit cc generates 32 bit binaries and the 64 bit > cc generates 64 bit binaries; the -m32 and -m64 options override > the default > > (5) alternatively a 64 bit ksh can specify > vpath / /32 > to effectively add a /32 prefix to all paths; similarly a 32 bit ksh > can specify > vpath / /64 > this is what we used to bootstrap compile the first working 64 bit > uwin-base from 32 bit uwin earlier this year; > to turn off the default prefix specify > vpath / - > > (6) some binaries in the 64 bit packages are still 32 bit; this is mainly > for applications that require non-redistributable 64 bit microsoft > libraries > (yes we have learned our lesson) and we won't ship binaries that can't > be > built from source with freely available software > > _______________________________________________ > uwin-users mailing list > [email protected] > https://mailman.research.att.com/mailman/listinfo/uwin-users > -- *yves* crespin t. +33.(0)6.86.42.86.81 [image: Skype:] yvescrespin [image: Linkedin]
_______________________________________________ uwin-users mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/uwin-users
