From: "Mike (mwester)" <mwester@dls.net>
To: openembedded-devel@openembedded.org
Subject: krb recipe
Date: Sat, 31 Jan 2009 00:49:51 -0600 [thread overview]
Message-ID: <4983F48F.20208@dls.net> (raw)
- This doesn't work. First, I don't think the unpack belongs in do_configure, but be that as it may. The big issue is that the patch creates a source file, which causes patching to fail because the source file already exists for any subsequent attempt to run do_configure.
do_configure() {
tar xzf ${WORKDIR}/krb5-1.6.3.tar.gz -C ${WORKDIR}/
patch -p1 < ${WORKDIR}/fix-uclibc-ruserpass-collision.patch
oe_runconf
}
- do_configure failes if TARGET_LINK_HASH_STYLE is not set. Right now it's only set for Angstrom distros, so this recipe only builds for Angstrom. Note the extra space between "-O1" and "-lpthread" in the first line; something stripped extra white space as it was passed through somewhere.
configure: error: `LDFLAGS' has changed since the previous run:
configure: former value: -L/u/slug/slugos/tmp/staging/armv5teb-linux-gnueabi/usr/lib -Wl,-rpath-link,/u/slug/slugos/\
tmp/staging/armv5teb-linux-gnueabi/usr/lib -Wl,-O1 -lpthread
configure: current value: -L/u/slug/slugos/tmp/staging/armv5teb-linux-gnueabi/usr/lib -Wl,-rpath-link,/u/slug/slugos/\
tmp/staging/armv5teb-linux-gnueabi/usr/lib -Wl,-O1 -lpthread
configure: error: changes in the environment can compromise the build
Regards,
Mike (mwester)
next reply other threads:[~2009-01-31 6:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-31 6:49 Mike (mwester) [this message]
2009-02-01 13:13 ` krb recipe Anatoly Shipitsin
[not found] <C2AB3E43-BDA7-4353-9496-C57DE480F612@ngndg.com>
2009-01-31 14:59 ` Tim Ellis
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=4983F48F.20208@dls.net \
--to=mwester@dls.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.