Been having a difficult time getting my galileo gen 2 up and running.
I simply need a yocto image with a standard build toolset (gcc, ..) and the ability to install deb/rpm/(smart?)/(ipk?) packages if possible.
The yocto image provided by Intel includes de standard build toolset. I don't know about "...deb/rpm/..." ... if you are referring to Linux debian packages I think you won't be able to install them directly in yocto... it's a different (and non-compatible AFAIK) Linux distribution.
1. Does such a yocto image exist, or do I need to build it using `bitbake`? I am under the impression that you need to bitbake your own image if you want the smart package manager or to have deb/rpm support. Is this true?
I've not used the smart package, but I found a specific thread on that: install packages from smart repository
2. What is the best yocto image to use for this purpose? Any recommendations? I'd rather not build my own image if possible.
I've not made it... but I think it's worth trying with the official-Intel provided yocto image, so you don't have to build your own.
I think that you are having too much trouble with the yocto image (you are using the right one, I think) so as to open a specific thread on that. Once you have the yocto image in an "up&runnung" SD, then I suggest you move on the package issue/s.
I will be needing to create my own packages containing go binaries that I plan to cross-compile using gccgo.
I'm not sure that it is possible.
GO requires to have MMX support (as you may check in GO sources go/asm_386.s at master · golang/go · GitHub ):
But Galileo's Quark CPU does not support MMX.
I just came cross your reply.
You mentioned that Go is not supported by Galileo as Go requires MMX.
I am wondering if this is truth or I can have other options for Galileo to support Go.
as I have shown on a picture above Go compiled from a source code located on Github does not work on Galileo board.
You may compile it by yourself to check is it truth or not.
In the documentation Installing Go from source - The Go Programming Language you may find that
GO386=387: use x87 for floating point operations; should support all x86 chips (Pentium MMX or later).
A string about MMX support you may find in a source code:
As I saw in the Go's source code it uses MMX & AES command set which is not implemented in Quark CPU.
It means that a lot of work need to be done to replace unsupported x86 commands by some equivalents.
Potentially it is possible to do. Also such a solution will work slower.