Re: Error running on amd64
Dries Desmet <[email protected]> Sat, 16 Jul 2005 23:45:12 +0000
| Newsgroups | gmane.network.directoryadmin |
|---|---|
| Organization | Urga |
| Message-ID | <[email protected]> |
Just used default ./configure, make and make install Don't know if you are familiar with gentoo, but these are my settings for it: System uname: 2.6.11-gentoo-r11 x86_64 AMD Opteron(tm) Processor 244 CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=k8 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CXXFLAGS="-O2 -pipe" MAKEOPTS="-j3" GCC: Thread model: posix gcc version 3.4.3 20041125 (Gentoo Linux 3.4.3-r1, ssp-3.4.3-0, pie-8.7.7) This is the output of configure: adam diradmin-1.6.0 # ./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for gnome-config... /usr/bin/gnome-config checking if /usr/bin/gnome-config works... yes checking for orbit-config... /usr/bin/orbit-config checking for orbit-idl... /usr/bin/orbit-idl checking for working ORBit environment... yes checking for gnorba libraries... yes checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking dependency style of gcc... gcc3 checking for strerror in -lcposix... no checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ANSI C... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking for gcc option to accept ANSI C... none needed checking how to run the C preprocessor... gcc -E checking for egrep... grep -E checking for ANSI C header files... yes checking what warning flags to pass to the C compiler... -Wall -Wunused checking what language compliance flags to pass to the C compiler... checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for pthread_create in -lpthread... yes checking for gtk-config... /usr/bin/gtk-config checking for GTK - version >= 1.2.0... yes checking for SmcSaveYourselfDone in -lSM... yes checking X11/SM/SMlib.h usability... yes checking X11/SM/SMlib.h presence... yes checking for X11/SM/SMlib.h... yes checking for XpmFreeXpmImage in -lXpm... yes checking for ldap_start_tls_s in -lldap... yes checking for OpenSSL_add_all_digests in -lcrypto... yes checking for SSL_new in -lssl... yes configure: creating ./config.status config.status: creating Makefile config.status: creating macros/Makefile config.status: creating src/Makefile config.status: creating config.h config.status: config.h is unchanged config.status: executing depfiles commands The program fires up with the wizard, the test connection option is positive, but when I hit the connect button it crashes with gnome segmentation fault. If you want more debug information, tell me how to get it to you. DRie.s On Saturday 16 July 2005 21:23, scientica (GMail) wrote: > Dries Desmet wrote: > >Hi all, > > > >Directory administrator 1.6 is crashing on my gentoo amd64 machine. > >Did anybody manage to compile it for such a system? > > > >Any help or directorion appreciated. > > > >DRie.s > > > >The error: > ><code> > >adam diradmin-1.6.0 # directory_administrator > > > >Icon list realized - setting up drag and drop > >Intentando conectar interactivamente > >Existe solo un perfil de conexion > > > >called: app_connect with profile name: Manager > > > > > >Se conecto con exito > > > >called: refresh_directory_data > ></code> > > yes, I've compiled it (many times) and it runs fine for me. Can you > describe the steps to reproduce the crash, from configure (what options > you passed etc), make to running it? > > Regards > Fredrik (aka Scientica)