[an error occurred while processing this directive]
Node:<a name="No%20EXE">No EXE</a>,
Next:<a rel=next href="faq8_17.html">Allegro and GRX</a>,
Previous:<a rel=previous href="faq8_15.html">DJGPP and DLLs</a>,
Up:<a rel=up href="faq8.html">Compiling</a>
<br>

<h2>8.16 Linker fails to produce the EXE program</h2>

<p><em><strong>Q</strong>: When I link my program, it fails to produce the .EXE
executable<small>...</small>.</em>

<br><p>
<p><em><strong>Q</strong>: I run STUBIFY on a networked drive under
Novell, but it doesn't produce a .EXE file.  How come?</em>

<br><p>
<p><strong>A</strong>:  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
<code>go32-v2</code> with no arguments and see what it reports, then follow
the advice in <a href="faq3_9.html">configuring your system</a>, for the optimal configuration.

<p>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
on your <code>PATH</code>, it is searched by Novell when the linker and
<code>STUBIFY</code> 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 <code>STUBIFY</code> are overwriting the files they
find on your <code>PATH</code> instead of creating new files in the current
directory.

<p>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:

<ol type=1 start=1>
</p><li>You can remove the other files, rename them, or move them to another
directory that isn't searched by Novell.

<li>You can rename the program you are trying to link.

<li>You can change the way Novell searches for files (a.k.a. <dfn>the
search mode</dfn>), so that it won't look in the directories on your
<code>PATH</code>.

<li>You can change your access rights to the directory on the <code>PATH</code>
where the other files reside, so that you won't have write privileges to
that directory.

<li>You can change the search mode for <code>STUBIFY</code> and the linker (or for
any other program that gives you that trouble) by running commands like
these:

<pre>  SMODE stubify.exe 2
  SMODE ld.exe 2
</pre>

</ol>

<p><hr>
[an error occurred while processing this directive]