Re: [mdb-dev] build mdb-export on OpenVMS

[Alexander L. <le...@ed...>]

Hi Frank,

when I started to get in touch with mdblib, I needed a cross-platform 
library to access mdb files and wanted it under a POSIX environment, using 
either Linux gcc or mingw, the Windows crosscompiler.

As far as I remember, I simply started by compiling and linking all the 
sourcefiles together and removed those, which had a main() function, that 
gave a duplicate.

The dependencies on system libraries and headers are very weak, so 
actually the 'configure' is a little bit overhead in this situation.

If you are strong enough to create Makefile's or automated compile 
scripts, I'd suggest to avoid the automake/configure method.

Feel free to contact me, also via PM -

A.



On Tue, 28 Aug 2012, Fra...@lp... wrote:

> Hi all,
>
> when I was looking for tools then can read data from mdb-files at not-windows-plattform I
> found this project. I tried to build the exe-files on my OpenVMS-System. Bash-Shell is
> installed, ZLIB and GLIB. But in generell OpenVMS has only poor unix-like tools.
>
> First I tried the "stable" version 0.5:
> ---------------------------------------
>
> bash$ configure
> checking for a BSD-compatible install... /bin/install -c
> checking whether build environment is sane... yes
> sed: couldn't open file %s: %s
> /dka100/software/mdbtools/mdbtools-0-5/missing: Unknown `--run' option
> Try `/dka100/software/mdbtools/mdbtools-0-5/missing --help' for more information
> configure: WARNING: `missing' script is too old or missing
> checking for gawk... gawk
> checking whether make sets ${MAKE}... yes
> checking for gcc... gcc
> checking for C compiler default output... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... no
> checking whether gcc accepts -g... yes
> checking for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> checking whether make sets ${MAKE}... (cached) yes
> checking build system type...
>                              config.sub: too many arguments
> Try `config.sub --help' for more information.
> configure: error: /bin/sh ./config.sub
>  exit (1);
> ..^
> %CC-I-IMPLICITFUNC, In this statement, the identifier "exit" is implicitly decla
> red as a function.
> at line number 110 in file DKA100:[SOFTWARE.mdbtools.mdbtools-0-5]dummy-3335.c;1
> failed
> bash$
>
>
> -------
> Next I tried version 0.6pre1:
> -----------------------------
>
> AXP06$ bash ./configure
> rm: cannot remove `conftest/sub': directory not empty
> checking for a BSD-compatible install... /bin/install -c
> checking whether build environment is sane... yes
> sed: couldn't open file %s: %s
> /dka100/000000/software/mdbtools/mdbtools-0-6pre1/missing: Unknown `--run' optio
> n
> Try `/dka100/000000/software/mdbtools/mdbtools-0-6pre1/missing --help' for more
> information
> configure: WARNING: `missing' script is too old or missing
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking for gcc... gcc
> checking for C compiler default output... a.out
> checking whether the C compiler works... yes
> rm: cannot remove `conftest': is a directory
> checking whether we are cross compiling... no
> checking for suffix of executables...
>                                      rm: cannot remove `conftest': is a directo
> ry
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... no
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ANSI C... none needed
> checking for style of include used by make... GNU
> checking dependency style of gcc...
>                                    mkdir: cannot create directory `conftest.dir
> ': file exists
> mkdir: cannot create directory `sub': file exists
> nonecannot remove `conftest.dir/sub': directory not empty
> checking whether make sets $(MAKE)... (cached) yes
> checking build system type...
>                              config.sub: too many arguments
> Try `config.sub --help' for more information.
> configure: error: /bin/sh ./config.sub
>  exit (1);
> ..^
> %CC-I-IMPLICITFUNC, In this statement, the identifier "exit" is implicitly decla
> red as a function.
> at line number 110 in file SYS$SYSROOT:[SYSMGR.VMS_TEMP.cgLuE4La]dummy.c;2 faile
> d
> AXP06$
>
> The last version I found is 0.7 rc1
> -----------------------------------
> This kit does not have a configure-file. 'autoconf' is needed. In order to install
> autoconf perl is needed to install first. (May be other also.) But I only like to build an
> exe-file from c-code.
>
> Why such overhead? This works only on the newest Linux-versions. For poor unix-systems
> (POSIX-conform) a munually build should be more easy.
> Example:
> % gcc mdb-export
> % link mdb-export
>
> Do I have a chance to build mdb-export without make and without configure and without
> autoconf, simply with gcc and link (and perhaps some qualifiers)?
>
>
> regards, Frank
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> mdbtools-dev mailing list
> mdb...@li...
> https://lists.sourceforge.net/lists/listinfo/mdbtools-dev
>