| # 00:17:44 |
systmkor |
quits : Ping timeout: 245 seconds |
| # 00:35:53 |
bhundven |
mingwandroid: ok, I forgot to do ^..HEAD |
| # 00:36:03 |
bhundven |
mingwandroid: I only did: ..HEAD |
| # 00:36:11 |
bhundven |
now you should have 7 patches |
| # 00:36:38 |
bhundven |
instead of 6 |
| # 00:37:04 |
bhundven |
the first patch moves scripts/build/cc/gcc.sh to scripts/build/cc/100-gcc.sh |
| # 00:39:22 |
bhundven |
then we update 100-gcc.sh in patch 5 |
| # 00:39:48 |
bhundven |
that way there is a clean difference between moving the file and updating it |
| # 04:14:38 |
djerome |
quits : Remote host closed the connection |
| # 06:13:51 |
mingwandroid |
quits : Read error: Connection reset by peer |
| # 07:42:29 |
diorcety |
joins #crosstool-ng |
| # 11:30:31 |
strobelight |
joins #crosstool-ng |
| # 11:35:57 |
strobelight |
quits : Quit: strobelight |
| # 11:36:18 |
strobelight |
joins #crosstool-ng |
| # 11:48:29 |
pev |
joins #crosstool-ng |
| # 11:48:41 |
pev |
Morning |
| # 11:49:27 |
pev |
Quick question I can't seem to find a simple answer to - I'm on a 64 bit ubuntu build host. What's the correct way to build a toolchain targetted at a 32 bit build host? |
| # 16:21:41 |
mnt_real |
joins #crosstool-ng |
| # 16:21:41 |
mnt_real |
quits : Changing host |
| # 16:21:41 |
mnt_real |
joins #crosstool-ng |
| # 16:29:55 |
blueness |
quits : Ping timeout: 244 seconds |
| # 16:34:11 |
y_morin |
joins #crosstool-ng |
| # 16:42:29 |
blueness |
joins #crosstool-ng |
| # 17:09:31 |
mnt_real |
parts #crosstool-ng |
| # 17:16:13 |
diorcety |
quits : Quit: Leaving. |
| # 17:31:02 |
strobelight |
quits : Ping timeout: 272 seconds |
| # 17:33:45 |
strobelight |
joins #crosstool-ng |
| # 18:08:42 |
strobelight_ |
joins #crosstool-ng |
| # 18:08:43 |
strobelight |
is now known as: Guest60026 |
| # 18:08:48 |
strobelight_ |
is now known as: strobelight |
| # 18:10:21 |
Guest60026 |
quits : Ping timeout: 250 seconds |
| # 18:12:58 |
diorcety |
joins #crosstool-ng |
| # 18:25:23 |
nandub |
quits : *.net *.split |
| # 18:27:26 |
nandub |
joins #crosstool-ng |
| # 18:39:42 |
bhundven |
pev: first make sure you get ct-ng from git (as, the latest code is about to release as 1.21.0 and has a ton of bug fixes over 1.20.0) |
| # 18:40:35 |
bhundven |
pev: second, bootstrap, configure, and install ct-ng to a local prefix. I recommend doing this: |
| # 18:41:00 |
bhundven |
pev: cd crosstool-ng; ./bootstrap; ./configure --prefix=${HOME}/.local; make; make install |
| # 18:41:17 |
bhundven |
pev: then make sure ${HOME}/.local/bin is in your PATH |
| # 18:41:47 |
bhundven |
pev: make a build directory: mkdir ${HOME}/i686-tc |
| # 18:42:07 |
bhundven |
pev: cd ${HOME}/i686-tc; ct-ng i686-nptl-linux-gnu; ct-ng menuconfig |
| # 18:42:28 |
bhundven |
pev: at the menuconfig, set options as you want them save when you exit |
| # 18:42:37 |
bhundven |
pev: ct-ng build |
| # 18:43:41 |
bhundven |
pev: the output should show up in ${HOME}/x-tools/i686-nptl-linux-gnu |
| # 18:46:06 |
bhundven |
pev: you might need multilib gcc and libraries installed to build x86_64/x86_64/i686 |
| # 18:46:20 |
bhundven |
pev: that last tuple means build/host/target |
| # 18:46:42 |
bhundven |
pev: meaning, the toolchain builds on x86_64, runs on x86_64, and creates target binaries for i686 |
| # 18:47:15 |
bhundven |
pev: if you are asking for something else, do provide more details, as well as what distribution you're building on. |
| # 18:47:25 |
bhundven |
pev: and I'll be glad to help |
| # 19:06:02 |
smartin |
quits : Ping timeout: 272 seconds |
| # 19:14:18 |
smartin |
joins #crosstool-ng |
| # 20:26:41 |
smartin |
quits : Ping timeout: 264 seconds |
| # 20:29:34 |
smartin |
joins #crosstool-ng |
| # 20:56:38 |
diorcety |
quits : Read error: Connection reset by peer |
| # 21:24:16 |
strobelight |
quits : Quit: strobelight |
| # 22:11:18 |
y_morin |
quits : Quit: leaving |