An installable gcc

[ffissore]

Consider using this blog post from dctsystems to prepare an installable toolchain, therefore providing the yun with gcc

[noblepepper]

Do you know if someone is actively pursuing this? I am about to follow dctsystems instructions and am thinking about learning enough about the OpenWRT buildroot to make a package but don't want to duplicate effort if someone else is working on it.

[ffissore]

Not yet. You're more than welcome :)

[noblepepper]

If anyone else is working on this please contact me so we can combine effort.

I'm compiling GCC 4.6.2 now, I wanted to stick with the exact version in the build root but I'm having to deal with at least one bug fixed in 4.6.4, apparently make doesn't like texinfo 5.x which I have on my Ubuntu box easy enough since we don't want docs anyway I just need to get ./configure to believe I don't want info pages. Once I get a clean compile I'll work on packaging.

[noblepepper]

I'm fine tuning the compilation, are there any special requests? Compiler name, like yun-gcc? Install location, is /usr/bin where we want it? etc, etc.

[dctsystems]

Thanks for picking this up... I really didn't want to have to learn the buildroot system. If you can make this into a package that would be great. How are the instructions working out?

/usr/bin seems to be the standard place that it lives (I'm also checking against the Tre build to see what they've don).

Standard practise would be that it would install in /usr/bin as mips-openwrt-linux-uclibc-gcc (and similarly appropriate names), with symbolic links from gcc (etc) to the arch specific name.

[ffissore]

@noblepepper default names are fine. As @dctsystems said, once configured and built for a particular target, temporary target folder (where all the files are installed before being packed into a .ipk file) should have all files and symbolic links in place (eg: gcc symlinked to mips-openwrt-linux-uclibc-gcc etc)

[noblepepper]

I just got my first completely clean compilation, now onto the world of feeds and packages...

Where is the stuff for the Tre? Mine arrived yesterday, between this and lawn duties I haven't had much time to play with it. All it has said to me at this point is blink, blink, blink....

[ffissore]

We are opening the beta testers dedicated basecamp for that kind of questions :)

[noblepepper]

Yes, I know.
/3 year old ON
I WANT IT NOW!!!!
/3 year old OFF

[dctsystems]

Tre has it all in /usr/bin.

(or it did until it appears to have bricked itself - slightly worried...)

[dctsystems]

Tre has it all in /usr/bin.

(or it did until it appears to have bricked itself - slightly worried...)

[noblepepper]

It is beta after all...

I haven't tested all my options to get in, the USB mini just gives me blink, blink, if I try to program it as the Leonardo that showed up in 1.5.6 IDE it acts weird, almost bricked, power cycles USB disconnect /connect eventually got it back.

I haven't played with the Ethernet port, is that how you got in? 192.168.1.1?

[dctsystems]

I hooked up keyboard/monitor, and did first boot that way. Once configured I was going in via ethernet.

[noblepepper]

This task almost beat me, I have learned more about openwrt packaging than I ever wanted to (probably I learned mostly the wrong way to do things).

I now have a staging_dir/target-mips_r2_uClibc-0.9.33.2/root-ar71xx/usr/bin/gcc and need to do some testing an clean up the Makefile and set up the packaging yet.

You should see something in the next couple of days, I'm ready to play with the Tre!