Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12331] New: meson issue
Date: Wed, 20 Nov 2019 14:08:47 +0000	[thread overview]
Message-ID: <bug-12331-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=12331

            Bug ID: 12331
           Summary: meson issue
           Product: buildroot
           Version: 2019.02.7
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: jpcartal at free.fr
                CC: buildroot at uclibc.org
  Target Milestone: ---

Meson script uses full path to python3 when executed which gives errors when
the path is too long :

$ cat host/bin/meson 
#!/home/Dev/Ssd/buildroot/buildroot-2019.02.7/host/bin/python3
# EASY-INSTALL-ENTRY-SCRIPT: 'meson==0.49.0','console_scripts','meson'
__requires__ = 'meson==0.49.0'
import re
import sys
from pkg_resources import load_entry_point

if __name__ == '__main__':
    sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0])
    sys.exit(
        load_entry_point('meson==0.49.0', 'console_scripts', 'meson')()
    )

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2019-11-20 14:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20 14:08 bugzilla at busybox.net [this message]
2019-11-20 15:19 ` [Buildroot] [Bug 12331] meson issue bugzilla at busybox.net
2019-11-27  7:58 ` bugzilla at busybox.net
2019-11-27  8:09 ` bugzilla at busybox.net
2020-01-13 17:37 ` bugzilla at busybox.net
2020-01-13 18:08 ` bugzilla at busybox.net
2020-02-03 12:10 ` bugzilla at busybox.net

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=bug-12331-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox