From: Randy MacLeod <randy.macleod@windriver.com>
To: Nicolas Dechesne <ndec13@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Perl 'native' path
Date: Thu, 29 Nov 2012 01:01:54 -0500 [thread overview]
Message-ID: <50B6FA52.7070300@windriver.com> (raw)
In-Reply-To: <CAOT3miKfftRKyBbPZCSmq=jKVx=pqRVLQtn-4azH_FbrmOqE4A@mail.gmail.com>
On 12-11-27 11:57 AM, Nicolas Dechesne wrote:
> hi,
>
> i am getting the following build error:
> ...
> i am trying to setup some daily builds on some corporate administrated
> machines... and what happens is that dpkg-scanpackage perl script has
> this:
>
> $ more sysroots/x86_64-linux/usr/bin/dpkg-scanpackages
> #!/usr/local/bin/perl
>
> So in turns my build will attempt to use whatever I have in
> /usr/local/bin (AFAIU), which is problematic in my case as this points
> to a corporate version (/apps/perl), which then leads to build
> failure.
Yes, it seems that dpkg-scanpackages needs to be fixed.
> I would expect all scripts to use the perl-native binary, instead, and
> search for Perl modules in the sysroot folder.
>
> does that make any sense?
Your explanation makes sense.
>is there something wrong with what I am
> doing (beyond using a corporate server which I can't administrate ;-)
I believe that using .debs in itself puts you in a less
tested environment; nonetheless, it should work.
Can you patch it?
Oh and I'm just curious, does an rpm system not work for you?
>
> thx
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
--
# Randy MacLeod
prev parent reply other threads:[~2012-11-29 6:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 16:57 Perl 'native' path Nicolas Dechesne
2012-11-29 6:01 ` Randy MacLeod [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=50B6FA52.7070300@windriver.com \
--to=randy.macleod@windriver.com \
--cc=ndec13@gmail.com \
--cc=openembedded-core@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.