# 00:38:26 |
plfiorini |
quits : Quit: Leaving |
# 02:09:06 |
b_rare |
quits : Remote host closed the connection |
# 04:38:04 |
alan_o |
quits : Quit: Leaving |
# 05:34:41 |
sfan5|OFF |
is now known as: sfan5 |
# 06:46:45 |
diorcety |
quits : Quit: Leaving. |
# 06:55:02 |
smartin |
quits : Read error: Connection reset by peer |
# 06:55:13 |
smartin_ |
joins #crosstool-ng |
# 06:55:43 |
smartin_ |
is now known as: smartin |
# 07:15:07 |
aalv |
joins #crosstool-ng |
# 07:38:00 |
hrubi |
quits : Ping timeout: 264 seconds |
# 07:40:49 |
hrubi |
joins #crosstool-ng |
# 08:57:54 |
smartin_ |
joins #crosstool-ng |
# 08:58:44 |
smartin |
quits : Ping timeout: 252 seconds |
# 09:04:12 |
Net147 |
joins #crosstool-ng |
# 09:06:27 |
diorcety1 |
joins #crosstool-ng |
# 09:45:24 |
V0idExp |
joins #crosstool-ng |
# 09:45:37 |
V0idExp |
Hello everybody! |
# 09:45:41 |
diorcety1 |
hi |
# 09:45:45 |
V0idExp |
I need your help for a simple task :( |
# 09:45:55 |
V0idExp |
so simple, that it may seem stupid asking stuff like that |
# 09:46:17 |
V0idExp |
well, using latest stable ct-ng I've built a GCC-Glibc toolchain successfully. |
# 09:47:34 |
V0idExp |
I'm running a x86-64 distro, and built a toolchain which also targets x86-64. Just to distinguish between my system compiler and toolchain's one, i've set the vendor string to 'acme', so I ended up having a lot of executables like x86_64-acme-linux-gnu-g++ and so on... |
# 09:48:58 |
V0idExp |
I have a basic Linux micro-distro, which consists only of a module-less kernel and a busybox toolset, which is running inside a virtual machine. Just boots and opens a shell.. So there's nothing a part /bin, /dev/, /etc directories. MINIMAL ;) |
# 09:49:42 |
V0idExp |
What I want is to cross compile a simple dynamically-linked 'hello' program, which is a simple C++ hello world, using the generated toolchain ('acme' ;)) |
# 09:50:39 |
V0idExp |
so, the command is simple: |
# 09:50:39 |
V0idExp |
x86_64-acme-linux-gnu-g++ hello.cpp -o hello |
# 09:52:42 |
V0idExp |
there are two problems: |
# 09:52:42 |
V0idExp |
1) `ldd hello` says that it's linked to my system libc and libstdc++ libraries |
# 09:52:42 |
V0idExp |
2) if I use the LD_LIBRARY_PATH env var to point to my toolchain's library directory, libstdc++ links to my toolchain's lib, but libc still links to system... |
# 09:52:42 |
V0idExp |
So, the hello program doesn't execute on my microdistro, even if I copy all the sysroot/usr/lib directory to distro's /lib |
# 09:54:26 |
V0idExp |
What I'm doing wrong? :( |
# 10:09:14 |
smartin_ |
is now known as: smartin |
# 10:32:47 |
Net147 |
quits : Ping timeout: 252 seconds |
# 11:19:53 |
Net147 |
joins #crosstool-ng |
# 13:31:13 |
aalv |
quits : Read error: Connection reset by peer |
# 13:31:25 |
aalv |
joins #crosstool-ng |
# 13:37:18 |
alan_o |
joins #crosstool-ng |
# 13:55:49 |
Net147 |
quits : Quit: HydraIRC -> http://www.hydrairc.com <- In tests, 0x09 out of 0x0A l33t h4x0rz prefer it :) |
# 15:09:02 |
V0idExp |
parts #crosstool-ng |
# 15:51:04 |
sfan5 |
is now known as: sfan5|OFF |
# 15:52:37 |
sfan5|OFF |
is now known as: sfan5 |
# 15:52:39 |
y_morin |
joins #crosstool-ng |
# 16:04:22 |
diorcety1 |
quits : Quit: Leaving. |
# 17:38:44 |
plfiorini |
joins #crosstool-ng |
# 18:16:11 |
smartin_ |
joins #crosstool-ng |
# 19:29:06 |
alan_o |
quits : Quit: Leaving |
# 20:10:23 |
sfan5 |
is now known as: sfan5|OFF |
# 21:09:25 |
smartin |
quits : Ping timeout: 246 seconds |
# 21:13:33 |
smartin |
joins #crosstool-ng |
# 21:29:24 |
plfiorini |
quits : Quit: Leaving |
# 21:30:00 |
linuxjacques |
quits : Ping timeout: 256 seconds |
# 21:48:40 |
plfiorini |
joins #crosstool-ng |
# 22:09:00 |
smartin__ |
joins #crosstool-ng |
# 22:09:41 |
smartin |
quits : Ping timeout: 248 seconds |
# 22:12:09 |
bhundven |
joins #crosstool-ng |
# 22:12:24 |
bhundven |
muhahaha: http://git.pengutronix.de/?p=ukl/linux.git;a=summary |
# 22:12:51 |
bhundven |
specifically: http://git.pengutronix.de/?p=ukl/linux.git;a=shortlog;h=refs/heads/efm32 |
# 22:14:09 |
y_morin |
bhundven: Hello! efm32 == ? |
# 22:14:14 |
bhundven |
linux on a cortex-m3 mcu |
# 22:14:21 |
bhundven |
by energy micro |
# 22:14:23 |
bhundven |
lol |
# 22:14:50 |
bhundven |
http://en.wikipedia.org/wiki/EFM32 |
# 22:15:36 |
bhundven |
granted, I'd have to hack userspace a bit, to make it smaller. |
# 22:15:48 |
y_morin |
bhundven: cortex-m3 are thunb2 only, iirc? And last I heard, it is absolutely possible to build the kernel in thumb2 only. |
# 22:16:12 |
bhundven |
I've been doing my builds with thumb (1) |
# 22:17:08 |
bhundven |
it should support both |
# 22:17:19 |
y_morin |
bhundven: The kernel can't run in thumb-1 only. Thumb-1 misses a few insns (interrupt-related). |
# 22:17:25 |
bhundven |
ah |
# 22:17:29 |
bhundven |
ok |
# 22:17:50 |
y_morin |
bhundven: I really mean: the Linux _kernel_, not the userland, which can indeed run in thunb1 only. |
# 22:18:00 |
bhundven |
right |
# 22:18:17 |
bhundven |
does ctng support thumb2 yet? |
# 22:18:40 |
y_morin |
bhundven: However, thunb2 is thunb1 plus a few 32-bit insns that makes it possible to run the kernel in Thumb2 mode (ie. 16-bit, no 32-bit arm-mode) |
# 22:18:52 |
y_morin |
bhundven: Well, yes. |
# 22:19:19 |
y_morin |
bhundven: If by support you men "there's an option for that in the menu", then yes. |
# 22:19:29 |
bhundven |
hah |
# 22:19:44 |
y_morin |
bhundven: Then, whether thumb2 or thumb1 is used depends on the processor you configure gcc for. |
# 22:20:01 |
bhundven |
-march=cortex-m3 |
# 22:20:44 |
y_morin |
bhundven: yes, something like that. Or even "-march=cortex-a9 -mthumb" will generate thumb2 |
# 22:21:11 |
y_morin |
Well: s/will/should/ |
# 22:21:14 |
y_morin |
:-) |
# 22:21:17 |
bhundven |
right |
# 22:28:26 |
bhundven |
anyways, seems like a fun project |
# 22:29:20 |
y_morin |
bhundven: Yep. |
# 22:29:37 |
bhundven |
trying with uclibc |
# 22:29:48 |
y_morin |
Anyway, 00:30 here, sleepiness is kicking in... |
# 22:29:55 |
bhundven |
g'night yann |
# 22:30:08 |
y_morin |
Bye, see ya! |
# 22:30:18 |
y_morin |
quits : Quit: Nighty Night! |
# 22:37:04 |
smartin_ |
quits : Quit: leaving |
# 22:55:01 |
diorcety |
joins #crosstool-ng |
# 23:35:01 |
aalv |
quits : Ping timeout: 245 seconds |
# 23:39:44 |
aalv |
joins #crosstool-ng |