| # 04:27:01 | cpackham | 1. which architecture? |
| # 04:27:19 | cpackham | 2. the toolchain should work as long as it's on your path |
| # 04:28:23 | cpackham | i.e. export PATH="/home/me/x-tools/arm-unknown-linux-gnueabi/bin:$PATH" |
| # 10:32:50 | egeyar | joins #crosstool-ng |
| # 11:49:23 | egeyar | quits : Remote host closed the connection |
| # 11:52:00 | egeyar | joins #crosstool-ng |
| # 12:26:44 | ali1234 | cpackham: arm-linux-gnueabi, but this is completely irrelevant to multiarch support, which merely implies adjusting the default search paths of gcc and ld |
| # 12:27:26 | ali1234 | and 2. what if i install it in a different directory? based on past experience, gcc will fail if i do this. i know it is possible though, because it works with toolchains made by other tools such as abe |
| # 12:30:01 | ali1234 | it will say something like "/opt/x-tools/bin/../lib/gcc/arm-linux-gnueabihf/8.3.0/../../../../arm-linux-gnueabihf/bin/ld: cannot find /home/me/x-tools/arm-linux-gnueabihf/lib/libc.so.6" |
| # 21:40:40 | egeyar | quits : Remote host closed the connection |
| # 21:44:57 | egeyar | joins #crosstool-ng |
| # 22:53:28 | egeyar | quits : Quit: Leaving |