On 2 March 2018 at 07:15, Joshua Root wrote:
> On 2018-3-2 08:27 , Mojca Miklavec wrote:
>> On 1 March 2018 at 20:42, Michael Dickens wrote:
>>> In the past, I've handled this situation by using the muniversal PortGroup,
>>> so that the sizeof is correct for each build independent of the other. -
On 2018-3-2 08:27 , Mojca Miklavec wrote:
> On 1 March 2018 at 20:42, Michael Dickens wrote:
>> In the past, I've handled this situation by using the muniversal PortGroup,
>> so that the sizeof is correct for each build independent of the other. - MLD
>
> I'm aware of that. I was wondering if
Since the port is using GNU Autotools, AC_COMPILE_CHECK_SIZEOF will return one
of 2 values depending on which -arch flag is used / set / set first / some
random reason; it cannot return both values. Hence why using muniversal if
truly in doubt.
The best solution is to use pre-sized types such
On 1 March 2018 at 20:42, Michael Dickens wrote:
> In the past, I've handled this situation by using the muniversal PortGroup,
> so that the sizeof is correct for each build independent of the other. - MLD
I'm aware of that. I was wondering if there was some *proper* solution
that could allow
In the past, I've handled this situation by using the muniversal PortGroup, so
that the sizeof is correct for each build independent of the other. - MLD
On Thu, Mar 1, 2018, at 2:40 PM, Mojca Miklavec wrote:
> While checking some patches of a library I decided to try whether the
> library would
Hi,
While checking some patches of a library I decided to try whether the
library would build universally. The configure.ac part contains:
AC_COMPILE_CHECK_SIZEOF([long])
and that happily fails with
checking size of long... configure: error: cannot determine a size for long
when
