Hi sir i need help please. I want to install a software called Archimedes-2.0.1, but I have not succeeded. If you please here is the compilation




king@king:~/Bureau/archimedes-2.0.1$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
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 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 ISO C89... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
checking for ranlib... ranlib
checking for latex... latex
checking for dvips... dvips
checking for dvipdf... dvipdf
checking for log in -lm... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
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 memory.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for strings.h... (cached) yes
checking for unistd.h... (cached) yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking whether struct tm is in sys/time.h or time.h... time.h
checking for memset... yes
checking for pow... yes
checking for sqrt... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating doc/Makefile
config.status: creating src/Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
king@king:~/Bureau/archimedes-2.0.1$ make
make all-recursive
make[1]: entrant dans le répertoire « /home/king/Bureau/archimedes-2.0.1 »
Making all in src
make[2]: entrant dans le répertoire « /home/king/Bureau/archimedes-2.0.1/src »
make[2]: Rien à faire pour « all ».
make[2]: quittant le répertoire « /home/king/Bureau/archimedes-2.0.1/src »
Making all in doc
make[2]: entrant dans le répertoire « /home/king/Bureau/archimedes-2.0.1/doc »
make[2]: Rien à faire pour « all ».
make[2]: quittant le répertoire « /home/king/Bureau/archimedes-2.0.1/doc »
make[2]: entrant dans le répertoire « /home/king/Bureau/archimedes-2.0.1 »
make[2]: quittant le répertoire « /home/king/Bureau/archimedes-2.0.1 »
make[1]: quittant le répertoire « /home/king/Bureau/archimedes-2.0.1 »
king@king:~/Bureau/archimedes-2.0.1$ make check
Making check in src
make[1]: entrant dans le répertoire « /home/king/Bureau/archimedes-2.0.1/src »
make[1]: Rien à faire pour « check ».
make[1]: quittant le répertoire « /home/king/Bureau/archimedes-2.0.1/src »
Making check in doc
make[1]: entrant dans le répertoire « /home/king/Bureau/archimedes-2.0.1/doc »
make[1]: Rien à faire pour « check ».
make[1]: quittant le répertoire « /home/king/Bureau/archimedes-2.0.1/doc »
make[1]: entrant dans le répertoire « /home/king/Bureau/archimedes-2.0.1 »
make[1]: quittant le répertoire « /home/king/Bureau/archimedes-2.0.1 »
king@king:~/Bureau/archimedes-2.0.1$ make install
Making install in src
make[1]: entrant dans le répertoire « /home/king/Bureau/archimedes-2.0.1/src »
make[2]: entrant dans le répertoire « /home/king/Bureau/archimedes-2.0.1/src »
/bin/mkdir -p '/usr/local/bin'
/usr/bin/install -c archimedes '/usr/local/bin'
/usr/bin/install: impossible de supprimer «/usr/local/bin/archimedes»: Permission non accordée
make[2]: *** [install-binPROGRAMS] Erreur 1
make[2]: quittant le répertoire « /home/king/Bureau/archimedes-2.0.1/src »
make[1]: *** [install-am] Erreur 2
make[1]: quittant le répertoire « /home/king/Bureau/archimedes-2.0.1/src »
make: *** [install-recursive] Erreur 1
king@king:~/Bureau/archimedes-2.0.1$ sudo make install
[sudo] password for king:
Making install in src
make[1]: entrant dans le répertoire « /home/king/Bureau/archimedes-2.0.1/src »
make[2]: entrant dans le répertoire « /home/king/Bureau/archimedes-2.0.1/src »
/bin/mkdir -p '/usr/local/bin'
/usr/bin/install -c archimedes '/usr/local/bin'
make[2]: Rien à faire pour « install-data-am ».
make[2]: quittant le répertoire « /home/king/Bureau/archimedes-2.0.1/src »
make[1]: quittant le répertoire « /home/king/Bureau/archimedes-2.0.1/src »
Making install in doc
make[1]: entrant dans le répertoire « /home/king/Bureau/archimedes-2.0.1/doc »
make[2]: entrant dans le répertoire « /home/king/Bureau/archimedes-2.0.1/doc »
make[2]: Rien à faire pour « install-exec-am ».
make[2]: Rien à faire pour « install-data-am ».
make[2]: quittant le répertoire « /home/king/Bureau/archimedes-2.0.1/doc »
make[1]: quittant le répertoire « /home/king/Bureau/archimedes-2.0.1/doc »
make[1]: entrant dans le répertoire « /home/king/Bureau/archimedes-2.0.1 »
make[2]: entrant dans le répertoire « /home/king/Bureau/archimedes-2.0.1 »
make[2]: Rien à faire pour « install-exec-am ».
make[2]: Rien à faire pour « install-data-am ».
make[2]: quittant le répertoire « /home/king/Bureau/archimedes-2.0.1 »
make[1]: quittant le répertoire « /home/king/Bureau/archimedes-2.0.1 »
king@king:~/Bureau/archimedes-2.0.1$

Can you change the language to english?
And then post the output angain.

Hi and welcome to LQ,

It is successful.
Apart from the fact that you first ran "make install" as normal user and got a permission error (if I translate correctly from french), then when you ran it as superuser your software was installed successfully.


BTW, since you're new here, please next time use a more descriptive title for your threads

Regards

1 members found this post helpful.

For initial post please try making the description easier to understand. Ex. Source compile problem or such.

Apart from that, you are running the compilation with a non root user trying to install into a restricted directory. It will fail because of permissions.

Compile the programme as root if you want it in that location, or change the directory to compile to.

@ericson007
The 1st time OP ran "make install" as normal user and failed:
After that it ran it again with sudo and it was successful as it finished without errors:
So the S/W is installed and ready to be used

Cheers

I would not recommend compiling programs as root. You should never do anything as root if you don't have to.

In future, unpack the source code in your own directory and run the configure and make steps as yourself. Then become root with su or sudo and run "make install". It's only the installation (i.e. the copying of the files you have built to their final destinations) that needs to be done with root privileges.

no.
compile (make) as normal user, install as root (if so desired).

Oh dear, fingers faster than brain. Lol. Yup, the make does not require the permissions.

1 members found this post helpful.