From: Gary Thomas <gary@mlbassoc.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: Poky Project <poky@yoctoproject.org>
Subject: Re: Autotools problem
Date: Fri, 01 Apr 2011 04:15:48 -0600 [thread overview]
Message-ID: <4D95A5D4.3030208@mlbassoc.com> (raw)
In-Reply-To: <625BA99ED14B2D499DC4E29D8138F15059F629DBAD@shsmsx502.ccr.corp.intel.com>
On 03/31/2011 10:35 PM, Tian, Kevin wrote:
>> From: Gary Thomas
>> Sent: Thursday, March 31, 2011 1:28 AM
>>
>> I'm trying to build a recipe I imported from OE (tcpdump_4.1.1.bb)
>> This used to build on Poky, but now fails. I fixed the issue with
>> the LIC_CHKSUM_FILES, but now I have a problem with the automatic
>> [re]generation of the config files.
>>
>> Rebuilding in a fresh tree from today's master
>> (6f4fbfe272f5d85cee95660a9278f3031533aec4),
>> I'm getting this error
>> | Perl lib version (5.12.2) doesn't match executable version (v5.10.1) at
>> /home/local/p60_poky/tmp/sysroots/i686-linux/usr/lib/perl/5.12.2/Config.pm
>> line 50.
>> | Compilation failed in require at
>> /home/local/p60_poky/tmp/sysroots/i686-linux/usr/lib/perl/5.12.2/File/Copy.p
>> m line 14.
>> | BEGIN failed--compilation aborted at
>> /home/local/p60_poky/tmp/sysroots/i686-linux/usr/lib/perl/5.12.2/File/Copy.p
>> m line 14.
>> | Compilation failed in require at
>> /home/local/p60_poky/tmp/sysroots/i686-linux/usr/share/autoconf/Autom4te/
>> FileUtils.pm line 166.
>> | BEGIN failed--compilation aborted at
>> /home/local/p60_poky/tmp/sysroots/i686-linux/usr/share/autoconf/Autom4te/
>> FileUtils.pm line 166.
>> | Compilation failed in require at
>> /home/local/p60_poky/tmp/sysroots/i686-linux/usr/bin/autom4te line 41.
>> | BEGIN failed--compilation aborted at
>> /home/local/p60_poky/tmp/sysroots/i686-linux/usr/bin/autom4te line 41.
>>
>> This leads to a cascade of other problems because the configure script is out of
>> date :-(
>
> could you post other problems too? Though above does be an issue, it may cause
> real problem...
The autotools problem has been filed as bug #941
My other problem with this recipe was actually the fact that configure sanity
errors are now treated as fatal (they used to just be warnings). This particular
configure script was trying to access some non-existent [Solaris only] libraries
with absolute paths. That set off the sanity checker, but was fairly easy to
identify and remove.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2011-04-01 10:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 17:27 Autotools problem Gary Thomas
2011-04-01 4:35 ` Tian, Kevin
2011-04-01 10:15 ` Gary Thomas [this message]
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=4D95A5D4.3030208@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=kevin.tian@intel.com \
--cc=poky@yoctoproject.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.