aMule Forum

English => Compilation problems => Topic started by: luquino on May 19, 2007, 10:16:06 PM

Title: Problem compiling aMule from CVS tarball on Ubuntu Edgy
Post by: luquino on May 19, 2007, 10:16:06 PM
Hello. Thisi is my first try to compile aMule and doesn't work.
1) Configure output:
Code: [Select]
luca@luca:~/sistema/sorgenti/amule/amule-cvs$ ./configure
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
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 whether to enable maintainer-specific portions of Makefiles... no
checking for g++... g++
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 g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for gcc... gcc
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 how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking whether make sets $(MAKE)... (cached) yes
checking for flex... no
checking for lex... no
checking for yywrap in -lfl... no
checking for yywrap in -ll... no
checking for a BSD-compatible install... /usr/bin/install -c
checking for ranlib... ranlib
checking for bison... no
checking for byacc... no
checking for ranlib... (cached) ranlib
checking for strip... strip
checking for ar... ar
checking for ld... ld
checking for zlib >= 1.1.4... yes (version 1.2.3)
checking for File::Copy... ok
checking whether we need the GUI... yes
checking for using IP2Country class...
checking for wx-config... /usr/bin/wx-config
checking for wxWidgets version >= 2.8.0... yes (version 2.8.0)
checking for wxWidgets static library... no
checking that wxWidgets has support for large files... yes
checking that wxWidgets was compiled with unicode support... yes
checking whether to use embedded Crypto... yes
checking for bfd headers... yes
checking for autopoint... yes (0.15)
checking for X... libraries , headers
checking for working alloca.h... yes
checking for alloca... yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for ANSI C header files... yes
checking argz.h usability... yes
checking argz.h presence... yes
checking for argz.h... yes
checking arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking inttypes.h usability... yes
checking inttypes.h presence... yes
checking for inttypes.h... yes
checking langinfo.h usability... yes
checking langinfo.h presence... yes
checking for langinfo.h... yes
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking mntent.h usability... yes
checking mntent.h presence... yes
checking for mntent.h... yes
checking netdb.h usability... yes
checking netdb.h presence... yes
checking for netdb.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking stddef.h usability... yes
checking stddef.h presence... yes
checking for stddef.h... yes
checking nl_types.h usability... yes
checking nl_types.h presence... yes
checking for nl_types.h... yes
checking stdint.h usability... yes
checking stdint.h presence... yes
checking for stdint.h... yes
checking stdio_ext.h usability... yes
checking stdio_ext.h presence... yes
checking for stdio_ext.h... yes
checking stdlib.h usability... yes
checking stdlib.h presence... yes
checking for stdlib.h... yes
checking string.h usability... yes
checking string.h presence... yes
checking for string.h... yes
checking strings.h usability... yes
checking strings.h presence... yes
checking for strings.h... yes
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking sys/mount.h usability... yes
checking sys/mount.h presence... yes
checking for sys/mount.h... yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking sys/resource.h usability... yes
checking sys/resource.h presence... yes
checking for sys/resource.h... yes
checking sys/select.h usability... yes
checking sys/select.h presence... yes
checking for sys/select.h... yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking sys/statvfs.h usability... yes
checking sys/statvfs.h presence... yes
checking for sys/statvfs.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking sys/timeb.h usability... yes
checking sys/timeb.h presence... yes
checking for sys/timeb.h... yes
checking sys/types.h usability... yes
checking sys/types.h presence... yes
checking for sys/types.h... yes
checking unistd.h usability... yes
checking unistd.h presence... yes
checking for unistd.h... yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking for stdbool.h that conforms to C99... yes
checking for _Bool... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for mode_t... yes
checking for off_t... yes
checking for size_t... yes
checking whether time.h and sys/time.h may both be included... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for uid_t in sys/types.h... yes
checking for working volatile... yes
checking for ptrdiff_t... yes
checking whether closedir returns void... no
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for library containing strerror... none required
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking for getpagesize... yes
checking for working mmap... yes
checking whether we are using the GNU C Library 2.1 or newer... yes
checking whether integer division by zero raises SIGFPE... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unsigned long long... yes
checking for inttypes.h... yes
checking whether the inttypes.h PRIxNN macros are broken... no
checking for ld used by GCC... ld
checking if the linker (ld) is GNU ld... yes
checking for shared library run path origin... done
checking for argz.h... (cached) yes
checking for limits.h... (cached) yes
checking for locale.h... (cached) yes
checking for nl_types.h... (cached) yes
checking for malloc.h... (cached) yes
checking for stddef.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for unistd.h... (cached) yes
checking for sys/param.h... (cached) yes
checking for feof_unlocked... yes
checking for fgets_unlocked... yes
checking for getc_unlocked... yes
checking for getcwd... yes
checking for getegid... yes
checking for geteuid... yes
checking for getgid... yes
checking for getuid... yes
checking for mempcpy... yes
checking for munmap... yes
checking for putenv... yes
checking for setenv... yes
checking for setlocale... yes
checking for stpcpy... yes
checking for strcasecmp... yes
checking for strdup... yes
checking for strtoul... yes
checking for tsearch... yes
checking for __argz_count... yes
checking for __argz_stringify... yes
checking for __argz_next... yes
checking for iconv... yes
checking for iconv declaration...
         extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft);
checking for nl_langinfo and CODESET... yes
checking for LC_MESSAGES... yes
checking for bison... no
checking whether NLS is requested... yes
checking whether included gettext is requested... no
checking for GNU gettext in libc... yes
checking for getmntent in -lsun... no
checking for getmntent in -lseq... no
checking for getmntent in -lgen... no
checking for getmntent... yes
checking whether gcc needs -traditional... no
checking for pid_t... yes
checking for unistd.h... (cached) yes
checking vfork.h usability... no
checking vfork.h presence... no
checking for vfork.h... no
checking for fork... yes
checking for vfork... yes
checking for working fork... yes
checking for working vfork... (cached) yes
checking whether lstat dereferences a symlink specified with a trailing slash... no
checking whether lstat accepts an empty string... no
checking whether lstat dereferences a symlink specified with a trailing slash... (cached) no
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for working memcmp... yes
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking for getpagesize... (cached) yes
checking for working mmap... (cached) yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible realloc... yes
checking for sys/select.h... (cached) yes
checking for sys/socket.h... (cached) yes
checking types of arguments for select... int,fd_set *,struct timeval *
checking for function prototypes... yes
checking whether setvbuf arguments are reversed... no
checking return type of signal handlers... void
checking whether stat accepts an empty string... no
checking for strftime... yes
checking for working strtod... yes
checking for vprintf... yes
checking for _doprnt... no
checking for __argz_count... (cached) yes
checking for __argz_next... (cached) yes
checking for __argz_stringify... (cached) yes
checking for endpwent... yes
checking for floor... no
checking for ftruncate... yes
checking for getcwd... (cached) yes
checking for gethostbyaddr... yes
checking for gethostbyname... yes
checking for gethostname... yes
checking for getmntent... (cached) yes
checking for getmntinfo... no
checking for getpass... yes
checking for gettimeofday... yes
checking for inet_ntoa... yes
checking for localeconv... yes
checking for memmove... yes
checking for mempcpy... (cached) yes
checking for memset... yes
checking for munmap... (cached) yes
checking for nl_langinfo... yes
checking for pow... no
checking for select... yes
checking for setlocale... (cached) yes
checking for socket... yes
checking for sqrt... no
checking for stpcpy... (cached) yes
checking for strcasecmp... (cached) yes
checking for strchr... yes
checking for strcspn... yes
checking for strdup... (cached) yes
checking for strerror... yes
checking for strncasecmp... yes
checking for strstr... yes
checking for strtoul... (cached) yes
checking for mkdir... yes
checking for getrlimit... yes
checking for setrlimit... yes
checking if the applications should be statically linked... no
checking for docdir... ${prefix}/share/doc/aMule-CVS
checking for CVSDATE... Fri May 18 07:02:05 CEST 2007
checking if this is a FreeBSD 4 or earlier system... no
checking denoising level... 0
checking whether ccache support should be added... no
configure: creating ./config.status
config.status: creating Makefile
config.status: creating docs/Makefile
config.status: creating docs/man/Makefile
config.status: creating intl/Makefile
config.status: creating m4/Makefile
config.status: creating src/Makefile
config.status: creating src/kademlia/Makefile
config.status: creating src/kademlia/utils/Makefile
config.status: creating src/kademlia/kademlia/Makefile
config.status: creating src/kademlia/routing/Makefile
config.status: creating src/kademlia/net/Makefile
config.status: creating src/pixmaps/Makefile
config.status: creating src/pixmaps/flags_xpm/Makefile
config.status: creating src/libs/Makefile
config.status: creating src/libs/ec/Makefile
config.status: creating src/libs/ec/abstracts/Makefile
config.status: creating src/libs/ec/cpp/Makefile
config.status: creating src/libs/common/Makefile
config.status: creating src/utils/Makefile
config.status: creating src/utils/aLinkCreator/Makefile
config.status: creating src/utils/aLinkCreator/docs/Makefile
config.status: creating src/utils/aLinkCreator/src/Makefile
config.status: creating src/utils/cas/Makefile
config.status: creating src/utils/cas/docs/Makefile
config.status: creating src/utils/wxCas/Makefile
config.status: creating src/utils/wxCas/docs/Makefile
config.status: creating src/utils/wxCas/src/Makefile
config.status: creating src/utils/xas/Makefile
config.status: creating src/utils/xas/autostart-xas
config.status: creating src/utils/xas/docs/Makefile
config.status: creating src/webserver/Makefile
config.status: creating src/webserver/src/Makefile
config.status: creating src/webserver/default/Makefile
config.status: creating src/webserver/php-default/Makefile
config.status: creating src/webserver/chicane/Makefile
config.status: creating unittests/Makefile
config.status: creating unittests/muleunit/Makefile
config.status: creating unittests/tests/Makefile
config.status: creating po/Makefile.in
config.status: creating Compilation.flags
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing default-1 commands
config.status: creating po/POTFILES
config.status: creating po/Makefile
config.status: executing denoiser commands


  Configure script has finished system check.

  Configured aMule CVS for 'i686-pc-linux-gnu'.

  aMule enabled options:

  **** aMule Core ****
  Prefix where aMule should be installed?                    /usr/local
  Should aMule be compiled with i18n support?                yes
  Should aMule be compiled in debug mode?                    yes
  Should aMule be compiled with profiling?                   no
  Should aMule be compiled with optimizations?               no
  Should aMule be compiled with UPnP support?                yes
  Should aMule be compiled with IP2country support?          yes
  Should aMule monolithic application be built?              yes
  Should aMule daemon version be built?                      no
  Should aMule remote gui be built? (EXPERIMENTAL)           no
  Crypto++ library/headers style?                            embedded

  **** aMule TextClient ****
  Should aMule Command Line Client be built?                 no

  **** aMule WebServer ****
  Should aMule WebServer be built?                           no

  **** aMule ED2K Links Handler ****
  Should aMule ED2K Links Handler be built?                  yes

  **** aMuleLinkCreator ****
  Should aMuleLinkCreator GUI version (alc) be built?        no
  Should aMuleLinkCreator for console (alcc) be built?       no

  **** aMule Statistics ****
  Should C aMule Statistics (CAS) be built?                  no
  Should aMule GUI Statistics (wxCas) be built?              no

  **** General Libraries and Tools ****
  Should ccache support be enabled?                          no
  Libraries aMule will use to build:
                                       wxWidgets             2.8.0
                                       crypto++              embedded
                                       zlib                  1.2.3

2) Make errors... the system gives a plenty of this:
Code: [Select]
'Statistics.cpp' || echo './'`Statistics.cpp; \
        then mv -f ".deps/amule-Statistics.Tpo" ".deps/amule-Statistics.Po"; else rm -f ".deps/amule-Statistics.Tpo"; exit 1; fi
/usr/include/wx-2.8/wx/gdicmn.h: In member function ‘bool wxRect::Inside(int, int) const’:
/usr/include/wx-2.8/wx/gdicmn.h:486: warning: declaration of ‘y’ shadows a member of 'this'
/usr/include/wx-2.8/wx/gdicmn.h:486: warning: declaration of ‘x’ shadows a member of 'this'
if g++ -DHAVE_CONFIG_H -I. -I. -I..    -DENABLE_UPNP=1 -I/usr/lib/wx/include/gtk2-unicode-release-2.8 -I/usr/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXGTK__ -pthread    -I./libs -Ilibs -DUSE_EMBEDDED_CRYPTO -W -Wall -Wshadow -Wundef -g -ggdb -fno-inline -D__DEBUG__ -fmessage-length=0 -D_GLIBCXX_DEBUG -D_GLIBCXX_DEBUG_PEDANTIC   -DUSE_WX_EXTENSIONS -MT amule-StatTree.o -M

3) The outputs required:

Code: [Select]
luca@luca:~/sistema/sorgenti/amule/amule-cvs$ ls -l /usr/bin/wx*
lrwxrwxrwx 1 root root 27 2007-04-08 02:31 /usr/bin/wx-config -> /etc/alternatives/wx-config
luca@luca:~/sistema/sorgenti/amule/amule-cvs$
Code: [Select]
luca@luca:~/sistema/sorgenti/amule/amule-cvs$ ls -l /usr/local/bin/wx*
ls: /usr/local/bin/wx*: No such file or directory
Code: [Select]
luca@luca:~/sistema/sorgenti/amule/amule-cvs$ rpm -qa | grep wx
luca@luca:~/sistema/sorgenti/amule/amule-cvs$
Title: Re: Problem compiling aMule from CVS tarball on Ubuntu Edgy
Post by: Kry on May 20, 2007, 01:20:58 AM
I don't see any error
Title: Re: Problem compiling aMule from CVS tarball on Ubuntu Edgy
Post by: skolnick on May 20, 2007, 06:27:40 AM
There are differences between "warning" and "error", you know. What you are seeing are just warnings, which can sometimes be safely ignored. An error stops the compilation process. Just like Kry said, there are no errors on your post. Also, I think the "rpm -qa | grep wx" command is meaningless on your PC, since you use ubuntu (based on debian). Maybe you should use the dpkg command to know if there are any wx* packages installed on your system.

Regards.
Title: Re: Problem compiling aMule from CVS tarball on Ubuntu Edgy
Post by: luquino on May 20, 2007, 09:23:09 PM
well, I apologize but I'm totally newbie in compiling. But I need to do that because there is any recent version of aMule prepacked for Ubuntu Edgy.
After ./configure command I give a make and at the end appears this
Code: [Select]
make[3]: Leaving directory `/home/luca/sistema/sorgenti/amule/amule-cvs/src'
make[2]: Leaving directory `/home/luca/sistema/sorgenti/amule/amule-cvs/src'
Making all in unittests
make[2]: Entering directory `/home/luca/sistema/sorgenti/amule/amule-cvs/unittests'
make[3]: Entering directory `/home/luca/sistema/sorgenti/amule/amule-cvs/unittests'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/home/luca/sistema/sorgenti/amule/amule-cvs/unittests'
make[2]: Leaving directory `/home/luca/sistema/sorgenti/amule/amule-cvs/unittests'
Making all in intl
make[2]: Entering directory `/home/luca/sistema/sorgenti/amule/amule-cvs/intl'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/luca/sistema/sorgenti/amule/amule-cvs/intl'
Making all in po
make[2]: Entering directory `/home/luca/sistema/sorgenti/amule/amule-cvs/po'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/luca/sistema/sorgenti/amule/amule-cvs/po'
make[2]: Entering directory `/home/luca/sistema/sorgenti/amule/amule-cvs'
make[2]: Leaving directory `/home/luca/sistema/sorgenti/amule/amule-cvs'
make[1]: Leaving directory `/home/luca/sistema/sorgenti/amule/amule-cvs'

I suppose is ok, but if I try to start aMule:
Code: [Select]
luca@luca:~/sistema/sorgenti/amule/amule-cvs$ amule
bash: amule: command not found

Do I need to install as well? Is it right to install with
Code: [Select]
sudo make install?
Title: Re: Problem compiling aMule from CVS tarball on Ubuntu Edgy
Post by: wuischke on May 20, 2007, 10:22:11 PM
Yes, this is the right command.
Title: Re: Problem compiling aMule from CVS tarball on Ubuntu Edgy
Post by: luquino on May 20, 2007, 10:37:02 PM
ok. So the problem is here
Code: [Select]
Making install in m4
make[1]: Entering directory `/home/luca/sistema/sorgenti/amule/amule-cvs/m4'
make[2]: Entering directory `/home/luca/sistema/sorgenti/amule/amule-cvs/m4'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/home/luca/sistema/sorgenti/amule/amule-cvs/m4'
make[1]: Leaving directory `/home/luca/sistema/sorgenti/amule/amule-cvs/m4'
Making install in docs
make[1]: Entering directory `/home/luca/sistema/sorgenti/amule/amule-cvs/docs'
Making install in man
make[2]: Entering directory `/home/luca/sistema/sorgenti/amule/amule-cvs/docs/man'
make[3]: Entering directory `/home/luca/sistema/sorgenti/amule/amule-cvs/docs/man'
make[3]: Nothing to be done for `install-exec-am'.
test -z "/usr/local/man/man1" || mkdir -p -- "/usr/local/man/man1"
mkdir: impossibile creare la directory `/usr/local/man': Il file esiste
make[3]: *** [install-man1] Error 1
make[3]: Leaving directory `/home/luca/sistema/sorgenti/amule/amule-cvs/docs/man'
make[2]: *** [install-am] Error 2
make[2]: Leaving directory `/home/luca/sistema/sorgenti/amule/amule-cvs/docs/man'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/home/luca/sistema/sorgenti/amule/amule-cvs/docs'
make: *** [install-recursive] Error 1
Title: Re: Problem compiling aMule from CVS tarball on Ubuntu Edgy
Post by: luquino on May 22, 2007, 10:21:32 AM
Up.... sorry for the bump  ::)
Title: Re: Problem compiling aMule from CVS tarball on Ubuntu Edgy
Post by: skolnick on May 23, 2007, 01:09:31 AM
For some reason it seems the install is not able to miss the creation of an existant folder. Try running amule from inside the compilation folder, just go to that folder, and run:

./src/amule

It should work.

Regards.
Title: Re: Problem compiling aMule from CVS tarball on Ubuntu Edgy
Post by: luquino on May 23, 2007, 11:48:48 PM
Yes. It works in that way. There is any chance to correct installation step?
And is it possible to have Italian language?
Title: Re: Problem compiling aMule from CVS tarball on Ubuntu Edgy
Post by: skolnick on May 24, 2007, 03:47:17 AM
I do not use it, but I think Italian is one of the suported languages (aMule supports lots of languages :)). It seems the problem with the install is on your mkdir program, it's failing to create an already-existant folder. I had never seen that :(, which distro are you using?

Regards.

Edit: I just saw you are using Ubunty Edgy.
Title: Re: Problem compiling aMule from CVS tarball on Ubuntu Edgy
Post by: luquino on May 24, 2007, 11:25:50 AM
If I well understand mkdir fails only installing manual(s), in the others step of installation the error is just "nothing to be done" ....
Title: Re: Problem compiling aMule from CVS tarball on Ubuntu Edgy
Post by: luquino on May 25, 2007, 12:39:48 PM
Just for more info: I compiled and installed without any problem wxGTK.2.8.4 and other software like AMSN.... ???
Title: Re: Problem compiling aMule from CVS tarball on Ubuntu Edgy
Post by: phoenix on May 25, 2007, 02:28:38 PM
Are you running "make install" as root or as a common user?
Title: Re: Problem compiling aMule from CVS tarball on Ubuntu Edgy
Post by: luquino on May 25, 2007, 06:10:09 PM
I give the command
Code: [Select]
sudo make install thus I run install as root
Title: Re: Problem compiling aMule from CVS tarball on Ubuntu Edgy
Post by: skolnick on May 26, 2007, 07:51:33 AM
Just for a try: become root (su -) and then execute make install. It could work differently from sudo and maybe it will work.

Regards.
Title: Re: Problem compiling aMule from CVS tarball on Ubuntu Edgy
Post by: luquino on May 27, 2007, 12:36:25 AM
no, unfortunately it doesn't work.
Title: Re: Problem compiling aMule from CVS tarball on Ubuntu Edgy
Post by: skolnick on May 27, 2007, 12:54:33 AM
Then try installing like this:

make install prefix=/opt/amule

That will install aMule on the /opt/amule tree (/opt/amule/bin, /opt/amule/lib, etc). If this works fine, then you can move every file from this folder to the folder you want it to be (example: mv /opt/amule/bin/* /usr/local/bin/)

Regards.
Title: Re: Problem compiling aMule from CVS tarball on Ubuntu Edgy
Post by: luquino on May 27, 2007, 06:46:33 PM
Ok it works, but install produce a huge output, I had to attach because exceeds the maximum lenght of a message.

I can't understand if it is ok
Title: Re: Problem compiling aMule from CVS tarball on Ubuntu Edgy
Post by: skolnick on May 28, 2007, 03:09:00 AM
The log seems fine. One clue: When there is an error, it's usually shown in the last lines of the log (it applies to compilation, as well as configure and installation). If everything finishes, and there is not the "error" word in the last lines of the log, then most probably everything went fine.

Regards.
Title: Re: Problem compiling aMule from CVS tarball on Ubuntu Edgy
Post by: lfroen on May 28, 2007, 07:14:01 AM
Just for a try: become root (su -) and then execute make install. It could work differently from sudo and maybe it will work.

Regards.

In Ubuntu there's no "root" user, so "su -" will not work. You can "sudo tcsh" to start shell with root privileges
Title: Re: Problem compiling aMule from CVS tarball on Ubuntu Edgy
Post by: luquino on May 28, 2007, 11:06:43 AM
@ skolnick.
Thanks a lot for your patience, I'm learning a lot of things. For the future I'll try to don't bother you all again.

@ lfroen.
On Ubuntu the user root exist, what you never know is the password, but if you change the root password with
Code: [Select]
sudo passwd rootthen you can use the su command ;D
Title: Re: Problem compiling aMule from CVS tarball on Ubuntu Edgy
Post by: skolnick on May 28, 2007, 07:11:53 PM
In Ubuntu there's no "root" user, so "su -" will not work. You can "sudo tcsh" to start shell with root privileges
Maybe because of this the permissions in the /usr/local tree are strange and that's why the "make install" fails to recreate the existant folder? in other UNIXes the root user has full read/write permission to folders and files, maybe ubuntu assigns that same permission to other user. I don't know, just a theory.

Regards.
Title: Re: Problem compiling aMule from CVS tarball on Ubuntu Edgy
Post by: luquino on May 28, 2007, 10:29:45 PM
As I said in my last post, on my system the su command is fully functional and the root user as well:
Code: [Select]
luca@luca:~$ su -
Password:
root@luca:~# exit
logout
luca@luca:~$

 ;D