From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12461] New: libglib2 build files with deep directory structure
Date: Mon, 13 Jan 2020 12:50:11 +0000 [thread overview]
Message-ID: <bug-12461-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=12461
Bug ID: 12461
Summary: libglib2 build files with deep directory structure
Product: buildroot
Version: 2019.11.1
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: m.weisser.m at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
When building my current config it fails (to be more precise it hangs) when
trying to build libglib2
The last message is
/xxxx/yyyyy/xxxxxxxx/yyyyyyyy/zz/xxx/yyyyyyy/zzzz/xxxx/yyyyyy/zzzzzzzzzzzzzzzzz/xxxxxx/yyyyy/zzzzz/xxxxxx/yyy/output/host/bin/meson:
line 3: __requires__: command not found
This is caused by the shebang in output/host/bin/meson
#!/xxxx/yyyyy/xxxxxxxx/yyyyyyyy/zz/xxx/yyyyyyy/zzzz/xxxx/yyyyyy/zzzzzzzzzzzzzzzzz/xxxxxx/yyyyy/zzzzz/xxxxxx/yyy/output/host/bin/python3
which has a length of 135 characters which is to long for the kernel. Any other
workaround besides reducing the directory nesting?
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-01-13 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 12:50 bugzilla at busybox.net [this message]
2020-01-13 17:37 ` [Buildroot] [Bug 12461] libglib2 build files with deep directory structure 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-12461-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 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.