[MacPorts] #50686: py-psutil 4.0.0 does not build on a PPC
MacPorts
noreply at macports.org
Mon Feb 22 07:27:05 PST 2016
#50686: py-psutil 4.0.0 does not build on a PPC
--------------------------+------------------------
Reporter: drjesacco@… | Owner: stromnov@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.3.4
Resolution: | Keywords: powerpc
Port: py-psutil |
--------------------------+------------------------
Description changed by mf2k@…:
Old description:
> Programming a PPC-based Mac is akin to riding a dead horse. Conventional
> wisdom suggests the best strategy when you discover you are riding a dead
> horse is to dismount. Still, we persist... :-)
>
> The culprit file is psutil/_psutil_osx.c. If this file is replaced with
> its predecessor from version 3.4.2, the module builds, albeit with some
> minor complaints.
>
> The compiler errors are shown below.
>
> -Joseph
>
> /usr/bin/gcc-4.2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -arch
> ppc -DPSUTIL_VERSION=400
> -I/opt/local/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7
> -c psutil/_psutil_osx.c -o
> build/temp.macosx-10.5-ppc-2.7/psutil/_psutil_osx.o
> psutil/_psutil_osx.c: In function âpsutil_proc_memory_mapsâ:
> psutil/_psutil_osx.c:351: warning: format â%016lxâ expects type
> âlong unsigned intâ, but argument 3 has type âvm_address_tâ
> psutil/_psutil_osx.c:351: warning: format â%016lxâ expects type
> âlong unsigned intâ, but argument 4 has type âvm_address_tâ
> psutil/_psutil_osx.c: In function âpsutil_proc_memory_ussâ:
> psutil/_psutil_osx.c:603: error: âforâ loop initial declaration used
> outside C99 mode
> psutil/_psutil_osx.c:624: error: âSM_LARGE_PAGEâ undeclared (first
> use in this function)
> psutil/_psutil_osx.c:624: error: (Each undeclared identifier is reported
> only once
> psutil/_psutil_osx.c:624: error: for each function it appears in.)
> error: command '/usr/bin/gcc-4.2' failed with exit status 1
New description:
Programming a PPC-based Mac is akin to riding a dead horse. Conventional
wisdom suggests the best strategy when you discover you are riding a dead
horse is to dismount. Still, we persist... :-)
The culprit file is psutil/_psutil_osx.c. If this file is replaced with
its predecessor from version 3.4.2, the module builds, albeit with some
minor complaints.
The compiler errors are shown below.
-Joseph
{{{
/usr/bin/gcc-4.2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -arch
ppc -DPSUTIL_VERSION=400
-I/opt/local/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7
-c psutil/_psutil_osx.c -o
build/temp.macosx-10.5-ppc-2.7/psutil/_psutil_osx.o
psutil/_psutil_osx.c: In function âpsutil_proc_memory_mapsâ:
psutil/_psutil_osx.c:351: warning: format â%016lxâ expects type
âlong unsigned intâ, but argument 3 has type âvm_address_tâ
psutil/_psutil_osx.c:351: warning: format â%016lxâ expects type
âlong unsigned intâ, but argument 4 has type âvm_address_tâ
psutil/_psutil_osx.c: In function âpsutil_proc_memory_ussâ:
psutil/_psutil_osx.c:603: error: âforâ loop initial declaration used
outside C99 mode
psutil/_psutil_osx.c:624: error: âSM_LARGE_PAGEâ undeclared (first use
in this function)
psutil/_psutil_osx.c:624: error: (Each undeclared identifier is reported
only once
psutil/_psutil_osx.c:624: error: for each function it appears in.)
error: command '/usr/bin/gcc-4.2' failed with exit status 1
}}}
--
--
Ticket URL: <https://trac.macports.org/ticket/50686#comment:2>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list