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 12481] minicom fails when output directory path contains "m4"
Date: Fri, 17 Jan 2020 12:08:20 +0000	[thread overview]
Message-ID: <bug-12481-163-hsfSbLFGV4@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12481-163@https.bugs.busybox.net/>

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

--- Comment #3 from Arnout Vandecappelle <arnout@mind.be> ---
It seems to be caused by host-gettext-tiny, which installs stuff in the wrong
directory, so the relevant m4 files can't be found.

I've done a quick check and found no upstream commits or PRs or issues that
seem relevant.

This one looks funny:

gettext-gnu/gettext-tools/misc/autopoint.in:    m4/ ) destfile=`echo "$1" | sed
-e "s,^m4/,$m4dir/,"` ;;

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

  parent reply	other threads:[~2020-01-17 12:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 21:23 [Buildroot] [Bug 12481] New: minicom fails when output directory path contains "m4" bugzilla at busybox.net
2020-01-16 21:43 ` [Buildroot] [Bug 12481] " bugzilla at busybox.net
2020-01-17  7:45 ` bugzilla at busybox.net
2020-01-17 11:46 ` bugzilla at busybox.net
2020-01-17 12:08 ` bugzilla at busybox.net [this message]
2020-01-17 12:18 ` bugzilla at busybox.net
2020-01-17 12:32 ` bugzilla at busybox.net
2020-01-17 14:28 ` bugzilla at busybox.net
2020-01-17 17:44 ` bugzilla at busybox.net
2020-01-17 17:55 ` bugzilla at busybox.net
2020-01-18 22:22 ` 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-12481-163-hsfSbLFGV4@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