Mail Archives: djgpp/1997/04/03/12:47:53
OK, we meticulously went through and installed all of the binaries and
sources . . . Here's what we get:
c:\gnu\sources\gnu\gcc-2721> configur winnt i386
Configuring GCC for Windows NT on i386
1 file(s) copied
This results in a makefile which, for starters, has two tabs missing . . .
in lines 424 and 705. I edit the file by hand and insert the tabs. Then
I run make.
c:\gnu\sources\gnu\gcc-2721> make
cl -DIN_GCC -Di386 -DWIN32 -D_WIN32 -D_M_IX86=300 -D_X86_=1
-DALMOST_STDC -D_MSC_VER=800 -I. -I. -I./config \
-DGCC_INCLUDE_DIR=\"/usr/local/lib/gcc-lib/winnt3.5/2.7.2.1/include\" \
-DGPLUSPLUS_INCLUDE_DIR=\"/usr/local/lib/g++-include\" \
-DLOCAL_INCLUDE_DIR=\"/usr/local/include\" \
-DCROSS_INCLUDE_DIR=\"/usr/local/lib/gcc-lib/winnt3.5/2.7.2.1/sys-include\"
\
-DTOOL_INCLUDE_DIR=\"/usr/local/winnt3.5/include\" \
-c cccp.c
make.exe: *** [cccp.obj] Error -1
Now, if I try to use the "unix-like" commands:
configur --build=i386-*-winnt3.5
I get:
c:\gnu\sources\gnu\gcc-2721> sh ./configur --build=i386-*-winnt3.5
Using `./config/i386/i386.c' to output insns.
Using `./config/i386/i386.md' as machine description file.
Using `./config/i386/win-nt.h' as target machine macro file.
Using `./config/i386/xm-winnt.h' as host machine macro file.
Merged winnt/x-winnt.
Merged i386/t-winnt.
Cannot open output file to generate
Links are now set up to build a native compiler for i386-*-winnt3.5
c:\gnu\sources\gnu\gcc02721> make
gcc -DIN_GCC -g -I. -I. -I./config \
-DGCC_INCLUDE_DIR=\"/usr/local/lib/gcc-lib/i386-*-winnt3.5/2.7.2.1/include\"
\
-DGPLUSPLUS_INCLUDE_DIR=\"/usr/local/lib/g++-include\" \
-DLOCAL_INCLUDE_DIR=\"/usr/local/include\" \
-DCROSS_INCLUDE_DIR=\"/usr/local/lib/gcc-lib/i386-*-winnt3.5/2.7.2.1/sys-include\"
\
-DTOOL_INCLUDE_DIR=\"/usr/local/i386-*-winnt3.5/include\" \
-c `echo ./cccp.c | sed 's,^\./,,'`
gcc: C:/TEMP/dj100000 1: cannot execute: The parameter is incorrect.
make.exe: *** [cccp.o] Error 126
We're at our wits end with this . . . been working on this for over 2
weeks now, and I'm starting to think that we are completely on the wrong
track. It shouldn't be this difficult to compile the sources for djgpp .
. . right?
BTW, the reason we need to compile the sources is that we want to write a
new front end to compile java bytecode. Therefore, we MUST be able to
compile the sources . . .
|...... Casey K. Corcoran ......| University of Illinois
|...... ckcorcor AT uiuc DOT edu ......| Center for Supercomputing R & D
|....... (217) 244-0049 ........| 1308 W. Main Street, Urbana, IL 61801
On Thu, 3 Apr 1997, Eli Zaretskii wrote:
>
> On Thu, 3 Apr 1997, Casey Corcoran wrote:
>
> > No, I'm talking about compiling the djgpp sources on my NT machine. We've
> > scrapped the idea of using MSVC at all. We're going to do it the
> > "traditional" way using editors and RHIDE where we can. First,
> > though, I need to get djgpp to compile on my machine.
>
> Why? DJGPP already comes with a compiled GCC binary, so why do you need
> to recompile it yourself?
>
> > program). Basically what I need is a list of tools and versions and a
> > step-by-step list of how to build it.
>
> Install these and you should be all set:
>
> mak375b.zip
> fil313b.zip
> shl112b.zip
> grep20b.zip
> sed118b.zip
> find41b.zip
> diff271b.zip
> txt122b.zip
> txi390b.zip
>
> and of course djdev201.zip, gcc2721b.zip and bnu27b.zip (without which
> you won't be able to compile at all).
>
> All of the above are in the v2gnu directory on DJGPP sites.
>
> There should be CONFIG.BAT and/or MAKE.BAT in the gcc source
> distribution; these are what you need to invoke. If you have problems,
> post here.
>
> But I think you don't need to recompile gcc at all. Everything is
> already built for you, just use the binary packages (those which end with
> a `b').
>
- Raw text -