Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Boeckel <mathstuf@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] taskd: add patch to fix musl build issue
Date: Wed, 15 Jun 2016 23:44:00 +0000 (UTC)	[thread overview]
Message-ID: <njsp80$bbh$1@ger.gmane.org> (raw)
In-Reply-To: 20160507071838.BB2F8817CA@busybox.osuosl.org

On Sat, 07 May, 2016 at 07:17:00 GMT, Thomas Petazzoni wrote:
> taskd checks for `get_current_dir_name` but forgets to add a `cmakedefine`
> in cmake.h.in, so `HAVE_GET_CURRENT_DIR_NAME` is always undefined.
>
> CMake detects correctly that the musl C library defines `get_current_dir_name`.
> However, as `HAVE_GET_CURRENT_DIR_NAME` is not set, the block of code evaluated
> cannot be compiled as musl does not define `PATH_MAX`.
>
> Reported upstream:
> https://bug.tasktools.org/browse/TD-120

I didn't see the patch on the issue, so I sent it to the development
list:

    https://groups.google.com/forum/#!topic/taskwarrior-dev/bxIftgz-hBI

--Ben

  reply	other threads:[~2016-06-15 23:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-07  7:17 [Buildroot] [git commit] taskd: add patch to fix musl build issue Thomas Petazzoni
2016-06-15 23:44 ` Ben Boeckel [this message]
2016-06-17  1:02   ` Ben Boeckel

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='njsp80$bbh$1@ger.gmane.org' \
    --to=mathstuf@gmail.com \
    --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