From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Sat, 13 Jul 2002 04:31:59 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 271 ************************************************** Friday 12 July 2002 Number 271 ************************************************** Subjects for today 1 Re: PHP 4.0.6 : IanM" 2 Re: Baseline toolset RC1 : Maynard" 3 Re: Baseline toolset RC1 : John Poltorak 4 Re: Baseline toolset : John Poltorak 5 Re: Make problem with BYACC : Thomas Dickey 6 Re: Baseline toolset RC1 : Maynard" 7 Re: Baseline toolset RC1 : John Poltorak 8 Re: Baseline toolset RC1 : John Poltorak 9 Make problem with BYACC : John Poltorak 10 Re: Baseline toolset RC1 : Michael Taylor **= Email 1 ==========================** Date: Sat, 13 Jul 2002 01:36:42 +1000 (EST) From: "IanM" Subject: Re: PHP 4.0.6 Hi John >Is PHP 4.0.6 available anywhere? http://www.os2site.com/sw/dev/php4/old/ Cheers IanM http://www.os2site.com/ WINERR 01F - ERROR IN PROGRESS; PLEASE WAIT.... **= Email 2 ==========================** Date: Sat, 13 Jul 2002 06:21:12 -0500 (CDT) From: "Maynard" Subject: Re: Baseline toolset RC1 Hi John, >> I'm working on putting your baseline and build_system together here as >> a novice. > >> Thanks again. I'll chirp up when I've rounded the next bend, > >Just wondered how you or anyone else had got on. I did manage to get all the files; that's the kind of thing that is supposed to happen in the background. My task now is to attempt the build; that's the kind of thing which is going to require focused attention at least to getting it launched. The first "hurdle" at least in my mind, is figuring out the proper directory tree, and how to interrelate 'baseline' and 'build_system'. I'm figuring to get to it this weekend; and will now attempt to advance that toward the beginning. It's good that you inquired ;-} `~Maynard **= Email 3 ==========================** Date: Sat, 13 Jul 2002 09:17:19 +0100 From: John Poltorak Subject: Re: Baseline toolset RC1 On Tue, Jul 09, 2002 at 04:20:46PM -0500, Maynard wrote: > > I'm working on putting your baseline and build_system together here as > a novice. > Thanks again. I'll chirp up when I've rounded the next bend, Just wondered how you or anyone else had got on. There have been quite a few downloads but no word on whether anything actually works. I've tried to make this as straightforward as possible, but I can only guess that it doesn't work for anyone else because I've made some assumptions which are not relevant anywhere else... There are a number of changes I'd like to make but would prefer to wait until I get some feedback about the present system. > > `~Maynard -- John **= Email 4 ==========================** Date: Sat, 13 Jul 2002 10:54:55 +0100 From: John Poltorak Subject: Re: Baseline toolset On Mon, Jul 08, 2002 at 08:39:31AM -0400, John Small wrote: > ** Reply to message from John Poltorak on Sun, 7 Jul 2002 > 20:35:03 +0100 > > > > SED http://hobbes.nmsu.edu/pub/os2/dev/util/sed302.zip > > > > When did this disappear? > > Try This is the version I would like to build, but I want one which doesn't use libregex initially. > -- > John Small -- John **= Email 5 ==========================** Date: Sat, 13 Jul 2002 12:05:34 -0400 From: Thomas Dickey Subject: Re: Make problem with BYACC On Sat, Jul 13, 2002 at 04:30:04PM +0100, John Poltorak wrote: > > I've run into a problem when using Make 3.79.1 to build BYACC:- > > ftp://invisible-island.net/byacc/byacc.tar.gz > > > I get a SYS1034 error:- > > The system cannot find the command processor in the path specified. > > > It occurs at the point shown below:- > > > $(PROGRAM): $(OBJS) $(LIBS) > at echo -n "Loading $(PROGRAM) ... " > --------> at $(LINKER) $(LDFLAGS) -o $(PROGRAM) $(OBJS) $(LIBS) > at echo "done" > > > > LINKER is defined as cc, and Make is clever enough to use gcc instead. But not clever enough. The makefile doesn't define $(CC), otherwise I'd change the definition of $(LINKER), e.g., LINKER = $(CC) The standard name for the compiler is 'cc', of course. This is one of those cases where symbolic links would be very useful (or else a script named 'cc' which calls gcc). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 6 ==========================** Date: Sat, 13 Jul 2002 15:34:37 -0500 (CDT) From: "Maynard" Subject: Re: Baseline toolset RC1 OK John, I used the following three lines at the top of each of three .cmd files set repository=\213.152.37.92\pub\unixos2\baseline\archives set path=\usr\bin;n:\os2 set beginlibpath=\usr\lib I put the contents of your baseline\ into my root \ and ran the scripts from there. I had to modify build_perl.sh by removing the leading slash before $repository While logging emx_inst.cmd I note that \emx\include\long.cmd does not 'exit' or 'return' to the parent logging. The perl build seems to be OK until this point in the log: Use which C compiler? [gcc] Configure: ./checkcc[55]: gcc: not found Uh-oh, the C compiler 'gcc' doesn't seem to be working. You need to find a working C compiler. Either (purchase and) install the C compiler supplied by your OS vendor, or for a free C compiler try http://gcc.gnu.org/ I cannot continue any further, aborting. make: *** No targets specified and no makefile found. Stop. make: *** No rule to make target `test'. Stop. [X:\]path PATH=x:\usr\bin;x:\emx\bin;n\os2; [X:\]dir \emx\bin\gcc.exe 12-21-98 1:55a 110596 0 gcc.exe I'll keep playing with it. I ought to be able to run build_perl.cmd by itself now. `~Maynard **= Email 7 ==========================** Date: Sat, 13 Jul 2002 16:07:34 +0100 From: John Poltorak Subject: Re: Baseline toolset RC1 On Sat, Jul 13, 2002 at 06:21:12AM -0500, Maynard wrote: > Hi John, > > >> I'm working on putting your baseline and build_system together here as > >> a novice. > > > >> Thanks again. I'll chirp up when I've rounded the next bend, > > > >Just wondered how you or anyone else had got on. > > I did manage to get all the files; that's the kind of thing that is > supposed to happen in the background. My task now is to attempt the > build; that's the kind of thing which is going to require focused > attention at least to getting it launched. Actually, it should be easy as pie... > The first "hurdle" at least in my mind, is figuring out the proper > directory tree, and how to interrelate 'baseline' and 'build_system'. For the time being forget about the build_system. Installing the baseline should, in theory build Perl. Just run baseline_inst.cmd. That's what I'm concentrating on at the moment. The build_system was devised sperately, assuming all the required tools were in place. It has not yet been tested with the baseline toolset, in fact there probably are several files missing for building something like sed or grep. I want to see if others can get Perl 5.6.1 built automatically as part of the this baseline installation. Once I know that works I can try integrating it with the build_system. > `~Maynard -- John **= Email 8 ==========================** Date: Sat, 13 Jul 2002 16:15:34 +0100 From: John Poltorak Subject: Re: Baseline toolset RC1 On Sat, Jul 13, 2002 at 10:41:01PM +0100, Michael Taylor wrote: > John Poltorak wrote: > > > > On Tue, Jul 09, 2002 at 04:20:46PM -0500, Maynard wrote: > > > > > > I'm working on putting your baseline and build_system together here as > > > a novice. > > > > > Thanks again. I'll chirp up when I've rounded the next bend, > > > > Just wondered how you or anyone else had got on. > > > > There have been quite a few downloads but no word on whether anything > > actually works. > > > > Hi John, > I followed your instructions and it did work in the end. > The only problem I had was setting the path. I had to add > a few directories to the path to get the build to work. Could you let me know what you needed to change? > I also had renamed "link386.exe" in the OS2 directories so it > didn't get used before the one from one of the toolkits. I tried to set the PATH explicitly to as few directories as possible to obviate the need for doing anything like that > Anyway apart from that it worked and "perl" built with only > 8 or 9 tests failing. I'd actually like to see a summary of the tests to see if there is any difference. In fact, better still would be the summary produced by running ./perl harness in the directory ./t. > > -- > Regards, > Mick > > -- > ----------------------------------------------------------------------- > Michael Taylor miket at pcug.org.au > ----------------------------------------------------------------- > Home Page: http://users.bigpond.net.au/miket5au > ----------------------------------------------------------------- -- John **= Email 9 ==========================** Date: Sat, 13 Jul 2002 16:30:04 +0100 From: John Poltorak Subject: Make problem with BYACC I've run into a problem when using Make 3.79.1 to build BYACC:- ftp://invisible-island.net/byacc/byacc.tar.gz I get a SYS1034 error:- The system cannot find the command processor in the path specified. It occurs at the point shown below:- $(PROGRAM): $(OBJS) $(LIBS) at echo -n "Loading $(PROGRAM) ... " --------> at $(LINKER) $(LDFLAGS) -o $(PROGRAM) $(OBJS) $(LIBS) at echo "done" LINKER is defined as cc, and Make is clever enough to use gcc instead. At the time the error occurs an OS/2 batch file is called from a shell script and the current path has been converted to Unix seperators, ie c:/os2;c:/usr/bin; which may be the problem. I don't get the problem with Make 3.76.1, but it stops earlier because it can't find cc in the path. If I change the I LINKER to gcc, it works OK, but I would prefer to leave everything intact if possible. Should Make be able to cope with this situation or should I convert the PATH back to standard OS/2 format before running Make? -- John **= Email 10 ==========================** Date: Sat, 13 Jul 2002 22:41:01 +0100 From: Michael Taylor Subject: Re: Baseline toolset RC1 John Poltorak wrote: > > On Tue, Jul 09, 2002 at 04:20:46PM -0500, Maynard wrote: > > > > I'm working on putting your baseline and build_system together here as > > a novice. > > > Thanks again. I'll chirp up when I've rounded the next bend, > > Just wondered how you or anyone else had got on. > > There have been quite a few downloads but no word on whether anything > actually works. > Hi John, I followed your instructions and it did work in the end. The only problem I had was setting the path. I had to add a few directories to the path to get the build to work. I also had renamed "link386.exe" in the OS2 directories so it didn't get used before the one from one of the toolkits. Anyway apart from that it worked and "perl" built with only 8 or 9 tests failing. -- Regards, Mick -- ----------------------------------------------------------------------- Michael Taylor miket at pcug.org.au ----------------------------------------------------------------- Home Page: http://users.bigpond.net.au/miket5au ----------------------------------------------------------------- -----------------------------------------------------------------------