| Anonymous | Login | Signup for a new account | 11-10-2008 10:40 PST |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0000091 | [buildroot] Other | minor | always | 02-09-05 02:30 | 02-12-07 05:50 | ||||
| Reporter | Michael | View Status | public | ||||||
| Assigned To | buildroot | ||||||||
| Priority | normal | Resolution | duplicate | ||||||
| Status | closed | Product Version | |||||||
| Summary | 0000091: toolchain c++ compiler was not built | ||||||||
| Description |
- Configure buildroot wihthout the c++ compiler - Build the system by calling make in the top level dir - Call make menuconfig and select 'Build/install c++ compiler and libstdc++' - Call make again and the c++ compiler will not be build |
||||||||
| Additional Information | |||||||||
| Attached Files | |||||||||
|
|
|||||||||
Notes |
|
|
(0000053) scott 02-22-05 10:54 |
I've had this same problem. It's because that flag (to build C++) only changes an option passed to configure for gcc. The solution is to force configure to run again either my removing the '.configured' file or by doing a full clean on gcc. remove the .configured file, which will cause gcc mk to run configure: rm $(TOOL_BUILD_DIR)/gcc-$(GCC_VERSION)-final which for me, looks like: rm toolchain_build_powerpc/gcc-3.4.3-final/.configured Or, you can remove the whole gcc area, causing it to build again. make gcc-clean; make gcc The ideal solution would sense a change in the flag setting, and remove the .configured file automatically. hope this helps. |
|
(0000630) vapier 10-17-05 15:11 |
dupe of http://busybox.net/bugs/view.php?id=51 [^] |
| Copyright © 2000 - 2006 Mantis Group |