From: Andrey Repin <anrdaemon@yandex.ru>
To: Daniel Goldman <dgoldman@ehdp.com>, cygwin@cygwin.com
Subject: Re: Compile test ncurses program to run independent of cygwin?
Date: Thu, 05 Nov 2015 17:35:00 -0000 [thread overview]
Message-ID: <1938935272.20151105203026@yandex.ru> (raw)
In-Reply-To: <563B0A76.3060509@ehdp.com>
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 -I /usr/x86_64-pc-cygwin/sys-root/usr/include/
> ncurses.c -L /usr/x86_64-pc-cygwin/sys-root/usr/lib/ -lncurses
> ... undefined reference to `initscr'
> ... more "undefined reference" error messages
> ------------------------------------------------------------
> 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.
> 2) If not, to compile ncurses.c to run in dos window, independent of
> cygwin, do I have to set up the ncurses library myself?
> I tried to get an answer from the docs, it seems unclear.
--
With best regards,
Andrey Repin
Thursday, November 5, 2015 20:29:01
Sorry for my terrible english...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2015-11-05 17:35 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 [this message]
2015-11-05 17:48 ` Corinna Vinschen
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=1938935272.20151105203026@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=dgoldman@ehdp.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).