Welcome to iraf.net Thursday, April 18 2024 @ 03:34 PM GMT


 Forum Index > Help Desk > Applications New Topic Post Reply
 guiapps segmentation violation on macosx
   
sirmarcos
 02/05/2007 07:10PM (Read 4523 times)  
++---
Junior

Status: offline


Registered: 12/05/2005
Posts: 32
Hello,I tried the pre-compiled binaries of guiapps for macosx (ppc) today and all guiapps programs produced a segmentation violation. So, I then tried to rebuild them binaries from the source and several errors occured, and no x_spectool.e gets created... it fact no .e files of any kind get made.Let's see, it looks like it's complaining about some header files in hlib$libc/includes missing in sptarith.x, and sptcolon.x, and many other .x files.The biggest error seems to be[code:1:bf0de1d587]
/usr/bin/ld can't locate file for -lsmw
[/code:1:bf0de1d587]And some other linking errors for other parts of guiapps. Any ideas anyone? I can post the complete spool file if that helps.I'm on a PPC mac running IRAF 2.13BETA2, MacOS X 10.4.8, the latest xcode, and the latest guiapps source from iraf.net in the external directory.As an aside, the guiapp pre-compiled binaries worked fine for my Macintel machine.

The re-born Mac IRAF web site: http://macsingularity.org
 
Profile Email Website
 Quote
fitz
 02/05/2007 07:10PM  
AAAAA
Admin

Status: offline


Registered: 09/30/2005
Posts: 4040
The 'smw' library comes from ONEDSPEC and should be in the noao$lib directory as a symlink to "../bin/libsmw.a". Be sure you have IRAFARCH set in your environment (to 'macosx') for cpmpilation, and try adding a "-p noao" to the mkpkg command for guiapps to pick up the NOAO package environment. I haven't looked at the GUIAPPS stuff in a while but can supply new ppc binaries if there's a problem.Cheers,
-Mike

 
Profile Email
 Quote
sirmarcos
 02/05/2007 07:10PM  
++---
Junior

Status: offline


Registered: 12/05/2005
Posts: 32
Well, setting the IRAFARCH and/or setting the -p noao flag did it. I was logging in as the IRAF user which I just assumed would set IRAFARCH but it didn't seem to...One weird error remained - the mkpkg command moves the *.e files to the appropriate bin directory... well for whatever reason guibin$ wasn't set properly or working.Instead of putting them in bin.macosx it renamed the files appending guibin to the front so I had a file named guiappsx_spectool.e in the spt/ source directory and not named x_spectool.e in bin.macosx.But, a few manual mv commands later and everything was working.

The re-born Mac IRAF web site: http://macsingularity.org
 
Profile Email Website
 Quote
fitz
 02/05/2007 07:10PM  
AAAAA
Admin

Status: offline


Registered: 09/30/2005
Posts: 4040
Ahh, then you also forgot the "-p guiapps" flag. In general, external package must always be compiled with at least "mkpkg -p <pkgname>". Some packages will automatically load other environments by adding more -p flags, a good catch-all command is "mkpkg -p <pkg> -p noao -p tables".-Mike

 
Profile Email
 Quote
sirmarcos
 02/05/2007 07:10PM  
++---
Junior

Status: offline


Registered: 12/05/2005
Posts: 32
Well, you learn something new every day. Most external package instructions I end up compiling just say do mkpkg update >& spool (after first doing a mkpkg macosx or what have you), so that's all I usually do.After all this, a PPC guiapps installer should be on Macsingularity soon...

The re-born Mac IRAF web site: http://macsingularity.org
 
Profile Email Website
 Quote
   
Content generated in: 0.18 seconds
New Topic Post Reply

Normal Topic Normal Topic
Sticky Topic Sticky Topic
Locked Topic Locked Topic
New Post New Post
Sticky Topic W/ New Post Sticky Topic W/ New Post
Locked Topic W/ New Post Locked Topic W/ New Post
View Anonymous Posts 
Anonymous users can post 
Filtered HTML Allowed 
Censored Content 
dog allergies remedies cialis 20 mg chilblain remedies


Privacy Policy
Terms of Use

User Functions

Login