| Anonymous | Login | Signup for a new account | 11-10-2008 11:48 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 | |||||||
| 0002524 | [buildroot] Architecture Specific | minor | always | 03-12-08 02:03 | 04-11-08 00:59 | |||||||
| Reporter | KHAksnes | View Status | public | |||||||||
| Assigned To | buildroot | |||||||||||
| Priority | normal | Resolution | open | |||||||||
| Status | assigned | Product Version | ||||||||||
| Summary | 0002524: kernel symlinks broken | |||||||||||
| Description |
This bug is present in current trunk versions of buildroot. I am at revision 21311 in subversion. I am building a fairly plain i686 system. The kernel builds nicely after applying my workaround for bug 0002504, but it doesn't install well under binaries. A symlink is installed pointing to a nonexisting file. This symlink also breaks previous naming conventions as it doesn't add the .bz suffix for a bzImage kernel. At least 3 things are wrong. 1) The binaries directory should contain physical copies not symlinks. 2) The right kernel file must be copied to the binaries/$PROJECTNAME 3) Changing naming strategy shouldn't be done unless strictly necessary, some of us have installation scripts that stops working |
|||||||||||
| Additional Information |
My config file is attached as FW.config The only reason this bug isn't classified as major is that a fairly obvious manual workaround exists. Replace the offending symlink with a properly named copy of the x86 bzImage file from the kernel build. |
|||||||||||
| Attached Files |
|
|||||||||||
|
|
||||||||||||
| Copyright © 2000 - 2006 Mantis Group |