public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Vadim Zeitlin <zeitlin@dptmaths.ens-cachan.fr>
To: Chris <Christine.Pourcelot@inria.fr>
Cc: cygwin <cygwin@sourceware.cygnus.com>,
	wxwin-developers <wxwin-developers@wx.dent.med.uni-muenchen.de>
Subject: RE: troubles while building wxWindows/C++ Mingw executables usin
Date: Wed, 31 Mar 1999 19:45:00 -0000	[thread overview]
Message-ID: <XFMail.990310141736.zeitlin@dptmaths.ens-cachan.fr> (raw)
Message-ID: <19990331194500.BXCjH-y0fgYtCCWGRIU7nv_wgo7oPp9VvudLpomlPYg@z> (raw)
In-Reply-To: <36E64070.944A6B90@inria.fr>

 Hello,

On 10-Mar-99 Chris wrote:
> I'm also using wxWindows 2.0 and i've some troubles while linking some
> samples. For example, I want to run the "minimal" sample and I get some
> "undefined reference ":
...
> /wx/lib/libwx.a(textctrl.o): In function
> `wxTextCtrl::GLOBAL_$I$GetClassInfo(void) const':
> /wx/src/msw/textctrl.cpp:71: undefined reference to
> `streambuf::xsputn(char const *, long)'
> /wx/src/msw/textctrl.cpp:71: undefined reference to
> `streambuf::xsgetn(char *, long)'

 this might actually just mean that there are no such functions in
Cygwin's version of C++ iostream library (I do believe they're
standard - at least they're in the standard draft I have here).
  
> /wx/src/msw/textctrl.cpp:71: undefined reference to
> `streambuf::sys_read(char *, long)'
> /wx/src/msw/textctrl.cpp:71: undefined reference to
> `streambuf::sys_write(char const *, long)'

 The same here, except that these symbols don't seem to be standard.

 To work around these errors you might try to define NO_TEXT_WINDOW_STREAM
for wxWindows compilation.

> /usr/local/mingw-libs/libstdc++.a(iostream.o)(.text+0x18a9): undefined
> reference to `__imp__iob'
> /usr/local/mingw-libs/libstdc++.a(iostream.o)(.text+0x18b7): undefined
> reference to `__imp__iob'
> /usr/local/mingw-libs/libstdc++.a(streambuf.o)(.text+0x30c): undefined
> reference to `_errno'
> /usr/local/mingw-libs/libstdc++.a(stdstrbufs.o)(.text+0x2d): undefined
> reference to `__imp__iob'
> /usr/local/mingw-libs/libstdc++.a(fileops.o)(.text+0x173): undefined
> reference to `_errno'
> /usr/local/mingw-libs/libstdc++.a(fileops.o)(.text+0x1de): undefined
> reference to `_errno'
> /usr/local/mingw-libs/libstdc++.a(fileops.o)(.text+0x232): undefined
> reference to `_errno'
> /usr/local/mingw-libs/libstdc++.a(fileops.o)(.text+0x343): undefined
> reference to `_errno'
> /usr/local/mingw-libs/libstdc++.a(fileops.o)(.text+0x3f6): undefined
> reference to `_errno'
> /usr/local/mingw-libs/libstdc++.a(fileops.o)(.text+0x539): more
> undefined references to `_errno' follow
> /usr/local/mingw-libs/libstdc++.a(floatconv.o)(.text+0x12e7): undefined
> reference to `__imp__HUGE_dll'
> /usr/local/mingw-libs/libstdc++.a(floatconv.o)(.text+0x145a): undefined
> reference to `_errno'
> collect2: ld returned 1 exit status
> make: *** [minimal.exe] Error 1

 No idea about these. 

> So, my question is :
> Am I doing something wrong or should is it impossible to make
> cross-compilation with wxWindows tools ?

 There is no reason it shouldn't be possible. It would be interesting
to hear whether you succeed with it finally and what had you to change
to do it.

 Good luck!
VZ

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


  reply	other threads:[~1999-03-31 19:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-10  1:46 troubles while building wxWindows/C++ Mingw executables using Cygwin Chris
     [not found] ` < 36E64070.944A6B90@inria.fr >
1999-03-10  5:17   ` Vadim Zeitlin [this message]
     [not found]     ` < XFMail.990310141736.zeitlin@dptmaths.ens-cachan.fr >
1999-03-11 16:47       ` troubles while building wxWindows/C++ Mingw executables usin Mumit Khan
1999-03-31 19:45         ` Mumit Khan
1999-03-31 19:45     ` Vadim Zeitlin
1999-03-10 11:18   ` troubles while building wxWindows/C++ Mingw executables using Cygwin Mumit Khan
1999-03-31 19:45     ` Mumit Khan
1999-03-31 19:45 ` Chris

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=XFMail.990310141736.zeitlin@dptmaths.ens-cachan.fr \
    --to=zeitlin@dptmaths.ens-cachan.fr \
    --cc=Christine.Pourcelot@inria.fr \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=wxwin-developers@wx.dent.med.uni-muenchen.de \
    /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).