Next:Allegro and GRX,
Previous:DJGPP and DLLs,
Q: When I link my program, it fails to produce the .EXE
Q: I run STUBIFY on a networked drive under
Novell, but it doesn't produce a .EXE file. How come?
A: One possible reason for this is that your disk is full, or
there's no swap space available for the DOS box on Windows. Run
go32-v2 with no arguments and see what it reports, then follow
the advice in configuring your system, for the optimal configuration.
If you are running DJGPP on a networked drive, you might have another
copy of the file with the same name that GCC is creating in another
directory somewhere on that networked drive. If that other directory is
PATH, it is searched by Novell when the linker and
STUBIFY try to create the executable file, because that file
doesn't exist in the current directory. So what might actually happen
is that the linker and
STUBIFY are overwriting the files they
find on your
PATH instead of creating new files in the current
You can verify that this indeed is the problem by searching your networked disks for files with the same name as those you are trying to build, and looking at their time stamps. If that is indeed the problem, then you have several possible ways of solving it:
PATHwhere the other files reside, so that you won't have write privileges to that directory.
STUBIFYand the linker (or for any other program that gives you that trouble) by running commands like these:
SMODE stubify.exe 2 SMODE ld.exe 2