Opened 12 years ago

Closed 12 years ago

#17333 closed defect (wontfix)

cmake 2.6.2 build failure on Mac OS X 10.3.9 Panther

Reported by: ryandesign (Ryan Schmidt) Owned by: cssdev
Priority: Normal Milestone:
Component: ports Version: 1.6.0
Keywords: panther Cc:
Port: cmake

Description

cmake 2.6.2 doesn't build for me, on a Power Mac G4 with Mac OS X 10.3.9 and Xcode 1.5:

--->  Fetching cmake
--->  Verifying checksum(s) for cmake
--->  Extracting cmake
--->  Configuring cmake
--->  Building cmake
Error: Target org.macports.build returned: shell command " cd "/mp/var/macports/build/_Volumes_data_macports_ports_devel_cmake/work/cmake-2.6.2" && nice -n 10 make all " returned error 2
Command output: [ 55%] Building C object Source/CursesDialog/form/CMakeFiles/cmForm.dir/fty_num.o
[ 55%] Building C object Source/CursesDialog/form/CMakeFiles/cmForm.dir/fty_regex.o
Linking C static library libcmForm.a
[ 55%] Built target cmForm
Scanning dependencies of target CMakeLib
[ 55%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmBootstrapCommands.o
[ 55%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmCacheManager.o
[ 56%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmCommands.o
[ 56%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmCommandArgumentLexer.o
[ 56%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmCommandArgumentParser.o
[ 57%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmCommandArgumentParserHelper.o
[ 57%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmComputeComponentGraph.o
[ 57%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmComputeLinkDepends.o
[ 58%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmComputeLinkInformation.o
[ 58%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmComputeTargetDepends.o
[ 58%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmCustomCommand.o
[ 59%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDepends.o
[ 59%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDependsC.o
[ 59%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDependsFortran.o
[ 60%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDependsFortranLexer.o
[ 60%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDependsFortranParser.o
[ 60%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDependsJava.o
[ 61%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDependsJavaLexer.o
[ 61%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDependsJavaParser.o
*** malloc_zone_malloc[5824]: argument too large: 3609800964

cc1plus: out of memory allocating 3609800964 bytes after a total of 0 bytes
make[2]: *** [Source/CMakeFiles/CMakeLib.dir/cmDependsJavaParser.o] Error 1
make[1]: *** [Source/CMakeFiles/CMakeLib.dir/all] Error 2
make: *** [all] Error 2

Error: Status 1 encountered during processing.
elapsed: 03:31:26

The same version of cmake builds just fine on Tiger and Leopard on the same Power Mac, and also on my Intel Mac.

I don't see an upstream bug report for this, but I do see other issues about Panther support, some of which have been fixed, so they seem to have an interest in still supporting Panther.

Attachments (2)

CMakeCache.txt (41.7 KB) - added by ryandesign (Ryan Schmidt) 12 years ago.
CMakeCache-comparison.diff (14.4 KB) - added by cssdev 12 years ago.
comparison between the 10.3 cache and my 10.5.6 cache

Download all attachments as: .zip

Change History (16)

comment:1 Changed 12 years ago by cssdev

Status: newassigned

I have no access to a Panther machine, so it's going to be hard to track down.

A verbose build might show more information, I'll have to dig out the sources see which flags are needed. I could give you a patch that would at least output more information during the build process. Which specific version of gcc are you using?

comment:2 in reply to:  1 Changed 12 years ago by ryandesign (Ryan Schmidt)

Replying to css@…:

I have no access to a Panther machine, so it's going to be hard to track down.

I can give you shell access to my G4 if you want, but it's 466 MHz so it takes 3.5 hours to reach the problem with cmake. I'm sure it would be rather infuriating.

A verbose build might show more information, I'll have to dig out the sources see which flags are needed. I could give you a patch that would at least output more information during the build process. Which specific version of gcc are you using?

Unfortunately verbose mode is broken on Panther; I don't know why. I can try building it by hand, outside of MacPorts, to get more output. I'm using "gcc version 3.3 20030304 (Apple Computer, Inc. build 1666)". AFAIK that's the latest Apple provides for Panther.

comment:3 Changed 12 years ago by cssdev

Please try this:

sudo port -o extract cmake
cd [cmake worksrcpath]
sudo ./configure
sudo make VERBOSE=1

This will build CMake using a verbose mode that shows full build output.

comment:4 Changed 12 years ago by ryandesign (Ryan Schmidt)

Hmm. It builds just fine outside of MacPorts, and takes less than an hour to do so.

comment:5 in reply to:  4 Changed 12 years ago by cssdev

Replying to ryandesign@…:

Hmm. It builds just fine outside of MacPorts, and takes less than an hour to do so.

Now that's certainly interesting! Could you attach the CMakeLists.txt that was created in your source? There must be something different about the configuration that makes things fail when building with the MacPorts environment.

comment:6 Changed 12 years ago by cssdev

oops, I meant to ask if you could attach CMakeCache.txt. That contains all the variables I need to check against when configured via MacPorts.

comment:7 Changed 12 years ago by cssdev

Does this issue still occur with CMake 2.6.3?

Changed 12 years ago by ryandesign (Ryan Schmidt)

Attachment: CMakeCache.txt added

comment:8 in reply to:  7 Changed 12 years ago by ryandesign (Ryan Schmidt)

Yes, it does. CMakeCache.txt is now attached.

comment:9 Changed 12 years ago by cssdev

There aren't many differences compared to the CMakeCache.txt on my MacBook Pro, but I did find a NetBSD post containing a similar error. I've never used the ulimit command, but maybe it can be used to modify something before doing the build in MacPorts? What's your output from ulimit -a? Mine for Mac OS X 10.5.6 is:

core file size          (blocks, -c) 0
data seg size           (kbytes, -d) 6144
file size               (blocks, -f) unlimited
max locked memory       (kbytes, -l) unlimited
max memory size         (kbytes, -m) unlimited
open files                      (-n) 256
pipe size            (512 bytes, -p) 1
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 266
virtual memory          (kbytes, -v) unlimited

I'm curious see what it is for Panther as well as for MacPorts sub-environments.

Changed 12 years ago by cssdev

Attachment: CMakeCache-comparison.diff added

comparison between the 10.3 cache and my 10.5.6 cache

comment:10 Changed 12 years ago by cssdev

Rainer suggested:

Ryan, when you tried compiling outside of MacPorts, did you enable the same CFLAGS? MacPorts applies -O2 to CFLAGS and CXXFLAGS by default, it could be that the bug is only experienced with optimization enabled. Try setting configure.optflags to an empty value.

Glancing at the cache, it looks like CMake doesn't set its flags, but it is possible that it's inheriting them from the shell. Could you try Rainer's suggestion?

comment:11 Changed 12 years ago by (none)

Milestone: Port Bugs

Milestone Port Bugs deleted

comment:12 Changed 12 years ago by tobypeterson

Keywords: panther added

comment:13 Changed 12 years ago by tobypeterson

Resolution: wontfix

panther is dead

comment:14 Changed 12 years ago by tobypeterson

Status: assignedclosed
Note: See TracTickets for help on using tickets.