All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neuer User <auslands-kv@gmx.de>
To: yocto@yoctoproject.org
Subject: Re: Help with building app recipe
Date: Fri, 16 May 2014 14:33:38 +0200	[thread overview]
Message-ID: <ll50j2$f2p$1@ger.gmane.org> (raw)
In-Reply-To: <ll4vid$196$1@ger.gmane.org>

Am 16.05.2014 14:16, schrieb Neuer User:
> Am 16.05.2014 14:04, schrieb Anders Darander:
> 
> Great, that helped with no 1.). Still a lot to learn for me.
> 
> No 2. is still open, though. Is that a problem of my recipe or rather a
> generic problem of the python3 recipe? I could patch the python3 recipe,
> so that it changes the interpreter line to "python3".
> 

Hmm the python3-native recipe has this install function:

----------------------------------------------------------
do_install() {
        install -d ${D}${libdir}/pkgconfig
        oe_runmake 'DESTDIR=${D}' install
        if [ -e ${WORKDIR}/sitecustomize.py ]; then
                install -m 0644 ${WORKDIR}/sitecustomize.py
${D}/${libdir}/python${PYTHON_MAJMIN}
        fi
        install -d ${D}${bindir}/${PN}
        install -m 0755 Parser/pgen ${D}${bindir}/${PN}

        # Make sure we use /usr/bin/env python
        for PYTHSCRIPT in `grep -rIl ${bindir}/${PN}/python
${D}${bindir}/${PN}`; do
                sed -i -e '1s|^#!.*|#!/usr/bin/env python|' $PYTHSCRIPT
        done
}
----------------------------------------------------------


If I change the sed line to "#!/usr/bin/env python3", that would
probably work then. But would it break something else?



  reply	other threads:[~2014-05-16 12:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-16 11:23 Help with building app recipe Neuer User
2014-05-16 12:04 ` Anders Darander
2014-05-16 12:16   ` Neuer User
2014-05-16 12:33     ` Neuer User [this message]
2014-05-17  5:18       ` Khem Raj
2014-05-22 13:50         ` Diego Sueiro

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='ll50j2$f2p$1@ger.gmane.org' \
    --to=auslands-kv@gmx.de \
    --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.