apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From William A Rowe Jr <wr...@rowe-clan.net>
Subject Re: -q64 flag - gets in the way
Date Mon, 04 Dec 2017 02:56:49 GMT
On Dec 3, 2017 15:09, "Michael" <aixtools@felt.demon.nl> wrote:

On 17/11/2017 13:48, Michael Felt wrote:

>
>
> On 11/13/2017 7:46 AM, William A Rowe Jr wrote:
>
>> So, when we prepare source packages, we are using vendor or raw autocruft
>> packages... Depending on which release, this varies every by a specific RM.
>>
>
Well, I was hoping to be able to dual-build (i.e., 32 and 64-bit in one
package apr and apr-util - but it seems I'll have to package the
seperately) - lots of lines (sorry) - but there are differences in include
files that would make me uncomfortable to have a dual package now. And, no
real suggestion on how to make one. So, it seems keeping the -q64 flag for
64-bit is a good idea (to prevent mixes) - and I'll just manually add -q32
to my 32-bit package.


----------

Michael,

To reiterate, if you want a change, the right way is the arch and host
flags to autoconf, and the correct translations within libtool. Further
discussion actually belongs to autoconf and libtool maintainers IMO, unless
it is our override.

My own preference is to force -q64/32 on the actual CC, LD, AR commands
etc. At that point, all autoconf choices aught to resolve correctly.

Mime
View raw message