From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001914]: many packages do not run CONFIG_UPDATE
Date: Tue, 8 Jan 2008 11:38:03 -0800 [thread overview]
Message-ID: <e2557627849e8ab8fe735ffaa50ce492@busybox.net> (raw)
The following issue has been SUBMITTED.
======================================================================
http://busybox.net/bugs/view.php?id=1914
======================================================================
Reported By: dann
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 1914
Category: Other
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
======================================================================
Date Submitted: 01-08-2008 11:38 PST
Last Modified: 01-08-2008 11:38 PST
======================================================================
Summary: many packages do not run CONFIG_UPDATE
Description:
Many packages do not run ${CONFIG_UPDATE} so they cannot be compiled on
platforms
that require a more up to date config.guess and config.sub that what is
shipped with the package.
A patch to do that for a few packages is attached.
Please check it in.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
01-08-08 11:38 dann New Issue
01-08-08 11:38 dann Status new => assigned
01-08-08 11:38 dann Assigned To => buildroot
01-08-08 11:38 dann File Added: buildroot-CONFIG_UPDATE.patch
======================================================================
reply other threads:[~2008-01-08 19:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e2557627849e8ab8fe735ffaa50ce492@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