All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Ham <jimham@porcine.com>
To: openembedded-devel@lists.openembedded.org
Subject: bitbake gs fails
Date: Wed, 01 Nov 2006 13:33:32 -0800	[thread overview]
Message-ID: <1162416812.18790.14.camel@linux.site> (raw)

Hi,

I just got OE working yesterday, so please bear with me if I'm making
any obvious mistakes.

Problem #1: The "file" package is on the dependency list and fails

I found that the archive referred to in "file_4.16.bb" 
"ftp://ftp.astron.com/pub/file/file-${PV}.tar.gz" only has rev 4.17 and
4.18, no 4.16. I changed the name of the .bb files to xxx4.17.bb and
this task completed. As I have not yet made gs completely I don't know
if I broke something or not.

Problem #2: The qemu package is on the dependency list and fails

Apparently qemu wants gcc <4.0. Here's the results. My target is an
Arcom Viper SBC that has a PXA255 on it. It looks like the "tosa"
configuration is pretty close.

OE Build Configuration:
BB_VERSION     = "1.6.1"
OE_REVISION    = "95d2b2a99ed6c847a4d694730352bf03fab11239"
TARGET_ARCH    = "arm"
TARGET_OS      = "linux"
MACHINE        = "tosa"
DISTRO         = "familiar"
DISTRO_VERSION = "unstable-20061101"
TARGET_FPU     = ""

NOTE: multiple providers are available (glibc, glibc-intermediate);
NOTE: consider defining
PREFERRED_PROVIDER_virtual/arm-linux-libc-for-gcc
NOTE: multiple providers are available (qemu-native,
qemu-qop-nogfx-native);
NOTE: consider defining PREFERRED_PROVIDER_qemu-native
NOTE: package qemu-native-0.8.2+cvs20060723: started
NOTE: package qemu-native-0.8.2+cvs20060723-r1: task do_configure:
started
ERROR: function do_configure failed
ERROR: log data follows (/stuff/tmp/work/i686-linux/qemu-native-0.8.2
+cvs20060723-r1/temp/log.do_configure.18828)
| NOTE: Running /stuff/tmp/work/i686-linux/qemu-native-0.8.2
+cvs20060723-r1/qemu/configure                  --build=i686-linux
--host=i686-linux               --target=i686-linux
--prefix=/stuff/tmp/staging
--exec_prefix=/stuff/tmp/staging/i686-linux
--bindir=/stuff/tmp/staging/i686-linux/bin
--sbindir=/stuff/tmp/staging/i686-linux/bin
--libexecdir=/stuff/tmp/staging/i686-linux/libexec
--datadir=/stuff/tmp/staging/i686-linux/share
--sysconfdir=/stuff/tmp/staging/etc
--sharedstatedir=/stuff/tmp/staging/com
--localstatedir=/stuff/tmp/staging/var
--libdir=/stuff/tmp/staging/i686-linux/lib
--includedir=/stuff/tmp/staging/i686-linux/include
--oldincludedir=/stuff/tmp/staging/i686-linux/include
--infodir=/stuff/tmp/staging/i686-linux/share/info
--mandir=/stuff/tmp/staging/i686-linux/share/man                                         ...
| ERROR: "gcc" looks like gcc 4.x
| QEMU is known to have problems when compiled with gcc 4.x
| It is recommended that you use gcc 3.x to build QEMU
| To use this compiler anyway, configure with --disable-gcc-check
| FATAL: oe_runconf failed
NOTE: Task failed: /stuff/tmp/work/i686-linux/qemu-native-0.8.2
+cvs20060723-r1/temp/log.do_configure.18828
NOTE: package qemu-native-0.8.2+cvs20060723-r1: task do_configure:
failed
ERROR: TaskFailed event exception, aborting
NOTE: package qemu-native-0.8.2+cvs20060723: failed
ERROR: Build of gs failed

Can anyone tell me how to pass the "--disable-gcc-check" argument into
configure? I don't really want to go back to gcc 3.xx. Is there a better
way of handling this?

I'd appreciate any general pointers to help me along with this process.

Regards,

Jim Ham





                 reply	other threads:[~2006-11-01 21:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1162416812.18790.14.camel@linux.site \
    --to=jimham@porcine.com \
    --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.