Glenn, please see my answers inline:

--- On Wed, 5/20/09, Glenn Fowler <[email protected]> wrote:

> From: Glenn Fowler <[email protected]>
> Subject: Re: [uwin-users] which source package contains 'pcc.c' ?
> To: [email protected], [email protected], [email protected]
> Date: Wednesday, May 20, 2009, 12:54 PM
> 
> the uwin specific source is in this package
>     uwin - UWIN base source package
> the source for the uwin cc is in
>     src/cmd/cc
> and the "source" of confusion is that the source file name
> is
>     pcc.c

At the time I am confused regarding the URL of "UWIN base source package".

As I am looking at

http://www.research.att.com/sw/download/beta/beta.html

, I do _not_ see "UWIN base source package", this is what I see:

"

astksh-20090505-1.setup.hint              ksh standalone cygwin setup hint
astksh-20090505-1-src.tar.bz2     (md5)           ksh standalone cygwin source
astksh-20090505-1.tar.bz2         (md5)           ksh standalone cygwin binary

INIT.2009-05-05.tgz       (md5)           INIT beta package
ast-ksh.2009-05-05.tgz            (md5)           ast-ksh beta package
ast-base.2009-05-05.tgz           (md5)           ast-base beta package
ast-open.2009-05-05.tgz           (md5)           ast-open beta package
ast-gpl.2009-05-05.tgz            (md5)           ast-gpl beta package
ast-dss.2009-01-20.tgz            (md5)           ast-dss beta package

uwin-base.2009-05-15.win32.i386.exe       (md5)           uwin base beta self 
extracting archive
uwin-dev.2009-05-07.win32.i386.exe        (md5)           uwin development beta 
self extracting archive
uwin-groff.2009-01-20.win32.i386.exe      (md5)           uwin groff beta self 
extracting archive
uwin-perl.2009-01-20.win32.i386.exe       (md5)           uwin perl beta self 
extracting archive
uwin-xbase.2009-01-20.win32.i386.exe      (md5)           uwin xbase beta self 
extracting archive
uwin-xdev.2009-01-20.win32.i386.exe       (md5)           uwin xdev beta self 
extracting archive
uwin-xfonts.2009-01-20.win32.i386.exe     (md5)           uwin xfonts beta self 
extracting archive
posix.dll         (md5)           latest unofficial uwin posix.dll
".

As one can see, the uwin-base package only appears as

uwin-base.2009-05-15.win32.i386.exe

, i.e. it is _not_ a source package or, at least, not a source which
can be extracted on any platform.

As I am looking at

http://www.research.att.com/sw/download/

I do see:

"uwin    - UWIN base source package", however, when I go to the actual

link: http://www.research.att.com/~gsf/download/tgz/uwin.2008-07-25.tgz

and when I unpack the uwin.2008-07-25.tgz tarball, I do _not_ see pcc.c
anywhere in it:

"
ser...@amdam2:/mnt/sdb8/sergei/QEMU/portable_perl/uwin> tar zxvf 
uwin.2008-07-25.tgz 1>unpack.log
ser...@amdam2:/mnt/sdb8/sergei/QEMU/portable_perl/uwin> grep pcc unpack.log
ser...@amdam2:/mnt/sdb8/sergei/QEMU/portable_perl/uwin> echo $?
1
ser...@amdam2:/mnt/sdb8/sergei/QEMU/portable_perl/uwin> find . -name pcc.c
ser...@amdam2:/mnt/sdb8/sergei/QEMU/portable_perl/uwin> find . -name cc
ser...@amdam2:/mnt/sdb8/sergei/QEMU/portable_perl/uwin>   
",

i.e. there neither pcc.c, nor (at all) 'cc' directory.


> 
> pcc.c generates one executable
> the hard link to the executable determines how the compiler
> behaves
>     c89
>     cc
>     ncc
>     CC
>     nCC
> the executable uses PACKAGE_cc to determine the underlying
> compiler
> e.g., cl.exe for msvc (it picks msvc by default)
> 
> On Wed, 20 May 2009 11:25:52 -0700 (PDT) Sergei Steshenko
> wrote:
> > --- On Wed, 5/20/09, Matt Lewandowsky <[email protected]>
> wrote:
> 
> > > From: Matt Lewandowsky <[email protected]>
> > > Subject: Re: [uwin-users] which source package
> contains 'pcc.c' ?
> > > To: [email protected]
> > > Date: Wednesday, May 20, 2009, 11:10 AM
> > > > From "Sergei Steshenko" <[email protected]>
> > > on Wednesday, May 20, 2009 
> > > 10:04 AM:
> > > 
> > > > So, I really don't have a clue at the moment
> where to
> > > look for the 'pcc.c'
> > > > file.
> > > 
> > > As David Korn wrote, you need to look at the cc
> sources,
> > > which may or may not be in the UWIN source
> package; they may
> > > be in one of the others. Also, it may simply be
> cc.c that
> > > you're looking for; it may carry a different
> output name
> > > from the source filename. I'm sure that the
> AT&T
> > > Research guys can give more info on that though.
> > > 
> > > But, I have to wonder why you're interested in
> trying to
> > > use UWIN to compile for the POSIX subsystem...
> Interix's
> > > environment already has a perfectly good and
> well-tested
> > > compiler. Cross-compiling from UWIN just doesn't
> sound like
> > > something that's going to be fun to debug, to
> me... Or, are
> > > you trying to just get the ast stuff to build for
> SFU/SUA?
> > > In that case, it's definitely easier to do so
> "natively" in
> > > the POSIX environment, let me assure you of
> that... ;)
> > > (Off-topic: Why isn't there a binary release of
> ksh for
> > > Interix environments? The MKS ksh just gives a
> terrible
> > > impression to people... ;) )
> > > 
> > > --Matt 
> 
> > Matt, I downloaded _all_ the source packages, I tried
> to build them all
> > both under Linux and Windows (in the latter case under
> CYGWIN, just to
> > start things going, before I discovered the beta
> binary packages which
> > _can_ be installed), and I ran 'grep -r ...' and 'find
> . -iname "pcc*"'
> > on the _whole_ tree, i.e. on _all_ the packages.
> 
> > Still, I couldn't find the file.
> 
> > As to what I'm trying to do - in the end I need
> something stand-alone
> > which is UNIXish/Linuxish in its source, and it should
> run on _any_
> > Windows computer, under _any_ user ID, so I need (if i
> understand
> > correctly) posix.dll and AST library. The application
> is simple enough, it 
> > doesn't change UIDs, etc, so, I hope, I do not need
> the server.
> > Essentially, I need fork/exec* and UNIX dlopen
> semantics - UWIN appears to
> > provide them all.
> 
> > In simple English I need the whole thing I'm working
> on to be 
> > self-contained; it'll be portable/relocatable WRT
> paths; it won't require
> > installation in Windows sense.
> 
> > Thanks,
> >   Sergei.
> 
> >       


So, could anyone please confirm my findings which are:

1) no uwin-base package in beta downloads;

2) no 'cc' subdirectory in
http://www.research.att.com/~gsf/download/tgz/uwin.2008-07-25.tgz ;

3) no 'pcc.c' file in
http://www.research.att.com/~gsf/download/tgz/uwin.2008-07-25.tgz .


To confirm the finding means to download the package and to unpack it.

Or, if I'm missing the obvious, could anyone please point me to the exact
URL of uwin base source package - as I have already asked ?


Thanks,
  Sergei.



      

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

Reply via email to