Bug 4772 - Add uClibc configuration file option to crosstool-ng toolchain support
Summary: Add uClibc configuration file option to crosstool-ng toolchain support
Status: RESOLVED WONTFIX
Alias: None
Product: buildroot
Classification: Unclassified
Component: Other (show other bugs)
Version: 2012.02
Hardware: PC Linux
: P5 enhancement
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-18 04:32 UTC by hank
Modified: 2013-05-26 08:54 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description hank 2012-02-18 04:32:39 UTC 
Currently when selecting a crosstool-ng-uClibc toolchain you cannot specify the uClibc config file as it is always written over by the default. This patch adds an option to the menuconfig to specify an alternative.
Comment 1 Samuel Martin 2012-02-18 11:50:41 UTC 
(In reply to comment #0)
> Currently when selecting a crosstool-ng-uClibc toolchain you cannot specify the
> uClibc config file as it is always written over by the default. This patch adds
> an option to the menuconfig to specify an alternative.

Actually, when selecting a crosstool-NG toolchain in 'make menuconfig', you can then run 'make ctng-menuconfig' to customize it, and specify an uclibc config-file for uClibc toolchains.
Comment 2 hank 2012-02-19 02:50:02 UTC 
Ah ok, I wasn't aware that you could do that. 
Even though, you can't really support multiple configs using the make *_defconfig targets if you have to  manually specify the uclibc library. 
In that case I guess you can over write the default config in the toolchain dir.
Comment 3 Thomas Petazzoni 2013-05-26 08:54:44 UTC 
The feature already exists, and the Crosstool-NG backend has been marked deprecated. I believe it's not really worth fixing this particular bug.