From:	bxkim%camars DOT kaist DOT ac DOT kr AT daiduk DOT kaist DOT ac DOT kr (Kim Byung Ho)
Subject:	Re: [2nd] porting gcc...
To:	turnbull AT shako DOT sk DOT tsukuba DOT ac DOT jp
Date:	Wed, 23 Mar 94 18:57:34 KST
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu

Thank you very much for your response.

I'll explain our trouble more detail.
I have build a new compiler system using GNU CC:
	1) a compiler (from gcc version 1.37.1, all machine description 
		are updated to our target machine, and
		some MSDOS-related codes (as like pexecute() in gcc.c)
		are tuned (I refer to gcc's djgpp part).

	2) assembler and linker (from gas and gnu binutils's ld)

So, I have compiled this code with djgpp, and
the new compiler mostly work succesfully.

Next is each strings that gcc controller call:
 -- the variables: 'program' and 'argv[]' are used in pexecute() in gcc.c
 -- below is an example,

1)
 program = c:/comp/bin/cpp
 argv[1] = -undef
 argv[2] = -D__GNUC__
 .
 .
 .
 argv[14] = -D__LANGUAGE_C__
 argv[15] = tt.c
 argv[16] = c:/tmp/cca29989.cpp

2) 
 program = c:/comp/bin/cc1
 argv[1] = c:/tmp/cca29989.cpp
 argv[2] = -quiet
 argv[3] = -dumpbase
 argv[4] = tt.c
 argv[5] = -o
 argv[6] = /usr/tmp/cca29989.s

3)
 program = c:/comp/bin/as
 argv[1] = -o
 argv[2] = tt.o
 argv[3] = c:/tmp/cca29989.s

4)
 program = c:/comp/bin/ld
 argv[1] = gisccrt0.o
 argv[2] = tt.o
 argv[3] = c:/comp/lib/gisc-gnulib
 argv[4] = c:/comp/lib/gisc-gnulib


Then, 
our trouble is that
when I run the gcc as like "gcc tt.c",
the gcc call cpp, cc1, as successfuly,
BUT, after call ld (only calling),
our PC (386) die. (rest work is only to reboot the PC).

Our PC use only 640KB,
So, I suspect some reason,
   1) About system() call, as you noticed, a certain buffer,
     for cascaded system() call or for many activation record 
     creation, is lack.

   2) About command line problem:
     I use system() callas like,
     	system("command @arglist-file");
     So, I think that no problem on that.

   3) Or, each program ( as like ld)'s return value may 
     cause some trouble?..

----------------
well,
Thanks very much about reading our mail.
I know that my text is so crazy to read..
I`d like to listen to your advice, again.

		Thanks in advance,
		Kim, Byungho,
		bxkim AT camars DOT kaist DOT ac DOT kr

----------------------------------------
This is your response;

> 
> It's not clear exactly what you're doing from your very brief report.
> You really must supply more information to get any useful feedback.
>     (1) Have you run gcc -v to get a complete report of what's
> failing?  What error messages, if any, did you receive?  What program
> are you compiling?  What is the gcc command line?  What commands does
> gcc issue?  If the compile fails before reaching ld, what ld command
> did you expect?
>     (2) Typically ld command lines are quite long, longer than cpp,
> cc1, and as commands.  You seem to say you've modified the system
> calls in the compiler control program.  Have you checked to be sure
> that to make sure that your new gcc can handle long command lines?
>     (3) Most of the reported GO32 bugs that affected compiling with
> DJGPP had to do with make.  Still, do you have the most recent version
> of GO32 (1.11.maint.4)?
>     (4) How much memory do you have?  How is it configured?  Generally
> there's only a problem when you use make (so that you must stack 3
> copies of GO32 under the 640KB line), but I can imagine a situation
> where you might run out of memory with just gcc.
>     --Steve
> 

- Raw text -