> Why would a universal library be incompatible with building for a single
> arch? What is the actual failing command?
>
>
I went through the old travis builds again. it was because I added arch
flags to a variable named `CFLAFS` which being a typo never got added to
CFLAGS.
The issue is now
On 2020-2-10 09:44 , Mihir Luthra wrote:
> Hi,
>
> Creating a static library from fat object files works fine as long as
> there's an index. That means using the -s option with ar, or running
> ranlib after creation. The usual command is "ar crs .a *.o".
>
>
> I was making a static
The first cctools update in about 14 months looks ready to commit to me. This
matches Xcode 10.2, and is the last one Apple has released so far.
As a core component of macOS and MacPorts, touching almost every system, I
would appreciate anyone interested to give this a review, try to break it,
Hi,
Creating a static library from fat object files works fine as long as
> there's an index. That means using the -s option with ar, or running
> ranlib after creation. The usual command is "ar crs .a *.o".
>
>
I was making a static lib that can be used by both darwintracelib1.0 and
pextlib1.0.
