Menu
▾
▴
blob-cvs-commit
|
From: Yamijala S. <Sri...@si...> - 2003-10-01 10:38:45
|
Hallo All !!! Could someone pls clarify as to why the linux kernel source path is required for compiling 'blob'? I suppose the bootloader is a stand-alone program and should not have anything to do with the kernel source tree on my development machine when im cross-compiling. Pls help me by clarifying my doubt. Thank You Sridhar -----Original Message----- From: blo...@li... [mailto:blo...@li...] Sent: Tuesday, September 30, 2003 8:33 AM To: blo...@li... Subject: blob-cvs-commit digest, Vol 1 #232 - 2 msgs Send blob-cvs-commit mailing list submissions to blo...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/blob-cvs-commit or, via email, send a message with subject or body 'help' to blo...@li... You can reach the person managing the list at blo...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of blob-cvs-commit digest..." Today's Topics: 1. cross-compiling blob for LART from i386 (Yamijala Sridhar) 2. Re: cross-compiling blob for LART from i386 (Holger Schurig) --__--__-- Message: 1 From: Yamijala Sridhar <Sri...@si...> To: blo...@li... Subject: cross-compiling blob for LART from i386 Date: Mon, 29 Sep 2003 15:29:16 +0530 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C38670.579927E0 Content-Type: text/plain; charset="iso-8859-1" Hallo All ! May be this is a simple doubt but I would be glad to someone could help me. I read the "porting.txt" file that comes with blob but the instructions therein didnt help me completely. I tried the instructons in README file too but even then I wasnt successful.May be Im missing something vital. Could someone please help. First of all,I would like to know whether the source path mentioned in blob instructions is blob source path or the linux kernel source path?I have a feeling that kernel source path need not be required but i dont know.And, if in case it is kernel source path, is it the host x86 Linux source path or the SA-1110 Linux kernel source path?Could someone please clarify. And can someone please give me a step-by-step guidelines to do this. My environment is as below: Im cross-compiling blob on a host x86 machine for SA-1110/Linux(ARM), LART. My blob folder path is: home/sridhar/blob-2.0.5-pre2 with all subfolders and files in it. I followed the instructions in "porting.txt" but seem to falter after that. What do i do from here? Thanks in Advance Sridhar ------_=_NextPart_001_01C38670.579927E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-8859-1"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 5.5.2653.12"> <TITLE>cross-compiling blob for LART from i386</TITLE> </HEAD> <BODY> <P><FONT SIZE=3D2>Hallo All !</FONT> </P> <P><FONT SIZE=3D2>May be this is a simple doubt but I would be glad to = someone could help me.</FONT> <BR><FONT SIZE=3D2>I read the "porting.txt" file that comes = with blob but the instructions therein didnt help me completely.</FONT> <BR><FONT SIZE=3D2>I tried the instructons in README file too but even = then I wasnt successful.May be Im missing something vital.</FONT> <BR><FONT SIZE=3D2>Could someone please help.</FONT> </P> <P><FONT SIZE=3D2>First of all,I would like to know whether the source = path mentioned in blob instructions </FONT> <BR><FONT SIZE=3D2>is blob source path or the linux kernel source = path?I have a feeling that kernel source path</FONT> <BR><FONT SIZE=3D2>need not be required but i dont know.And, if in case = it is kernel source path, is it the host x86 Linux source path</FONT> <BR><FONT SIZE=3D2>or the SA-1110 Linux kernel source path?Could = someone please clarify.</FONT> </P> <P><FONT SIZE=3D2>And can someone please give me a step-by-step = guidelines to do this.</FONT> <BR><FONT SIZE=3D2>My environment is as below:</FONT> </P> <P><FONT SIZE=3D2>Im cross-compiling blob on a host x86 machine for = SA-1110/Linux(ARM), LART.</FONT> <BR><FONT SIZE=3D2>My blob folder path is: home/sridhar/blob-2.0.5-pre2 = with all subfolders and files in it.</FONT> <BR><FONT SIZE=3D2>I followed the instructions in = "porting.txt" but seem to falter after that.</FONT> </P> <P><FONT SIZE=3D2>What do i do from here?</FONT> </P> <P><FONT SIZE=3D2>Thanks in Advance</FONT> <BR><FONT SIZE=3D2>Sridhar</FONT> </P> </BODY> </HTML> ------_=_NextPart_001_01C38670.579927E0-- --__--__-- Message: 2 From: Holger Schurig <h.s...@mn...> To: blo...@li... Subject: Re: cross-compiling blob for LART from i386 Date: Mon, 29 Sep 2003 15:20:51 +0200 > need not be required but i dont know.And, if in case it is kernel > source path, is it the host x86 Linux source path > or the SA-1110 Linux kernel source path? The source path to the SA1110/PXA Linux kernel. It must be a kernel that already compiled successfully, so that include/asm and include/asm/arch point to the rigth directories. --__--__-- _______________________________________________ blob-cvs-commit mailing list blo...@li... https://lists.sourceforge.net/lists/listinfo/blob-cvs-commit End of blob-cvs-commit Digest |
|
From: Yamijala S. <Sri...@si...> - 2003-10-06 11:11:10
|
Well, could you pls tell me as to why blob needs the Linux kernel headers? I want to know because here, I have a configured Linux kernel source tree without the *.c files of the configured kernel.I have the *.h files though and all the makefiles etc. too with me. When I try to configure and compile the blob with this kernel source tree (without the *.c files) the configuration seems to be successful but at the gmake stage i get an error output which says "Nothing to do for 'all' " and stops. Could someone pls let me know what the problem is and why blob needs the kernel headers? Thank You Sridhar -----Original Message----- From: Christopher Hoover [mailto:ch...@mu...] Sent: Wednesday, October 01, 2003 9:39 PM To: Yamijala Sridhar; blo...@li... Subject: RE: blob-cvs-commit digest, Vol 1 #232 - 2 msgs >> Hallo All !!! >> Could someone pls clarify as to why the linux kernel >> source path is required for compiling 'blob'? >> I suppose the bootloader is a stand-alone program and >> should not have anything to do >> with the kernel source tree on my development machine >> when im cross-compiling. Blob (unfortunately) uses the kernel headers. You are correct that this is not the best idea, not only for the reasons you mention but also because the kernel headers change from time to time. -ch |
|
From: Christopher H. <ch...@mu...> - 2003-10-06 16:26:47
|
> Well, could you pls tell me as to why blob needs the Linux kernel = headers? blob doesn't use the kernel headers ($LINUX/include/linux) per se, but = it does leverage the architecture-specific headers ($LINUX/include/asm) to = get to the defines and structures that describe the processor and = peripherals. -ch =20 -----Original Message----- From: Yamijala Sridhar [mailto:Sri...@si...]=20 Sent: Monday, October 06, 2003 3:09 AM To: Christopher Hoover Cc: blo...@li... Subject: RE: blob-cvs-commit digest, Vol 1 #232 - 2 msgs Well, could you pls tell me as to why blob needs the Linux kernel = headers?=20 I want to know because here, I have a configured Linux kernel source = tree without=20 the *.c files of the configured kernel.I have the *.h files though and = all the makefiles etc. too=20 with me.=20 When I try to configure and compile the blob with this kernel source = tree (without the *.c files)=20 the configuration seems to be successful but at the gmake stage i get an error output which says=20 "Nothing to do for 'all' " and stops.=20 Could someone pls let me know what the problem is and why blob needs the kernel headers?=20 Thank You=20 Sridhar=20 -----Original Message-----=20 From: Christopher Hoover [mailto:ch...@mu...]=20 Sent: Wednesday, October 01, 2003 9:39 PM=20 To: Yamijala Sridhar; blo...@li...=20 Subject: RE: blob-cvs-commit digest, Vol 1 #232 - 2 msgs=20 >> Hallo All !!!=20 >> Could someone pls clarify as to why the linux kernel=20 >> source path is required for compiling 'blob'?=20 >> I suppose the bootloader is a stand-alone program and=20 >> should not have anything to do=20 >> with the kernel source tree on my development machine=20 >> when im cross-compiling.=20 Blob (unfortunately) uses the kernel headers. You are correct that this = is=20 not the best idea, not only for the reasons you mention but also because = the kernel headers change from time to time.=20 -ch=20 |
|
From: Yamijala S. <Sri...@si...> - 2003-10-09 12:49:22
|
Hi All!
Sorry for the long mail but could someone please be more specific and tell
me
what exactly BLOB looks for in a Configured Linux Kernel tree and why?
I mean could you pls confirm whether or not it needs *.c files from a
configured kernel tree.
I suppose it is logical that it should neither look for $LINUX/src/*.c files
nor should it look for $LINUX/include/linux/*.h files. Is this true?
Im asking these because i am trying to customise BLOB to my requirement and
Im facing problems.
The customisation that i did for BLOB is:
In "configure.in", I changed the --with-board=NAME to --with-board=lart.
Then in acconfig.h, I changed the #undef LART to #define LART and also
defined CPU as SA1100
Then in "configure", I changed the --with-board=NAME to --with-board=lart
and
--with-linux-prefix=/home/sridhar/linux-2.4.20 where i have a configured
Linux kernel tree
but with not all *.c files available.
The $LINUX/include/asm files are in the path:
/home/sridhar/linux-2.4.20/asm-arm/arch-sa1100
Then i type the following at the bash shell command prompt:
export CC=arm-linux-gcc
export OBJCOPY=arm-linux-objcopy
Then i run ./configure
I get the following output on the terminal:
Loading cache ./config.cache
checking for a BSD compatible install... (cached) /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... (cached) yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking whether to enable maintainer-specific portions of Makefiles... no
checking host system type... i686-pc-linux-gnu
checking for arm-linux-gcc... (cached) arm-linux-gcc
checking for arm-linux-objcopy... (cached) arm-linux-objcopy
checking for arm-linux-ranlib... (cached) arm-linux-ranlib
checking for arm-linux-ar... (cached) arm-linux-ar
checking for gcc... (cached) arm-linux-gcc
checking whether the C compiler (arm-linux-gcc ) works... yes
checking whether the C compiler (arm-linux-gcc ) is a cross-compiler... yes
checking whether we are using GNU C... (cached) yes
checking whether arm-linux-gcc accepts -g... (cached) yes
checking for ranlib... (cached) arm-linux-ranlib
checking for a BSD compatible install... /usr/bin/install -c
checking whether ln -s works... (cached) yes
checking target board... Delft University of Technology LART
checking if the Linux source tree in /usr/src/linux is sane... yes
checking for inline... (cached) inline
checking for C flags to get more warnings... -Wall
creating ./config.status
creating Makefile
creating doc/Makefile
creating include/Makefile
creating include/blob/Makefile
creating include/blob/arch/Makefile
creating src/Makefile
creating src/blob/Makefile
creating src/diag/Makefile
creating src/lib/Makefile
creating tools/Makefile
creating utils/Makefile
creating utils/build/Makefile
creating utils/mkparamblock/Makefile
creating include/blob/config.h
include/blob/config.h is
unchangedConfiguration------------------------------------------------------
------------------
Target board Delft University of Technology LART
C compiler arm-linux-gcc
C flags -Os -I/usr/src/linux/include -Wall -march=armv4
-mtune=strongarm1100 -fomit-frame-pointer
-fno-builtin -mapcs-32 -nostdinc
Linker flags -static -nostdlib
Objcopy tool arm-linux-objcopy
Objcopy flags -O binary -R .note -R .comment -S
Clock scaling support no
Memory test support no
Debugging commands support no
LCD support no
MD5 support no
Run-time debug information no
However, could someone please clarify as to why i get the following error,
when i run make:
Making all in docmake[1]: Entering directory
`/home/sridhar/blob-2.0.5-pre2/doc'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/sridhar/blob-2.0.5-pre2/doc'
Making all in tools
make[1]: Entering directory `/home/sridhar/blob-2.0.5-pre2/tools'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/sridhar/blob-2.0.5-pre2/tools'
Making all in utils
make[1]: Entering directory `/home/sridhar/blob-2.0.5-pre2/utils'
Making all in buildmake[2]: Entering directory
`/home/sridhar/blob-2.0.5-pre2/utils/build'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/sridhar/blob-2.0.5-pre2/utils/build'
Making all in mkparamblock
make[2]: Entering directory
`/home/sridhar/blob-2.0.5-pre2/utils/mkparamblock'
gcc -Wall -O2 -I../../include -I../../include -o mkparamblock mkparamblock.c
make[2]: Leaving directory
`/home/sridhar/blob-2.0.5-pre2/utils/mkparamblock'
make[2]: Entering directory `/home/sridhar/blob-2.0.5-pre2/utils'
make[2]: Nothing to be done for `all-am'.
make[2]: Leaving directory `/home/sridhar/blob-2.0.5-pre2/utils'
make[1]: Leaving directory `/home/sridhar/blob-2.0.5-pre2/utils'
Making all in include
make[1]: Entering directory `/home/sridhar/blob-2.0.5-pre2/include'
Making all in blobmake[2]:
Entering directory `/home/sridhar/blob-2.0.5-pre2/include/blob'
make all-recursivemake[3]: Entering directory
`/home/sridhar/blob-2.0.5-pre2/include/blob'
Making all in archmake[4]: Entering directory
`/home/sridhar/blob-2.0.5-pre2/include/blob/arch'
make[4]: Nothing to be done for `all'.make[4]:
Leaving directory `/home/sridhar/blob-2.0.5-pre2/include/blob/arch'
make[4]: Entering directory `/home/sridhar/blob-2.0.5-pre2/include/blob'
make[4]: Leaving directory `/home/sridhar/blob-2.0.5-pre2/include/blob'
make[3]: Leaving directory `/home/sridhar/blob-2.0.5-pre2/include/blob'
make[2]: Leaving directory `/home/sridhar/blob-2.0.5-pre2/include/blob'
make[2]: Entering directory `/home/sridhar/blob-2.0.5-pre2/include'
make[2]: Nothing to be done for `all-am'.
make[2]: Leaving directory `/home/sridhar/blob-2.0.5-pre2/include'
make[1]: Leaving directory `/home/sridhar/blob-2.0.5-pre2/include'
Making all in src
make[1]: Entering directory `/home/sridhar/blob-2.0.5-pre2/src'
Making all in lib
make[2]: Entering directory `/home/sridhar/blob-2.0.5-pre2/src/lib'
arm-linux-gcc -DHAVE_CONFIG_H -I. -I. -I../../include/blob -I../../include
-I../../include -Os -I/usr/src/linux/include -Wall -march=armv4
-mtune=strongarm1100 -fomit-frame-pointer -fno-builtin -mapcs-32 -nostdinc
-c command.c
make[2]: Leaving directory `/home/sridhar/blob-2.0.5-pre2/src/lib'
make[1]: Leaving directory `/home/sridhar/blob-2.0.5-pre2/src'
In file included from command.c:42:
../../include/blob/command.h:57: parse error before
`#'
../../include/blob/command.h:57: stray '\' in program
../../include/blob/command.h:58: stray '\' in program
../../include/blob/command.h:59: stray '\' in program
../../include/blob/command.h:60: stray '\' in program
In file included from command.c:42:
../../include/blob/init.h:46: parse error before `#'
../../include/blob/init.h:46: stray '\' in program
../../include/blob/init.h:47: stray '\' in program
../../include/blob/init.h:48: stray '\' in program
../../include/blob/init.h:55: parse error before `#'
../../include/blob/init.h:55: stray '\' in program
../../include/blob/init.h:56: stray '\' in program
../../include/blob/init.h:57: stray '\' in program
command.c:78: stray '\' in program
command.c:261: stray '\' in program
command.c:59: warning: `init_commands' defined but not
used
command.c:226: warning: `help' defined but not used
command.c:257: warning: `helphelp' defined but not
used
make[2]: *** [command.o] Error 1
make[2]: Leaving directory
`/root/blob_dsp8/blob-2.0.5-pre2/src/lib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/root/blob_dsp8/blob-2.0.5-pre2/src'
make: *** [all-recursive] Error 1
Is there anything wrong with the configuration process?
To me that seems to be OK as i got the expected output msg but im not sure.
Pls help me.
Thank You
Sridhar
-----Original Message-----
From: Christopher Hoover [mailto:ch...@mu...]
Sent: Monday, October 06, 2003 9:56 PM
To: Yamijala Sridhar
Cc: blo...@li...
Subject: RE: blob-cvs-commit digest, Vol 1 #232 - 2 msgs
> Well, could you pls tell me as to why blob needs the Linux kernel headers?
blob doesn't use the kernel headers ($LINUX/include/linux) per se, but it
does leverage the architecture-specific headers ($LINUX/include/asm) to get
to the defines and structures that describe the processor and peripherals.
-ch
-----Original Message-----
From: Yamijala Sridhar [mailto:Sri...@si...]
Sent: Monday, October 06, 2003 3:09 AM
To: Christopher Hoover
Cc: blo...@li...
Subject: RE: blob-cvs-commit digest, Vol 1 #232 - 2 msgs
Well, could you pls tell me as to why blob needs the Linux kernel headers?
I want to know because here, I have a configured Linux kernel source tree
without
the *.c files of the configured kernel.I have the *.h files though and all
the makefiles etc. too
with me.
When I try to configure and compile the blob with this kernel source tree
(without the *.c files)
the configuration seems to be successful but at the gmake stage i get an
error output which says
"Nothing to do for 'all' " and stops.
Could someone pls let me know what the problem is and why blob needs the
kernel headers?
Thank You
Sridhar
-----Original Message-----
From: Christopher Hoover [mailto:ch...@mu...]
Sent: Wednesday, October 01, 2003 9:39 PM
To: Yamijala Sridhar; blo...@li...
Subject: RE: blob-cvs-commit digest, Vol 1 #232 - 2 msgs
>> Hallo All !!!
>> Could someone pls clarify as to why the linux kernel
>> source path is required for compiling 'blob'?
>> I suppose the bootloader is a stand-alone program and
>> should not have anything to do
>> with the kernel source tree on my development machine
>> when im cross-compiling.
Blob (unfortunately) uses the kernel headers. You are correct that this is
not the best idea, not only for the reasons you mention but also because the
kernel headers change from time to time.
-ch
|
|
From: Christopher H. <ch...@mu...> - 2003-10-09 17:06:09
|
Sorry for the long mail but could someone please be more specific and = tell me=20 what exactly BLOB looks for in a Configured Linux Kernel tree and why? =20 I've already explained why we use from the kernel tree.. If you want = to know the specific files, look through the source. =20 In "configure.in", I changed the --with-board=3DNAME to = --with-board=3Dlart.=20 Then in acconfig.h, I changed the #undef LART to #define LART and also defined CPU as SA1100=20 Then in "configure", I changed the --with-board=3DNAME to = --with-board=3Dlart and=20 --with-linux-prefix=3D/home/sridhar/linux-2.4.20 where i have a = configured Linux kernel tree=20 but with not all *.c files available. =20 Have you read the README file??=20 =20 Do not modifiy configure.in and acconfig.h. =20 =20 Follow the instructions precisely and get blob working, before you = attempt to "optimize" the process. =20 =20 I won't help you until further until you *follow the instructions*.=20 =20 -ch=20 =20 |
|
From: Yamijala S. <Sri...@si...> - 2003-10-10 13:55:33
|
Sorry Chris ! Thank you for your reminder.It did help me really ! The problem was that the blob-2.0.5-pre2.tar.gz that I had downloaded was not proper. There was some download problem because of which certain files that were missing upon extraction. I realised it only after your reminder. Now, with a correct download, I am able to generate the binary image. Thank You Sridhar -----Original Message----- From: Christopher Hoover [mailto:ch...@mu...] Sent: Thursday, October 09, 2003 10:35 PM To: Yamijala Sridhar Cc: blo...@li... Subject: RE: blob-cvs-commit digest, Vol 1 #232 - 2 msgs Sorry for the long mail but could someone please be more specific and tell me what exactly BLOB looks for in a Configured Linux Kernel tree and why? I've already explained why we use from the kernel tree.. If you want to know the specific files, look through the source. In "configure.in", I changed the --with-board=NAME to --with-board=lart. Then in acconfig.h, I changed the #undef LART to #define LART and also defined CPU as SA1100 Then in "configure", I changed the --with-board=NAME to --with-board=lart and --with-linux-prefix=/home/sridhar/linux-2.4.20 where i have a configured Linux kernel tree but with not all *.c files available. Have you read the README file?? Do not modifiy configure.in and acconfig.h. Follow the instructions precisely and get blob working, before you attempt to "optimize" the process. I won't help you until further until you *follow the instructions*. -ch |
|
From: Yamijala S. <Sri...@si...> - 2003-10-13 11:57:11
|
Hallo All ! Now, Im trying to compile blob for "system3" board, but i find that although i change the board name in ./configure, the compilation is still done for LART only and with such a blob image, im not able to boot linux.My board is SA-1110 based. I find that LART by default, uses sa1100 CPU and related files.Also, it doesnt use an LCD. With my new board, I have an LCD, CPU is sa1110 and uses SDRAM. So, I tried to compile for system3. When Im trying to compile blob for system3, by changing the board-name to system3, I find that the changes have no effect. I find blob using the same lart related files. why is this so? The changes made were: In ./configure file: ------------------------ --with-board=system3 --with-linux-prefix=home/sridhar/linux-2.4.20 In ./configure.in file: ---------------------------- -mtune=strongarm1110 In acconfig.h file: ------------------------ #define PT_SYSTEM3 #define SA1110 I know Chris told me not to tamper with ./configure.in and ./acconfig.h files and i tried but even that didnt help. So, after reading "porting.txt", I tried with the above modifications. Now, could someone please tell me what are the changes that i need to do to compile blob for system3. I did read the "porting.txt" file also the "README" file. I dont know where im going wrong. Thank You Sridhar -----Original Message----- From: Christopher Hoover [mailto:ch...@mu...] Sent: Thursday, October 09, 2003 10:35 PM To: Yamijala Sridhar Cc: blo...@li... Subject: RE: blob-cvs-commit digest, Vol 1 #232 - 2 msgs Sorry for the long mail but could someone please be more specific and tell me what exactly BLOB looks for in a Configured Linux Kernel tree and why? I've already explained why we use from the kernel tree.. If you want to know the specific files, look through the source. In "configure.in", I changed the --with-board=NAME to --with-board=lart. Then in acconfig.h, I changed the #undef LART to #define LART and also defined CPU as SA1100 Then in "configure", I changed the --with-board=NAME to --with-board=lart and --with-linux-prefix=/home/sridhar/linux-2.4.20 where i have a configured Linux kernel tree but with not all *.c files available. Have you read the README file?? Do not modifiy configure.in and acconfig.h. Follow the instructions precisely and get blob working, before you attempt to "optimize" the process. I won't help you until further until you *follow the instructions*. -ch |
|
From: Yamijala S. <Sri...@si...> - 2003-10-16 09:50:06
|
Hi All ! Ok...I got to the stage of compiling "blob" to any known board (Assabet,Creditlart,Lart,system3 etc.) but I have one problem. The compiled blob image doesnt boot Linux from FLASH when downloaded to target.I tried it with various images but it doesnt work.Could it be that the board isnt any of the standard ones? Moreover, when I tried to compile "blob" by setting -mtune=strongarm1110, there was a configuration error saying that the cross-compiler tool chain doesnt support that but it compiles fine when i retain the value of -mtune=strongarm1100.My board is SA1110-based, uses an LCD and SDRAM. So, could someone pls tell me what exactly is the problem? Im trying to get the schematics from the vendor to know whether the board is different from the standard board. Any help or suggestions meanwhile will be very much welcome. Thank You Sridhar |
|
From: Christopher H. <ch...@mu...> - 2003-10-01 16:10:02
|
>> Hallo All !!!=20 >> Could someone pls clarify as to why the linux kernel=20 >> source path is required for compiling 'blob'?=20 >> I suppose the bootloader is a stand-alone program and >> should not have anything to do=20 >> with the kernel source tree on my development machine >> when im cross-compiling.=20 Blob (unfortunately) uses the kernel headers. You are correct that this = is not the best idea, not only for the reasons you mention but also because = the kernel headers change from time to time. -ch |
Thanks for helping keep SourceForge clean.
X