From: Filippo Basso <phy@linux.it>
To: openembedded-devel@lists.openembedded.org
Subject: different hosts, different OE images
Date: Tue, 09 Oct 2007 17:26:21 +0200 [thread overview]
Message-ID: <470B9D9D.5080501@linux.it> (raw)
Hi,
here is another developer jumped into the world of OE... Wow! really
amazing tool...!
Anyway, today I got into a strange behaviours that depends on the
machine on which I'm bitbakin' (a debian testing/lenny and a debian
stable/etch on vmware).
I understood that the results should be highly independent from host
system, so I begun debugging a bit.
So, I luckily (!) got also into a difference that lead me to a
compile/non-compile, much easier to debug. On a angstrom-2007.1 and i586
architecture, I added "minimo" web-browser and I got that with the same
identical OE installation it compiles on my machine and fails compiling
in my vmware.
2 new points are now in my debug log:
1st point - (one of these "I want to understand why...")
in general, quite all the files "run.do_configure.xxx" or similar are
not sorted in the same way; definitions of environment variables are in
different order, depending on the system... is it normal?
2nd point - (one that let me thing "is this a bug...?")
in mozilla minimo webbrowser (minimo-1_0.02+cvs20070626-r0) the
log.do_compile is strange:
***debian etch***
....
ccache gcc -o host_xpidl
-isystem/home/nbt/OSSTBOX/trunk/oe/build-nbt-crownbeach/tmp/staging/i586-angstrom-linux/include
-fexpensive-optimizations -fomit-frame-pointer -frename-registers -Os
-DXP_UNIX -O3
-I/home/nbt/OSSTBOX/trunk/oe/build-nbt-crownbeach/tmp/staging/i586-angstrom-linux/include/libIDL-2.0
-I/home/nbt/OSSTBOX/trunk/oe/build-nbt-crownbeach/tmp/staging/i586-angstrom-linux/include/glib-2.0
-I/home/nbt/OSSTBOX/trunk/oe/build-nbt-crownbeach/tmp/staging/i586-angstrom-linux/lib/glib-2.0/include
-DMDCPUCFG=\"md/_linux.cfg\" host_xpidl.o host_xpidl_idl.o
host_xpidl_util.o host_xpidl_header.o host_xpidl_typelib.o
host_xpidl_doc.o host_xpidl_java.o ../../../dist/host/lib/libhostxpt.a
-L/home/nbt/OSSTBOX/trunk/oe/build-nbt-crownbeach/tmp/staging/i586-angstrom-linux/lib
-lIDL-2 -lglib-2.0
/home/nbt/OSSTBOX/trunk/oe/build-nbt-crownbeach/tmp/staging/i586-angstrom-linux/lib/libc.so.6:
undefined reference to `_dl_tls_get_addr_soft@GLIBC_PRIVATE'
collect2: ld returned 1 exit status
make[7]: *** [host_xpidl] Error 1
...
FATAL: oe_runmake failed
***debian lenny***
the above "ccache gcc -o host_xpidl..." works well, even if there
are some warnings in compiling "ccache gcc -o host_xpidl_java.o ..."
that are not present in etch.
is this a bug? shouldn't the recipe invoke "ccache
i586-angstrom-linux-gcc" instead of "ccache gcc" (as is doing in other
parts of the recipe)???
Am I right saying that there it's using my gcc and not the cross-gcc? is
there an elegant way to check which other packages are using somewhere
my gcc and not the right one? (there was also another difference in
behaviours, before minimo, between the 2 images created)
thank you for all,
hope to contribute more actively soon, now just need some newbie
confirmations!
phy
next reply other threads:[~2007-10-09 15:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 15:26 Filippo Basso [this message]
2007-10-11 0:11 ` different hosts, different OE images Filippo Basso
2007-10-24 19:08 ` Filippo Basso
2007-10-26 10:35 ` Stelios Koroneos
2007-10-26 19:32 ` Filippo Basso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=470B9D9D.5080501@linux.it \
--to=phy@linux.it \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.