Thread: [ooc-compiler] Problems bootsrapping OO2C under MinGW/MSYS
Brought to you by:
mva
Menu
▾
▴
ooc-compiler
|
From: Bernhard T. <Bd...@wi...> - 2006-06-24 13:52:30
|
Dear OO2C users,
I am trying to bootstrap OO2C under MinGW/MSYS,
I successfully compiled the current gc.
./configure had no apparent problems.
but make fails in the last steps of stage0 (at least
I have the impression). Somehow it gets an windows-like
path specification (D:/Programme/Msys/...),
see below. Does anybody have an idea how to correct that.
regard & thanks in advance
--
Bernhard Treutwein
Bernhard.Treutwein(at)verwaltung uni-muenchen de (work)
BdT(at)wildwein de (home)
PS: The complete log is available, but I hope that I extracted the relevant
parts:
Bernhard@JANUS /usr/src/OO2C
$ cd oo2c_32-2.1.10
Bernhard@JANUS /usr/src/OO2C/oo2c_32-2.1.10
$ ./configure
checking for gcc... gcc
... no apparent errors ...
Bernhard@JANUS /usr/src/OO2C/oo2c_32-2.1.10
$ make
make -C stage0 -f Makefile.ext setup-src oo2c
make[1]: Entering directory `/usr/src/OO2C/oo2c_32-2.1.10/stage0'
test -h src || (rm -Rf src lib/src; cp -R ../src .; cp -R ../lib/src lib)
gcc -g -O2 -Ilib/src -I./obj -I./lib/obj -c ./lib/obj/ADT/ArrayList.c -o
./lib/obj/ADT/ArrayList.o
... some warnings ...
make[1]: Leaving directory `/usr/src/OO2C/oo2c_32-2.1.10/stage0'
sed -e 's?%libdir%?/usr/local/lib?g' \
-e 's?%oocdir%?/usr/local/lib/oo2c?g' \
-e 's?%bindir%?/usr/local/bin?g' \
-e 's?%INSTALL%?/bin/install -c?g' \
-e 's?%INSTALL_PROGRAM%?/bin/install -c?g' \
-e 's?%INSTALL_DATA%?/bin/install -c -m 644?g' \
/usr/src/OO2C/oo2c_32-2.1.10/rsrc/OOC/oo2crc.xml.mk
>/usr/src/OO2C/oo2c_32-2.1.10/rsrc/OOC/oo2crc.xml
sed -e 's:<file-system>:<!--:g' \
-e 's:</file-system>:-->:g' \
-e
's:<repositories>:<repositories><file-system>/usr/src/OO2C/oo2c_32-2.1.10/li
b
</file-system><file-system>/usr/src/OO2C/oo2c_32-2.1.10</file-system>:' \
/usr/src/OO2C/oo2c_32-2.1.10/rsrc/OOC/oo2crc.xml
>/usr/src/OO2C/oo2c_32-2.1.10/oo2crc-install.xml
stage0/oo2c --config oo2crc-install.xml -v -r lib -r . --build-package
liboo2c
- D:/Programme/Msys/1.0/src/OO2C/oo2c_32-2.1.10/lib/pkginfo.xml
- D:/Programme/Msys/1.0/src/OO2C/oo2c_32-2.1.10/pkginfo.xml
- lib/src/liboo2c.Mod
... no apparent errors ...
- lib/sym/liboo2c.Doc
/bin/libtool --tag=CXX --mode=compile gcc -g -O2 -Ilib/src -Iobj -Ilib/obj
-I/usr/src/OO2C/oo2c_32-2.1.10/obj -I/usr/src/OO2C/oo2c_32-2.1.10/lib/obj -c
D:/Programme/Msys/1.0/src/OO2C/oo2c_32-2.1.10/lib/src/RT0.c -o
lib/obj/RT0.lo
make: *** [lib/obj/liboo2c.la] Error 1
Bernhard@JANUS /usr/src/OO2C/oo2c_32-2.1.10
$ libtool --version
ltmain.sh (GNU libtool) 1.4e (1.1162 2002/11/22 22:36:25)
Copyright 1996, 1997, 1998, 1999, 2000, 2001
Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Bernhard@JANUS /usr/src/OO2C/oo2c_32-2.1.10
$ gcc --version
gcc.exe (GCC) 3.4.2 (mingw-special)
Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
|
From: Stewart G. <sgr...@us...> - 2006-06-25 12:47:44
|
Hi Bernhard,
There are a few issues with the configuration of oo2c under Windows.
These are explained at length in README.WIN32.
I suggest that you first try to bootstrap the system without using
libtool. This means using "./configure --disable-libs" so that you get
static linking, rather than trying to build shared libraries. AFAIK,
oo2c+libtool is untested under mingw/msys. At least in recent releases,
oo2c should not be bothered by Windows path names, and neither should
gcc. Can't say the same for libtool though...
From README.WIN32, the full configure command for msys looks something
like this:
env \
"INSTALL=c:/msys/1.0/bin/install.exe" \
LDFLAGS=-L/usr/local/lib \
CFLAGS=-O2 \
"CPPFLAGS=-I/usr/local/include -DGC_WIN32_THREADS" \
./configure --disable-libs
Hope this helps.
Cheers,
Stewart
Bernhard Treutwein wrote:
> Dear OO2C users,
>
> I am trying to bootstrap OO2C under MinGW/MSYS,
>
> I successfully compiled the current gc.
>
> ./configure had no apparent problems.
>
> but make fails in the last steps of stage0 (at least
> I have the impression). Somehow it gets an windows-like
> path specification (D:/Programme/Msys/...),
> see below. Does anybody have an idea how to correct that.
>
> regard & thanks in advance
>
> --
> Bernhard Treutwein
> Bernhard.Treutwein(at)verwaltung uni-muenchen de (work)
> BdT(at)wildwein de (home)
>
> PS: The complete log is available, but I hope that I extracted the relevant
> parts:
>
> Bernhard@JANUS /usr/src/OO2C
> $ cd oo2c_32-2.1.10
>
> Bernhard@JANUS /usr/src/OO2C/oo2c_32-2.1.10
> $ ./configure
> checking for gcc... gcc
>
> ... no apparent errors ...
>
> Bernhard@JANUS /usr/src/OO2C/oo2c_32-2.1.10
> $ make
> make -C stage0 -f Makefile.ext setup-src oo2c
> make[1]: Entering directory `/usr/src/OO2C/oo2c_32-2.1.10/stage0'
> test -h src || (rm -Rf src lib/src; cp -R ../src .; cp -R ../lib/src lib)
> gcc -g -O2 -Ilib/src -I./obj -I./lib/obj -c ./lib/obj/ADT/ArrayList.c -o
> ./lib/obj/ADT/ArrayList.o
>
> ... some warnings ...
>
> make[1]: Leaving directory `/usr/src/OO2C/oo2c_32-2.1.10/stage0'
> sed -e 's?%libdir%?/usr/local/lib?g' \
> -e 's?%oocdir%?/usr/local/lib/oo2c?g' \
> -e 's?%bindir%?/usr/local/bin?g' \
> -e 's?%INSTALL%?/bin/install -c?g' \
> -e 's?%INSTALL_PROGRAM%?/bin/install -c?g' \
> -e 's?%INSTALL_DATA%?/bin/install -c -m 644?g' \
> /usr/src/OO2C/oo2c_32-2.1.10/rsrc/OOC/oo2crc.xml.mk
>
>>/usr/src/OO2C/oo2c_32-2.1.10/rsrc/OOC/oo2crc.xml
>
> sed -e 's:<file-system>:<!--:g' \
> -e 's:</file-system>:-->:g' \
> -e
> 's:<repositories>:<repositories><file-system>/usr/src/OO2C/oo2c_32-2.1.10/li
> b
> </file-system><file-system>/usr/src/OO2C/oo2c_32-2.1.10</file-system>:' \
> /usr/src/OO2C/oo2c_32-2.1.10/rsrc/OOC/oo2crc.xml
>
>>/usr/src/OO2C/oo2c_32-2.1.10/oo2crc-install.xml
>
> stage0/oo2c --config oo2crc-install.xml -v -r lib -r . --build-package
> liboo2c
> - D:/Programme/Msys/1.0/src/OO2C/oo2c_32-2.1.10/lib/pkginfo.xml
> - D:/Programme/Msys/1.0/src/OO2C/oo2c_32-2.1.10/pkginfo.xml
> - lib/src/liboo2c.Mod
>
> ... no apparent errors ...
>
> - lib/sym/liboo2c.Doc
> /bin/libtool --tag=CXX --mode=compile gcc -g -O2 -Ilib/src -Iobj -Ilib/obj
> -I/usr/src/OO2C/oo2c_32-2.1.10/obj -I/usr/src/OO2C/oo2c_32-2.1.10/lib/obj -c
> D:/Programme/Msys/1.0/src/OO2C/oo2c_32-2.1.10/lib/src/RT0.c -o
> lib/obj/RT0.lo
> make: *** [lib/obj/liboo2c.la] Error 1
>
>
> Bernhard@JANUS /usr/src/OO2C/oo2c_32-2.1.10
> $ libtool --version
> ltmain.sh (GNU libtool) 1.4e (1.1162 2002/11/22 22:36:25)
>
> Copyright 1996, 1997, 1998, 1999, 2000, 2001
> Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> Bernhard@JANUS /usr/src/OO2C/oo2c_32-2.1.10
> $ gcc --version
> gcc.exe (GCC) 3.4.2 (mingw-special)
> Copyright (C) 2004 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
>
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> ooc-compiler mailing list
> ooc...@li...
> https://lists.sourceforge.net/lists/listinfo/ooc-compiler
>
|
|
From: Bernhard T. <Bd...@wi...> - 2006-06-25 17:31:24
|
Hi Stewart,
> These are explained at length in README.WIN32.
in the meantime I've found them, but it did not help me very much.
>
> I suggest that you first try to bootstrap the system without using
> libtool. This means using "./configure --disable-libs" so that you get
I'll try that.
> static linking, rather than trying to build shared libraries. AFAIK,
> oo2c+libtool is untested under mingw/msys. At least in recent releases,
> oo2c should not be bothered by Windows path names, and neither should
> gcc. Can't say the same for libtool though...
>
hmm, it gets installed :-)
> From README.WIN32, the full configure command for msys looks something
> like this:
> env \
> "INSTALL=c:/msys/1.0/bin/install.exe" \
> LDFLAGS=-L/usr/local/lib \
> CFLAGS=-O2 \
> "CPPFLAGS=-I/usr/local/include -DGC_WIN32_THREADS" \
> ./configure --disable-libs
>
> Hope this helps.
>
I'll keep you informed ...
regards & thanks
Bernhard
|
Thanks for helping keep SourceForge clean.
X