From: Mumit Khan <khan@xraylith.wisc.edu>
To: Brad Porter <bporter@NETdelivery.com>
Cc: Steve Biskis <mlx@san.rr.com>, cygwin@sourceware.cygnus.com
Subject: RE: _ctype_
Date: Thu, 25 Feb 1999 10:10:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.93.990225120730.7845J-100000@modi.xraylith.wisc.edu> (raw)
In-Reply-To: <604BE7100DB8D21180C900805FC772ABEC29@berlin.netdelivery>
On Thu, 25 Feb 1999, Brad Porter wrote:
> Sorry. I didn't intend this to be a "bug report" but more
> of "what have I done wrong?" I believe it is due to having the snapshot
> release, as Steve suggested. Anyway, the libstdc++.a modules that have the
> undefined symbols are iostream.o and iovscanf.o
Thank you! That's what I needed to know. Looks like we need to rebuild all
the object modules that uses ctype etc when using the new cygwin development
snapshots. The interface for ctype was changed since b20.1, so it's
something that I don't see (I build everything with a stock b20.1 copy).
Unfortunately, I don't a simple workaround other than rebuilding the C++
runtime library in this case.
Regards,
Mumit
ps: I'm going to copy this to the cygwin list as well. Hopefully that's
not a problem.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: Mumit Khan <khan@xraylith.wisc.edu>
To: Brad Porter <bporter@NETdelivery.com>
Cc: Steve Biskis <mlx@san.rr.com>, cygwin@sourceware.cygnus.com
Subject: RE: _ctype_
Date: Sun, 28 Feb 1999 23:02:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.93.990225120730.7845J-100000@modi.xraylith.wisc.edu> (raw)
Message-ID: <19990228230200.7hC24JJA1ihlJVttBPwKJFT8vYz1LxVG2v93U7PFh0Q@z> (raw)
In-Reply-To: <604BE7100DB8D21180C900805FC772ABEC29@berlin.netdelivery>
On Thu, 25 Feb 1999, Brad Porter wrote:
> Sorry. I didn't intend this to be a "bug report" but more
> of "what have I done wrong?" I believe it is due to having the snapshot
> release, as Steve suggested. Anyway, the libstdc++.a modules that have the
> undefined symbols are iostream.o and iovscanf.o
Thank you! That's what I needed to know. Looks like we need to rebuild all
the object modules that uses ctype etc when using the new cygwin development
snapshots. The interface for ctype was changed since b20.1, so it's
something that I don't see (I build everything with a stock b20.1 copy).
Unfortunately, I don't a simple workaround other than rebuilding the C++
runtime library in this case.
Regards,
Mumit
ps: I'm going to copy this to the cygwin list as well. Hopefully that's
not a problem.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next parent reply other threads:[~1999-02-25 10:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <604BE7100DB8D21180C900805FC772ABEC29@berlin.netdelivery>
1999-02-25 10:10 ` Mumit Khan [this message]
1999-02-28 23:02 ` _ctype_ Mumit Khan
1999-02-25 20:38 _ctype_ N8TM
1999-02-28 23:02 ` _ctype_ N8TM
-- strict thread matches above, loose matches on Subject: below --
1999-02-25 8:52 _ctype_ Steve Biskis
[not found] ` < 005d01be60df$31354220$080216c0@newt.san.rr.com >
1999-02-25 9:55 ` _ctype_ Mumit Khan
1999-02-28 23:02 ` _ctype_ Mumit Khan
1999-02-28 23:02 ` _ctype_ Steve Biskis
1999-02-24 15:10 _ctype_ Brad Porter
[not found] ` < 604BE7100DB8D21180C900805FC772ABEC22@berlin.netdelivery >
1999-02-24 20:01 ` _ctype_ Mumit Khan
1999-02-28 23:02 ` _ctype_ Mumit Khan
1999-02-28 23:02 ` _ctype_ Brad Porter
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=Pine.SUN.3.93.990225120730.7845J-100000@modi.xraylith.wisc.edu \
--to=khan@xraylith.wisc.edu \
--cc=bporter@NETdelivery.com \
--cc=cygwin@sourceware.cygnus.com \
--cc=mlx@san.rr.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).