On Sep 2, 2008, at 10:52 AM, Tom Russo wrote:
On Tue, Sep 02, 2008 at 10:17:08AM -0500, we recorded a bogon-
computron collision of the <[EMAIL PROTECTED]> flavor, containing:
Thanks Curt,
I guess I'm going to have to wait for Apple to update OpenMotif
internally because no matter what I do, Xastir compiles with v2.3.0.
Are you absolutely sure you're running the same binary that you're
compiling?
This sounds suspiciously like there's a binary in some path other
than the
one you're installing to (perhaps /sw/bin/xastir?). Perhaps this
was installed
by a packaged binary and was never uninstalled?
Try typing this in a shell:
type -a xastir
this will list all the copies of Xastir that appear in your path.
When you're
building from source, the binary will go to /usr/local/bin unless
you've
specified "--prefix=..." to tell it to go elsewhere.
If you've got more than one answer to "type -a xastir" then you need
to get
rid of the others somehow.
If you've uninstalled motif 2.3.0 and it keeps coming up with that
version,
there's something very fishy going on and an old binary seems the
likely
culprit.
--
Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/
Tijeras, NM QRPL#1592 K2#398 SOC#236 AHTB#1 http://kevan.org/brain.cgi?DDTNM
"Argue for your limitations and sure enough, they're yours." -- R.
Bach
_______________________________________________
Xastir mailing list
[email protected]
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Tom I think you're on to something here;
$type -a xastir
xastir is /usr/bin/xastir
xastir is /usr/local/bin/xastir
I just deleted the /usr/bin/xastir, but heres the thing, I know there
is also one in /sw/bin how come that one didn't show up? Then I did a
recompile of Xastir making sure it went to /usr/local/bin but it still
says it's using 2.3.0 of OpenMotif
_______________________________________________
Xastir mailing list
[email protected]
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
