I am trying to figure out why GDB is crashing (see previous email).
1. Here is a dump of my mingw32 environment. Are the variables right? Is the
path right? Is anything missing? Is anything conflicted? Is anything
unnecessary?
1. install clean Windows Server 2008 R2
2. install emacs-24.5-bin-i686-mingw32.zip (c:/progra~2/emacs)
3. install gnustep-msys-system-0.30.0-setup.exe (c:/msys)
4. install gnustep-devel-1.4.0-setup.exe (c:/msys)
5. install tortoise svn client
6. set env to:
GNUSTEP ......... c:/msys/GNUstep
GNUSTEP_MAKEFILES c:/msys/GNUstep/System/Library/Makefiles
MANPATH .........
c:/msys/GNUstep/System/Library/Documentation/man;c:/msys/share/man
MSYS ............ c:/msys
MSYSTEM ......... mingw32
PATH
.
c:/msys/bin
c:/msys/msys/1.0/bin
c:/msys/mingw32/bin
c:/msys/gnustep/system/tools
c:/progra~1/tortoi~1/bin
c:/progra~2/emacs/bin
%systemroot%
%systemroot%/system32
%systemroot%/system32/wbem
%systemroot%/system32/windowspowershell/v1.0
2. In building gnustep-base32 on mingw32, the make/configure script could not
determine my processor or hardware (vmware / x5675).
uname -s = mingw32_NT-6.1 (kernel name)
uname -r = 1.0.17(0.48/3/2) (kernel release)
uname -v = 2011-04-24 23:39 (kernel version)
uname -m = i686 (machine)
uname -p = unknown (processor)
uname -i = unknown (hardware)
uname -o = Msys (operating system)
Therefore, I added the following temporary hack to the windows-build script.
# Architecture Goop
ARCH=i686-pc-mingw32 # config.guess failed
ARCH_GOOP="--build ${ARCH} --target ${ARCH} --host ${ARCH}"
CONFIGURE="./configure ${ARCH_GOOP}"
Was i686-pc-mingw32 the right triple to use?
Thank you._______________________________________________
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev
