Gavin Lambert wrote: > > dist/vendors/config/armnommu/config.arch" file? > > Usually in your board-specific config.arch file (not the generic armnommu one > -- the one that you selected in the toplevel Makefile) there are three lines > like this: > > # DISABLE_XIP := 1 # XIP works fine > # DISABLE_MOVE_RODATA := 1 # move-rodata is fine > # DISABLE_SHARED_LIBS := 1 # shared libs are fine > > Uncomment all three of these to disable XIP. You will also need to do a > complete rebuild (make clean), otherwise you can have mixed object files, > which cause problems.
So we conclude that the tool on uclinux.org does incorrectly compiles the generic ARM-nommu architecture support from uclinux.org? I've been collecting posts related to toolchains from uclinux-dev for a while, so that I have a clue next time I need to find a working toolchain. There are quite a few toolchain branches, and seemingly no reliable authority for compiled toolchains that work for every target variation. Nor even a place where you can be sure all the patches get to "eventually". Back in ye olde days we posted GCC patches to the GCC developers and they appeared in GCC releases :-) The toolchain links on uclinux.org are a bit hit-and-miss, depending on what you're building for. Between the lines (it could be more clear) is "Try this toolchain - it works very well for us - but it's work in progress and you'll need a toolchain from somewhere else (find it yourself) for some configurations different to ours". I'm wondering if uclinux's toolchain page could be a bit more informative about the locations of toolchains that people ought to try, instead of offering a single one and no hint that it's not for everyone? -- Jamie _______________________________________________ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
