Author: stepan Date: Fri Mar 26 15:32:25 2010 New Revision: 120 URL: http://tracker.coreboot.org/trac/filo/changeset/120
Log: not much use in keeping old Kconfig examples lying around, let's rather improve documentation and help texts
Signed-off-by: Stefan Reinauer stepan@coresystems.de
Deleted: trunk/filo/configs/config.grub trunk/filo/configs/config.nogrub
On Fri, 26 Mar 2010 15:32:25 +0100, repository service svn@coreboot.org wrote:
Author: stepan Date: Fri Mar 26 15:32:25 2010 New Revision: 120 URL: http://tracker.coreboot.org/trac/filo/changeset/120
Log: not much use in keeping old Kconfig examples lying around, let's rather improve documentation and help texts
Speaking of docs, any way we could get building libpayload on x86_64 documented?
I could not get it to build on AMD x86_64.
On 3/26/10 5:07 PM, Joseph Smith wrote:
Speaking of docs, any way we could get building libpayload on x86_64 documented?
I could not get it to build on AMD x86_64.
Look at FILO's build.sh script.
On Fri, 26 Mar 2010 17:09:31 +0100, Stefan Reinauer stepan@coresystems.de wrote:
On 3/26/10 5:07 PM, Joseph Smith wrote:
Speaking of docs, any way we could get building libpayload on x86_64 documented?
I could not get it to build on AMD x86_64.
Look at FILO's build.sh script.
OK, so it will build with crossgcc. Good but bad. It looks for i386-elf-* in the util/crossgcc/xgcc/bin directory. I use crossgcc out of my coreboot repo, by adding my cross gcc bin to my $PATH. Any way we could add another line that looks for crossgcc in the builders $PATH?
Am 26.03.2010 17:20, schrieb Joseph Smith:
It looks for i386-elf-* in the util/crossgcc/xgcc/bin directory. I use crossgcc out of my coreboot repo, by adding my cross gcc bin to my $PATH. Any way we could add another line that looks for crossgcc in the builders $PATH?
Normally, I'd say "patches accepted". However, read the following line, taken from FILO's build.sh:
for gccprefixes in `pwd`/../coreboot/util/crossgcc/xgcc/bin/i386-elf- i386-elf- ""; do
see that "i386-elf-"? That looks for i386-elf-gcc in your $PATH.
Regards, Patrick
On Fri, 26 Mar 2010 17:27:29 +0100, Patrick Georgi patrick.georgi@coresystems.de wrote:
Am 26.03.2010 17:20, schrieb Joseph Smith:
It looks for i386-elf-* in the util/crossgcc/xgcc/bin directory. I use crossgcc out of my coreboot repo, by adding my cross gcc bin to my $PATH. Any way we could add another line that looks for crossgcc in the
builders
$PATH?
Normally, I'd say "patches accepted". However, read the following line, taken from FILO's build.sh:
for gccprefixes in `pwd`/../coreboot/util/crossgcc/xgcc/bin/i386-elf- i386-elf- ""; do
see that "i386-elf-"? That looks for i386-elf-gcc in your $PATH.
ok cool. So next question, build.sh builds libpayload and filo with default settings correct? If I want to change some settings in say libpayload can I do make menuconfig first and then run build.sh and it use my new config instead of the default one?
On Fri, 26 Mar 2010 17:09:31 +0100, Stefan Reinauer stepan@coresystems.de wrote:
On 3/26/10 5:07 PM, Joseph Smith wrote:
Speaking of docs, any way we could get building libpayload on x86_64 documented?
I could not get it to build on AMD x86_64.
Look at FILO's build.sh script.
Is it documented anywhere to use build.sh for crossgcc on AMD x86_64?
On 3/26/10 5:36 PM, Joseph Smith wrote:
On Fri, 26 Mar 2010 17:09:31 +0100, Stefan Reinauer stepan@coresystems.de wrote:
On 3/26/10 5:07 PM, Joseph Smith wrote:
Speaking of docs, any way we could get building libpayload on x86_64 documented?
I could not get it to build on AMD x86_64.
Look at FILO's build.sh script.
Is it documented anywhere to use build.sh for crossgcc on AMD x86_64?
Just try the wiki once... it contains great information that just needs to be cut and pasted into a shell... ;-)
On Fri, 26 Mar 2010 17:41:32 +0100, Stefan Reinauer stepan@coresystems.de wrote:
On 3/26/10 5:36 PM, Joseph Smith wrote:
On Fri, 26 Mar 2010 17:09:31 +0100, Stefan Reinauer
wrote:
On 3/26/10 5:07 PM, Joseph Smith wrote:
Speaking of docs, any way we could get building libpayload on x86_64 documented?
I could not get it to build on AMD x86_64.
Look at FILO's build.sh script.
Is it documented anywhere to use build.sh for crossgcc on AMD x86_64?
Just try the wiki once... it contains great information that just needs to be cut and pasted into a shell... ;-)
ok cool. Then can
$ make CC="gcc -m32" LD="ld -b elf32-i386" HOSTCC="gcc" AS="as --32"
be used on libpayload as well? I guess I was confused by the libpayload README.
"libpayload is for 32bit x86 systems only"
On 3/26/10 6:06 PM, Joseph Smith wrote:
Just try the wiki once... it contains great information that just needs to be cut and pasted into a shell... ;-)
ok cool. Then can
$ make CC="gcc -m32" LD="ld -b elf32-i386" HOSTCC="gcc" AS="as --32"
be used on libpayload as well?
I don't use Linux for software development, so I can't tell you. Why don't you try it out and contribute your findings to the Wiki?
Stefan
-
Joseph Smith -
Patrick Georgi -
repository service -
Stefan Reinauer