On Sep 01 12:12:11, eg...@gwmail.gwu.edu wrote:
> So I was going thru my drafts folder and found this unsent message in
> it from a few years ago; much of it may no longer be relevant now that
> MacPorts has already added interactivity, but I figured I might as
> well send this anyways for the arch
Hi,
After upgrading ports on 10.6 (I probably didn't touch the machine
since about May this year) I ran into issue compiling software with
clang-5.0 against libc++:
/usr/bin/ranlib: object: .libs/libfoo.a(libfoo_la-bar-file.o)
malformed object (unknown load command 2)
ar: internal ranlib command
Hi,
I’ve seen similar in the past, and it normal results when the compiler used is
too new for the toolkit you are using (for ar etc.) and is generating code the
assembler cannot understand.
Do you have cctools installed ? Try updating your build to use the toolkit that
provides instead.
Chri
> After upgrading ports on 10.6 (I probably didn't touch the machine since
> about May this year) I ran into issue compiling software with clang-5.0
> against libc++:
/usr/bin/ranlib: object: .libs/libfoo.a(libfoo_la-bar-file.o)
malformed object (unknown load command 2)
ar: internal ranlib comman
On 2018-09-03, at 3:54 AM, Jan Stary wrote:
>> - after running `selfupdate`, MacPorts could ask the user if they
>> next want to upgradeall their outdated ports.
>
> No. This insistence on the latest bugs is a disease.
> I want the version I have, which I know to work, unless I have
> a re
Hi,
On Mon, 3 Sep 2018 at 21:51, Christopher Jones wrote:
>
> Hi,
>
> I’ve seen similar in the past, and it normal results when the compiler used
> is too new for the toolkit you are using (for ar etc.) and is generating code
> the assembler cannot understand.
>
> Do you have cctools installed ?
