Forum Discussion
Altera_Forum
Honored Contributor
20 years ago --- Quote Start --- originally posted by jdhar@Feb 13 2006, 09:22 PM my server suffered a little internal fire recently (note, fans are more valuable than you think!), so i had to setup a new box, and i decided to switch linux distributions from slackware to ubuntu.
i rebuilt the toolchain the way i always have (i'm using the older version from marcs page, not the newer ones), and built a new kernel image... but it won't work on my board; it won't even start to boot (nothing happens after i run the terminal). to see if it was hardware, i used the same sof image and downloaded an older vmlinux binary that i had, and it worked, indicating it wasn't hardware. i then recompiled that same vmlinux binary with the same config file used to generate it originally, and the new image didn't work. this really seems like a toolchain build problem, and i thought maybe because i'm using different versions of everything to compile. for reference, im' using gcc 3.3.6 (but i configure buildroot to use 3.4.3).
any ideas?
<div align='right'><{post_snapback}> (index.php?act=findpost&pid=12698)
--- quote end ---
--- Quote End --- No one has any suggestions? I was thinking that maybe it was because I switched to an AMD64-bit architecture. If I extract old toolchain binaries that I have lying around, I can't execute them (when I try, I just get 'no such file or directory'), which is very odd; is there something specific ni the toolchain build that targets only 32-bit architectures, or should this not matter?