help / color / mirror / Atom feed
From: "Stephen Gregoratto" <dev@sgregoratto.me>
To: <discuss@mandoc.bsd.lv>
Subject: Cannot compile on Arch Linux due to conflicing int types
Date: Fri, 03 Apr 2020 14:14:37 +1100	[thread overview]
Message-ID: <C1R8UFWVURJZ.1ZFF5RNAN6OCW@dextop.sgregoratto.me> (raw)

The ohash functions included in tag.c use the stdint.h types, but tag.c
does not include them directly. This leads to compile errors like so:

In file included from mandoc_ohash.h:20,
                 from tag.c:31:
compat_ohash.h:56:20: error: unknown type name ‘uint32_t’; did you mean ‘u_int32_t’?
   56 |      const char *, uint32_t);
      |                    ^~~~~~~~
      |                    u_int32_t
compat_ohash.h:58:14: error: unknown type name ‘uint32_t’; did you mean ‘u_int32_t’?
   58 |      size_t, uint32_t);
      |              ^~~~~~~~
      |              u_int32_t
compat_ohash.h:67:1: error: unknown type name ‘uint32_t’; did you mean ‘u_int32_t’?
   67 | uint32_t ohash_interval(const char *, const char **);
      | ^~~~~~~~
      | u_int32_t
 To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv

             reply	other threads:[~2020-04-03  3:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03  3:14 Stephen Gregoratto [this message]
2020-04-03 10:39 ` Ingo Schwarze

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C1R8UFWVURJZ.1ZFF5RNAN6OCW@dextop.sgregoratto.me \
    --to=dev@sgregoratto.me \
    --cc=discuss@mandoc.bsd.lv \


* 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).