I was able to compile a "hello world" and also compile a kernel module. That was all I wanted to do for now so I haven't moved past that. My next step was to figure out how to properly set up a layer so that bitbake can scan the recipe. I ran my recipe using the -b flag and pointing it to the bb file. The interesting part is that I HAD to give it an absolute path (starting with /), if I didn't, it looked for a package named as the path (for example it interpreted blah/
recipe.bb as a recipe name rather than a path to the recipe file, so I had to use /home/me/blah/
recipe.bb for example).
I imagine that building something more would just involve using the proper -l flags, because bitbake sets up the compiler with sysroot, so basically it means it uses the include and lib directories of the cross-compiled environment instead of your machine, but I haven't actually tried this yet.
The fact that you are depending on glibc is odd if you are building for the bone, because eglibc is used. Maybe the message is because bitbake is getting confused by multiple libcs. But really that's just a shot in the air since I've only done two recipes so far.
If you can get your program to be something that is just compiled by a typical ./configure; make; make install, then I would expect that you should be able to look at existing recipes for simple programs and how they are compiled and just duplicate that. The recipe doesn't actually do the guts of the build process, it's just supposed to "wrap around" your existing build process.
Jason