[oe] different hosts, different OE images

[Filippo Basso]

> I understood that the results should be highly independent from host
> system, so I begun debugging a bit.
>   
Hi everybody,
    my investigation is going ahead...
The main point is: an image should be highly independent from the host
system, but seems that I've some problem in this regards... maybe my
mistake, but should be understood.

Another machine (Ubuntu) gave even another different runtime result... :-(

Now I've debugged differences in the log.do_compile files, and have
these "strange" results:
* the order of gcc arguments is not always fixed, depends on the machine
(es: ipkg, perl)
* in many packages the make[n] is make[n+1], sometimes there is a
duplicated chdir, or there is a duplicated message like "OE: Not
hardcoding..."
* in many packages on lenny is present in the options for "ccache
i586-angstrom-linux-gcc" a -L/usr/lib (isn't that potentially dangerous???)


Not OE-related, more .bb recipy-related:
* minimo is using gcc (and not i586-angstrom-linux-gcc), so is failing
on etch and working on lenny (I've to investigate more if this can work,
imagine if I want to use an ARM, hehehe!)
* and a strange behaviour in coreutils-native (this I've to investigate
more, about openat.c and getcwd.c, maybe not a OE issue)


To be sure that the versions are the same, the OE tree is the same (mtn
status: 1c938b19625a9b636c77145c8a420c71768f0595), bitbake is the same,
I've double checked everything.

Now it's  late night, I'll investigate ubuntu problems (X11 restarting
continuously) with same image compiling on lenny, not compiling on etch...

some suggestions?
thank you 10000!
    phy