Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: harald <ba0547@bnv-bamberg.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Compile OE on Sun Ultrasparc 64 architecture?
Date: Wed, 04 Mar 2009 20:35:38 +0100	[thread overview]
Message-ID: <1236195338.4249.20.camel@debian.dorg.org> (raw)
In-Reply-To: <20090304153617.GQ26343@smtp.west.cox.net>

Am Mittwoch, den 04.03.2009, 08:36 -0700 schrieb Tom Rini:
> On Wed, Mar 04, 2009 at 03:52:30PM +0100, harald wrote:
> 
> > Hello,
> > 
> > tried to compile OE on my Sun Ultrasparc 64 machine running on debian
> > lenny. 
> > Compilation fails, package qemu-native fails to compile with an error in
> > zlib. please see build logs, machine h4000, user ba0547.
> 
> You might want to disable binary locale generation on the host and see
> what else falls down.  ENABLE_BINARY_LOCALE_GENERATION = 0 in your
> local.conf
> 
hello, 

binary_locale_generation has been set to 0.

now other packages fail to compile/install:

| Making all in mpn
| make[2]: Entering directory
`/home/stuff/tmp/work/sparc64-linux/gmp-native-4.2.4-r0/gmp-4.2.4/mpn'
| /bin/sh ../sparc64-linux-libtool --mode=compile
--tag=CC ../mpn/m4-ccas --m4="m4" ccache gcc -std=gnu99 -c
-DHAVE_CONFIG_H -I. -I.. -D__GMP_WITHIN_GMP -I.. -DOPERATION_`echo add_n
| sed 's/_$//'`
-isystem/home/stuff/tmp/staging/sparc64-linux/usr/include
-isystem/home/stuff/tmp/staging/sparc64-linux/usr/include -O2
-Wa,--noexecstack `test -f 'add_n.asm' || echo './'`add_n.asm
| sparc64-linux-libtool: compile:  ../mpn/m4-ccas --m4=m4 ccache gcc
-std=gnu99 -c -DHAVE_CONFIG_H -I. -I.. -D__GMP_WITHIN_GMP -I..
-DOPERATION_add_n
-isystem/home/stuff/tmp/staging/sparc64-linux/usr/include
-isystem/home/stuff/tmp/staging/sparc64-linux/usr/include -O2
-Wa,--noexecstack add_n.asm  -fPIC -DPIC -o .libs/add_n.o
| m4  -DHAVE_CONFIG_H -D__GMP_WITHIN_GMP -DOPERATION_add_n -DPIC
add_n.asm >tmp-add_n.s
|  ccache gcc -std=gnu99 -c -DHAVE_CONFIG_H -I. -I.. -D__GMP_WITHIN_GMP
-I.. -DOPERATION_add_n
-isystem/home/stuff/tmp/staging/sparc64-linux/usr/include
-isystem/home/stuff/tmp/staging/sparc64-linux/usr/include -O2
-Wa,--noexecstack tmp-add_n.s -fPIC -DPIC -o .libs/add_n.o
| tmp-add_n.s: Assembler messages:
| tmp-add_n.s:66: Error: Architecture mismatch on "lduw".
| tmp-add_n.s:66:  (Requires v9|v9a|v9b; requested architecture is
sparclite.)
| tmp-add_n.s:67: Error: Architecture mismatch on "lduw".
| tmp-add_n.s:67:  (Requires v9|v9a|v9b; requested architecture is
sparclite.)
| tmp-add_n.s:69: Error: Architecture mismatch on "bl,pn %icc,.Lend1".
| tmp-add_n.s:69:  (Requires v9|v9a|v9b; requested architecture is
sparclite.)
| tmp-add_n.s:70: Error: Architecture mismatch on "lduw".
| tmp-add_n.s:70:  (Requires v9|v9a|v9b; requested architecture is
sparclite.)
| tmp-add_n.s:

cut....

for further details please see build log.
Any idea?

regards, harald.





  reply	other threads:[~2009-03-04 19:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-04 14:52 Compile OE on Sun Ultrasparc 64 architecture? harald
2009-03-04 15:36 ` Tom Rini
2009-03-04 19:35   ` harald [this message]
2009-03-04 19:45     ` Tom Rini
2009-03-04 20:11       ` harald
2009-03-04 20:23         ` Tom Rini
2009-03-04 20:42           ` harald

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=1236195338.4249.20.camel@debian.dorg.org \
    --to=ba0547@bnv-bamberg.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox