From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 16027] problems building on fedora-40
Date: Wed, 01 May 2024 05:30:52 +0000 [thread overview]
Message-ID: <bug-16027-163-lPRUN1fgDU@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-16027-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=16027
swerve_olive366@simplelogin.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|INVALID |---
Status|RESOLVED |REOPENED
--- Comment #6 from swerve_olive366@simplelogin.com ---
Indeed, ncurses is working again. What about the error in comment #2? Is it
working for you?
I have fedora 40 too, but after running `make` I still get an error:
Unknown option 'passive-ftp'
make: *** [package/pkg-generic.mk:179:
/buildroot/output/build/host-pkgconf-1.6.3/.stamp_downloaded] Error 1
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-05-01 5:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 18:45 [Buildroot] [Bug 16027] New: problems building on fedora-40 bugzilla
2024-04-09 19:21 ` [Buildroot] [Bug 16027] " bugzilla
2024-04-09 19:23 ` bugzilla
2024-04-09 19:42 ` bugzilla
2024-04-30 14:13 ` bugzilla
2024-04-30 14:59 ` bugzilla
2024-05-01 5:30 ` bugzilla [this message]
2024-05-01 7:25 ` bugzilla
2024-05-01 9:53 ` bugzilla
2024-05-01 10:08 ` bugzilla
2024-05-01 15:08 ` bugzilla
2024-06-08 13:00 ` bugzilla
2024-06-15 15:22 ` bugzilla
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=bug-16027-163-lPRUN1fgDU@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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