From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Compile test ncurses program to run independent of cygwin?
Date: Thu, 05 Nov 2015 17:48:00 -0000 [thread overview]
Message-ID: <20151105174851.GA20857@calimero.vinschen.de> (raw)
In-Reply-To: <1938935272.20151105203026@yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 1828 bytes --]
On Nov 5 20:30, Andrey Repin wrote:
> Greetings, Daniel Goldman!
>
> > # Found /usr/x86_64-pc-cygwin/sys-root/usr/lib/libncurses.a
> > # Will this let me compile for dos window? Apparently not.
> > $ i686-pc-mingw32-gcc \
^^^^
So you're building for 32 bit mingw
> > -I /usr/x86_64-pc-cygwin/sys-root/usr/include/
^^^^^^^^^^^^^^^^
Pointing the compiler to header files for a Cygwin build,
which is a *different* target (i686 vs. x86_64 *and* mingw
vs. cygwin)...
> > ncurses.c -L /usr/x86_64-pc-cygwin/sys-root/usr/lib/ -lncurses
^^^^^^^^^^^^^^^^
same here
> > ... undefined reference to `initscr'
> > ... more "undefined reference" error messages
...and that's logical result. Along the same lines you could try to
link powerpc-linux ncurses against arm-freebsd binary. That just won't
work.
What you need is a i686-mingw ncurses. Have a look around on the net or
try to build your own. However, it will probably not work correctly in
a Cygwin pseudo tty due to lack of the Cygwin compat layer implementing
them.
> > ------------------------------------------------------------
>
> > My questions:
>
> > 1) Did I make a compile-line syntax error? Is there a variation of the
> > i686-pc-mingw32-gcc command line so I can use cygwin to compile
> > ncurses.c to run in dos window, independent of cygwin?
>
> I'm no expert, but my first answer would be "yes".
> You shouldn't use cross-compilers directly, rather, use appropriate GCC
> switches to specify host and target subsystems.
Nope, use cross compilers.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-11-05 17:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 7:51 Daniel Goldman
2015-11-05 17:35 ` Andrey Repin
2015-11-05 17:48 ` Corinna Vinschen [this message]
2015-11-05 18:29 ` Yaakov Selkowitz
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=20151105174851.GA20857@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.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).