[Paraview] ParaView 2.4 on Mac OS 10.4, PowerPC

Fri Jul 7 21:29:14 EDT 2006

on 7/7/06 4:01 PM, Chad Glendenin at chad at uchicago.edu wrote:

> Thank you for sharing the linker trick! I was able to build ParaView
> 2.4.4 with GCC 3.3 and with GCC 4.0 on Mac OS X 10.4.7 on a G4, and
> both binaries are working perfectly so far. I think I remember trying
> those linker settings a few months ago and only getting a segfault,
> but I must have been making some other mistake.
> 
> ccg
Chad,

Apple usually breaks OS X for open source builds during its major upgrades.
By about 10.x.6, open source builds start to work again. This is because
both Apple and the open source developers work on the libraries, make files,
etc. 

Watch out when OS X 10.5.0 appears. This has held true for 10.2 => 10.3 and
10.3 => 10.4 in my experience. I think Apple is listening, but they never
say so.

Joe 

> 
> On Jul 6, 2006, at 11:34 PM, Rick Wagner wrote:
> 
>> 
>> On Jul 6, 2006, at 7:46 PM, Mike Jackson wrote:
>> 
>>> 
>>> 
>>> 
>>> On Jul 6, 2006, at 10:33 PM, Randy Hudson wrote:
>>> 
>>>> 
>>>> Mike,
>>>> 
>>>> I have built paraview 2.4.3 on my Intel Mac (just so the record's
>>>> complete), and it does not seg fault.  (Or, it might've the first
>>>> time I ran it, but it has worked fine since.)
>>>> 
>>>> But, if I'm the only one in the galaxy who's been able to do
>>>> that, your claim that it's a non-starter is still true.
>>>> 
>>>> 
>>>> Mike Jackson wrote:
>>>>> 
>>>>> 
>>>>> Um.. actually it is the other way around. Paraview is a non-
>>>>> starter on Intel Macs. It compiles and then segfaults.
>>>>> 
>>>>> --------
>>>>> Mike Jackson
>>>>> imikejackson <at> gmail <dot> com
>>>>> 
>>>>> _______________________________________________
>>>> -- 
>>>> 
>>>> 
>>>> Randy.
>>> 
>>> 
>>> Either send me your CMakeCache file or send me the binaries... If
>>> they work I will offer a public apology.. until then I stand by
>>> what I have found.
>>> 
>>>    Also, what hardware are you running? I am running OS X 10.4.6/7
>>> on a MacBook PRO.
>>> 
>>> --------
>>> Mike Jackson
>>> imikejackson <at> gmail <dot> com
>>> 
>>> 
>>> _______________________________________________
>>> ParaView mailing list
>>> ParaView at paraview.org
>>> http://www.paraview.org/mailman/listinfo/paraview
>> 
>> 
>> Hi Mike,
>> 
>> Try this CMakeCache.txt, it's the result of some advice I received
>> when I was try to build ParaView. The post must of been off of the
>> mailing list. Hopefully I remembered to thank Ivan. (His message is
>> at the bottom of this one.)
>> 
>> --Rick
>> 
>> <CMakeCache.txt>
>> 
>> Some info on my PowerBook.
>> 
>> Hardware Overview:
>> 
>>   Machine Name: PowerBook G4 15"
>>   Machine Model: PowerBook5,8
>>   CPU Type: PowerPC G4 (1.5)
>>   Number Of CPUs: 1
>>   CPU Speed: 1.67 GHz
>>   L2 Cache (per CPU): 512 KB
>>   Memory: 1 GB
>>   Bus Speed: 167 MHz
>>   Boot ROM Version: 4.9.6f0
>>   Serial Number: W86051UKSWZ
>>   Sudden Motion Sensor:
>>   State: Enabled
>> 
>> System Software Overview:
>> 
>>   System Version: Mac OS X 10.4.6 (8I127)
>>   Kernel Version: Darwin 8.6.0
>>   Boot Volume: Macintosh HD
>>   Computer Name: cable
>>   User Name: Rick Wagner (rpwagner)
>> 
>> 
>> /********** original message from Ivan *************/
>> 
>> 
>> From:    guajanai at student.ethz.ch
>> Subject:  Re: [Paraview] ParaView 2.4.3 and OS X 10.4.6 - Build
>> Problems
>> Date:  April 27, 2006 2:56:22 AM PDT
>> To:    guardian72 at guardian72.com
>> 
>> Hi Rick,
>> I used to have similar problems as I tried to compile ParaView form
>> my MacBook. The solution was to  set both CMAKE_EXE_LINKER_FLAGS
>> and CMAKE_SHARED_LINKER_FLAGS to
>> -Wl,-serch_paths_first .
>> By default paraview was linked against the wrong ones. Here's a
>> quote from my own thread in this mailing list as I had the
>> compiling problems:
>> 
>> 
>>> Success! Everything seems to work fine now (although I use
>>> just a very small subset of paraview's capabilities).
>>> 
>>> I had to to the following, in case someone faces the same problems:
>>> 
>>> - disable VTK_USE_CARBON, VTK_USE_COCOA and enable VTK_USE_USE_X
>>> (see this FAQ entry:
>>> http://www.paraview.org/Wiki/
>>> ParaView:FAQ#How_do_I_compile_ParaView_for_Mac_OS_X.3F)
>>> 
>>> - make sure that cmake is using the OpenGL implementation found
>>> in /usr/X11R6/lib
>>> (both libGL and libGLU) and the headers in /usr/X11R6/include/
>>> 
>>> - set ALL the CMAKE_EXE_LINKER_FLAGS* and
>>> CMAKE_SHARED_LINKER_FLAGS* (just
>>> to be sure) to -Wl,-search_paths_first
>>> 
>>> - run make
>>> 
>>> I'd like to thank Kenneth Moreland for his invaluable help with
>>> this issue!
>>> 
>>> Ivan Guajana
>>> 
>> 
>> I hope this helps,,
>> 
>> Ivan
>> 
>> 
>> On 20/apr/06, at 23:23, Rick Wagner wrote:
>> 
>> 
>>> Hi,
>>> 
>>> I've just built ParaView 2.4.3 on my G4 PowerBook running OS X
>>> 10.4.6, using the instructions from the wiki: BUILD_SHARED_LIBS
>>> ON; VTK_USE_CARBON_OFF; VTK_USE_X ON. I used gcc4.0 and CMake 2.2.3.
>>> 
>>> The build chugs along and finishes, but when I try to run the
>>> paraview executable, I get a segmentation fault. This also happens
>>> if I try to run pvclient and connect to pvserver. The server
>>> process starts up, but when paraview or pvclient display "Creating
>>> UI (main view)...", they crash. I've tried running from both the
>>> build directory and doing an install.
>>> 
>>> This seems similar to other postings I've seen, does anyone have a
>>> suggestion as to how I should go about debugging this?
>>> 
>>> Thanks,
>>> Rick
>>> _______________________________________________
>>> ParaView mailing list
>>> ParaView at paraview.org
>>> http://www.paraview.org/mailman/listinfo/paraview
>>> 
>> 
>> 
>> _______________________________________________
>> ParaView mailing list
>> ParaView at paraview.org
>> http://www.paraview.org/mailman/listinfo/paraview
> 
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview