Mail Archives: djgpp/1998/05/29/08:45:50
Since the introduction of 2.8.1 version of gcc I found two
differences in the way it compiles programs.
First, the way gcc calls other programs changed. I had a little
program called `as.cc' in one of my projects and it worked. Now
after first compilation, when `as.exe' exists in the current
directory it is called by `gcc' instead of assembler program (with
poor results). I had to change the name of my `as.cc' to
something else. I'm slightly afraid what other names are in
danger?
Second, in 2.7.2.1, after compilation with a command `gcc a.c -o
a' there were two files left: `a' and `a.exe' (image and stubified
image, both rather big, second slightly bigger). Now these two
files are identical (both are stubified). Is it intended
behaviour or simple side effect?
I must say that these two big files are kind of waste of disk
space, especially on systems with limited resources, like Novell.
I know (and appreciate it very much) that `a' file must exists for
UNIX makefiles compatibility.
So, maybe `stubify' program should have a kind of `-l' (symbolic
link) option to create only 2kB `a.exe' pointing to big `a' image
(this option should be on by default when called by gcc). Is it
possible to have such a behaviour with current setup? (command
`stubify -g a.exe; stubedit a.exe runfile=a' does't work - program
`a.exe' adds `.EXE' suffix to `a' name when invoked...)
And I think that DJGPP is great - many thanks to all who created
and maintained it!!!
--
Jerzy Witkowski <Jerzy DOT Witkowski AT ii DOT uni DOT wroc DOT pl> o o
University of Wroclaw, Institute of Computer Science /| | |/|
Przesmyckiego 20, PL-51151 Wroclaw |/| | |
room: 11, phone: 0048 71 3247360 /| |/^\| |
phone/fax office secretary: 0048 71 3251271 <__|
- Raw text -