public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "Lusk, Timothy             CCS" <Timothy.Lusk@lenel.com>
To: "crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: crosstool-NG Cygwin Build Fails
Date: Mon, 07 May 2012 21:06:00 -0000	[thread overview]
Message-ID: <022F8C6A86906F4CA6FCE17F54B1BFCE07AFC5@UUSNWE1M.na.utcmail.com> (raw)

The newest two versions of crosstool-NG (1.14.x and 1.15.x) no longer build correctly on Cygwin.  It fails to find libintl and nconf fails to find the folder with the ncurses sources.  It also doesn't like it if you're using the wide character version of ncurses (ncursesw), but the first two issues still occur when using the original ncurses library.  I used the following patches to get it building in Cygwin.  Just a heads up for anyone else who might run into this problem.

$ diff crosstool-ng-1.15.0_old/kconfig/Makefile crosstool-ng-1.15.0/kconfig/Makefile
10c10
< LDFLAGS =
---
> LDFLAGS =
37a38
> conf: LDFLAGS += -lintl
44c45
< mconf: LDFLAGS += $(NCURSES_LDFLAGS)
---
> mconf: LDFLAGS += -lintl $(NCURSES_LDFLAGS)
50,51c51,52
< $(nconf_OBJ) $(nconf_DEP): CFLAGS += $(INTL_CFLAGS)
< nconf: LDFLAGS += -lmenu -lpanel -lncurses
---
> $(nconf_OBJ) $(nconf_DEP): CFLAGS += -I/usr/include/ncursesw/ $(INTL_CFLAGS)
> nconf: LDFLAGS += -lintl -lmenuw -lpanelw -lncursesw

$ diff crosstool-ng-1.15.0_old/kconfig/nconf.c crosstool-ng-1.15.0/kconfig/nconf.c
1521c1521
<       ESCDELAY = 1;
---
>       set_escdelay(1);

Tim


--
For unsubscribe information see http://sourceware.org/lists.html#faq

             reply	other threads:[~2012-05-07 21:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07 21:06 Lusk, Timothy             CCS [this message]
2012-05-08 10:28 ` Yann E. MORIN
2012-05-08 15:18 Lusk, Timothy             CCS

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=022F8C6A86906F4CA6FCE17F54B1BFCE07AFC5@UUSNWE1M.na.utcmail.com \
    --to=timothy.lusk@lenel.com \
    --cc=crossgcc@sourceware.org \
    /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).