From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Cc: Marco Atzeri <marco.atzeri@gmail.com>
Subject: Re: type mismatch on cpuset.h
Date: Mon, 6 Mar 2023 01:14:34 -0800 (PST) [thread overview]
Message-ID: <Pine.BSF.4.63.2303060113390.23629@m0.truegem.net> (raw)
In-Reply-To: <ZAWqmGwaqbDtwNF8@calimero.vinschen.de>
Hi Corinna, Marco,
I will look into this shortly. Sorry for the inconvenience.
..mark
On Mon, 6 Mar 2023, Corinna Vinschen wrote:
> Hi Mark,
>
> On Mar 6 07:57, Marco Atzeri via Cygwin wrote:
>> Hi,
>>
>> building latest gdal I noticed a type mismatch, that forced me to build
>> with "-fpermissive"
>>
>> on /usr/include/sys/cpuset.h
>>
>> #define CPU_ALLOC(num) __builtin_malloc (CPU_ALLOC_SIZE(num))
>>
>>
>> but on
>> https://linux.die.net/man/3/cpu_alloc
>>
>> cpu_set_t *CPU_ALLOC(int num_cpus)
>>
>>
>> so void* versus cpu_set_t*
>
> Marco is correct. cpuset.h was your pet project a while back. Would
> you like to pick it up? Maybe we should convert all the macros into
> type-safe inline functions, or macros calling type-safe (inline)
> functions, as on Linux as well as on BSD?
>
>
> Thanks,
> Corinna
prev parent reply other threads:[~2023-03-06 9:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 6:57 Marco Atzeri
2023-03-06 8:55 ` Corinna Vinschen
2023-03-06 9:14 ` Mark Geisert [this message]
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=Pine.BSF.4.63.2303060113390.23629@m0.truegem.net \
--to=mark@maxrnd.com \
--cc=cygwin@cygwin.com \
--cc=marco.atzeri@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).