public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: john biro <biro@asic-alliance.com>
To: gnu-win32@cygnus.com, biro@asic-alliance.com
Subject: B19: problem running DLLTOOL on NT4.0 on a drive that the dlltool is not installed on
Date: Tue, 28 Jul 1998 10:05:00 -0000	[thread overview]
Message-ID: <35BE053D.5134F03C@asic-alliance.com> (raw)

Hi,

I am having trouble running DLLTOOL on a NT4.0 dual P2(200) platform,
and on a dual boot (c: win95 d:NT4.0).

The DLLTOOL will work if it is run from the same drive that the DLLTOOL
is
installed on, or a partition on that same disk.
(c:\cygnus\b19\H-i386-cygwin32\bin\ )

If however I move my script to another drive on the same system then the

DLLTOOL dumps many *.o files
(dh.o, dh.s, dh0.o, dh1.o, dh10.o ......... etc. until you break out of
the program)

I tried it on a dual boot (c: win95, d: nt4.0) and no matter which disk
I try to
use DLLTOOL it dumps many *.o files.

The path is right as it can see the DLLTOOL and the gcc etc. tools.

I am using PERL (makedll.pl) to make the $PLILIB.dll, but I have also
tried it
as a command line on a dos window and it does the same thing,


.... begin perl code fragment
print "Building $PLILIB.a library ...    ";
system "dlltool --as=as --dllname $PLILIB.dll --def $PLILIB.def
--output-lib $PLILIB.a";
check_status($?);
... end perl code fragment

thanks john


-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

                 reply	other threads:[~1998-07-28 10:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=35BE053D.5134F03C@asic-alliance.com \
    --to=biro@asic-alliance.com \
    --cc=gnu-win32@cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).