| # 00:07:46 |
smartin |
quits |
| # 01:05:59 |
dagg123 |
quits : Ping timeout: 265 seconds |
| # 01:07:50 |
dagg123 |
joins #crosstool-ng |
| # 03:13:28 |
mnt_real |
joins #crosstool-ng |
| # 03:39:57 |
nandub |
quits : Quit: Get MacIrssi - http://www.sysctl.co.uk/projects/macirssi/ |
| # 09:07:02 |
smartin |
joins #crosstool-ng |
| # 11:43:18 |
demarchi1 |
quits : Quit: leaving |
| # 14:17:06 |
impulze |
hm how do i change the build compiler? |
| # 14:17:35 |
impulze |
adjusting PATH or writing a g++/gcc wrapper seems hacky |
| # 14:49:31 |
dagg123 |
impulze, what exactly are you trying to do? |
| # 14:50:33 |
impulze |
dagg123: trying to build my target-toolchain against 32bit libraries |
| # 14:50:46 |
impulze |
i.e. adding -m32 to LDFLAGS/CFLAGS or i'd rather use g++ -m32 and gcc -m32 als CC/CXX |
| # 14:51:15 |
impulze |
i'm almost sure that cflags aren't properly propagated :D |
| # 14:52:05 |
dagg123 |
you are trying to create a 32 cross compiler to compile something with in 32bit using a crosscompiler? |
| # 14:52:45 |
impulze |
i can't follow |
| # 14:53:15 |
dagg123 |
you are trying to build a 32bit cross compiler? |
| # 14:53:35 |
impulze |
no |
| # 14:53:44 |
impulze |
dagg123: trying to build my target-toolchain against 32bit libraries |
| # 14:54:06 |
alan_o |
joins #crosstool-ng |
| # 14:54:19 |
dagg123 |
how is this related to crosstool-ng? |
| # 14:55:06 |
impulze |
isn't crosstool able to select the building compiler? |
| # 14:56:14 |
dagg123 |
it uses your default compiler to create a cross compiler |
| # 14:56:31 |
dagg123 |
it uses your local gcc |
| # 14:57:12 |
impulze |
yes, i want to change that |
| # 14:57:21 |
dagg123 |
why? |
| # 14:58:03 |
impulze |
nvm, i will figure it out |
| # 14:58:51 |
dagg123 |
I'm pretty sure you don't understand crosstool-ng's design then |
| # 14:59:16 |
mnt_real |
quits : Ping timeout: 276 seconds |
| # 15:00:18 |
sh4rm4 |
the -m32 stuff doesnt seem to work very well, it is recommended to use a 32bit VM for such stuff |
| # 15:00:56 |
dagg123 |
sh4rm4, I assume you understood what he is trying to do because I didn't. |
| # 15:00:57 |
impulze |
sh4rm4: ah ok |
| # 15:01:08 |
impulze |
sh4rm4: though arch i386 is probably not sufficient? |
| # 15:01:16 |
impulze |
*setarch |
| # 15:01:38 |
sh4rm4 |
i dunno, i use a minimal debian netboot for such stuff |
| # 15:01:43 |
dagg123 |
afaik, setarch is a hack that shouldn't be used... |
| # 15:01:46 |
sh4rm4 |
never got -m32 to work correctly |
| # 15:02:46 |
sh4rm4 |
however to compile gcc successfully the VM should have 1.2 GB RAM available |
| # 15:03:54 |
sh4rm4 |
unless you use LDFLAGS="-Wl,--no-keep-memory" |
| # 15:07:01 |
impulze |
oki |
| # 15:10:53 |
sh4rm4 |
if you build a static 32bit toolchain with sysroot features, you can use that one later without problems on a 64bit host |
| # 15:11:49 |
impulze |
yep |
| # 15:11:52 |
sh4rm4 |
acts like a 64->32 crosscompiler |
| # 15:11:52 |
impulze |
that's what i want to do |
| # 15:12:06 |
impulze |
well not not really |
| # 15:12:14 |
sh4rm4 |
which libc do you intend to use ? |
| # 15:12:15 |
impulze |
i'm trying to build a static 32bit toolchain that compiles for arm |
| # 15:12:22 |
impulze |
so i can use that one on 64 and 32bit |
| # 15:12:29 |
impulze |
glibc |
| # 15:12:31 |
sh4rm4 |
oh ok |
| # 15:13:25 |
sh4rm4 |
well, you could bootstrap a static x86 compiler on a 32bit host OS, and then use the resulting toolchain to create your ARM toolchain from your 64bit host ;) |
| # 15:13:35 |
mnt_real |
joins #crosstool-ng |
| # 15:13:43 |
impulze |
sure |
| # 15:13:58 |
impulze |
but i rather find out how to do it sanely :D |
| # 15:14:04 |
impulze |
maybe a few tweaks and that'll be it |
| # 15:14:28 |
impulze |
if not, then i'll use a vm |
| # 17:19:17 |
impulze |
sh4rm4: so far so good, all that was needed was adjusting CT_BUILD in menuconfig |
| # 17:19:25 |
impulze |
and gmp required CC to be set to "cc -m32" |
| # 17:19:41 |
impulze |
will report back once i get an error or it succeeds :) |
| # 18:52:29 |
smartin |
quits |
| # 18:52:34 |
y_morin |
joins #crosstool-ng |
| # 19:26:22 |
impulze |
done |
| # 19:53:29 |
mnt_real |
quits : Read error: Operation timed out |
| # 19:53:36 |
mnt_real_ |
joins #crosstool-ng |
| # 20:16:40 |
mnt_real_ |
quits : Quit: Leaving |
| # 20:17:33 |
mnt_real |
joins #crosstool-ng |
| # 21:22:41 |
ben1066 |
joins #crosstool-ng |
| # 21:22:45 |
ben1066 |
hey? |
| # 21:23:35 |
alan_o |
quits : Quit: Leaving |
| # 21:23:49 |
y_morin |
ben1066: hello! If you have a question, just ask. Don't ask to ask, just ask! ;-) |
| # 21:24:13 |
ben1066 |
This isnt strictly related, but i saw it discussed in some logs from this channel |
| # 21:24:19 |
y_morin |
If anyone knows the answer, and/or has the bandwidth to answer, he/she'll do. |
| # 21:24:33 |
y_morin |
ben1066: go ahead! ;-) |
| # 21:24:36 |
ben1066 |
Im trying to build newlib with the codesourcery toolchain |
| # 21:24:47 |
ben1066 |
However it defaults to cortex-m3 armv6m |
| # 21:24:53 |
ben1066 |
I need cortex-a9 armv7-a |
| # 21:25:11 |
ben1066 |
I know what cflags need setting, however, how I pass the to the configure script....not so much |
| # 21:25:17 |
y_morin |
ben1066: no idea. You'd be better off asking the codesourcery guys. |
| # 21:25:28 |
ben1066 |
Its the same as standard gcc |
| # 21:25:41 |
ben1066 |
-mcpu=cortex-a9 -march=armv7-a |
| # 21:25:43 |
y_morin |
ben1066: for the cflags, it's usually: ./configure CFLAGS="--foo --bar... |
| # 21:25:55 |
y_morin |
Ditto for LDFLAGS |
| # 21:26:21 |
ben1066 |
ASFLAGS? |
| # 21:26:25 |
ben1066 |
do such things exist :P |
| # 21:26:34 |
y_morin |
ASFLAGS, yes. |
| # 21:26:55 |
y_morin |
ben1066: try: ./configure --help <- it wil tell you what flags it recognises. |
| # 21:27:07 |
ben1066 |
yea...it didnt..uh help |
| # 21:27:24 |
y_morin |
ASFLAGS are special, because usually the assembler is not called directly. |
| # 21:28:07 |
y_morin |
If your Makefile does call as directly, then probably ASFLAGS are recongised, otherwise, pass them as: CFLAGS="-Wa,--asflag" |
| # 21:29:33 |
ben1066 |
ah bugger, setting those cflags/cxxflags resulted in C compiler cannot create executables |
| # 21:38:35 |
ben1066 |
im comfused |
| # 21:38:42 |
ben1066 |
I added that to the CFLAGS CXXFLAGS |
| # 21:38:50 |
ben1066 |
Yet still its making an armv6m target |
| # 21:38:51 |
ben1066 |
>)> |
| # 21:39:01 |
ben1066 |
this is newlib doing this |
| # 21:39:03 |
ben1066 |
not the compiler |
| # 21:39:05 |
ben1066 |
:S |
| # 21:39:45 |
y_morin |
ben1066: I think the CodeSourcery guys or the newlib guys would be of better help for this issue... |
| # 21:42:29 |
ben1066 |
neither of them have an irc channel :P |
| # 21:48:23 |
y_morin |
Try their mailing list (newlib), or contact info (codesourcery) |
| # 21:56:16 |
alan_o |
joins #crosstool-ng |
| # 22:05:51 |
ben1066 |
i think my best bet is to compile my own toolchain |
| # 22:05:55 |
ben1066 |
specifically for cortex-a9 |
| # 22:16:13 |
smartin |
joins #crosstool-ng |