This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
arm-unknown-linux-gnu/include/asm/param.h:13:41: asm/arch/param.h: No such file or directory
Say, I wonder if make ARCH=$ARCH include/asm include/linux/version.h isn't quite sufficient? Maybe toolchain.sh needs to do something like make ARCH=$ARCH include/asm include/asm/arch include/linux/version.h
This depends on the particular ARM architecture (Integrator, Footbridge, etc) you want to compile for. ... make oldconfig ... automatically creates any needed symlinks. You can also short-circuit this with:
make symlinks
which only creates the needed symlinks in include/asm-arm, if you defined a specific architecture.
Right -- for linux-2.4. I guess my question is for linux-2.6, which did away with the 'symlinks' target. (Say, does 'make oldconfig' really create symlinks? If it does in linux-2.6, that'd be quite handy. I bet it doesn't, though.)
A number of canned configuration files are in arch/arm/def-configs.
Hrm. Yes, I should probably use one of them, since the arm maintainer prefers it over 'make defconfig'. - Dan
------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |