Opened 16 years ago

Closed 14 years ago

#13148 closed defect (fixed)

odcctools fails to build under OS X 10.5 Leopard (Intel)

Reported by: bfulgham@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.5.0
Keywords: Cc: bfulgham@…, liontooth@…, mjhsieh@…, ryandesign (Ryan Carsten Schmidt)
Port: odcctools

Description (last modified by blb@…)

Attempting to build odcctools under Leopard (OS X 10.5.0) with XCode 3.0 installed:

--->  Fetching odcctools
--->  Verifying checksum(s) for odcctools
--->  Extracting odcctools
--->  Configuring odcctools
--->  Building odcctools with target default
Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_Users_brent_Projects_macports-trunk_dports_devel_odcctools/work/odcctools/odcctools" && make default " returned error 2
Command output: cd libstuff && make
gcc -Wall -Wno-long-double -Wno-import  -DHAVE_CONFIG_H   -I/opt/local/include -I../include -I../include   -O2 -fno-builtin-round -fno-builtin-trunc -no-cpp-precomp -mdynamic-no-pic  -c -o allocate.o allocate.c
In file included from ../include/libkern/OSByteOrder.h:70,
                 from ../include/mach/ndr.h:94,
                 from ../include/mach/clock_priv.h:7,
                 from ../include/mach/mach_interface.h:37,
                 from ../include/mach/mach.h:62,
                 from allocate.c:26:
../include/libkern/machine/OSByteOrder.h:45: error: redefinition of '_OSSwapInt16'
/usr/include/libkern/i386/_OSByteOrder.h:49: error: previous definition of '_OSSwapInt16' was here
../include/libkern/machine/OSByteOrder.h:54: error: redefinition of '_OSSwapInt32'
/usr/include/libkern/i386/_OSByteOrder.h:58: error: previous definition of '_OSSwapInt32' was here
../include/libkern/machine/OSByteOrder.h:63: error: redefinition of '_OSSwapInt64'
/usr/include/libkern/i386/_OSByteOrder.h:69: error: previous definition of '_OSSwapInt64' was here
make[1]: *** [allocate.o] Error 1
make: *** [libstuff] Error 2

This probably occurred with gcc 4.0.1, as that seems to be the default selection.

Change History (10)

comment:1 Changed 16 years ago by nox@…

Cc: bfulgham@… added
Milestone: Port Bugs
Summary: odcctools fails to build under Leopard (Intel)odcctools fails to build under OS X 10.5 Leopard (Intel)

comment:2 Changed 16 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: liontooth@… added

Has duplicate #13489.

comment:3 Changed 15 years ago by blb@…

Description: modified (diff)
Port: odcctools added

Is the odcctools project still alive? The homepage at http://odcctools.macosforge.org/ gives an error and looking at its subversion repo, the changelog hasn't been updated in a couple of years...

comment:4 Changed 15 years ago by (none)

Milestone: Port Bugs

Milestone Port Bugs deleted

comment:5 Changed 15 years ago by mjhsieh@…

There seems to be a newer version at http://pogma.com/2009/08/08/odcctools-20090808/ ...

comment:6 Changed 14 years ago by mjhsieh@…

Cc: mjhsieh@… added

Cc Me!

comment:7 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added

Thanks for the tip, I updated odcctools to version 20090808 in r67362. Could someone with Leopard on Intel test to see if it now works? It builds now for me on Tiger i386 and Leopard ppc.

comment:8 in reply to:  7 Changed 14 years ago by dmitrij.ledkov@…

Replying to ryandesign@…:

Thanks for the tip, I updated odcctools to version 20090808 in r67362. Could someone with Leopard on Intel test to see if it now works? It builds now for me on Tiger i386 and Leopard ppc.

Confirming builds fine: Snow Leopard Intel i386

comment:9 in reply to:  7 Changed 14 years ago by mjhsieh@…

Replying to ryandesign@…:

Thanks for the tip, I updated odcctools to version 20090808 in r67362. Could someone with Leopard on Intel test to see if it now works? It builds now for me on Tiger i386 and Leopard ppc.

Leopard on Intel builds and I was able to build gcc42 +odcctools without problem.

comment:10 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: fixed
Status: newclosed

Thanks, then we'll call it fixed.

Note: See TracTickets for help on using tickets.