"Alexey L. Tcharykov" wrote:
>
> Emile,
>
> E> Any existing FreeBSD users, this is the time to pitch in
> E> with either success- or horrorstories.
>
> I still have problems with installing Midgard on FreeBSD 2.2.8.
> Alexander has all needed information about this case -- looks like
> something wrong with ldconfig and libs.
> You know, ldconfig in FreeBSD is not the same as in Linux.
The only place I've found that uses ldconfig is the data package (where
it is indeed linux-centric).
I installed a fresh copy of freebsd4.0.
I installed glib from the ports collection. The glib ports maintainer,
in his/her infinite wisdom, renamed glib-config to glib12-config.
Furrfu.
# ln -s /usr/local/bin/glib12-config /usr/local/bin/glibconfig
You need gmake, and I've found it convenient to
$ export MAKE=gmake
before anything else, and use gmake everywhere you would normally use
make.
** expat
Nothing weird
** lib
After all has been installed
# ldconfig -m /usr/local/lib
** mod
$ ./configure --with-midgard=/usr/local
I'll fix this in configure
** php:
php: ./configure --with-midgard=/usr/local --with-mysql
--with-apxs=`which apxs`
I'll fix the --with-midgard=/usr/local in configure so it will look for
/usr/local
by itself
** data:
Change the ldconfig line to
LIBMIDGARD=`/sbin/ldconfig -r | grep libmidgard.so | awk '{ print $3;
}' | tail -1`
The best way to handle this transparently is to ship midgard-data with a
small C source
that we'll compile and have query these values. This should also handle
the situation
where people do not have a shared libmidgard.
That was it. I have a fully functioning Midgard running on FreeBSD 4.0
right here.
Emile
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
