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] |
this kinda presumes you've already done something like "make oldconfig" and generated linux/autoconf.h ... bgat@open-widgets.com wrote: > Where are you getting include/linux/autoconf.h from? It isn't created > if I strictly follow your procedure below... > > b.g. > > On Sun, May 06, 2001 at 01:06:09PM -0500, Joe deBlaquiere wrote: > >> My solution to this has always been to specify ARCH,PROCESSOR, and >> INCDIR. Here's the StrongARM version... >> >> (cd $sysroot_stage1/usr ; \ >> $MAKE -I$kernel_src ARCH=arm PROCESSOR=armv INCDIR=sa1100 >> TOPDIR=`pwd` symlinks include/linux/version.h) >> >> What somebody really needs to do is determine how generic something like >> this is. My initial guess is that the compiler is probably accepable for >> any armv system. Any reason to suspect otherwise? >> >> -- >> Joe >> >> bgat@open-widgets.com wrote: >> >> >>> Phil: >>> >>> >>> I had assumed that, but it turns out that there are two symlinks in >>> the asm-arm subdir that get set to architecture-specific and >>> platform-specific subdirs. I couldn't find another way to set the >>> symlinks, and the includes used during the glibc build don't seem to >>> work without them. >>> >>> All I'm after is a way to set the symlinks to *something*. Menuconfig >>> was a quick-and-dirty. >>> >>> b.g. >>> >>> >>> On Fri, Apr 27, 2001 at 09:30:13PM +0100, Philip Blundell wrote: >>> >>> >>>>> On my way to an updated crossgcc faq, I have produced a script that >>>>> automatically builds an arm-linux or powerpc-linux toolchain FROM >>>>> SCRATCH, *without* using newlib headers anywhere. >>>> >>>> It's probably not necessary to actually run menuconfig for ARM. I think you >>>> can get away with running `make oldconfig' and redirecting input from >>>> /dev/null. Nothing in the toolchain build process that I can think of cares >>>> about the kernel configuration, and indeed the binaries that you end up with >>>> will run on any subarchitecture. >>>> >>>> p. >>>> >>>> >>>> >>>> ------ >>>> Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ >>>> Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com >>>> >>> >> >> -- >> Joe deBlaquiere >> Red Hat, Inc. >> 307 Wynn Drive >> Huntsville AL, 35805 >> voice : (256)-704-9200 >> fax : (256)-837-3839 >> -- Joe deBlaquiere Red Hat, Inc. 307 Wynn Drive Huntsville AL, 35805 voice : (256)-704-9200 fax : (256)-837-3839 ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |