pcp
[Top] [All Lists]

Re: [pcp] compilation warnings on Mac OS X

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] compilation warnings on Mac OS X
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Wed, 8 Oct 2014 00:02:32 -0400 (EDT)
Cc: PCP <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <5434B54D.1030401@xxxxxxxxxxxxxxxx>
References: <5434B54D.1030401@xxxxxxxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: AoyEeu8cT16UyfDJdvB/OzP1Pdg/Nw==
Thread-topic: compilation warnings on Mac OS X

----- Original Message -----
> I'm just getting my steam powered iMac back into QA harness.

(is that an old PowerPC or any x86 model - the latter I think?)

> Does this look familiar to anyone?
> 

Yep...

> fuji:pcp kenj$ grep -i warning Logs/pcp
> ld: warning: directory '../libpcp_qed/src/build/release' following -L not
> found

These ones should be safe to ignore; they flow from platform differences
between the generated makefiles, and the various debug/release builds on
each being in different places IIRC.

> ld: warning: in ../../src/libpcp/src/libpcp.dylib, missing required
> architecture ppc in file

This will be qmake trying to build "universal binaries" for the GUI tools
(i.e. containing both PPC and x86 code in the one binary) but we no longer
build libpcp that way - tossed sometime back, and we build only x86 now.

There may be qmake mechanisms to make it build GUI tools only for x86...?
Or we could start building universal binaries in PCP again (IIRC, that'd
involve using multiple -arch invocations in CFLAGS - but I don't think we
have any users on PowerPC Macs anymore).

cheers.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>