All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: It's a [PERL] lie...
Date: Fri, 26 Jul 2013 10:07:06 -0600	[thread overview]
Message-ID: <51F29EAA.4070702@mlbassoc.com> (raw)
In-Reply-To: <CAJTo0LYbiY-qiAgcSEBD2GVO7m9bF1VU4YTu0qP4W4ydhuNixg@mail.gmail.com>

On 2013-07-26 09:54, Burton, Ross wrote:
> On 26 July 2013 16:49, Gary Thomas <gary@mlbassoc.com> wrote:
>>   It turns out that PERL is the only package
>> that cares about this DISTRO_FEATURE and it builds incorrectly
>> if it's left out :-(  Adding this feature back into my settings
>> made PERL build properly and now Amanda runs as well.
>
> According to grep it's perl, cmake and libarchive that respect the
> largefile feature.

Indeed, I missed them in my zeal :-(  I new I was looking for something
that affected my problem, and perl was the key (I'm not using either
of the other packages)

>
> If perl is known to break without largefile it's simple enough to make
> it error when building if the feature isn't enabled, but to be honest
> should we just remove this feature as it's so infrequently used?

I'd vote for at least fixing the perl recipe.  The problem is insidious;
it only fails at runtime and then in mysterious ways...  It also fails
on every architecture I tried (x86, ARM, PPC)

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


      reply	other threads:[~2013-07-26 16:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26 15:49 It's a [PERL] lie Gary Thomas
2013-07-26 15:54 ` Burton, Ross
2013-07-26 16:07   ` 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=51F29EAA.4070702@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=ross.burton@intel.com \
    --cc=yocto@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.