From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0002634]: path to ncurses seems to contain extra 'gnu/'
Date: Mon, 24 Mar 2008 10:14:23 -0700 [thread overview]
Message-ID: <63bbbfcd98df8c1450360c376e6652fb@busybox.net> (raw)
A NOTE has been added to this issue.
======================================================================
http://busybox.net/bugs/view.php?id=2634
======================================================================
Reported By: travishein
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 2634
Category: Other
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
======================================================================
Date Submitted: 03-22-2008 09:42 PDT
Last Modified: 03-24-2008 10:14 PDT
======================================================================
Summary: path to ncurses seems to contain extra 'gnu/'
Description:
The value of the variable $(BR2_GNU_MIRROR) seems to contain the /gnu/ path
component, so in the package/ncurses/ncurses.mk where it includes
gnu/ncurses again it is not finding it
======================================================================
----------------------------------------------------------------------
travishein - 03-22-08 13:21
----------------------------------------------------------------------
hmm actually everything that relies on the BR2_GNU_MIRROR variable is
currently suffering from this issue.
Im not sure, if the BR2_GNU_MIRROR in the .config (and .defconfig) should
be changed from http://ftp.gnu.org/pub/gnu to http://ftp.gnu.org/pub
or if the following package that refer to BR2_GNU_MIRROR should have their
path updated ?
package/gawk/gawk.mk
package/gzip/gzip.mk
package/autoconf/autoconf.mk
package/ncurses/ncurses.mk
package/findutils/findutils.mk
package/gettext/gettext.mk
package/editors/ed/ed.mk
package/bash/bash.mk
package/diffutils/diffutils.mk
package/wget/wget.mk
package/tar/tar.mk
package/m4/m4.mk
package/make/make.mk
package/bison/bison.mk
package/sed/sed.mk
package/automake/automake.mk
package/readline/readline.mk
package/libtool/libtool.mk
package/coreutils/coreutils.mk
----------------------------------------------------------------------
gnat - 03-24-08 10:14
----------------------------------------------------------------------
a patch to fix all gnu packages is attached to bug
http://busybox.net/bugs/view.php?id=2654.
Issue History
Date Modified Username Field Change
======================================================================
03-22-08 09:42 travishein New Issue
03-22-08 09:42 travishein Status new => assigned
03-22-08 09:42 travishein Assigned To => buildroot
03-22-08 09:42 travishein File Added: ncurses_path_20080321.diff
03-22-08 13:21 travishein Note Added: 0005834
03-24-08 10:14 gnat Note Added: 0005854
======================================================================
next reply other threads:[~2008-03-24 17:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 17:14 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-26 9:48 [Buildroot] [buildroot 0002634]: path to ncurses seems to contain extra 'gnu/' bugs at busybox.net
2008-03-26 3:30 bugs at busybox.net
2008-03-22 20:21 bugs at busybox.net
2008-03-22 16:42 bugs at busybox.net
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=63bbbfcd98df8c1450360c376e6652fb@busybox.net \
--to=bugs@busybox.net \
--cc=buildroot@busybox.net \
/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