Fwd: ORBit not upgrading

Da Rock freebsd-questions at herveybayaustralia.com.au
Sat Nov 20 08:41:49 UTC 2010

Ok. So this is not just an upgrade issue, I can't build it on a fresh 
install on another m/c either. Any fixes/workarounds? Is anyone aware of 
this issue?

I'm afraid I'm not experienced enough to work this out- unless someone 
can explain what the check is?


-------- Original Message --------
Subject: 	ORBit not upgrading
Date: 	Wed, 10 Nov 2010 15:09:04 +1100
From: 	freebsd-questions at herveybayaustralia.com.au
Reply-To: 	freebsd-questions at herveybayaustralia.com.au
To: 	<freebsd-questions at freebsd.org>

	I have a wee problem... :) I've been naughty because I've been
working on other things and I was going to simply rebuild this m/c
when I got the chance anyway. Unfortunately I've run into a problem
where I need to upgrade because I've found a bug in php 5.3.2 which is
killing me. So I've run an upgrade at a rather late date, and
alswell... except ORBit is not behaving.
	I've checked UPDATING and looked into the Makefiles, but for the life
of me I can't fathom what the hell is going on. It is running thru the
checks and stalls completely here:

	checking for a BSD compatible install... /usr/bin/install -c -o root
-g wheel
checking whether build environment is sane... yes
checking whether gmake sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking for gcc... cc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for executable suffix...
checking for object suffix... o
checking whether we are using the GNU C compiler... yes
checking whether cc accepts -g... yes
checking for strerror in -lcposix... no
checking for gcc... (cached) cc
checking whether we are using the GNU C compiler... (cached) yes
checking whether cc accepts -g... (cached) yes
checking how to run the C preprocessor... cpp
checking if C preprocessor likes IDL... yes
checking if C preprocessor can read from stdin... yes
checking how to ignore standard include path...
	Huh? Any reason it'd be looking for a non standard include path?
Whats the hold up?
	Now this is ORBit-0.5.17_5, and I don't think a manual reinstall
would make much difference. But WTF? Any Ideas?
	As for the php error: anybody have trouble with preg_match and the
subject string being a variable? If I manually put the contents in as
the subject it works, but it won't read out of the variable. I'm
actually exec something and the variable holds the output (and yes, it
does work, and the variable holds the info right- just ran a print on
the variable) but the stupid thing is sending me bald and I can't
register a bug before an upgrade.

Message sent via Atmail Open - http://atmail.org/
freebsd-questions at freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"

More information about the freebsd-questions mailing list