OS/2, eCS & ArcaOS - Technical > Programming

trying a first port

<< < (2/2)

Silvan Scherrer:

--- Quote from: Dave Yeo on February 16, 2015, 04:46:31 pm ---Easiest is to have a config.site file. The config.site file will be automatically found if at $PREFIX/share/config.site or found by set CONFIG_SITE.
Also note that different shells work different and with the RPM/YUM environment and ash as the shell you're better off recreating the auto files.

--- Code: ---export ac_executable_extensions=.exe
export ac_exeext=.exe

--- End code ---
You can add other needed stuff if configure has a problem finding it

--- Code: ---export INSTALL=f:/usr/bin/install.exe
export lt_cv_path_SED=sed.exe
export lt_ac_sed=sed.exe

--- End code ---

--- End quote ---
with all latest rpm/yum dev packages like autoconf, libtool, automake ... you can bootstrap everything nicely. No need to fiddle with a config.site file.

Meeko:

--- Quote from: Dave Yeo on February 16, 2015, 07:50:47 am ---Currently most people are using yum/rpm to install a build environment as well as other software. Most software is close to up to date, eg GCC 4.9.2, Python 2.7.6. See http://trac.netlabs.org/rpm/wiki

--- End quote ---

I downloaded ftp://ftp.netlabs.org/pub/gcc/GCC-3.3.5-csd6.zip but did not find documentation on configuration (environment variables, etc.). Would this conflict with emx or can it actually replace emx?

Dave Yeo:
On Warp v4 I had both installed with EMX set up in config.sys and installed in \emx and klibc installed in \usr.
Opening a cmd prompt and running \usr\bin\gccenv.cmd will set everything up for klibc and gcc 3.3.5.  IIRC with the right parameters it'll set things up for other locations as well.
I then put other stuff in \usr\local and had a simple batch file, localenv.cmd to set that up. Parts are particular to my environment.

--- Code: ---echo off
SET PATH=foo;g:\mzfntcfgft\bin;g:\usr\local\bin;%PATH%
set BEGINLIBPATH=g:\usr\local\lib;%BEGINLIBPATH%
SET C_INCLUDE_PATH=g:/mzfntcfgft/include;g:/usr/local/include;%C_INCLUDE_PATH%
SET CPLUS_INCLUDE_PATH=g:/mzfntcfgft/include;g:/usr/local/include;%CPLUS_INCLUDE_PATH%
SET LIBRARY_PATH=g:/mzfntcfgft/lib;g:/usr/local/lib;%LIBRARY_PATH%
SET PKG_CONFIG_PATH=g:/mzfntcfgft/lib/pkgconfig;g:/usr/local/lib/pkgconfig;%PKG_CONFIG_PATH%
SET MANPATH=g:/usr/local/share/man;g:/usr/local/man;%MANPATH%
set PATH=g:\perl5\bin;%PATH%
set BEGINLIBPATH=g:\perl5\bin;%BEGINLIBPATH%
set PERLDIR=g:\perl5
set PERL_LIBPATH=g:/perl5/lib;g:/git/
set PERLLIB_PREFIX=u:/perl5/lib;g:/perl5/lib
set PERL_SH_DIR=/bin
set USE_PERL_FLOCK=0
set MAKESHELL=f:/bin/sh.exe
set CONFIG_SITE=g:/usr/local/share/config.site

--- End code ---

Now I set up various things much the same way.
You can get rid of EMX if you want though keep the dlls as much depends on them. The documentation also kind of applies as klibc is sorta a rewrite of EMX and uses many of the same tools, functions and flags
You also should install a better linker, ld works but is so old that it is GPL v1 and original author is RMS. You can use link386 that was an optional install item on your Warp V4 CD or download wl (patched OpenWatcom Wlink) from the same place you found GCC 3.3.5, run emxomfld.exe without parameters to find the environment variables to set it up. Use LDFLAGS=-Zomf to use. OMF is the native object format, GCC compiles to aout and then it can be converted during the build and/or linking phase.
Also check out http://os2ports.smedley.info/

Martin Iturbide:
Hi Erich.

I really hope you are doing fine with your first port.

If you want to share something about your results, the binaries, or if you want to post an article about your fist steps on EDM/2 wiki, please let me know.

Regards

Navigation

[0] Message Index

[*] Previous page

Go to full version