From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: iputils fails to build due to missing sgmlspl
Date: Fri, 13 Aug 2010 14:32:52 -0700 [thread overview]
Message-ID: <4C65BA04.9020908@mentor.com> (raw)
In-Reply-To: <AANLkTi=haC49V6XnCQpBCY8ickT24PL1F0sKYoh8h6=J@mail.gmail.com>
AJ ONeal wrote:
> This is with a fresh install of oe and bitbake (as per the gumstix docs)
>
> |
> /mnt/data/Code/overo-oe/tmp/sysroots/i686-linux/usr/armv7a/lib/gcc/arm-angstrom-linux-gnueabi/4.3.3/../../../../arm-angstrom-linux-gnueabi/bin/ld:
> warning: libc.so, needed by
> /mnt/data/Code/overo-oe/tmp/sysroots/i686-linux/usr/armv7a/lib/gcc/arm-angstrom-linux-gnueabi/4.3.3/../../../../arm-angstrom-linux-gnueabi/lib/libgcc_s.so,
> not found (try using -rpath or -rpath-link)
> | make -C doc man
> | make[1]: Entering directory
> `/mnt/data/Code/overo-oe/tmp/work/armv7a-angstrom-linux-gnueabi/iputils-20071127-r1/iputils_20071127.orig/doc'
> | /bin/sh: sgmlspl: command not found
> | make[1]: *** [arping.8] Error 127
> | make[1]: Leaving directory
> `/mnt/data/Code/overo-oe/tmp/work/armv7a-angstrom-linux-gnueabi/iputils-20071127-r1/iputils_20071127.orig/doc'
> | make: *** [man] Error 2
> | FATAL: oe_runmake failed
>
>
> The problem is not solved by
> bitbake -c clean iputils; bitbake sgmlspl; bitbake iputils
You would need to do bitbake sgmlspl-native ; bitbake iputils, to get
sgmlspl that runs on the host. sgmlspl-native will bring in perl-native
and some other stuff, FYI.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-08-13 21:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 21:18 iputils fails to build due to missing sgmlspl AJ ONeal
2010-08-13 21:32 ` Tom Rini [this message]
2010-08-13 22:05 ` AJ ONeal
2010-08-14 0:25 ` AJ ONeal
2010-08-14 15:35 ` AJ ONeal
2010-08-19 23:02 ` Denys Dmytriyenko
2010-08-20 6:25 ` Frans Meulenbroeks
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=4C65BA04.9020908@mentor.com \
--to=tom_rini@mentor.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.