**** BEGIN LOGGING AT Wed Oct 07 02:59:58 2015
Oct 07 11:22:38 <tasslehoff> Besides a machine.conf, what is needed to create a new machine?
Oct 07 11:24:48 <hrw> tasslehoff: in perfect world nothing else
Oct 07 11:27:09 <tasslehoff> hrw: good. I was missing a COMPATIBLE_MACHINE in my kernel .bbappend, but other than that it seems good.
Oct 07 11:27:27 <tasslehoff> just need to figure out how the angstrom setup scripts work
Oct 07 11:27:39 <hrw> tasslehoff: angstrom-manifest you mean?
Oct 07 11:27:56 <tasslehoff> hrw: yes. need to get used to saying that :)
Oct 07 11:27:57 <hrw> http://www.angstrom-distribution.org/setup-scripts-are-now-called-angstrom-manifest/
Oct 07 11:28:17 <tasslehoff> yes, that is what I'm using
Oct 07 11:28:44 <tasslehoff> I thougt "MACHINE=new-machine . ./setup-environment" would change my machine, but that is not the case
Oct 07 11:29:20 <hrw> last time I was adding machine into OE was 3 years ago.
Oct 07 11:29:44 <hrw> had to edit classes, toolchains, kernel, machine config and includes and lot of other stuff
Oct 07 11:32:31 <tasslehoff> after setup-environment it says the build env is configured for the new machine, but when I build a recipe it uses another one.
Oct 07 11:33:11 <hrw> tasslehoff: so edit conf/* files?
Oct 07 11:33:54 <tasslehoff> hrw: yeah. just stumbled over auto.conf
Oct 07 12:45:53 <tasslehoff> is it intended that auto.conf overrides a machine specified on the command line?
Oct 07 12:50:41 <hrw> tasslehoff: replace MACHINE = "something" with 
Oct 07 12:50:48 <hrw> with ?= instead of =
Oct 07 12:50:55 <hrw> set if not set
Oct 07 12:51:45 <tasslehoff> hrw: that is what auto.conf had, but the machine I set was unset all the same.
Oct 07 12:51:54 <tasslehoff> oh well, I'll figure it out. thanks.
Oct 07 22:14:28 <LetoThe2nd> is there a proper way to have the cross toolchains include f77? seems like only changing FORTRAN in gcc-configure-common.inc doesn't do the trick
**** ENDING LOGGING AT Thu Oct 08 02:59:58 2015