General TC > Programming & Scripting - Unofficial

building realtime kernel & remastering for tiny core linux

<< < (6/10) > >>

Rich:
Hi webb

--- Quote ---this appears to do nothing:
--- End quote ---
Not even any error messages?

Arslan S.:
when compiling kernel modules it is sufficient to set ARCH=x86_64 and CROSS_
COMPILE=x86_64-unknown-linux-

but for others you should also set LDFLAGS see toolchain64's info for details

webb:
as arslan points out, this does work for cross-compiling the kernel :)

--- Code: (bash) ---ARCH=x86_64 and CROSS_
COMPILE=x86_64-unknown-linux-
--- End code ---
it only didn't work for a test cross-compile of a small non-kernel source file.
my apologies for crying wolf.

ps:
actually, i used:

--- Code: (bash) ---COMPILE=x86_64-unknown-linux-gnu-
--- End code ---
and compiling is going ok so far. is there any reason not to use the gnu-?

pps:
these forms seem to work for non-kernel cross-compilation:
./configure --host=x86_64-unknown-linux-gnu (instead of ./configure)
/usr/local/x64/bin/x86_64-unknown-linux-gnu-gcc [x.c] (instead of gcc [x.c])

many thanks,
webb

Juanito:
..or you could compile natively using corepure64  8)

webb:
> ..or you could compile natively using corepure64

that does sound nice, but so far neither 3.0.21-tinycore64 nor 3.0.32-tinyrt64 will boot on my thinkpad t510. i'll check out 3.0.3-tinycore64 again (which boots) and see how that compares to 3.0.32-tinyrt32-pae performance-wise. hmm. i'm wondering now why i didn't just use 3.0.3-tinycore64 in the first place...

-webb

Navigation

[0] Message Index

[#] Next page

[*] Previous page