From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Mon, 25 Aug 2003 14:10:15 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 177 ************************************************** Sunday 24 August 2003 Number 177 ************************************************** Subjects for today 1 Re: [Ux2bs] Perl errors : Henry Sobotka 2 Re: [Ux2bs] Perl errors : T.Sikora" 3 Re: [Ux2bs] Perl errors : Henry Sobotka 4 UX2BS readme : T.Sikora" **= Email 1 ==========================** Date: Mon, 25 Aug 2003 11:28:25 -0400 From: Henry Sobotka Subject: Re: [Ux2bs] Perl errors T.Sikora wrote: > > I been trying to build Perl with gcc-3.2.1 and a major obstacle is this > optimizer/debugger error: > > cc1.exe: warning: -malign-loops is obsolete, use -falign-loops > cc1.exe: warning: -malign-jumps is obsolete, use -falign-jumps > cc1.exe: warning: -malign-functions is obsolete, use -falign-functions > > Where would I define this? That's coming from hints/os2.sh in the Perl tree. To build Perl with 3.2.1 you also have to fix the -Zomf problem. gcc 3.x no longer automatically outputs files with the .obj extension that the Perl build system expects. I've worked around it manually by adding "-o $ at " to config.sh and possibly another file (don't recall offhand and that tree isn't on this machine). There might be a spot to add it in the hints file, from where it can be propagated to config.sh and all the other generated files. h~ **= Email 2 ==========================** Date: Mon, 25 Aug 2003 11:54:25 -0400 From: "T.Sikora" Subject: Re: [Ux2bs] Perl errors Henry Sobotka wrote: > T.Sikora wrote: > >>I been trying to build Perl with gcc-3.2.1 and a major obstacle is this >>optimizer/debugger error: >> >>cc1.exe: warning: -malign-loops is obsolete, use -falign-loops >>cc1.exe: warning: -malign-jumps is obsolete, use -falign-jumps >>cc1.exe: warning: -malign-functions is obsolete, use -falign-functions >> >>Where would I define this? > > > That's coming from hints/os2.sh in the Perl tree. I changed it in config.h after Configure but failed at make test with missing obj files. > > To build Perl with 3.2.1 you also have to fix the -Zomf problem. gcc 3.x > no longer automatically outputs files with the .obj extension that the > Perl build system expects. I've worked around it manually by adding "-o > $ at " to config.sh and possibly another file (don't recall offhand and Yeah I came across that in make test couldn't find $ at " and the object files. > that tree isn't on this machine). There might be a spot to add it in the > hints file, from where it can be propagated to config.sh and all the > other generated files. Maybe config_H.sh ? > > h~ > > > -- T.Sikora tsikora at ntplx dot net **= Email 3 ==========================** Date: Mon, 25 Aug 2003 12:37:39 -0400 From: Henry Sobotka Subject: Re: [Ux2bs] Perl errors T.Sikora wrote: > > I changed it in config.h after Configure but failed at make test with > missing obj files. I don't understand how you could do that. The alignment flags are optimization instructions for the compiler; they belong in the makefiles, not a header. > Maybe config_H.sh ? That would just put them in config.h. h~ **= Email 4 ==========================** Date: Mon, 25 Aug 2003 14:29:17 -0400 From: "T.Sikora" Subject: UX2BS readme This is a multi-part message in MIME format. --------------060903090508070103050304 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit This should clear things up a bit. -- T.Sikora tsikora at ntplx dot net --------------060903090508070103050304 Content-Type: text/plain; name="ux2bs.README" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ux2bs.README" The UX2 Developers Build System for OS/2 ------------------------------------------ Assuming you have the ux2bs_inst.cmd script already, edit the drive letters at the top to reflect your drives where (osrt) OS/2 is installed and where you want to install (uxrt) the Unix environment. UX2 installs many directories in root so be forwarned. A seperate partition or drive is highly recommended. It will create these in your (uxrt) root directory: bin/ boot/ dev/ emx/ etc/ home/ install/ lib/ ports/ proc/ root/ sbin/ tmp/ usr/ var/ If any of the above directories exist rename them or delete them. Prerequisites -------------------------------------------------- None except a clean environment (config.sys) devoid of all Unix environmental settings including EMX. Recommended EMX config.sys settings for 3rd party programs: LIBPATH=D:\emx\dll;D:\emx\lib; PATH=D:\emx\bin; HELP=D:\emx\help; BOOK=D:\emx\book; SET HELPNDX=emxbook.ndx SET EMXBOOK=emxdev.inf+emxlib.inf+emxgnu.inf+emxbsd.inf This will provide seamless interaction with all 3rd party EMX programs like Python. Set the drive letter to (uxrt) where you will install the Unix environment. Install ----------------------------------------------------- Edit the drive letters at the top of the script to reflect your drives where (osrt) OS/2 is installed and where you want to install (uxrt) the Unix environment. Then run ux2bs_inst. It will download and install the required packages and build several libraries before finishing up with Perl. Two shell desktop icons will be made. The UX2BS Shell which is the default gcc-2.8.1 environment. The GCC-3.2.1 Shell is set up for the GCC-3.2.1 environment. User-defined Enviroment settings ------------------------------------------------------ User defined env settings can be added to etc\ux2_local which is system wide. Specific GCC-3.2.1 settings can be added to etc\gcc_local. The system is designed to be used with the desktop shells. The ux2 environment can be used at anytime by a regular OS/2 window by calling \sbin\ux2_env first. Using GCC-3.2.1 REQUIRES the desktop shell as the specific settings are defined in the shell itself. Updates ------------------------------------------------------ Your Build System can be updated at anytime with the latest changes by running ux2bs_update in the default shell. The ports tree can also be made current by running ports_update. Using the Ports tree ------------------------------------------------------- What is the ports tree you ask? Rooted in the FreeBSD tradition it allows the developer, hobbyist or anyone for that matter to build his/her own ports from source with a single command. The ports are named by directories so cd to \ports\gmp for example. Do a 'clean' to ensure the old workdir is removed and to build the port just run 'build gmp'. What it does is check for the existance of the source in your local \install\archives. If it does not exist it downloads it, extracts it, builds and installs it. It's really that simple. You can do a 'clean' afterwards to remove the workdir. As of this writing we have four working ports in the tree. Perl, gmp, gnugdbm, and gnuufc. Reinstalls -------------------------------------------------------- If you should ever decide to reinstall the UX2BS for any reason, delete everything *except* \install\archives. This will save you the expense of redownloading it again. The install script checks for the existance of it and will continue the install. As of this writing there is no way to refresh it automatically so you will have to maintain it yourself. Once the install completes the subdirectories are no longer of use since the source required for the ports tree are automagiclly downloaded to \install\archives. Websites and Mailists -------------------------------------------------------- UnixOS2.org http://unixos2.com/ UX2 Build System http://os2ports.com/sections/ux2bs UX2BS Mailing List http://os2ports.com/mailman/listinfo/ux2bs OS2-Unix Developers List majordomo at mail.warpix.org Complaints -------------------------------------------------------- > /dev/null Raves -------------------------------------------------------- Just send the beer... Enjoy! The UnixOS2.org Team --------------060903090508070103050304--