Date: Fri, 28 Mar 2003 02:39:21 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [Ux2bs_Archive] No. 118 ************************************************** Thursday 27 March 2003 Number 118 ************************************************** Subjects for today 1 Re: Autoconf error...? : John Poltorak 2 Re: Autoconf error...? : Hannes Hromadka 3 Re: Building Apache : John Poltorak 4 Re: Autoconf error...? : Hannes Hromadka 5 Building Perl with gcc v3.2.1 : John Poltorak 6 Re: Autoconf error...? : John Poltorak 7 Re: Building READLINE : sma at sohnen-moe.com 8 Re: Mozilla : Henry Sobotka 9 Re: Mozilla : Henry Sobotka 10 Re: Building Perl with gcc v3.2.1 : sma at sohnen-moe.com 11 Re: Mozilla : John Poltorak 12 Building READLINE : John Poltorak 13 GNU Text Utils v2.0 : John Poltorak 14 Re: Mozilla : John Poltorak **= Email 1 ==========================** Date: Fri, 28 Mar 2003 09:43:32 +0000 From: John Poltorak Subject: Re: Autoconf error...? On Thu, Mar 27, 2003 at 08:08:23PM -0700, Sohnen-Moe Associates, Inc wrote: > On Thu, 27 Mar 2003 21:22:56 +0000, John Poltorak wrote: > > >./configure[12809]: syntax error: `done' unexpected > > > >This was a configure script created by running Autoconf (v2.57) > > > I have seen this, too, while trying to build GnuPG v1.2.x. If I done the > line with the spurious "done", I get another error later on which is > clearly a bungled output from autoconf: incomplete code. > I haven't had time to work on this yet. Maybe this weekend I'll try a > different version of autoconf. 2.57 is the most recent version and it looks as though is has a bug, but I have no idea how to pinpoint the source of the error. Any suggestions from anyone?.... -- John _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 2 ==========================** Date: Fri, 28 Mar 2003 09:53:59 +0100 From: Hannes Hromadka Subject: Re: Autoconf error...? --===============45457220873337567== Content-Type: application/pgp; x-action=sign; format=text Content-Disposition: inline; filename="msg.pgp" -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, Mar 27, 2003 at 08:08:23PM -0700, Sohnen-Moe Associates, Inc wrote: > I have seen this, too, while trying to build GnuPG v1.2.x. If I done the > line with the spurious "done", I get another error later on which is > clearly a bungled output from autoconf: incomplete code. I can add a "me too" here. I got such an error when trying to run the full configuration for slrn Ciao, Hannes - -- Johannes Hromadka | Email Office: HromadkaJ at gmx.at | Home : Johannes.Hromadka at gmx.net Vienna/Austria/Europe | OECC: http://www.oecc.org/ >>> Rust never sleeps (borrowed from Neil YOUNG) <<< -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Weitere Infos: siehe http://www.gnupg.org iD8DBQE+hA2n4DqFEwSHQSwRAmmeAKDkki3rIQJIJAbvSxchJ2hwaXr+lQCguETs FpZpKmq2Ncc2rDo8AB4z82k= =O3IJ -----END PGP SIGNATURE----- --===============45457220873337567== 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 --===============45457220873337567==-- **= Email 3 ==========================** Date: Fri, 28 Mar 2003 10:27:25 +0000 From: John Poltorak Subject: Re: Building Apache On Wed, Mar 26, 2003 at 10:53:41AM -0700, sma at sohnen-moe.com wrote: > > > >I guess I don't have a 'true'. There isn't one in UX2BS so this must be > > something you have supplied yourself... > > > Ah, yes, that's true (har, har). > Here is my "true" program (the whole thing, complete): > > > void main () > { > ; > } I guess until we add an updated version of GNU Shell Utils which does include true.exe (and false.exe), I add a couple of REXX programs to UX2BS... This is true.cmd:- /* REXX */ return 0 -- John _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 4 ==========================** Date: Fri, 28 Mar 2003 11:15:16 +0100 From: Hannes Hromadka Subject: Re: Autoconf error...? Uups, I forgot to disable pgp signing. Many mailprogs, and maillistsoftware too have problems with pgp-mime 8-( On Fri, Mar 28, 2003 at 09:53:59AM +0100, Hannes Hromadka wrote: > On Thu, Mar 27, 2003 at 08:08:23PM -0700, Sohnen-Moe Associates, Inc wrote: > > > I have seen this, too, while trying to build GnuPG v1.2.x. If I done the > > line with the spurious "done", I get another error later on which is > > clearly a bungled output from autoconf: incomplete code. > I can add a "me too" here. I got such an error when trying to run the full configuration for slrn Ciao, Hannes -- Johannes Hromadka | Email Office: HromadkaJ at gmx.at | Home : Johannes.Hromadka at gmx.net Vienna/Austria/Europe | OECC: http://www.oecc.org/ >>> Rust never sleeps (borrowed from Neil YOUNG) <<< _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 5 ==========================** Date: Fri, 28 Mar 2003 12:04:10 +0000 From: John Poltorak Subject: Building Perl with gcc v3.2.1 Has anyone tried building Perl with gcc v3.2.1? I'd like to update gcc in the near future and would be interested to know if anyone has had success using it to build Perl or any other common apps. -- John _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 6 ==========================** Date: Fri, 28 Mar 2003 14:00:05 +0000 From: John Poltorak Subject: Re: Autoconf error...? On Fri, Mar 28, 2003 at 11:15:16AM +0100, Hannes Hromadka wrote: > Uups, I forgot to disable pgp signing. Many mailprogs, and > maillistsoftware too have problems with pgp-mime 8-( > > On Fri, Mar 28, 2003 at 09:53:59AM +0100, Hannes Hromadka wrote: > > On Thu, Mar 27, 2003 at 08:08:23PM -0700, Sohnen-Moe Associates, Inc wrote: > > > > > I have seen this, too, while trying to build GnuPG v1.2.x. If I done the > > > line with the spurious "done", I get another error later on which is > > > clearly a bungled output from autoconf: incomplete code. > > > I can add a "me too" here. > > I got such an error when trying to run the full configuration for slrn Can you think of any way to identify the source of the error? > Ciao, Hannes > > -- > Johannes Hromadka | Email Office: HromadkaJ at gmx.at > | Home : Johannes.Hromadka at gmx.net > Vienna/Austria/Europe | OECC: http://www.oecc.org/ > >>> Rust never sleeps (borrowed from Neil YOUNG) <<< -- John _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 7 ==========================** Date: Fri, 28 Mar 2003 15:02:06 -0700 From: sma at sohnen-moe.com Subject: Re: Building READLINE > >Has anyone tried building READLINE? > >How did you get on? > Yes, v4.3 built with both gcc v2.8.1, and v3.2.1. It had some minor warnings: "'XXX' discards `const' from pointer target type". The main thing was to add "--disable-shared". It installed to /usr/local/. _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 8 ==========================** Date: Fri, 28 Mar 2003 15:22:50 -0500 From: Henry Sobotka Subject: Re: Mozilla John Poltorak wrote: > > And in case anyone is feeling particularly brave, you could try adding the > following line to build.table:- > > mozilla;;http://ftp.mozilla.org/pub/mozilla/releases/mozilla1.3/src/mozilla-source-1.3.tar.gz;;;;;. > > then running:- > > build mozilla > > and see how far you get. I don't expect to get far just yet, but it should > work with a little perseverance before too long... I wouldn't advise that because the tarball would have to be patched first with the patches attached to the three or four gcc on OS/2 bugs. Moreover, that's a branch tarball whereas AFAIK the patches are based on diffs against the tip. But I believe most if not all of the patches got checked in during the past week, so it should be buildable by pulling the tip via cvs. h~ _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 9 ==========================** Date: Fri, 28 Mar 2003 16:38:20 -0500 From: Henry Sobotka Subject: Re: Mozilla John Poltorak wrote: > > Is it possible to grab the OS/2 patches relevant to this tarball? They're attached to the three or four bugs concerned. But you have to work backwards, i.e. grab the final approved version of each patch. And applying them to a 1.3 branch tarball could be messy as they're based on diffs against the tip. Given that most if not all the patches are in the tree now, you'd be better off grabbing: http://ftp.mozilla.org/pub/mozilla/nightly/latest/mozilla-source.tar.gz h~ _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 10 ==========================** Date: Fri, 28 Mar 2003 17:10:09 -0700 From: sma at sohnen-moe.com Subject: Re: Building Perl with gcc v3.2.1 > >Has anyone tried building Perl with gcc v3.2.1? > Here the complete diff between the log files of gcc 2.8.1 and 3.2.1: [H:>diff perl-gcc321.log perl-gcc281.log 1c1 < Fri Mar 28 15:09:41 MST 2003 --- > Fri Mar 28 15:32:39 MST 2003 12857,12858c12857,12858 < Fri Mar 28 15:22:05 MST 2003 < elapsed time: 744 secs --- > Fri Mar 28 15:44:38 MST 2003 > elapsed time: 719 secs gcc 3.2.1 is a bit slower. Here is the test result: Failed 35/726 test scripts, 95.18% okay. 981/68664 subtests failed, 98.57% okay. _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 11 ==========================** Date: Fri, 28 Mar 2003 19:59:05 +0000 From: John Poltorak Subject: Re: Mozilla --mdtEa1IpyD0fJVA6 Content-Type: text/plain; charset=us-ascii On Wed, Mar 26, 2003 at 03:56:26PM -0500, Henry Sobotka wrote: > John Poltorak wrote: > > > > Does anyone know where I can find docs for building Mozilla using gcc? > > The build docs are in the process of being updated as IBM switches to > gcc. The latest version can be found among the attachments to: > > http://bugzilla.mozilla.org/show_bug.cgi?id=177789 Just in case anyone here wants a copy of the doc, I'll attach it to this email... And in case anyone is feeling particularly brave, you could try adding the following line to build.table:- mozilla;;http://ftp.mozilla.org/pub/mozilla/releases/mozilla1.3/src/mozilla-source-1.3.tar.gz;;;;;. then running:- build mozilla and see how far you get. I don't expect to get far just yet, but it should work with a little perseverance before too long... > h~ -- John --mdtEa1IpyD0fJVA6 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="C:\\setup.html" Warpzilla Build Instructions Part One - Requirements (10/07/2002)

Warpzilla Build Instructions Part One - Requirements (03/13/2003)

This document explains what tools are required to build Warpzilla. We have tried to be as detailed as possible with these instructions. After each item is instructions on how to install it. This document is designed for someone creating a build environment from scratch. The build environment works best when all the tools are placed on a single drive. For our examples, we will use D:.

Download the following packages:

  • EMX Runtime
    Unzip EMXRT.ZIP in the root directory. It will create a directory called EMX.
    Add D:\EMX\DLL to your LIBPATH in CONFIG.SYS.
  • autoconf
    Unzip AUTOCONF.ZIP in the root directory. It will create a directory called AUTOCONF.
    Replace all 'pwd -D' references in autoconf with just 'pwd'.
  • glib AND libidl
    Unzip GLIBIDL.ZIP in the root directory. It will create a directory called GLIBIDL.
  • Perl 5.8.0 (bin & core)
    Unzip both zips in the root directory.  It will create a directory called PERL.
    In the file PERL\LIB\5.8.0\OS2\CONFIG.PM,  find the "archlib"  tag (line 120) and change the drive letter to point to where you have installed PERL.

Note:For the following packages, you only need to extract the files we specify from the ZIPs. We recommend putting all of the following EXEs and DLLs in one directory called MOZTOOLS.

EMX/GCC Development Packages

Unzip each of these packages in the directory above EMX. All the extracted files will go into the EMX directory.
Once you have unzipped these packages, go to D:\EMX\LIBS\ and run OMFLIBS.CMD.

GCC 3.0.3

Unzip each of these packages in the directory above EMX. All the extracted files will go into the EMX directory.
MAKE SURE YOU DO THIS AFTER YOU INSTALL THE EMX/GCC DEV PACKAGES.  These zips overwrite many of the files from the previous group.
Once you have unzipped these packages, go to D:\EMX\LIBS\ and type 'make'.  Then go to D:\EMX\LIB\GCC-LIB\I386-PC-OS2_EMX\3.0.3\and type 'make'.

OS/2 Toolkit

Install the Toolkit that comes with your version of Warp.

The following OS/2 utilities are required for the GCC build only

  • RC.EXE                    <= use this one, rather than the one that comes with the toolkit
  • LINK386.EXE (installed as part of OS/2) or ILINK.EXE (which comes with Visual Age C++ for OS/2)
  • ILINKWRAP.EXE if you choose to use ILINK.EXE as your linker.

    To verify that you have these utilities, check in the OS2 directory on your boot drive. If you do not have these utilities, you can install them by running OS/2 selective install and selecting "Link Object Modules" on the "Optional System Utilities" page.

    NOTE: It is recommended you use ILINK.EXE, since LINK386.EXE is old and you cannot build debug with it.  In fact, it may not be possible to build a non-debug optimized build with LINK386.EXE either, but I haven't tried to do so in a while.

Build it

Step 1:  Setup the environment.   For the weaksyms environment variable, specify the location of your build in your setmozenv.cmd file.  Edit it and change the line containing GCC_WEAKSYMS.  Here, we assume that you are building in an OBJDIR.  When done editing, just run:
  • setmozenv
Step 2: Pull the code.
  • cvs co mozilla/client.mk
  • cd mozilla
  • mkdir obj
  • copy \emx\lib\gcc-lib\i386-pc-os2_emx\3.0.3\weaksyms.omf obj
  • make -f client.mk pull_all
Step 3: Apply the patches from bugs 188246, 188247, 188249, and 195797.
  • patch -p0 < gcc_nspr.diff
  • patch -p0 < gcc_ldap.diff
  • patch -p0 < gcc_nss.diff
  • patch -p0 < gcc_moz.diff
Step 4: Generate the .mozconfig file, which is a file you create in the mozilla directory that specifies options for the build. Some of the more common options are creating an obj directory which separates the source code from the built code or enabling security. To create a .mozconfig file, see the Unix Build Configurator

We strongly recommend that you build with an obj directory

Here is what our typical .mozconfig file look like for a debug build: 

# sh
# Build configuration script
#
# See http://www.mozilla.org/build/unix.html for build instructions.
#

# Options for client.mk.
mk_add_options MOZ_OBJDIR= at TOPSRCDIR at /obj

# Options for 'configure' (same as command-line options).
#ac_add_options --disable-tests
#ac_add_options --enable-optimize
#ac_add_options --disable-debug
ac_add_options --enable-crypto
Step 5:  Build the code:
  • make -f client.mk build
--mdtEa1IpyD0fJVA6 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 --mdtEa1IpyD0fJVA6-- **= Email 12 ==========================** Date: Fri, 28 Mar 2003 20:03:43 +0000 From: John Poltorak Subject: Building READLINE Has anyone tried building READLINE? How did you get on? -- John _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 13 ==========================** Date: Fri, 28 Mar 2003 20:15:02 +0000 From: John Poltorak Subject: GNU Text Utils v2.0 Can anyone build this port of the GNU Test Utils v2.0 using UX2BS:- ? ftp://os2ports.com/pub/os2/unix/devtools/textutils/textutils-2_0.zip This ought to build quite easily because UX2BS already includes the required patches from it, but I have problems when trying to build it. Can someone read through the docs and suggest what needs to be added to the build environment to make it work? -- John _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 14 ==========================** Date: Fri, 28 Mar 2003 20:48:19 +0000 From: John Poltorak Subject: Re: Mozilla On Fri, Mar 28, 2003 at 03:22:50PM -0500, Henry Sobotka wrote: > John Poltorak wrote: > > > > And in case anyone is feeling particularly brave, you could try adding the > > following line to build.table:- > > > > mozilla;;http://ftp.mozilla.org/pub/mozilla/releases/mozilla1.3/src/mozilla-source-1.3.tar.gz;;;;;. > > > > then running:- > > > > build mozilla > > > > and see how far you get. I don't expect to get far just yet, but it should > > work with a little perseverance before too long... > > I wouldn't advise that because the tarball would have to be patched > first with the patches attached to the three or four gcc on OS/2 bugs. > Moreover, that's a branch tarball whereas AFAIK the patches are based on > diffs against the tip. Is it possible to grab the OS/2 patches relevant to this tarball? > But I believe most if not all of the patches got checked in during the > past week, so it should be buildable by pulling the tip via cvs. At this time UX2BS is not geared up to handling CVS. > h~ -- John _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs