[ADMB Users] Fwd: Re: macos weird install

[Johnoel Ancheta]

-------- Original Message --------
Subject: 	Re: [ADMB Users] macos weird install
Date: 	Thu, 30 Jun 2011 13:29:27 -1000
From: 	Johnoel Ancheta <johnoel at hawaii.edu>
To: 	jbrandon at gmail.com



$ cp -R /usr/local/admb/examples/admb/simple ~/simple
$ cd ~/simple
$ admb simple
$ ./simple

On 6/30/11 1:02 PM, John Brandon wrote:
> Hi All,
>
> Following up on this thread: I've been having some trouble compiling 
> *.tpl files on MacOS 10.6.7, Xcode 3.2.6 (the machine came with Xcode 
> 4 installed, but I installed v.3.2 following ADMB install documentation).
>
> I've installed ADMB 10.0 (64bit for MacOS) and I can type the 'admb' 
> command at the prompt and see the usage options.
>
> However, when I try to compile 'simple.tpl' by typing 'admb simple' 
> (from the directory: .../examples/admb/simple) I get the following 
> error message:
>
> "
> *** Parsing: tpl2cpp simple
> Error trying to open file xxhtop.tmp
> Error trying to open file xxglobal.tmp
> Error trying to open file simple.htp
> Error trying to open file xxalloc.tmp
> /usr/local/admb/bin/admb: line 64:  8137 Segmentation fault      
> tpl2cpp simple
>
> Error: Failed to build executable.
> "
>
> Does this look familiar to anyone? I've looked through all 
> documentation and the threads I could find online, but haven't been 
> able to find an example like this and am now stumped. I'd be happy to 
> provide more information if needed. Any ideas appreciated.
>
> Thanks,
> John Brandon
>
> PS: Here's what I get when I type the 'set' command (with .../admb/bin 
> added to PATH).
>
> ADMB_HOME=/usr/local/admb
> Apple_PubSub_Socket_Render=/tmp/launch-k7pxh0/Render
> BASH=/bin/bash
> BASH_ARGC=()
> BASH_ARGV=()
> BASH_LINENO=()
> BASH_SOURCE=()
> BASH_VERSINFO=([0]="3" [1]="2" [2]="48" [3]="1" [4]="release" 
> [5]="x86_64-apple-darwin10.0")
> BASH_VERSION='3.2.48(1)-release'
> COLUMNS=117
> COMMAND_MODE=unix2003
> DIRSTACK=()
> DISPLAY=/tmp/launch-BjDWdl/org.x:0
> EUID=501
> GROUPS=()
> HISTFILE=/Users/johnbrandon/.bash_history
> HISTFILESIZE=500
> HISTSIZE=500
> HOME=/Users/johnbrandon
> HOSTNAME=John-Brandons-MacBook-Pro.local
> HOSTTYPE=x86_64
> IFS=$' \t\n'
> LANG=en_US.UTF-8
> LINES=61
> LOGNAME=johnbrandon
> MACHTYPE=x86_64-apple-darwin10.0
> MAILCHECK=60
> OLDPWD=/Users/johnbrandon
> OPTERR=1
> OPTIND=1
> OSTYPE=darwin10.0
> PATH=/usr/local/admb/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin 
>
> PIPESTATUS=([0]="0")
> PPID=8314
> PS1='\h:\W \u\$ '
> PS2='> '
> PS4='+ '
> PWD=/usr/local/admb/examples/admb/simple
> SHELL=/bin/bash
> SHELLOPTS=braceexpand:emacs:hashall:histexpand:history:interactive-comments:monitor 
>
> SHLVL=1
> SSH_AUTH_SOCK=/tmp/launch-MMbOnL/Listeners
> TERM=xterm-color
> TERM_PROGRAM=Apple_Terminal
> TERM_PROGRAM_VERSION=273.1
> TMPDIR=/var/folders/0l/0l8ZAOWKEVe5r8btcKMQg++++TI/-Tmp-/
> UID=501
> USER=johnbrandon
> _=simple
> __CF_USER_TEXT_ENCODING=0x1F5:0:0
>
>
>
>
>
> On 6/30/2011 10:46 AM, John Sibert wrote:
>> Nice discussion, Mollie. You might want to export ADMB_HOME though
>>
>> It is possible to have multiple copies of ADMB installed on a single 
>> computer. It is not really necessary to install in /urs/local. It can 
>> be installed anywhere, eg ~/myadmb. All you need to do is to set 
>> ADMB_HOME to point to the directory where it is installed.
>>
>> John
>>
>> On 06/30/2011 06:42 AM, Mollie Brooks wrote:
>>> This isn't a problem; it's more of a surprise issue that I wanted to 
>>> be sure was documented for the next person...
>>>
>>> I unknowingly had an old version of admb in /usr/local/bin that my 
>>> computer was using. I could have found this out by typing in the 
>>> terminal
>>>
>>> which admb
>>>
>>> This says where the computer goes to get admb.
>>>
>>> I noticed it the hard way when an old bug wasn't going away when I 
>>> installed the new version. I deleted all existing versions, 
>>> installed from scratch and then my computer didn't recognize the 
>>> command admb because it was looking in the wrong place.
>>>
>>> I had ADMB_HOME=/usr/local/admb and path defined in .bashrc, but the 
>>> default terminal shell window on macs doesn't read .bashrc 
>>> automatically. I had to add the info to a file .bash_profile which 
>>> does get automatically read.
>>>
>>> So if, after correctly installing, your computer doesn't recognize 
>>> the command admb, you may need to do the following in the terminal
>>>
>>> cd
>>> nano .bash_profile
>>>
>>> ADMB_HOME=/usr/local/admb
>>> export PATH=$ADMB_HOME/bin:$PATH
>>>
>>> hit Control+X then yes to save
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at admb-project.org
>>> http://lists.admb-project.org/mailman/listinfo/users
>>
>
> _______________________________________________
> Users mailing list
> Users at admb-project.org
> http://lists.admb-project.org/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.admb-project.org/pipermail/users/attachments/20110630/852835e4/attachment.html>