All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paulo Cesar Zaneti" <paulo.zaneti@gmail.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
	 "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] perl: fix startperl configuration option for perl-native
Date: Mon, 3 May 2021 17:03:15 -0300	[thread overview]
Message-ID: <CAP77v2qZx8P0P8S0NrXFPM-9HGvhUrZP_cJhQZN5PysgYK39FA@mail.gmail.com> (raw)
In-Reply-To: <CAP9ODKp3n3gx-Op-4MnqkmnV=6TbJcF3hSA+Wc4dKQjH3A6ykQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2579 bytes --]

Yes, I agree to revert until we find out a solution for everyone needs.

Should I send a patch reverting it ?

On Mon, May 3, 2021 at 4:56 PM Otavio Salvador <
otavio.salvador@ossystems.com.br> wrote:

> Hello,
>
> Couldn't the OE-Core:f2d1523b19cb066a4a06609f036822fe4a8b43f0 to be
> reverted in meanwhile?
>
> Em sex., 30 de abr. de 2021 às 17:42, Peter Kjellerstedt <
> peter.kjellerstedt@axis.com> escreveu:
>
>> Well, it did break our builds. I now get the following error when
>> building a native recipe that inherits perlnative and tries to run pod2man:
>>
>>
>>
>> | /bin/sh: /home/pkj/…/recipe-sysroot-native/usr/bin/pod2man:
>> /home/pkj/…/recipe-sysroot-native/usr/bin/per: bad interpreter: No such
>> file or directory
>>
>>
>>
>> This is because the first two lines of the pod2man script now looks like
>>
>>
>>
>> #!/home/pkj/…/recipe-sysroot-native/usr/bin/perl
>>
>>     eval 'exec /home/pkj/…/recipe-sysroot-native/usr/bin/perl -S $0
>> ${1+"$@"}'
>>
>>
>>
>> instead of the previous:
>>
>>
>>
>> #!/usr/bin/env nativeperl
>>
>>     eval 'exec /usr/bin/env nativeperl -S $0 ${1+"$@"}'
>>
>>
>>
>> I.e., the sed command in perl’s do_install_append_class-native() does not
>> seem to have done anything, which is because there is no
>> “perl-native.*/perl" in the path to match (as can be seen above), it is
>> just “perl”, which is what the old code was looking for.
>>
>>
>>
>> [ In the above examples, I have replaced a longish part of the path with
>> … to protect the innocent. ]
>>
>>
>>
>> //Peter
>>
>>
>>
>> *From:* openembedded-core@lists.openembedded.org <
>> openembedded-core@lists.openembedded.org> *On Behalf Of *Paulo Cesar
>> Zaneti
>> *Sent:* den 19 april 2021 16:13
>> *To:* openembedded-core@lists.openembedded.org
>> *Subject:* Re: [OE-core] [PATCH] perl: fix startperl configuration
>> option for perl-native
>>
>>
>>
>> I just re-send the patch with additional fix for the build failure.
>>
>> I think the basic problem was an inconsistency in the way perl recipe and
>> cpan.bbclass convert the absolute perl path to env path.
>> Version 2 of the patch tries to use same cpan.bbclass approach on the
>> perl recipe.
>>
>> Before submitting I just ran "bitbake -k world". I hope it doesn't break
>> the build again.
>>
>> 
>>
>>
>
> --
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br        http://code.ossystems.com.br
> Mobile: +55 (53) 9 9981-7854          Mobile: +1 (347) 903-9750
>

[-- Attachment #2: Type: text/html, Size: 6116 bytes --]

  reply	other threads:[~2021-05-03 20:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 22:28 [PATCH] perl: fix startperl configuration option for perl-native paulo.zaneti
2021-04-17 15:01 ` [OE-core] " Khem Raj
2021-04-19  7:48   ` Naveen Saini
2021-04-19 14:13     ` Paulo Cesar Zaneti
2021-04-30 20:42       ` [OE-core] " Peter Kjellerstedt
2021-05-03 19:55         ` Otavio Salvador
2021-05-03 20:03           ` Paulo Cesar Zaneti [this message]
2021-05-03 22:10         ` Paulo Cesar Zaneti
2021-04-17 22:46 ` Richard Purdie

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=CAP77v2qZx8P0P8S0NrXFPM-9HGvhUrZP_cJhQZN5PysgYK39FA@mail.gmail.com \
    --to=paulo.zaneti@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    --cc=peter.kjellerstedt@axis.com \
    /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.