From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
To: 751337@bugs.debian.org, jeremie.galarneau@efficios.com,
lttng-dev@lists.lttng.org
Subject: Bug#751337: [PATCH] tests: test_ctf_writer: replace HOST_NAME_MAX
Date: Wed, 6 Aug 2014 09:03:24 +0200 [thread overview]
Message-ID: <20140806070324.GA2888@breakpoint.cc> (raw)
In-Reply-To: <20140805201412.GA11272@helmut>
On 2014-08-05 16:14:12 [-0400], Jon Bernard wrote:
> This may also work as well:
>
> diff --git a/configure.ac b/configure.ac
> index 80eba33..248044e 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -50,6 +50,17 @@ AC_C_INLINE
> AC_TYPE_PID_T
> AC_TYPE_SIZE_T
>
> +# FreeBSD does not define HOST_NAME_MAX
> +AC_CHECK_DECL(HOST_NAME_MAX,,
> + [
> + AC_CHECK_DECL(_POSIX_HOST_NAME_MAX,
> + AC_DEFINE(HOST_NAME_MAX, _POSIX_HOST_NAME_MAX, []),
> + AC_DEFINE(HOST_NAME_MAX, 256, [Define to 256 if neither have HOST_NAME_MAX nor _POSIX_HOST_NAME_MAX]),
> + [[#include <limits.h>]])
> + ],
> + [[#include <limits.h>]]
> +)
Sure it will. I have no strong opinion on how it gets fixed :)
> +
> # Checks for library functions.
> AC_FUNC_MALLOC
> AC_FUNC_MMAP
>
Sebastian
next prev parent reply other threads:[~2014-08-06 7:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140805200251.GA17716@breakpoint.cc>
2014-08-05 20:14 ` Bug#751337: [PATCH] tests: test_ctf_writer: replace HOST_NAME_MAX Jon Bernard
2014-08-05 20:14 ` Jon Bernard
2014-08-05 20:14 ` Jon Bernard
[not found] ` <20140805201412.GA11272@helmut>
2014-08-06 7:03 ` Sebastian Andrzej Siewior [this message]
2014-08-07 19:07 ` Jérémie Galarneau
2014-08-07 19:07 ` Jérémie Galarneau
2014-08-07 19:07 ` Jérémie Galarneau
2014-08-05 20:02 Sebastian Andrzej Siewior
-- strict thread matches above, loose matches on Subject: below --
2014-08-05 20:02 Sebastian Andrzej Siewior
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=20140806070324.GA2888@breakpoint.cc \
--to=sebastian@breakpoint.cc \
--cc=751337@bugs.debian.org \
--cc=jeremie.galarneau@efficios.com \
--cc=lttng-dev@lists.lttng.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).