# 02:45:23 |
plfiorini |
joins #crosstool-ng |
# 05:06:17 |
nandub |
joins #crosstool-ng |
# 06:00:48 |
nandub |
quits : Ping timeout: 264 seconds |
# 08:47:03 |
plfiorini |
quits : Quit: Communi 2.0.0 |
# 09:02:45 |
linuxjacques |
quits : Ping timeout: 248 seconds |
# 09:03:43 |
linuxjacques |
joins #crosstool-ng |
# 09:04:07 |
linuxjacques |
is now known as: Guest83033 |
# 09:30:29 |
Guest83033 |
quits : Ping timeout: 255 seconds |
# 09:36:55 |
Guest83033 |
joins #crosstool-ng |
# 09:38:52 |
smartin |
joins #crosstool-ng |
# 10:07:35 |
y_morin |
joins #crosstool-ng |
# 11:18:35 |
Net147 |
joins #crosstool-ng |
# 11:19:19 |
nandub |
joins #crosstool-ng |
# 12:24:37 |
nandub_ |
joins #crosstool-ng |
# 12:25:51 |
nandub_ |
quits : Client Quit |
# 13:07:03 |
Net147 |
quits : Quit: HydraIRC -> http://www.hydrairc.com <- In tests, 0x09 out of 0x0A l33t h4x0rz prefer it :) |
# 13:49:24 |
nandub |
quits : Ping timeout: 264 seconds |
# 14:57:53 |
ccole |
quits : Quit: leaving |
# 15:34:23 |
diorcety |
quits : Quit: Leaving. |
# 15:42:32 |
ccole |
joins #crosstool-ng |
# 16:05:52 |
y_morin |
quits : Quit: Me does not like thunderstorms... They make his computer reboot... |
# 16:11:45 |
y_morin |
joins #crosstool-ng |
# 16:32:03 |
Diaoul |
joins #crosstool-ng |
# 16:32:06 |
Diaoul |
hi |
# 16:32:28 |
Diaoul |
Is it possible to use an ooooold glibc? 2.3.6 |
# 16:32:45 |
Diaoul |
the oldest I see is 2.8 |
# 16:35:25 |
y_morin |
quits : Read error: Connection reset by peer |
# 16:36:27 |
y_morin |
joins #crosstool-ng |
# 16:48:44 |
y_morin |
Diaoul: no need to start a private query to ask questions about crosstool-NG. Just ask here on the channel. |
# 16:49:04 |
Diaoul |
I did |
# 16:49:07 |
Diaoul |
hi |
# 16:49:07 |
Diaoul |
Is it possible to use an ooooold glibc? 2.3.6 |
# 16:49:07 |
Diaoul |
the oldest I see is 2.8 |
# 16:49:07 |
Diaoul |
* y_morin est parti (Read error: Connection reset by peer) |
# 16:49:07 |
Diaoul |
* y_morin (~y_morin@ARennes-555-1-262-17.w2-12.abo.wanadoo.fr) a rejoint #crosstool-ng |
# 16:49:20 |
y_morin |
I need to reattach to another network, I'll be back soon... |
# 16:49:43 |
Diaoul |
but you had a connection reset |
# 16:51:12 |
y_morin_ |
joins #crosstool-ng |
# 16:52:11 |
y_morin_ |
Diaoul: what version of crosstool-NG do you use? |
# 16:52:30 |
Diaoul |
the one on the scm |
# 16:52:39 |
Diaoul |
hg or git |
# 16:53:47 |
y_morin_ |
Diaoul: git? crosstool-NG's official SCM is Hg: http://crosstool-ng.org/hg/crosstool-ng |
# 16:53:55 |
y_morin_ |
Diaoul: Is taht the one you are using? |
# 16:54:12 |
y_morin |
quits : Ping timeout: 264 seconds |
# 16:54:20 |
y_morin_ |
is now known as: y_morin |
# 16:54:47 |
y_morin |
Diaoul: It is currently not possible to use a glibc version that is not in the menuconfig. |
# 16:55:30 |
y_morin |
Diaoul: there isa patchset to allow using a local dir as source for glibc/eglibc, but there are a few issues with it for now, so I have not committed it yet. |
# 16:55:38 |
Diaoul |
yes hg, that's the one. |
# 16:56:03 |
y_morin |
Diaoul: Also, glibc 2.3.6 is really old, now, and crosstool-NG strives at using recent versions only. |
# 16:56:20 |
y_morin |
Diaoul: Why do you need glibc 2.3.6 ? |
# 16:56:36 |
Diaoul |
yeah I know, but I don't really have a choice here, I'd like to make a cross toolchain for my Synology NAS |
# 16:56:58 |
Diaoul |
I've just asked them if they were stuck in the past with that version of glibc... |
# 16:57:13 |
Diaoul |
Still waiting for a reply (email) |
# 16:57:17 |
y_morin |
Diaoul: you want to use the existing system, or replace it with a newer one? |
# 16:58:05 |
y_morin |
Diaoul: building a new toolchain for an existing system is risky: there is no guarantee about the ABI. |
# 16:58:35 |
Diaoul |
I'd like to use the existing but create my own toolchain to cross compile software on it. Synology provides toolchains but I have some issues with them so I wanted to try my own toolchain |
# 16:58:40 |
y_morin |
Diaoul: you would need to have the exact same glibc sources, plus use the same compiler, plus use the same binutils. |
# 16:59:06 |
y_morin |
Diaoul: then I would suggest you use the toolchain they provide and try to fix their issues. |
# 16:59:32 |
y_morin |
Diaoul: Targetting an existing system with crosstool-NG is not supported. |
# 16:59:52 |
y_morin |
(But may work. Or not.) |
# 17:00:05 |
Diaoul |
so basically creating toolchains for existing system is nearly impossible |
# 17:01:04 |
y_morin |
Diaoul: yes. |
# 17:01:39 |
Diaoul |
Upgrading system's glibc is impossible without recompiling everything right? |
# 17:01:49 |
Diaoul |
or is it backward compatible, |
# 17:02:10 |
diorcety |
joins #crosstool-ng |
# 17:05:05 |
Diaoul |
is there a way to make my binaries use my glibc? through rpath or LD_LIBRARY_PATH? that way I put my stuff somewhere in the system and it stays isolated from the rest |
# 17:05:25 |
y_morin |
Diaoul: you can create a chroot-jail for that. |
# 17:20:27 |
Diaoul |
libm, libdl and libc are provided by glibc? |
# 17:21:44 |
y_morin |
Diaoul: yes |
# 17:24:04 |
Diaoul |
So if I copy the libc.so.6 from my toolchain to my target that should work? |
# 17:38:15 |
Diaoul |
can I find those libs in the generated toolchain? |
# 17:54:40 |
Diaoul |
or should I use another tool like buildroot to get my libs? |
# 17:54:44 |
Diaoul |
y_morin |
# 18:05:31 |
tkil |
Diaoul -- y_morin might be asleep by now, he's at utc+1 IIRC. |
# 18:05:45 |
tkil |
as for what you're trying to do ... i think that you'll ultimately be better off with a buildroot / oe type tool. |
# 18:05:59 |
tkil |
the only reason to stick with stock vendor bits is if they have proprietary binary stuff. |
# 18:06:16 |
tkil |
which, on a NAS, might be a wifi driver. |
# 18:08:09 |
tkil |
https://github.com/SynoCommunity/spksrc might be helpful. |
# 18:08:37 |
tkil |
ha. wait. that's you. :) |
# 18:09:32 |
tkil |
but if i'm reading that correctly, that should be generating the entire image, so you shouldn't be constrained by the libc on the stock firmware. |
# 18:14:55 |
Diaoul |
well I'm UTC+1 too and it's pretty early here ;) |
# 18:16:15 |
Diaoul |
spksrc is relying on toolchains provided by Synology |
# 18:17:13 |
Diaoul |
what I'd like to achieve is build my own toolchain with my own glibc and only rely on the kernel in the NAS |
# 18:18:27 |
Diaoul |
like a chroot jail but with the minimum stuff: no shell, no user management, nothing but libs to execute a binary |
# 18:19:46 |
tkil |
yeah, just realized that utc+1 is more like dinner/supper time, than bedtime... |
# 18:20:36 |
tkil |
not sure what to suggest, really. from reading about it, yocto should be able to do what you want, but i haven't used it properly yet. |
# 18:20:54 |
tkil |
i use ctng plus my own distro build scripts, but that's proper cross (not same arch as native), and the latter is an issue. |
# 18:21:12 |
Diaoul |
my question is: does a cross toolchain generated by crosstool-ng contains the glib stuff to put on my target? |
# 18:21:34 |
Diaoul |
it seems it's only host stuff, not target's |
# 18:21:36 |
tkil |
... yes. look to see what the populate script does. |
# 18:22:54 |
tkil |
but if your target is same as native, it gets more difficult, as yann indicated above. |
# 18:24:54 |
tkil |
but in my case, i'm building for ppc32 on x86-64, and i have the appropriate libs for the target: $ file /opt/cross/platforms/csbx-6315/xtools/powerpc-e300c3-linux-gnu/lib/libc-2.13.so => ... ELF 32-bit MSB shared object, PowerPC or cisco 4500 ... |
# 18:25:12 |
tkil |
and i need to go afk for a bit. good luck! |
# 18:32:30 |
Diaoul |
well, when using those files i got "ELF file OS ABI invalid" |
# 19:12:30 |
y_morin |
Diaoul: if you do not want to replace the existing system, then a chroot-jail is the easiest. |
# 19:12:46 |
y_morin |
Diaoul: (and, no it's not yet time for bed, but I also have a life IRL) |
# 19:13:49 |
y_morin |
Diaoul: What I would do, is build a toolchain for the target, and use that to build my new programs, install that on the target in a separate directory (eg. not in /) and chroot to there. |
# 19:14:40 |
y_morin |
Diaoul: See in: docs/5 - Using the toolchain.tt |
# 19:14:51 |
y_morin |
Diaoul: there are some suggestions on how to do that. |
# 19:15:02 |
y_morin |
Diaoul: Hint: read about the 'populate' script. |
# 19:15:31 |
y_morin |
has to reconnect on another network and will be back shortly... |
# 19:15:35 |
y_morin |
quits : Quit: leaving |
# 19:16:41 |
y_morin |
joins #crosstool-ng |
# 19:28:14 |
Diaoul |
thanks i'll do that y_morin |
# 19:47:16 |
y_morin |
quits : Quit: Back in a moment... |
# 19:49:37 |
y_morin |
joins #crosstool-ng |
# 19:52:05 |
jevin |
quits : Ping timeout: 240 seconds |
# 19:56:22 |
jevin |
joins #crosstool-ng |
# 20:01:42 |
Diaoul |
y_morin, I've done what you said with the populate script except I didn't chroot there but use LD_LIBRARY_PATH. I have this now: librt.so.1: ELF file OS ABI invalid and I have no idea what that means |
# 20:17:25 |
sh4rm4 |
quits : Remote host closed the connection |
# 20:31:41 |
y_morin |
quits : Quit: Maybe back later... |
# 20:41:19 |
y_morin |
joins #crosstool-ng |
# 20:44:08 |
Diaoul |
y_morin, running the new libc.so.6 shows that: unexpected PLT reloc type 0x25 |
# 20:44:14 |
y_morin |
Diaoul: Before tryin the ugly trick with LD_LIBRARY_PATH, did you even *try* to chroot ? |
# 20:47:27 |
Diaoul |
yes but i'm missing some stuff to have a proper chrootable environment: "No such file or directory" |
# 20:48:50 |
y_morin |
Diaoul: Then, just find what is missing. |
# 20:49:40 |
y_morin |
Diaoul: and add it to your chroot. |
# 21:20:12 |
plfiorini |
joins #crosstool-ng |
# 21:35:00 |
sh4rm4 |
joins #crosstool-ng |
# 22:53:12 |
diorcety1 |
joins #crosstool-ng |
# 22:54:28 |
diorcety |
quits : Ping timeout: 248 seconds |
# 23:00:49 |
mnt_real |
quits : Ping timeout: 248 seconds |
# 23:01:31 |
mnt_real |
joins #crosstool-ng |
# 23:15:45 |
plfiorini |
quits : Ping timeout: 248 seconds |
# 23:36:53 |
smartin |
quits : Quit: good night |