Date: Sat, 8 May 2004 00:07:35 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600
Subject: [Ux2bs_Archive] No. 319

**************************************************
Friday 07 May 2004
 Number  319
**************************************************

Subjects for today
 
1  Re:  UX2 Distribution Install : John Poltorak <jp at warpix.org>
2  Re:  Starting Over : John Poltorak <jp at warpix.org>
3   Problems building readline : Davide Bresolin <davide at teamos2.it>
4  Re:  Problems building readline : John Poltorak <jp at warpix.org>
5  Re:  UX2 Distribution Install : IanM" <IanM>
6  Re:  Problems building readline : Davide Bresolin <davide at teamos2.it>
7  Re:  UX2 Distribution Install : John Poltorak <jp at warpix.org>
8  Re:  UX2 Distribution Install : IanM" <IanM>
9  Re:  Problems building readline : Davide Bresolin <davide at teamos2.it>
10  Re:  Succes on JFS, perl : Lyn St George" <lyn at zolotek.net>
11  Re:  Problems building readline : John Poltorak <jp at warpix.org>
12  Re:  UX2 Distribution Install : Lyn St George" <lyn at zolotek.net>
13  Re:  UX2 Distribution Install : John Poltorak <jp at warpix.org>
14  Re:  Problems building readline : John Poltorak <jp at warpix.org>
15  Re:  UX2 Distribution Install : John Poltorak <jp at warpix.org>
16  Re:  Problems building readline : John Poltorak <jp at warpix.org>
17  Re:  Succes on JFS, perl : John Poltorak <jp at warpix.org>
18  Re:  Any success? : Anton Monroe <akm at meer.net>
19  Re:  Succes on JFS, perl : Anton Monroe <akm at meer.net>
20   Error compiling BYACC-20040328 : Anton Monroe <akm at meer.net>
21  Re:  Problems building readline : Davide Bresolin <davide at teamos2.it>
22  Re:  Any success? : John Poltorak <jp at warpix.org>
23  Re:  Error compiling BYACC-20040328 : John Poltorak <jp at warpix.org>
24   Trying to build SWI-prolog : Davide Bresolin <davide at teamos2.it>
25  Re:  Problems building readline : John Poltorak <jp at warpix.org>
26  Re:  Trying to build SWI-prolog : John Poltorak <jp at warpix.org>
27   BerkeleyDB : John Poltorak <jp at warpix.org>
28  Re:  Trying to build SWI-prolog : Davide Bresolin <davide at teamos2.it>
29  Re:  Trying to build SWI-prolog : John Poltorak <jp at warpix.org>
30  Re:  Any success? : Anton Monroe <akm at meer.net>
31  Re:  Error compiling BYACC-20040328 : Anton Monroe <akm at meer.net>


**= Email   1 ==========================**

Date:  Thu, 6 May 2004 15:17:51 +0100
From:  John Poltorak <jp at warpix.org>
Subject:  Re:  UX2 Distribution Install

On Thu, May 06, 2004 at 08:12:38AM -0400, T.Sikora wrote:
> Jeff, Ian, you guys ready to go to work? John had enough of us sitting 
> on our hands. That dialog driven install we discussed would be pretty 
> cool. I'm setting up a ux2bs machine now so we can merge the 2 together. 
> I was thinking for now remove the 'old' development tools from that old 
> 'monster' and put the current ux2bs in it's place. We can do a 
> (full)install first with development tools so we can integrate the ports 
> tree into the distribution smoothly. 

It won't work. UX2BS and the previously bundled UnixOS/2 packages are not 
designed to go together.

The PKGs were built manually to resemble a Slackware distro. UX2BS was 
designed to build and install apps directly from source.

> What is the status of the 
> filesystem issue. Are we still using the unixroot for the packages or 
> are we using Unix legacy locations? Did anyone ever get that makepkg 
> tool working? I guess ideally we want everything built with the ux2bs 
> packaged for the distribution.

At this point in time UX2BS does not create PKGs.

 
> -- 
> T.Sikora
> tsikora at ntplx dot net



-- 
John


_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   2 ==========================**

Date:  Thu, 6 May 2004 15:25:50 +0100
From:  John Poltorak <jp at warpix.org>
Subject:  Re:  Starting Over

On Thu, May 06, 2004 at 08:18:05PM +0930, Paul Smedley wrote:

> > Just out of curiosity, could you post \unixos2\logs\per-test_results.log 
> > if you have one?
> Failed 4/867 test scripts, 99.54% okay. 11/79051 subtests failed, 99.99% 
> okay.
> Failed Test    Stat Wstat Total Fail  Failed  List of Failed
> -------------------------------------------------------------------------------
> lib/os2_base.t    1   256    19    1   5.26%  8
> lib/os2_ea.t                 21    8  38.10%  7-11 14-16
> op/magic.t                   53    1   1.89%  6
> op/stat.t                    78    1   1.28%  44
> 67 tests and 636 subtests skipped.
> 
> Same result on another machine I support... 

That does show reasonable consistancy.

> once I added link386.exe to 
> the other PC.  Seems that ux2bs doesn't check for link386.exe until 
> AFTER trying the build Perl??

No the check for link386.exe is almost the first thing the build script 
does. Check:-

\unixos2\lib\build.sh :-


if test ! -f $OSRT/os2/link386.exe ; then
{
  echo There is no LINK386.EXE on the path, which could cause problems
  echo Press ENTER to continue
  read reply
}
fi

 
> Cheers,
> 
> Paul.


-- 
John


_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   3 ==========================**

Date:  Thu, 06 May 2004 16:44:16 +0200
From:  Davide Bresolin <davide at teamos2.it>
Subject:   Problems building readline

Hi,
I've some problem in building readline 4.3, from a fresh re-installed 
UX2BS system.

If I do a build readline, i get the following errors in readline.log:

gcc -c -DHAVE_CONFIG_H   -I. -I. -DRL_LIBRARY_VERSION='"4.3"' -g -O 
readline.c
In file included from readline.c:30:
posixstat.h:138: warning: `S_IRUGO' redefined
e:\unixos2\posix2\include\sys/stat.h:208: warning: this is the location 
of the previous definition
posixstat.h:139: warning: `S_IWUGO' redefined

and, furthermore

e:\unixos2\posix2\include\sys/stagcc -c -DHAVE_CONFIG_H   -I. -I. 
-DRL_LIBRARY_VERSION='"4.3"' -g -O rltty.c
rltty.c: In function `set_winsize':
rltty.c:151: `TIOCSWINSZ' undeclared (first use in this function)
rltty.c:151: (Each undeclared identifier is reported only once
rltty.c:151: for each function it appears in.)
t.h:209: warning: this is the location of the previous definition

Any suggestion on how to fix it? There is something that I have to build 
  before readline?



Ciao...

        -=> DaViDe <=-
-=> davide(AT)teamos2.it <=-
_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   4 ==========================**

Date:  Thu, 6 May 2004 16:15:40 +0100
From:  John Poltorak <jp at warpix.org>
Subject:  Re:  Problems building readline

On Thu, May 06, 2004 at 04:44:16PM +0200, Davide Bresolin wrote:
> Hi,
> I've some problem in building readline 4.3, from a fresh re-installed 
> UX2BS system.

Readline is one of the apps I would like to get built myself, although I 
don't have much of an idea about what does. As far as UX2BS is concerned 
its presence in build.table is simply a convenience which might help 
someone to get it working
 
> If I do a build readline, i get the following errors in readline.log:
> 
> posixstat.h:138: warning: `S_IRUGO' redefined

> rltty.c:151: `TIOCSWINSZ' undeclared (first use in this function)

I've just tried it and get the same errors.
 
> Any suggestion on how to fix it? There is something that I have to build 
>   before readline?

By default, a build will use the Posix/2 headers and library. Sometimes, 
this results in errors, but they can be removed from the environment by  
adding the app name to \unixos2\lib\p2_exc.lst. When this is done a 
libreadline.a and libhistory.a get created, but I have no idea if the 
builds are correct. I would appreciate it if you could add this app to 
p2_exc.lst and try building readline again, and saying whether the build 
is any good.
 
> 
> 
> Ciao...
> 
>         -=> DaViDe <=-
> -=> davide(AT)teamos2.it <=-


-- 
John



_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   5 ==========================**

Date:  Fri, 07 May 2004 01:30:45 +1000 (EST)
From:  "IanM" <IanM>
Subject:  Re:  UX2 Distribution Install

As john said, I view them as two different beasts, for two different
purposes. One thing I've learn in the Unix world, and that has carried
over to the Linux world unfortunetly, that what works on one distribution
/flavour, will likely need to be modified for another distribution/flavour.

So I think we can live with UnixOS2, and Ux2bs, ie, two ways of doing
different but similar things, if you see what I mean.

I see were your coming from though Ted, it would be nice to have a
package that will create/add all the needed tools such as Ux2bs but
there will always be a need for UnixOS2 to provide source, and binaries
of 'other' tools for compiling code, as well as providing non Ux2bs binaries
to people who just want the latest make or whatever.

Am I on the wrong track ?

On Thu, 06 May 2004 08:12:38 -0400, T.Sikora wrote:

> Jeff, Ian, you guys ready to go to work? John had enough of us sitting 
> on our hands. That dialog driven install we discussed would be pretty 
> cool. I'm setting up a ux2bs machine now so we can merge the 2 together. 
> I was thinking for now remove the 'old' development tools from that old 
> 'monster' and put the current ux2bs in it's place. We can do a 
> (full)install first with development tools so we can integrate the ports 
> tree into the distribution smoothly. What is the status of the 
> filesystem issue. Are we still using the unixroot for the packages or 
> are we using Unix legacy locations? Did anyone ever get that makepkg 
> tool working? I guess ideally we want everything built with the ux2bs 
> packaged for the distribution.
> 
> -- 
> T.Sikora
> tsikora at ntplx dot net
> 
> 
> 
> 
> _______________________________________________
> UX2BS mailing list
> UX2BS at os2ports.com
> http://os2ports.com/mailman/listinfo/ux2bs

Cheers
IanM
http://www.os2site.com/

The best way to accelerate Windows is at escape velocity.
_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   6 ==========================**

Date:  Thu, 06 May 2004 17:43:32 +0200
From:  Davide Bresolin <davide at teamos2.it>
Subject:  Re:  Problems building readline

John Poltorak ha scritto:

> By default, a build will use the Posix/2 headers and library. Sometimes, 
> this results in errors, but they can be removed from the environment by  
> adding the app name to \unixos2\lib\p2_exc.lst. When this is done a 
> libreadline.a and libhistory.a get created, but I have no idea if the 
> builds are correct. I would appreciate it if you could add this app to 
> p2_exc.lst and try building readline again, and saying whether the build 
> is any good.
Ok, I've just tried doing this.
Now this is the error that I obtain:

( cd shlib ; make  all )
make[1]: Entering directory `E:/unixos2/workdir/readline-4.3/shlib'
make[1]: *** No rule to make target `readline.c', needed by 
`readline.so'.  Stop.
make[1]: Leaving directory `E:/unixos2/workdir/readline-4.3/shlib'

-- 
Ciao...

        -=> DaViDe <=-
-=> davide(AT)teamos2.it <=-
_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   7 ==========================**

Date:  Thu, 6 May 2004 16:54:20 +0100
From:  John Poltorak <jp at warpix.org>
Subject:  Re:  UX2 Distribution Install

On Fri, May 07, 2004 at 01:30:45AM +1000, IanM wrote:
> As john said, I view them as two different beasts, for two different
> purposes. 

They are not entirely different. My aim with UX2BS is to be able to 
produce PKGs at some point, but I haven't figured out just how to do 
that yet. I am not keen an _manually_ maintaining any PKGs. The ones  
already produced took a great deal of time and are virtually 
unmaintainable. What I'm looking to do at some point in UX2BS is add an 
extra step at the end - 'make PKG' which will automatically created a 
distributable package as part of a build. But this is still just an idea 
and no concrete solution has emerged yet.

> So I think we can live with UnixOS2, and Ux2bs, ie, two ways of doing
> different but similar things, if you see what I mean.

I see UX2BS as a mechanism for creating a UnixOS/2 distro eventually. If 
not as a set of PKGs, then at least as a single archive of some sort.

-- 
John


_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   8 ==========================**

Date:  Fri, 07 May 2004 02:09:34 +1000 (EST)
From:  "IanM" <IanM>
Subject:  Re:  UX2 Distribution Install

Hi John

> On Fri, May 07, 2004 at 01:30:45AM +1000, IanM wrote:
> > As john said, I view them as two different beasts, for two different
> > purposes. 
> 
> They are not entirely different. My aim with UX2BS is to be able to 

Tis why I said "different but similar things" :-)

> produce PKGs at some point, but I haven't figured out just how to do 
> that yet. I am not keen an _manually_ maintaining any PKGs. The ones  
> already produced took a great deal of time and are virtually 
> unmaintainable. What I'm looking to do at some point in UX2BS is add an 
> extra step at the end - 'make PKG' which will automatically created a 
> distributable package as part of a build. But this is still just an idea 
> and no concrete solution has emerged yet.

Yes, it would be a good way to keep a lot of UnixOS2 upto date, ie, by
running Ux2bs but there will always be other utilities needed that are
not a part of Ux2bs, and may never be due to updated code etc, though
in saying that, there is a lot that can be done with Ux2bs out of the box
so to speak.

> > So I think we can live with UnixOS2, and Ux2bs, ie, two ways of doing
> > different but similar things, if you see what I mean.
> 
> I see UX2BS as a mechanism for creating a UnixOS/2 distro eventually. If 
> not as a set of PKGs, then at least as a single archive of some sort.

I would like it to be that to, for obvious reasons but I still think thats a
way off, though we are a lot closer now.

Cheers
IanM
http://www.os2site.com/

"make lots of money",  "enjoy the work",  "operate within the law":  choose 2 -- Brian Anderson
_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   9 ==========================**

Date:  Thu, 06 May 2004 18:21:10 +0200
From:  Davide Bresolin <davide at teamos2.it>
Subject:  Re:  Problems building readline

Davide Bresolin ha scritto:

>> By default, a build will use the Posix/2 headers and library. 
>> Sometimes, this results in errors, but they can be removed from the 
>> environment by  adding the app name to \unixos2\lib\p2_exc.lst. When 
>> this is done a libreadline.a and libhistory.a get created, but I have 
>> no idea if the builds are correct. I would appreciate it if you could 
>> add this app to p2_exc.lst and try building readline again, and saying 
>> whether the build is any good.
> 
> Ok, I've just tried doing this.
> Now this is the error that I obtain:
> 
> ( cd shlib ; make  all )
> make[1]: Entering directory `E:/unixos2/workdir/readline-4.3/shlib'
> make[1]: *** No rule to make target `readline.c', needed by 
> `readline.so'.  Stop.
> make[1]: Leaving directory `E:/unixos2/workdir/readline-4.3/shlib'

Some good news: apart from this errors, I could get the readline 
examples working, after some changes on Makefile: it creates files with 
no extensions (unix-like) instead of .exe files.
Furthermore it creates libreadline.a instead of readline.a, as aspected 
by gcc when building the examples. Renaming the file solves the problem.

My next step would be trying to compile SWI-prolog, that requires 
readline.....


-- 
Ciao...

        -=> DaViDe <=-
-=> davide(AT)teamos2.it <=-
_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   10 ==========================**

Date:  Thu, 06 May 2004 17:33:00 +0100 (BST)
From:  "Lyn St George" <lyn at zolotek.net>
Subject:  Re:  Succes on JFS, perl

--_=_=_=IMA.BOUNDARY.HXBAJ0138764=_=_=_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

On Wed, 5 May 2004 15:07:08 +0100, John Poltorak wrote:

>On Wed, May 05, 2004 at 02:30:41PM +0100, Lyn St George wrote:
>> It seems to be all OK now, 
>
>Your crashed disk didn't detain you long....
>
>If I had lost 14GB, I'd be fairly distraught.

Distraught - the sobs should be audible from the next planet ...

>
>
>> As I've been out of the loop for a while on this, I wonder if 
>> people could bring me up to speed on the current status.
> 
>I wondered where you had got to... I feared you had been nabbed by the 
>dark side.

Never. Just buried in work. 

>> I see in the "wrong" files from unixos2.com that there are some
>> impressive references to symlinks. Is this currently working?
>
>I don't really know anything about it.

I will investigate this further. 

>> Why are there two different build systems? The philosophies
>> seem to be quite different, not just the scripts.
>
>Initially I dreamt up the idea of a standardised build framework for 
>building Unix apps on OS/2 starting off with what I called a 'baseline' 
>toolset. Ted liked the idea and enhanced it by including lots of other 
>apps into the framework which he thought would be useful for building all 
>sort of apps.
>
>The difference in philosophies is that I wanted everything apart fom the 
>'baseline' tools to be homegrown - ie built using UX2BS, Ted wanted to use 
>any existing ports.
>
> 
>> Is anybody actively maintaining and developing the system
>> (apart from John of course)? At first glance there seems to be
>> room for further development.
>
>There is a lot of scope for developing things, but there has been little 
>feedback.
>
>IMV the UX2BS framework is fairly sound but needs a little tidying up here 
>and there and a lot more apps included.
>
>My first milestone is to be able to rebuild all the apps originally 
>downloaded as pre-built binaries, and include them in update_base.cmd 
>which is something that gets run as part of the install. I'm quite close 
>now, although I'm intending to leave gcc alone for the moment, and there 
>doesn't seem to be any prospect at all of rebuilding tar which has now 
>become orphaned. 
>
>After that it is a process of adding more and more apps and finding what 
>environment needs to be set to be able to build and install them 
>successfully.

I've run the bootstrap a couple of times now on a completely
virginal machine, and it works beautifully. Looking a little more
closely into it, I see that a huge amount of work has been done.

Congratulations are due to all concerned.

In line with your mention of "tidying up the framework a little" I've
made a couple of small tweaks to start with.

1. At the bottom of ux2_bootstrap.cmd just before it calls ux2_inst.cmd
I've added:

echo: you may check and adjust the newly installed build scripts if you wish,
echo: otherwise press any key to continue the installation with the defaults.
echo:
pause

This could usefully include references to the locations of scripts.

2. The ux2_inst script was clobbering an existing %etc%/hosts file
so I've changed this

echo 127.0.0.1 localhost>%uxrt%\etc\hosts

to this:

if exist %ETC%\hosts cp -p %ETC%\hosts %uxrt%\etc & goto hosts
echo 127.0.0.1 localhost>%uxrt%\etc\hosts
:hosts

3. The perl patch for 5.8.0 is no good for 5.8.4, as I feared. Also
the existing patch for Find.pm on 5.8.3 is no good for 5.8.4 (the
line numbers have changed) so I've attached an updated patch.
While on perl, I don't understand why build_perl.cmd puts some
stuff into /usr and other stuff into /usr/local. It seems more logical
to me to put it all in one place, and AFAIK this is standard. I would
remove the /usr/local bits and just have /usr. BTW, -Dd_dosuid
built nothing on OS/2 - I don't have my notes any more but perhaps
I just copied perl.exe to suidperl.exe for OpenWebMail.

I'm going to look through the other build system and see what might
be useful. As you say though, UX2BS needs to build packages, not
just get and unzip existing ports. I've got some other ideas in mind
but I want to look through it all first.

 
>> Lyn
>
>
>-- 
>John

Lyn

--_=_=_=IMA.BOUNDARY.HXBAJ0138764=_=_=_
Content-Type: application/octet-stream; name="perl-5.8.4.diff"
Content-Transfer-Encoding: base64

LS0tIHBlcmwtNS44LjQvbGliL0ZpbGUvRmluZC5wbS5vcmlnICAgICAgICBUaHUgTWF5ICA2IDAx
OjU3OjEwIDIwMDQKKysrIHBlcmwtNS44LjQvbGliL0ZpbGUvRmluZC5wbSAgICAgVGh1IE1heSAg
NiAwMzowNToyNCAyMDA0CkBAIC02MjgsNyArNjI4LDcgQEAKICAgICAgICAgICAgICAgIGlmICgg
KC1kIF8pICYmICggJHRvcF9pdGVtICF+IC86LyApICk7CiAgICAgICAgfQogICAgICAgIGVsc2Ug
ewotICAgICAgICAgICAkdG9wX2l0ZW0gPX4gc3wvXHp8fCB1bmxlc3MgJHRvcF9pdGVtIGVxICcv
JzsKKyAgICAgICAgICAgICR0b3BfaXRlbSA9fiBzfC9cenx8IHVubGVzcyAkdG9wX2l0ZW0gPX4g
bTxeKFthLXpdezEsMn06KT8vXHo+aTsKICAgICAgICAgICAgKCR0b3BkZXYsJHRvcGlubywkdG9w
bW9kZSwkdG9wbmxpbmspID0gJGZvbGxvdyA/IHN0YXQgJHRvcF9pdGVtIDogbHN0YXQgJHRvcF9p
dGVtOwogICAgICAgIH0KCkBAIC03NjksNyArNzY5LDcgQEAKICAgICAgICAkZGlyX3ByZWY9ICgk
cF9kaXIgPX4gLzokLykgPyAkcF9kaXIgOiAiJHBfZGlyOiI7ICMgcHJlZmFjZQogICAgIH0KICAg
ICBlbHNlIHsKLSAgICAgICAkZGlyX3ByZWY9ICggJHBfZGlyIGVxICcvJyA/ICcvJyA6ICIkcF9k
aXIvIiApOworICAgICAgICAkZGlyX3ByZWY9ICggJHBfZGlyID1+IG0sL1x6LCA/ICRwX2RpciA6
ICIkcF9kaXIvIiApOwogICAgIH0KCiAgICAgbG9jYWwgKCRkaXIsICRuYW1lLCAkcHJ1bmUsICpE
SVIpOwpAQCAtOTM3LDcgKzkzNyw3IEBACiAgICAgICAgICAgICAgICAkZGlyX3ByZWYgPSAiJGRp
cl9uYW1lOiI7CiAgICAgICAgICAgIH0KICAgICAgICAgICAgZWxzZSB7Ci0gICAgICAgICAgICAg
ICAkZGlyX25hbWUgPSAoJHBfZGlyIGVxICcvJyA/ICIvJGRpcl9yZWwiIDogIiRwX2Rpci8kZGly
X3JlbCIpOworICAgICAgICAgICAgICAgICRkaXJfbmFtZSA9ICgkcF9kaXIgPX4gbTwvXHo+ID8g
IiRwX2RpciRkaXJfcmVsIiA6ICIkcF9kaXIvJGRpcl9yZWwiKTsKICAgICAgICAgICAgICAgICRk
aXJfcHJlZiA9ICIkZGlyX25hbWUvIjsKICAgICAgICAgICAgfQoKQEAgLTEwMDMsOCArMTAwMyw4
IEBACiAgICAgICAgJGRpcl9wcmVmID0gKCRwX2RpciA9fiAvOiQvKSA/ICIkcF9kaXIiIDogIiRw
X2RpcjoiOwogICAgICAgICRsb2NfcHJlZiA9ICgkZGlyX2xvYyA9fiAvOiQvKSA/ICIkZGlyX2xv
YyIgOiAiJGRpcl9sb2M6IjsKICAgICB9IGVsc2UgewotICAgICAgICRkaXJfcHJlZiA9ICggJHBf
ZGlyICAgZXEgJy8nID8gJy8nIDogIiRwX2Rpci8iICk7Ci0gICAgICAgJGxvY19wcmVmID0gKCAk
ZGlyX2xvYyBlcSAnLycgPyAnLycgOiAiJGRpcl9sb2MvIiApOworICAgICAgICRkaXJfcHJlZiA9
ICggJHBfZGlyICAgPX4gbSwvXHosID8gJHBfZGlyIDogIiRwX2Rpci8iICk7CisgICAgICAgJGxv
Y19wcmVmID0gKCAkZGlyX2xvYyA9fiBtLC9ceiwgPyAkZGlyX2xvYyA6ICIkZGlyX2xvYy8iICk7
CiAgICAgfQoKICAgICBsb2NhbCAoJGRpciwgJG5hbWUsICRmdWxsbmFtZSwgJHBydW5lLCAqRElS
KTsKQEAgLTExMjYsNyArMTEyNiw3IEBACiAgICAgICAgICAgICAgICAkbG9jX3ByZWYgPSAoJGRp
cl9sb2MgPX4gLzokLykgPyAkZGlyX2xvYyA6ICIkZGlyX2xvYzoiOwogICAgICAgICAgICB9CiAg
ICAgICAgICAgIGVsc2UgewotICAgICAgICAgICAgICAgJGRpcl9uYW1lID0gKCRwX2RpciBlcSAn
LycgPyAiLyRkaXJfcmVsIiA6ICIkcF9kaXIvJGRpcl9yZWwiKTsKKyAgICAgICAgICAgICAgICAk
ZGlyX25hbWUgPSAoJHBfZGlyID1+IG0sL1x6LCA/ICIkcF9kaXIkZGlyX3JlbCIgOiAiJHBfZGly
LyRkaXJfcmVsIik7CiAgICAgICAgICAgICAgICAkZGlyX3ByZWYgPSAiJGRpcl9uYW1lLyI7CiAg
ICAgICAgICAgICAgICAkbG9jX3ByZWYgPSAiJGRpcl9sb2MvIjsKICAgICAgICAgICAgfQotLS0g
cGVybC01LjguNC9vczIvb3MyLmMub3JpZwlUaHUgTWF5ICA2IDAyOjUyOjI0IDIwMDQKKysrIHBl
cmwtNS44LjQvb3MyL29zMi5jCVRodSBNYXkgIDYgMDM6MDE6MDAgMjAwNApAQCAtMzMsNiArMzMs
MTIgQEAKICNpbmNsdWRlICJFWFRFUk4uaCIKICNpbmNsdWRlICJwZXJsLmgiCgoraW50CitjaG93
bihjb25zdCBjaGFyICpwYXRoLCB1aWRfdCBvd25lciwgZ2lkX3QgZ3JvdXApCit7CisgICAgcmV0
dXJuIDA7ICAvKiBub29wICovCit9CisKIGVudW0gbW9kdWxlX25hbWVfaG93IHsgbW9kX25hbWVf
aGFuZGxlLCBtb2RfbmFtZV9zaG9ydG5hbWUsIG1vZF9uYW1lX2Z1bGwsCiAgIG1vZF9uYW1lX0Nf
ZnVuY3Rpb24gPSAweDEwMCwgbW9kX25hbWVfSE1PRFVMRSA9IDB4MjAwfTsKCi0tLSBwZXJsLTUu
OC40L29zMi9vczJpc2guaC5vcmlnCVRodSBNYXkgIDYgMDE6NTc6MjAgMjAwNAorKysgcGVybC01
LjguNC9vczIvb3MyaXNoLmgJVGh1IE1heSAgNiAwMzowMzowOCAyMDA0CkBAIC0zMCw2ICszMCwx
MSBAQAogICoJVGhlIGdldHB3ZW50KCkgaGFzIGEgc2VwYXJhdGUgZGVmaW5pdGlvbiwgSEFTX0dF
VFBXRU5ULgogICovCiAjZGVmaW5lIEhBU19QQVNTV0QKKyNkZWZpbmUgSEFTX0dFVFBXRU5UCisj
ZGVmaW5lIEhBU19DUllQVAorI2RlZmluZSBIQVNfQ0hPV04KKworZXh0ZXJuIGludCAgICAgY2hv
d24oY29uc3QgY2hhciAqcCwgdWlkX3QgbywgZ2lkX3QgZyk7CgogLyogSEFTX0dST1VQCiAgKglU
aGlzIHN5bWJvbCwgaWYgZGVmaW5lZCwgaW5kaWNhdGVzIHRoYXQgdGhlIGdldGdybmFtKCkgYW5k
Cg==

--_=_=_=IMA.BOUNDARY.HXBAJ0138764=_=_=_
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

--_=_=_=IMA.BOUNDARY.HXBAJ0138764=_=_=_--

**= Email   11 ==========================**

Date:  Thu, 6 May 2004 17:37:27 +0100
From:  John Poltorak <jp at warpix.org>
Subject:  Re:  Problems building readline

On Thu, May 06, 2004 at 05:43:32PM +0200, Davide Bresolin wrote:
> John Poltorak ha scritto:
> 
> > By default, a build will use the Posix/2 headers and library. Sometimes, 
> > this results in errors, but they can be removed from the environment by  
> > adding the app name to \unixos2\lib\p2_exc.lst. When this is done a 
> > libreadline.a and libhistory.a get created, but I have no idea if the 
> > builds are correct. I would appreciate it if you could add this app to 
> > p2_exc.lst and try building readline again, and saying whether the build 
> > is any good.
> Ok, I've just tried doing this.
> Now this is the error that I obtain:
> 
> ( cd shlib ; make  all )
> make[1]: Entering directory `E:/unixos2/workdir/readline-4.3/shlib'
> make[1]: *** No rule to make target `readline.c', needed by 
> `readline.so'.  Stop.
> make[1]: Leaving directory `E:/unixos2/workdir/readline-4.3/shlib'


Yes, I get that too, but if you look in the readline directory you will 
see to newly created library files.

For this to work correctly, it probably needs a patch of some sort.

Here are a couple of ports of readline:-

http://hobbes.nmsu.edu/pub/os2/dev/emx/contrib/gnureadl.zip

http://hobbes.nmsu.edu/pub/os2/dev/unix/readline.zip

and there are a couple of others which I can't find at the moment. It may 
well need some patches from one of those ports to build completely. I will 
gladly incorporate the required patches into UX2BS if someone can tell me 
what those patches should consist of.
 
> -- 
> Ciao...
> 
>         -=> DaViDe <=-
> -=> davide(AT)teamos2.it <=-


-- 
John


_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   12 ==========================**

Date:  Thu, 06 May 2004 17:53:20 +0100 (BST)
From:  "Lyn St George" <lyn at zolotek.net>
Subject:  Re:  UX2 Distribution Install

On Thu, 6 May 2004 16:54:20 +0100, John Poltorak wrote:

>On Fri, May 07, 2004 at 01:30:45AM +1000, IanM wrote:
>> As john said, I view them as two different beasts, for two different
>> purposes. 
>
>They are not entirely different. My aim with UX2BS is to be able to 
>produce PKGs at some point, but I haven't figured out just how to do 
>that yet. I am not keen an _manually_ maintaining any PKGs. The ones  
>already produced took a great deal of time and are virtually 
>unmaintainable. What I'm looking to do at some point in UX2BS is add an 
>extra step at the end - 'make PKG' which will automatically created a 
>distributable package as part of a build. But this is still just an idea 
>and no concrete solution has emerged yet.


I think there needs to be another step in the process - handling
dependencies and dependants. Eg, the classic example of grief
is OpenSSL - whenever this is updated then anything built against
it also needs updating (dependants). OpenSSH relies on 
openssl as a prerequisite dependency and needs to check for
its existence first. The CPAN install system handles this kind of
thing with panache (as opposed to the Redhat Package Mangler
which causes nothing but grief) and I am interested in developing
something to handle this. 


>> So I think we can live with UnixOS2, and Ux2bs, ie, two ways of doing
>> different but similar things, if you see what I mean.
>
>I see UX2BS as a mechanism for creating a UnixOS/2 distro eventually. If 
>not as a set of PKGs, then at least as a single archive of some sort.

I would also see something like this happening. 

>-- 
>John
>
>
>_______________________________________________
>UX2BS mailing list
>UX2BS at os2ports.com
>http://os2ports.com/mailman/listinfo/ux2bs
>


_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   13 ==========================**

Date:  Thu, 6 May 2004 18:51:20 +0100
From:  John Poltorak <jp at warpix.org>
Subject:  Re:  UX2 Distribution Install

On Thu, May 06, 2004 at 05:53:20PM +0100, Lyn St George wrote:
> On Thu, 6 May 2004 16:54:20 +0100, John Poltorak wrote:
> 
> >On Fri, May 07, 2004 at 01:30:45AM +1000, IanM wrote:
> >> As john said, I view them as two different beasts, for two different
> >> purposes. 
> >
> >They are not entirely different. My aim with UX2BS is to be able to 
> >produce PKGs at some point, but I haven't figured out just how to do 
> >that yet. I am not keen an _manually_ maintaining any PKGs. The ones  
> >already produced took a great deal of time and are virtually 
> >unmaintainable. What I'm looking to do at some point in UX2BS is add an 
> >extra step at the end - 'make PKG' which will automatically created a 
> >distributable package as part of a build. But this is still just an idea 
> >and no concrete solution has emerged yet.
> 
> 
> I think there needs to be another step in the process - handling
> dependencies and dependants. 

Yes I am aware of there being dependencies and have been looking into 
creating a large Makefile for handling all the apps. Eventually I would 
like to have a target of unixos2: which would start building every 
buildable app to create the equivalent of a UnixOS/2 distro.


I'm still at an early stage in thinking this out but this is a prototype 
for my Makefile:-


mailman: python 
	build $ at 


python: ncurses readline gdbm zlib expat gmp crypt
	build $ at 

..DEFAULT:
	build $<

..SILENT:

So instead of running 'build appX', I can run 'make appX' and the Makefile 
will run 'build appX' after first building all the apps which appX is 
dependent on. If appX is not explicitly mentioned as a target in the 
Makefile, it will follow the .DEFAULT: target. 


I'm not sure if that is the best way of doing it, but that is what I have 
thought of so far.



> Eg, the classic example of grief
> is OpenSSL - whenever this is updated then anything built against
> it also needs updating (dependants). OpenSSH relies on 
> openssl as a prerequisite dependency and needs to check for
> its existence first. The CPAN install system handles this kind of
> thing with panache (as opposed to the Redhat Package Mangler
> which causes nothing but grief) and I am interested in developing
> something to handle this. 
> 
> 
> >> So I think we can live with UnixOS2, and Ux2bs, ie, two ways of doing
> >> different but similar things, if you see what I mean.
> >
> >I see UX2BS as a mechanism for creating a UnixOS/2 distro eventually. If 
> >not as a set of PKGs, then at least as a single archive of some sort.
> 
> I would also see something like this happening. 

There may well be something within the GNU Build System which can be 
utilised. Some Makefiles have targets which mention rpm and this might be 
there to facilitate the creation of a binary RPM package for all I know.

This is how I would like PKGs to be created, but I don't yet know how 
feasible this would be.


-- 
John


_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   14 ==========================**

Date:  Thu, 6 May 2004 19:01:47 +0100
From:  John Poltorak <jp at warpix.org>
Subject:  Re:  Problems building readline

On Thu, May 06, 2004 at 06:21:10PM +0200, Davide Bresolin wrote:
> Davide Bresolin ha scritto:
> 
> >> By default, a build will use the Posix/2 headers and library. 
> >> Sometimes, this results in errors, but they can be removed from the 
> >> environment by  adding the app name to \unixos2\lib\p2_exc.lst. When 
> >> this is done a libreadline.a and libhistory.a get created, but I have 
> >> no idea if the builds are correct. I would appreciate it if you could 
> >> add this app to p2_exc.lst and try building readline again, and saying 
> >> whether the build is any good.
> > 
> > Ok, I've just tried doing this.
> > Now this is the error that I obtain:
> > 
> > ( cd shlib ; make  all )
> > make[1]: Entering directory `E:/unixos2/workdir/readline-4.3/shlib'
> > make[1]: *** No rule to make target `readline.c', needed by 
> > `readline.so'.  Stop.
> > make[1]: Leaving directory `E:/unixos2/workdir/readline-4.3/shlib'
> 
> Some good news: apart from this errors, I could get the readline 
> examples working, after some changes on Makefile: it creates files with 
> no extensions (unix-like) instead of .exe files.

Can you let me know what changes are required?

The changes themselves should be applied to Makefile.in because of the way 
UX2BS works - ie the default build method is to process a configure.in 
file to recreate configure, which is then run to build a Makefile using 
Makefile.in as an input file.

Sometimes the addition of an  at EXEEXT at  in the right place is sufficient to 
get the outcome you want.

> Furthermore it creates libreadline.a instead of readline.a, as aspected 
> by gcc when building the examples. Renaming the file solves the problem.

A simple change to Makefile.in would achieve that. I can create a patch to 
do that quite easily.
 
> My next step would be trying to compile SWI-prolog, that requires 
> readline.....

I'll be interested to see how you get on.
 
> -- 
> Ciao...
> 
>         -=> DaViDe <=-
> -=> davide(AT)teamos2.it <=-


-- 
John


_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   15 ==========================**

Date:  Thu, 6 May 2004 19:14:24 +0100
From:  John Poltorak <jp at warpix.org>
Subject:  Re:  UX2 Distribution Install

On Fri, May 07, 2004 at 02:09:34AM +1000, IanM wrote:

> Yes, it would be a good way to keep a lot of UnixOS2 upto date, ie, by
> running Ux2bs but there will always be other utilities needed that are
> not a part of Ux2bs, and may never be due to updated code etc, 

Even if they are not updated, I would want to be able to build them from 
source. This would make them more maintainable and we would be reliant on 
the original porterin the event of any problems.

> though
> in saying that, there is a lot that can be done with Ux2bs out of the box
> so to speak.

UX2BS is still very much an experimental framework. It contains a mixture 
of apps which build completely, nearly, a bit and not at all, and there is 
no indication of what category a particular app falls into.

At some point I would want to create a split between apps which work 
properly and those which are still in a test phase so that people know 
what they can rely on. At the moment they don't.


> Cheers
> IanM
> http://www.os2site.com/
> 
> "make lots of money",  "enjoy the work",  "operate within the law":  choose 2 -- Brian Anderson


-- 
John



_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   16 ==========================**

Date:  Thu, 6 May 2004 20:17:21 +0100
From:  John Poltorak <jp at warpix.org>
Subject:  Re:  Problems building readline

On Thu, May 06, 2004 at 05:37:27PM +0100, John Poltorak wrote:

> Here are a couple of ports of readline:-
> 
> http://hobbes.nmsu.edu/pub/os2/dev/emx/contrib/gnureadl.zip
> 
> http://hobbes.nmsu.edu/pub/os2/dev/unix/readline.zip


And a couple more:-

http://www.os2site.com/sw/util/gnu/readline4.1-os2.zip

http://download.innotek.de/gccos2/3.2.2-Beta4/ports/readline-4.3.zip
http://download.innotek.de/gccos2/3.2.2-Beta4/ports/readline-4.3-source.zip



As I said, I don't have much idea about readline, but it seems to be one 
of the basic apps that is needed in the building of other apps, so I would 
like to include in UX2BS, everything required to build an uptodate version 
capable of being used in the building of all apps which require it.


-- 
John





_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   17 ==========================**

Date:  Thu, 6 May 2004 20:44:42 +0100
From:  John Poltorak <jp at warpix.org>
Subject:  Re:  Succes on JFS, perl

On Thu, May 06, 2004 at 05:33:00PM +0100, Lyn St George wrote:
> On Wed, 5 May 2004 15:07:08 +0100, John Poltorak wrote:
> 
> >On Wed, May 05, 2004 at 02:30:41PM +0100, Lyn St George wrote:
> >> It seems to be all OK now, 
> >
> >Your crashed disk didn't detain you long....
> >
> >If I had lost 14GB, I'd be fairly distraught.
> 
> Distraught - the sobs should be audible from the next planet ...

I'm not surprised :-(

> >> I see in the "wrong" files from unixos2.com that there are some
> >> impressive references to symlinks. Is this currently working?
> >
> >I don't really know anything about it.
> 
> I will investigate this further. 

I know Marty Amodeo did something with symlinks but I never checked it 
out.

> I've run the bootstrap a couple of times now on a completely
> virginal machine, and it works beautifully. Looking a little more
> closely into it, I see that a huge amount of work has been done.

It's taken around two years to get so far and involved a great deal of 
head scratching and hair pulling. 

> Congratulations are due to all concerned.

Yes, it has involved a lot of sharing of expertise, sometimes just the 
tinyest of snippets of code or advice on obscure options that one wouldn't 
normally come across.

 
> In line with your mention of "tidying up the framework a little" I've
> made a couple of small tweaks to start with.
> 
> 1. At the bottom of ux2_bootstrap.cmd just before it calls ux2_inst.cmd
> I've added:
> 
> echo: you may check and adjust the newly installed build scripts if you wish,
> echo: otherwise press any key to continue the installation with the defaults.
> echo:
> pause
> 
> This could usefully include references to the locations of scripts.
> 
> 2. The ux2_inst script was clobbering an existing %etc%/hosts file
> so I've changed this
> 
> echo 127.0.0.1 localhost>%uxrt%\etc\hosts
> 
> to this:
> 
> if exist %ETC%\hosts cp -p %ETC%\hosts %uxrt%\etc & goto hosts
> echo 127.0.0.1 localhost>%uxrt%\etc\hosts
> :hosts

I thought there might be a chance of clobbering some files in someone's 
%ETC% directory but didn't think it would be too risky.

 
> 3. The perl patch for 5.8.0 is no good for 5.8.4, as I feared. Also
> the existing patch for Find.pm on 5.8.3 is no good for 5.8.4 (the
> line numbers have changed) so I've attached an updated patch.

So it wasn't a typo and 5.8.4 is out now?

Are you the first person to have built Perl 5.8.4 on OS/2? In theory, all 
that is needed is to change the entry for perl in build.table to 5.8.4 
before running 'build perl'

> While on perl, I don't understand why build_perl.cmd puts some
> stuff into /usr and other stuff into /usr/local. It seems more logical
> to me to put it all in one place, and AFAIK this is standard. I would
> remove the /usr/local bits and just have /usr. 

The reason was that it was becoming too cluttered. I only wanted perl.exe 
in /usr/bin.

> BTW, -Dd_dosuid
> built nothing on OS/2 - I don't have my notes any more but perhaps
> I just copied perl.exe to suidperl.exe for OpenWebMail.
> 
> I'm going to look through the other build system and see what might
> be useful. As you say though, UX2BS needs to build packages, not
> just get and unzip existing ports. I've got some other ideas in mind
> but I want to look through it all first.

Essentially, there is a default build process which includes these steps:-

wget
tar zxf
patch
autoconf
configure
make
make install


and then there are little bits here and there to try and make awkward apps 
conform to this standard process.

The missing piece from the process is:-

make PKG 

which will hopefully be added on to the end at some point.

In the mean time, there is also a matter of reviewing the build time 
options such a CFLAGS to see if the best build is getting produced. There 
is also a matter of getting some of the apps to install as they are 
bypassing the install step.


> Lyn

-- 
John


_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   18 ==========================**

Date:  Thu, 6 May 2004 20:40:13 -0500
From:  Anton Monroe <akm at meer.net>
Subject:  Re:  Any success?

On Fri, Apr 30, 2004 at 02:05:42PM +0100, John Poltorak wrote:
> What do you get when you run emxrev in the session started up whe you run 
> 'build'?

It turned out that's where the problem is.  EMXREV.CMD works before I
run 'build', but not after.  I inserted a call to emxrev after every
line in ux2_env.cmd to see where emxrev gets broken.  It was the "set
dpath" statement.

I changed 
   set DPATH=h:\os2\system
to
   set DPATH=h:\os2;h:\os2\system
   
Now emxrev.cmd works, hints/os2.sh returns the right value, and Perl
compiles. I won't try to figure out why emxrev needs dpath, I've torn
out too much hair today already.

Anton   


_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   19 ==========================**

Date:  Thu, 6 May 2004 23:38:57 -0500
From:  Anton Monroe <akm at meer.net>
Subject:  Re:  Succes on JFS, perl

On Thu, May 06, 2004 at 05:33:00PM +0100, Lyn St George wrote:
> 1. At the bottom of ux2_bootstrap.cmd just before it calls ux2_inst.cmd
> I've added:
> 
> echo: you may check and adjust the newly installed build scripts if you wish,
> echo: otherwise press any key to continue the installation with the defaults.
> echo:
> pause
> 
> This could usefully include references to the locations of scripts.

I like that.  A tweak I've made on my copy of ux2_bootstrap.cmd is to
have it call a script called ux2_init.cmd.  That script sets all the
variables, like %uxrt% and %repository%, so I don't have to re-edit 
everything in ux2_bootstrap.cmd every time it changes.  You could also
use it to set things like %path%, to make sure the existing environment
doesn't create problems.  So the beginning of ux2_bootstrap.cmd might
look like this:

   rem   default values:
   set osrt=c:
   set bldrt=c:
   set uxrt=c:
   set bld_home=unixos2
   set host=213.152.37.92

   rem   anything set in ux2_init.cmd will override the default value:
   if exist ux2_init.cmd call ux2_init.cmd

   echo:      * osrt is where OS/2 boots from.
   echo:
   echo:                  - currently %osrt%


Anton
_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   20 ==========================**

Date:  Thu, 6 May 2004 23:53:22 -0500
From:  Anton Monroe <akm at meer.net>
Subject:   Error compiling BYACC-20040328

>From byacc.log:

  DIR URL CFLAGS LDFLAGS CFGPARMS MAKEPARM SRC
  ftp://invisible-island.net/byacc/byacc-20040328.tgz -Zomf -O2 -s -Zmt -D__ST_MT_ERRNO__ -Zcrtdll -Zlinker /exepack:2 -Zlinker /pm:vio --prefix=/usr --mandir=/usr/share/man .
  URL ftp://invisible-island.net/byacc/byacc-20040328.tgz
  CFLAGS -Zomf -O2 -s -Zmt -D__ST_MT_ERRNO__
  LDFLAGS -Zcrtdll -Zlinker /exepack:2 -Zlinker /pm:vio
  CFGPARMS --prefix=/usr --mandir=/usr/share/man
  MAKEPARM
  SRC .
  retrieving byacc-20040328.tgz
  m:/unixos2/workdir
  m:/unixos2/workdir/byacc-20040328
  byacc-20040328
  using byacc specific Build script
  make: *** No targets specified and no makefile found.  Stop.
  install: yacc.exe: No such file or directory
  
It's right, there's no makefile.

Anton  
_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   21 ==========================**

Date:  Fri, 07 May 2004 10:12:57 +0200
From:  Davide Bresolin <davide at teamos2.it>
Subject:  Re:  Problems building readline

John Poltorak ha scritto:

>>Some good news: apart from this errors, I could get the readline 
>>examples working, after some changes on Makefile: it creates files with 
>>no extensions (unix-like) instead of .exe files.
> 
> Can you let me know what changes are required?

Ok, the changes I have made are the following:

   1. rename libreadline.a into readline.a, such that gcc could find it;
   2. in the directory examples, I have made the following changes to 	
      Makefile:

      EXECUTABLES = fileman.exe rltest.exe rl.exe rlcat.exe 
rlversion.exe
                    histexamp.exe
      [...]
      rl.exe: rl.o $(READLINE_LIB)
	
      and so on for rltest.exe, fileman.exe ....
      Previously the filenames was without .exe extensions.

> Sometimes the addition of an  at EXEEXT at  in the right place is sufficient to 
> get the outcome you want.

Ok, some suggestions on where I could try to place it?

As for the errors that I have, I've figured out that the problems is in 
building the shared libraries. If you run
	sh configure --enable-shared=no
you build only the static (.a) versions, and there are no errors, apart 
from the fact that it builds libreadline.a instead of readline.a

There is a section in the README that explains how to get shared 
libraries working:

"There is skeletal support for building shared versions of the
Readline and History libraries.  The configure script creates
a Makefile in the `shlib' subdirectory, and typing `make shared'
will cause shared versions of the Readline and History libraries
to be built on supported platforms.

If `configure' is given the `--enable-shared' option, it will attempt
to build the shared libraries by default on supported platforms.
Configure calls the script support/shobj-conf to test whether or
not shared library creation is supported and to generate the values
of variables that are substituted into shlib/Makefile.

If you need to update support/shobj-conf, you will need to create
a `stanza' for your operating system and compiler."

The fact is that there is no 'stanza' in shobj-conf for emx-os2, and the 
  shared libs cannot be correctly built. If someone can figure out how 
to add os2 support to shobj-conf, probably we will get the shared libs also.

-- 
Ciao...

        -=> DaViDe <=-
-=> davide(AT)teamos2.it <=-
_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   22 ==========================**

Date:  Fri, 7 May 2004 09:47:18 +0100
From:  John Poltorak <jp at warpix.org>
Subject:  Re:  Any success?

On Thu, May 06, 2004 at 08:40:13PM -0500, Anton Monroe wrote:
> On Fri, Apr 30, 2004 at 02:05:42PM +0100, John Poltorak wrote:

> It turned out that's where the problem is.  EMXREV.CMD works before I
> run 'build', but not after.  I inserted a call to emxrev after every
> line in ux2_env.cmd to see where emxrev gets broken.  It was the "set
> dpath" statement.
> 
> I changed 
>    set DPATH=h:\os2\system
> to
>    set DPATH=h:\os2;h:\os2\system

Nice to see you get the problem sorted.

    
> Now emxrev.cmd works, hints/os2.sh returns the right value, and Perl
> compiles. I won't try to figure out why emxrev needs dpath

It's probably because it needs to be able to access REX.MSG and REXH.MSG 
which are normally in \os2\system.


> Anton   


-- 
John


_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   23 ==========================**

Date:  Fri, 7 May 2004 10:01:57 +0100
From:  John Poltorak <jp at warpix.org>
Subject:  Re:  Error compiling BYACC-20040328

On Thu, May 06, 2004 at 11:53:22PM -0500, Anton Monroe wrote:
> >From byacc.log:
> 
>   DIR URL CFLAGS LDFLAGS CFGPARMS MAKEPARM SRC
>   ftp://invisible-island.net/byacc/byacc-20040328.tgz -Zomf -O2 -s -Zmt -D__ST_MT_ERRNO__ -Zcrtdll -Zlinker /exepack:2 -Zlinker /pm:vio --prefix=/usr --mandir=/usr/share/man .
>   URL ftp://invisible-island.net/byacc/byacc-20040328.tgz
>   CFLAGS -Zomf -O2 -s -Zmt -D__ST_MT_ERRNO__
>   LDFLAGS -Zcrtdll -Zlinker /exepack:2 -Zlinker /pm:vio
>   CFGPARMS --prefix=/usr --mandir=/usr/share/man
>   MAKEPARM
>   SRC .
>   retrieving byacc-20040328.tgz
>   m:/unixos2/workdir
>   m:/unixos2/workdir/byacc-20040328
>   byacc-20040328
>   using byacc specific Build script

I think I know what is happening here...

Do you have a \unixos2\scripts\build\build_byacc.cmd ?

If so you need to delete it. This is what was used in the past but has not 
been required for a couple of weeks. Unfortunately ux2_refresh updates 
your build system by providing you with more recent files but does not 
remove redundant ones, and because of the existance of this file the wrong 
build script is invoked.

Since BYACC is a fairly critical app, then a number of subsequent apps may 
also have failed to build correctly.

I would be tempted, after deleting build_byacc.cmd, to re-run 
update_base.cmd.

> Anton  


-- 
John



_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   24 ==========================**

Date:  Fri, 07 May 2004 11:59:21 +0200
From:  Davide Bresolin <davide at teamos2.it>
Subject:   Trying to build SWI-prolog

Ok, now that I get readline working, I'm trying to compile SWI-prolog.

After a sh configure, I do a 'make' with the following results:

make.exe[1]: Entering directory `E:/sources/pl-5.2.13/src'
****************
Making SWI-Prolog 5.2.13 for i386-os2-emx
To be installed in /usr/local/bin/pl
Home (libraries) in /usr/local/lib/pl-5.2.13
****************
awk: cmd. line:2: { printf(#define
awk: cmd. line:2:          ^ syntax error

There is some awk-expert that can figure out what is the error?

-- 
Ciao...

        -=> DaViDe <=-
-=> davide(AT)teamos2.it <=-
_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   25 ==========================**

Date:  Fri, 7 May 2004 11:03:06 +0100
From:  John Poltorak <jp at warpix.org>
Subject:  Re:  Problems building readline


--maP5Qt4Y8Qv+FiKc
Content-Type: text/plain; charset=us-ascii

On Fri, May 07, 2004 at 10:12:57AM +0200, Davide Bresolin wrote:
> John Poltorak ha scritto:
> 
> >>Some good news: apart from this errors, I could get the readline 
> >>examples working, after some changes on Makefile: it creates files with 
> >>no extensions (unix-like) instead of .exe files.
> > 
> > Can you let me know what changes are required?
> 
> Ok, the changes I have made are the following:
> 
>    1. rename libreadline.a into readline.a, such that gcc could find it;

I've created a patch which should be attached. This should be called 
readline-4.3.diff and placed in \unixos2\patches. It will correct that
problem. 

> > Sometimes the addition of an  at EXEEXT at  in the right place is sufficient to 
> > get the outcome you want.
> 
> Ok, some suggestions on where I could try to place it?

I was hoping Andreas Buening would jump in here. He's the expert on 
 at EXEEXT at .
 
> As for the errors that I have, I've figured out that the problems is in 
> building the shared libraries. If you run
> 	sh configure --enable-shared=no

The entry for readline in build.table should be ammended to include this 
as a configure parameter if you want it to be used automatically.

> If you need to update support/shobj-conf, you will need to create
> a `stanza' for your operating system and compiler."
> 
> The fact is that there is no 'stanza' in shobj-conf for emx-os2, and the 
>   shared libs cannot be correctly built. If someone can figure out how 
> to add os2 support to shobj-conf, probably we will get the shared libs also.

It only seems to require a few entries...

Would any of these entries be applicable to OS/2:-  ?

bsdi4*)
	# BSD/OS 4.x now supports ELF and SunOS-style dynamically-linked
	# shared libraries.  gcc 2.x is the standard compiler, and the
	# `normal' gcc options should work as they do in Linux.

	SHOBJ_CFLAGS=-fPIC
	SHOBJ_LD='${CC}'
	SHOBJ_LDFLAGS='-shared -Wl,-soname,$ at '

	SHLIB_XLDFLAGS='-Wl,-soname,`basename $ at  $(SHLIB_MINOR)`'
	SHLIB_LIBVERSION='$(SHLIB_LIBSUFF).$(SHLIB_MAJOR)$(SHLIB_MINOR)'
	;;



Maybe something could be gleaned from either of these ports:- 

http://www.os2site.com/sw/util/gnu/readline4.1-os2.zip

http://download.innotek.de/gccos2/3.2.2-Beta4/ports/readline-4.3-source.zip


It would be nice to see it getting built properly straight out of the box.


 
> -- 
> Ciao...
> 
>         -=> DaViDe <=-
> -=> davide(AT)teamos2.it <=-


-- 
John


--maP5Qt4Y8Qv+FiKc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment;
	filename="P:\\unixos2\\patches\\readline-4.3.diff"

--- readline-4.3/Makefile.in.org	Thu Jan 24 15:15:24 2002
+++ readline-4.3/Makefile.in	Fri May  7 10:08:38 2004
 at  at  -83,8 +83,8  at  at 
 	$(CC) -c $(CCFLAGS) $<
 
 # The name of the main library target.
-LIBRARY_NAME = libreadline.a
-STATIC_LIBS = libreadline.a libhistory.a
+LIBRARY_NAME = readline.a
+STATIC_LIBS = readline.a history.a
 
 # The C code source files for this library.
 CSOURCES = $(srcdir)/readline.c $(srcdir)/funmap.c $(srcdir)/keymaps.c \
 at  at  -137,12 +137,12  at  at 
 
 static: $(STATIC_LIBS)
 
-libreadline.a: $(OBJECTS)
+readline.a: $(OBJECTS)
 	$(RM) $ at 
 	$(AR) $(ARFLAGS) $ at  $(OBJECTS)
 	-test -n "$(RANLIB)" && $(RANLIB) $ at 
 
-libhistory.a: $(HISTOBJ) xmalloc.o
+history.a: $(HISTOBJ) xmalloc.o
 	$(RM) $ at 
 	$(AR) $(ARFLAGS) $ at  $(HISTOBJ) xmalloc.o
 	-test -n "$(RANLIB)" && $(RANLIB) $ at 
 at  at  -153,8 +153,8  at  at 
 	rm -f $ at 
 	$(CC) $(CCFLAGS) -DREADLINE_LIBRARY -c $(srcdir)/tilde.c
 
-readline: $(OBJECTS) readline.h rldefs.h chardefs.h ./libreadline.a
-	$(CC) $(CCFLAGS) -o $ at  ./examples/rl.c ./libreadline.a ${TERMCAP_LIB}
+readline: $(OBJECTS) readline.h rldefs.h chardefs.h ./readline.a
+	$(CC) $(CCFLAGS) -o $ at  ./examples/rl.c ./readline.a ${TERMCAP_LIB}
 
 lint:	force
 	$(MAKE) $(MFLAGS) CCFLAGS='$(GCC_LINT_CFLAGS)' static
 at  at  -208,12 +208,12  at  at 
 install:	$(INSTALL_TARGETS)
 
 install-static: installdirs $(STATIC_LIBS) install-headers
-	-$(MV) $(DESTDIR)$(libdir)/libreadline.a $(DESTDIR)$(libdir)/libreadline.old
-	$(INSTALL_DATA) libreadline.a $(DESTDIR)$(libdir)/libreadline.a
-	-test -n "$(RANLIB)" && $(RANLIB) $(DESTDIR)$(libdir)/libreadline.a
-	-$(MV) $(DESTDIR)$(libdir)/libhistory.a $(DESTDIR)$(libdir)/libhistory.old
-	$(INSTALL_DATA) libhistory.a $(DESTDIR)$(libdir)/libhistory.a
-	-test -n "$(RANLIB)" && $(RANLIB) $(DESTDIR)$(libdir)/libhistory.a
+	-$(MV) $(DESTDIR)$(libdir)/readline.a $(DESTDIR)$(libdir)/readline.old
+	$(INSTALL_DATA) readline.a $(DESTDIR)$(libdir)/readline.a
+	-test -n "$(RANLIB)" && $(RANLIB) $(DESTDIR)$(libdir)/readline.a
+	-$(MV) $(DESTDIR)$(libdir)/history.a $(DESTDIR)$(libdir)/history.old
+	$(INSTALL_DATA) history.a $(DESTDIR)$(libdir)/history.a
+	-test -n "$(RANLIB)" && $(RANLIB) $(DESTDIR)$(libdir)/history.a
 	-( if test -d doc ; then \
 		cd doc && \
 		${MAKE} ${MFLAGS} infodir=$(infodir) DESTDIR=${DESTDIR} install; \
 at  at  -226,7 +226,7  at  at 
 
 uninstall: uninstall-headers
 	-test -n "$(DESTDIR)$(libdir)" && cd $(DESTDIR)$(libdir) && \
-		${RM} libreadline.a libreadline.old libhistory.a libhistory.old $(SHARED_LIBS)
+		${RM} readline.a readline.old history.a history.old $(SHARED_LIBS)
 	-( if test -d doc ; then \
 		cd doc && \
 		${MAKE} ${MFLAGS} infodir=$(infodir) DESTDIR=${DESTDIR} $ at ; \

--maP5Qt4Y8Qv+FiKc
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

--maP5Qt4Y8Qv+FiKc--



**= Email   26 ==========================**

Date:  Fri, 7 May 2004 11:15:24 +0100
From:  John Poltorak <jp at warpix.org>
Subject:  Re:  Trying to build SWI-prolog

On Fri, May 07, 2004 at 11:59:21AM +0200, Davide Bresolin wrote:
> Ok, now that I get readline working, I'm trying to compile SWI-prolog.

Do you have a URL for prolog?

 
> After a sh configure, I do a 'make' with the following results:
> 
> make.exe[1]: Entering directory `E:/sources/pl-5.2.13/src'
> ****************
> Making SWI-Prolog 5.2.13 for i386-os2-emx
> To be installed in /usr/local/bin/pl
> Home (libraries) in /usr/local/lib/pl-5.2.13
> ****************
> awk: cmd. line:2: { printf(#define
> awk: cmd. line:2:          ^ syntax error
> 
> There is some awk-expert that can figure out what is the error?

Is this running in a shell or under cmd.exe?

 
> -- 
> Ciao...
> 
>         -=> DaViDe <=-
> -=> davide(AT)teamos2.it <=-


-- 
John



_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   27 ==========================**

Date:  Fri, 7 May 2004 12:16:15 +0100
From:  John Poltorak <jp at warpix.org>
Subject:   BerkeleyDB


Building BerkeleyDB *almost* works out of the box using UX2BS, and should 
actually build properly if I could make a slight adjustment to this 
patch:-

ftp://ftp.zolotek.net/os2/patch.db-4.1.25

I think it only needs a very slight modification in terms of the location 
of the changes to Makefile.in but I just can't figure where they should be 
move to...

I'm sure someone knows exactly where that should be ;-)...

-- 
John



_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   28 ==========================**

Date:  Fri, 07 May 2004 13:26:13 +0200
From:  Davide Bresolin <davide at teamos2.it>
Subject:  Re:  Trying to build SWI-prolog

John Poltorak ha scritto:

> Do you have a URL for prolog?
Main site is  http://www.swi-prolog.org/
The full source can be downloaded at:
http://www.swi.psy.uva.nl/cgi-bin/nph-download/SWI-Prolog/pl-5.2.13.tar.gz

> Is this running in a shell or under cmd.exe?
It was running under cmd.exe. If you put $(SHELL)=sh.exe in Makefile it 
works correctly. Now it complains about some gcc command-options that 
are version 3.x specific. I'will check if it can compile correctly 
simply by removing them, or if it really needs gcc 3.x


-- 
Ciao...

        -=> DaViDe <=-
-=> davide(AT)teamos2.it <=-
_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   29 ==========================**

Date:  Fri, 7 May 2004 13:01:08 +0100
From:  John Poltorak <jp at warpix.org>
Subject:  Re:  Trying to build SWI-prolog

On Fri, May 07, 2004 at 01:26:13PM +0200, Davide Bresolin wrote:
> John Poltorak ha scritto:
> 
> > Do you have a URL for prolog?
> Main site is  http://www.swi-prolog.org/
> The full source can be downloaded at:
> http://www.swi.psy.uva.nl/cgi-bin/nph-download/SWI-Prolog/pl-5.2.13.tar.gz


I'm intending to update build.table with:-

prolog;;http://www.swi.psy.uva.nl/cgi-bin/nph-download/SWI-Prolog/pl-5.2.13.tar.gz;;;;;.

 
> > Is this running in a shell or under cmd.exe?
> It was running under cmd.exe. If you put $(SHELL)=sh.exe in Makefile it 
> works correctly. 

This is solved by:-

echo export MAKESHELL=/bin/sh >\unixos2\scripts\pre-process\prolog

> Now it complains about some gcc command-options that 
> are version 3.x specific. I'will check if it can compile correctly 
> simply by removing them, or if it really needs gcc 3.x

I'm holding off migrating to gcc 3.x until I can get a number of other key
apps such as readline etc built, but the intention is to update as soon as 
practical.

Many thanks for trying out a few things in UX2BS. I'm sorry it doesn't 
build prolog out of the box yet, but I'm sure it will be able to in due 
course.
 
 
> -- 
> Ciao...
> 
>         -=> DaViDe <=-
> -=> davide(AT)teamos2.it <=-


-- 
John



_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   30 ==========================**

Date:  Fri, 7 May 2004 07:32:15 -0500
From:  Anton Monroe <akm at meer.net>
Subject:  Re:  Any success?

On Fri, May 07, 2004 at 09:47:18AM +0100, John Poltorak wrote:
> > Now emxrev.cmd works, hints/os2.sh returns the right value, and Perl
> > compiles. I won't try to figure out why emxrev needs dpath
> 
> It's probably because it needs to be able to access REX.MSG and REXH.MSG 
> which are normally in \os2\system.

My REX.MSG and REXH.MSG are in \os2\system, but it looks like there are some
other Rexx-related files in \os2.  Maybe it's a peculiarity of Warp 3.

Anton
_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   31 ==========================**

Date:  Fri, 7 May 2004 07:27:29 -0500
From:  Anton Monroe <akm at meer.net>
Subject:  Re:  Error compiling BYACC-20040328

On Fri, May 07, 2004 at 10:01:57AM +0100, John Poltorak wrote:
> I think I know what is happening here...
> 
> Do you have a \unixos2\scripts\build\build_byacc.cmd ?
> 
> If so you need to delete it. This is what was used in the past but has not 
> been required for a couple of weeks. Unfortunately ux2_refresh updates 
> your build system by providing you with more recent files but does not 
> remove redundant ones, and because of the existance of this file the wrong 
> build script is invoked.

That's it.  I can't blame it on ux2_refresh, though.  I try to do a
completely clean install before I post any feedback, but it's usually
from the rsync server on my Linux machine. It keeps a mirror of your
build_system and baseline modules.  (It's faster and doesn't tie up my
phone line).  But I left out a "--delete" from one of the rsync
parameters so my mirror had a leftover build_byacc.cmd.  Thanks.

Anton
_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs