PlaneShift

Support => Linux Specific Issues => Topic started by: Debci on March 22, 2009, 07:34:44 pm

Title: Guide compiling in open suse?
Post by: Debci on March 22, 2009, 07:34:44 pm

I need a complete guide to compiling in open suse linux distro.

regards

Title: Re: Guide compiling in open suse?
Post by: Caarrie on March 22, 2009, 07:35:27 pm

there is no official guide for opensuse.

Title: Re: Guide compiling in open suse?
Post by: Sen on March 22, 2009, 07:38:47 pm

Hello

The linux guide should work fine.

Sen

Title: Re: Guide compiling in open suse?
Post by: Debci on March 22, 2009, 07:53:50 pm

yes i tryed to compile with linux guide, the problem is, the packages requiereds, i dont know who are the packages required.
If you can post here the code to execute in shell i turn the most happy in the world.

regards  :P

Title: Re: Guide compiling in open suse?
Post by: Caarrie on March 22, 2009, 07:56:13 pm

check the ubuntu guide for a list of packages needed for that version, and then your task is to find those packages for your distro. there are way  too many distros for us to have a list of all package names for each distro.

Title: Re: Guide compiling in open suse?
Post by: Debci on March 22, 2009, 08:19:30 pm

i used autoreconf in cal3d folder and the console say this:

Code: [Select]

debci@linux-fcg2:~/development/cal3d> autoreconf --install --force
docs/Makefile.am:13: wildcard modeling/image*.jpg: non-POSIX variable name
docs/Makefile.am:13: (probably a GNU make extension)
docs/Makefile.am:13: wildcard modeling/tutorial.html: non-POSIX variable name
docs/Makefile.am:13: (probably a GNU make extension)
src/cal3d/Makefile.am:17: Libtool library used but `LIBTOOL' is undefined
src/cal3d/Makefile.am:17:   The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/cal3d/Makefile.am:17:   to `configure.in' and run `aclocal' and `autoconf' again.
src/cal3d/Makefile.am:17:   If `AC_PROG_LIBTOOL' is in `configure.in', make sure
src/cal3d/Makefile.am:17:   its definition is in aclocal's search path.
tests/Makefile.am:25: wildcard cal3d_converter/base.??f: non-POSIX variable name
tests/Makefile.am:25: (probably a GNU make extension)
autoreconf: automake failed with exit status: 1
sorry...

Title: Re: Guide compiling in open suse?
Post by: enderandrew on March 23, 2009, 12:20:20 am

That usually means it can't find aclocal.  Either it isn't installed, or it can't find the path.

I had a HDD take a dump on me, and I'm in the middle of migrating to a new rig that I'm building, but I do run openSUSE and I might write up a compile guide for it later.  I just don't know when I'm going to get around to rebuilind the RAID and reinstalling.

Title: Re: Guide compiling in open suse?
Post by: Mordraugion on March 23, 2009, 10:34:23 am

I do run opensuse and although I havent built the latest server and client, I have built all previous versions going back to 0.03.02 and the standard Linux guide works well.
When I get home tonight I'll do a build and check but as long as you have the Base Dev package group installed it should build without probs.

Well results: similar issue but not the same as  debci

Code: [Select]

libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.in and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
configure.in:18: installing `./config.guess'
configure.in:18: installing `./config.sub'
configure.in:20: installing `./install-sh'
configure.in:20: installing `./missing'
src/Makefile.am: installing `./depcomp'
tests/Makefile.am:14: wildcard cal3d_converter/base.??f: non-POSIX variable name
tests/Makefile.am:14: (probably a GNU make extension)

but finally got autoreconf to run by adding  the line and flags libtoolize suggested ./configure runs without errors but make fails

Code: [Select]

hardwaremodel.cpp:754: error: ‘memcpy’ was not declared in this scope
hardwaremodel.cpp:765: error: ‘memset’ was not declared in this scope
hardwaremodel.cpp:776: error: ‘memset’ was not declared in this scope
hardwaremodel.cpp:793: error: ‘memset’ was not declared in this scope
make[3]: *** [hardwaremodel.lo] Error 1
make[3]: Leaving directory `/home/john/planeshift/0.4.03/cal3d/src/cal3d'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/john/planeshift/0.4.03/cal3d/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/john/planeshift/0.4.03/cal3d'
make: *** [all] Error 2
Run out of time to try  further tonight so will try again tomorrow


Take 3
Didn't have time last night but pretty sure I used wrong rev of cal3d

Title: Re: Guide compiling in open suse?
Post by: Debci on March 28, 2009, 12:56:04 pm

ok, thanks for our help ^^

regards  :thumbup:

Title: Re: Guide compiling in open suse?
Post by: Khaki on March 31, 2009, 04:59:59 am

A guide to compiling for OpenSUSE has been added to compiling.html