From: Carl Thompson <cet@carlthompson.net>
To: "Parker, Ron" <rdparker@butlermfg.com>
Cc: Cygwin List <cygwin@sourceware.cygnus.com>
Subject: Re: problems with latest Cygwin 1.1
Date: Mon, 05 Jun 2000 18:20:00 -0000 [thread overview]
Message-ID: <393C523D.E1B38641@carlthompson.net> (raw)
In-Reply-To: <20000605223940.20829803A@carlthompson.net>
"Parker, Ron" wrote:
> ...
> I could refer you back to the same set of messages, but...
>
> Using g++ always causes the application to be linked against libm.a,
> which is a symlink to libcygwin.a. The work around is to use gcc with
> the -lstdc++ switch, if needed. This will link without libm.a.
This doesn't seem to work, unfortunately. Compiling this test program
// cet3.cxx
#include <stream.h>
main() {
cerr << "This is a test!" << endl ;
}
with this command line
gcc -g cet3.cxx -o cet3 -mno-cygwin -lstdc++
produces the attached copious error output. Also, what happens if I want to
use the math library in my app? Moreover, this "solution" requires hacking
my configure scripts and makefiles when they should work automatically.
Finally, I don't think it's unreasonable for me to say that compiling C++
apps with g++ should work, especially when it worked in a previous release
(b20).
> ...
> I will also send you the fixed g++.exe if you would like. It is about
> 29KB.
OK, thanks.
Thanks again,
Carl Thompson
/bin/../lib/gcc-lib/i686-pc-cygwin/2.95.2/libstdc++.a(iostream.o)(.text+0x154): undefined reference to `_imp___ctype_'
/bin/../lib/gcc-lib/i686-pc-cygwin/2.95.2/libstdc++.a(iostream.o)(.text+0x521): undefined reference to `_imp___ctype_'
/bin/../lib/gcc-lib/i686-pc-cygwin/2.95.2/libstdc++.a(iostream.o)(.text+0x17c7): undefined reference to `_impure_ptr'
/bin/../lib/gcc-lib/i686-pc-cygwin/2.95.2/libstdc++.a(iostream.o)(.text+0x17d8): undefined reference to `_impure_ptr'
/bin/../lib/gcc-lib/i686-pc-cygwin/2.95.2/libstdc++.a(streambuf.o)(.text+0x3e7): undefined reference to `__errno'
/bin/../lib/gcc-lib/i686-pc-cygwin/2.95.2/libstdc++.a(stdstrbufs.o)(.text+0x46): undefined reference to `_impure_ptr'
/bin/../lib/gcc-lib/i686-pc-cygwin/2.95.2/libstdc++.a(stdiostream.o)(.text+0x16c): undefined reference to `__srget'
/bin/../lib/gcc-lib/i686-pc-cygwin/2.95.2/libstdc++.a(iovfscanf.o)(.text+0x60): undefined reference to `_imp___ctype_'
/bin/../lib/gcc-lib/i686-pc-cygwin/2.95.2/libstdc++.a(iovfscanf.o)(.text+0x8d): undefined reference to `_imp___ctype_'
/bin/../lib/gcc-lib/i686-pc-cygwin/2.95.2/libstdc++.a(iovfscanf.o)(.text+0x584): undefined reference to `_imp___ctype_'
/bin/../lib/gcc-lib/i686-pc-cygwin/2.95.2/libstdc++.a(iovfscanf.o)(.text+0x5d1): undefined reference to `_imp___ctype_'
/bin/../lib/gcc-lib/i686-pc-cygwin/2.95.2/libstdc++.a(iovfscanf.o)(.text+0x85d): undefined reference to `_imp___ctype_'
/bin/../lib/gcc-lib/i686-pc-cygwin/2.95.2/libstdc++.a(iovfscanf.o)(.text+0x8b4): more undefined references to `_imp___ctype_' follow
/bin/../lib/gcc-lib/i686-pc-cygwin/2.95.2/libstdc++.a(fileops.o)(.text+0x194): undefined reference to `__errno'
/bin/../lib/gcc-lib/i686-pc-cygwin/2.95.2/libstdc++.a(fileops.o)(.text+0x206): undefined reference to `__errno'
/bin/../lib/gcc-lib/i686-pc-cygwin/2.95.2/libstdc++.a(fileops.o)(.text+0x261): undefined reference to `__errno'
/bin/../lib/gcc-lib/i686-pc-cygwin/2.95.2/libstdc++.a(fileops.o)(.text+0x390): undefined reference to `__errno'
/bin/../lib/gcc-lib/i686-pc-cygwin/2.95.2/libstdc++.a(fileops.o)(.text+0x459): undefined reference to `__errno'
/bin/../lib/gcc-lib/i686-pc-cygwin/2.95.2/libstdc++.a(fileops.o)(.text+0x5b1): more undefined references to `__errno' follow
/bin/../lib/gcc-lib/i686-pc-cygwin/2.95.2/libstdc++.a(floatconv.o)(.text+0x128d): undefined reference to `__infinity'
/bin/../lib/gcc-lib/i686-pc-cygwin/2.95.2/libstdc++.a(floatconv.o)(.text+0x13ed): undefined reference to `__errno'
/bin/../lib/gcc-lib/i686-pc-cygwin/2.95.2/libgcc.a(_eh.o)(.text+0x389): undefined reference to `_impure_ptr'
collect2: ld returned 1 exit status
next parent reply other threads:[~2000-06-05 18:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20000605223940.20829803A@carlthompson.net>
2000-06-05 18:20 ` Carl Thompson [this message]
2000-06-05 18:37 ` Chris Faylor
2000-06-05 18:42 ` Carl Thompson
[not found] <20000606170446.97480803A@carlthompson.net>
2000-06-06 11:48 ` Carl Thompson
2000-06-06 10:00 Parker, Ron
-- strict thread matches above, loose matches on Subject: below --
2000-06-05 15:35 Parker, Ron
[not found] <20000605175626.9DCBC803A@carlthompson.net>
2000-06-05 14:57 ` Carl Thompson
2000-06-05 10:52 Parker, Ron
2000-06-04 22:37 Carl Thompson
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=393C523D.E1B38641@carlthompson.net \
--to=cet@carlthompson.net \
--cc=cygwin@sourceware.cygnus.com \
--cc=rdparker@butlermfg.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).