Problem in building gcc 4.5 : error in tools.zip - gcc

I tryied to build gcc 4.5.0 on Linux version 2.6.18-164.6.1.el5, and found the following problems that I couldn't find an answer on Google. I used the following command.
../gcc-4.3.5/configure --prefix=/usr --prefix=/apps --with-gmp=/apps --with-mpc=/apps --with-mpfr=/apps --enable-shared --enable-threads=posix
make -j 8
Here is the part when it complained about the error
...
cp: preserving ACL for `./asm/org/objectweb/asm/ClassAdapter.class': Operation not supported
cp: preserving permissions for `./asm/org/objectweb/asm': Operation not supported
cp: preserving permissions for `./asm/org/objectweb': Operation not supported
cp: preserving permissions for `./asm/org': Operation not supported
cp: preserving permissions for `./asm': Operation not supported
make[6]: *** [tools.zip] Error 1
make[6]: Leaving directory `/home/gl/gcc4.3obj/x86_64-unknown-linux-gnu/32/libjava/classpath/tools'
make[6]: Entering directory `/home/gl/gcc4.3obj/x86_64-unknown-linux-gnu/32/libjava/classpath'
true DO=all multi-do # make
make[6]: Leaving directory `/home/gl/gcc4.3obj/x86_64-unknown-linux-gnu/32/libjava/classpath'
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory `/home/gl/gcc4.3obj/x86_64-unknown-linux-gnu/32/libjava/classpath'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/home/gl/gcc4.3obj/x86_64-unknown-linux-gnu/32/libjava'
make[3]: *** [multi-do] Error 1
make[3]: Leaving directory `/home/gl/gcc4.3obj/x86_64-unknown-linux-gnu/libjava'
make[2]: *** [all-multi] Error 2
make[2]: Leaving directory `/home/gl/gcc4.3obj/x86_64-unknown-linux-gnu/libjava'
make[1]: *** [all-target-libjava] Error 2
make[1]: Leaving directory `/home/gl/gcc4.3obj'
make: *** [all] Error 2
Any clarification and help will be highly appreciated. Thank you.

You say you're building gcc 4.5.0 but your error messages and ./configure line suggest that you are instead building gcc 4.3.5. I point this out because it's possible you have tripped over a bug in gcc 4.3.x's build scripts.
Second, the error messages you quoted make me think that you are doing your build on a weird file system, or else you have a buggy cp (unlikely but not impossible). What sort of file system is /home? You can find out with the mount command -- type it with no arguments, look for the /home line, see what it says next to "type". I have this:
/dev/sda3 on /home type ext4 (rw)
ext2, ext3, ext4, btrfs, xfs, and jfs should not be troublesome; anything else might well be for this use.
By the way, the precise version of your kernel ("Linux version 2.6.18-164.6.1.el5") is very unlikely to be relevant; for this sort of problem it would be much more useful to know which distribution you are using, and the version of that.

I had a similar problem building a different package (LAMMPS). The Makfile included a -p flag in a cp statement. I removed it and the error disappeared. It may be worth a try...

Related

Cygwin,lib: command not found while building Unix based library

I am trying to install the tblis library on my Cygwin installation and I am encountering in the following error:
$ make
make all-recursive
make[1]: Entering directory '/home/indiano/Test/tblis'
Making all in src/external/tci
make[2]: Entering directory '/home/indiano/Test/tblis/src/external/tci'
CXXLD lib/libtci.la
./libtool: line 1741: lib: command not found
make[2]: *** [Makefile:531: lib/libtci.la] Error 127
make[2]: Leaving directory '/home/indiano/Test/tblis/src/external/tci'
make[1]: *** [Makefile:2581: all-recursive] Error 1
make[1]: Leaving directory '/home/indiano/Test/tblis'
make: *** [Makefile:1203: all] Error 2
I don´t have a lot of experience with building big projects and even less in cross-compiling, can somebody land an hand or at least point me in some direction?
My suspect is that something is missing in the base installation of Cygwin, but I can not identify which package should be.
Also seams that there is nothing to be found on the internet.

how to install gdb 9.1 on debian from source code

I like to compile and use gdb 9.1. the source is here https://ftp.gnu.org/gnu/gdb/
Plus when I type make in config directory make says make: *** No targets specified and no makefile found. Stop. because there is not make file. on root folder there are Makefile.in and Makefile.tpl and Makefile.def. what are these files. and how can I install gdb 9 from source code.
Update
After the comment changes I made in command by G.M I am getting this error I think almost at the end of compiling process
mv GDBvn.new GDBvn.texi
/home/fawad/Desktop/gdb/gdb/gdb-9.1.1/missing makeinfo --split-size=5000000 --split-size=5000000 -I /home/fawad/Desktop/gdb/gdb
/gdb-9.1.1/gdb/doc/../../readline/readline/doc -I /home/fawad/Desktop
/gdb/gdb/gdb-9.1.1/gdb/doc/../mi -I /home/fawad/Desktop/gdb/gdb/gdb-9.1.1/gdb/doc
-o gdb.info /home/fawad/Desktop/gdb/gdb/gdb-9.1.1/gdb/doc/gdb.texinfo
/home/fawad/Desktop/gdb/gdb/gdb-9.1.1/missing: 81: makeinfo: not found
WARNING: 'makeinfo' is missing on your system.
You should only need it if you modified a '.texi' file, or
any other file indirectly affecting the aspect of the manual.
You might want to install the Texinfo package:
http://www.gnu.org/software/texinfo/
The spurious makeinfo call might also be the consequence of
using a buggy 'make' (AIX, DU, IRIX), in which case you might
want to install GNU make:
http://www.gnu.org/software/make/
make[4]: *** [Makefile:490: gdb.info] Error 127
make[4]: Leaving directory '/home/fawad/Desktop/gdb/gdb/gdb-9.1/build/build/gdb/doc'
make[3]: *** [Makefile:2010: subdir_do] Error 1
make[3]: Leaving directory '/home/fawad/Desktop/gdb/gdb/gdb-9.1/build/build/gdb'
make[2]: *** [Makefile:1655: all] Error 2
make[2]: Leaving directory '/home/fawad/Desktop/gdb/gdb/gdb-9.1/build/build/gdb'
make[1]: *** [Makefile:9564: all-gdb] Error 2
make[1]: Leaving directory '/home/fawad/Desktop/gdb/gdb/gdb-9.1/build/build'
make: *** [Makefile:852: all] Error 2

Trying to compile a script from github but getting errors

I'm trying to install https://github.com/xxorde/librekinect
but I'm running into the following issue:
$ make
make pc
make[1]: Entering directory '/home/pi/librekinect-master'
make -C /lib/modules/3.18.5+/build M= modules
make[2]: Entering directory '/home/pi/librekinect-master'
make[2]: *** /lib/modules/3.18.5+/build: No such file or directory. Stop.
make[2]: Leaving directory '/home/pi/librekinect-master'
Makefile:31: recipe for target 'pc' failed
make[1]: *** [pc] Error 2
make[1]: Leaving directory '/home/pi/librekinect-master'
Makefile:24: recipe for target 'default' failed
make: *** [default] Error 2
I tried searching for *** /lib/modules/3.18.5+/build: No such file or directory. Stop. on google but that produced nothing helpful.
What am I missing?
Since you are working on raspberry pi, you should follow the recipe here. Mostly, I think you miss parts of the toolchain (at least build-essentials and likely the headers). I would follow that example step by step.

Error installing glib

I am trying to install the glib-2.38.0 and upon executing the MAKE file and getting the following error:
make[5]: Leaving directory `/root/glib-2.38.0/glib/update-pcre'
make[4]: Leaving directory `/root/glib-2.38.0/glib/update-pcre'
Making install in .
make[4]: Entering directory `/root/glib-2.38.0/glib'
CCLD libglib-2.0.la
libtool: link: `glib_probes.lo' is not a valid libtool object
make[4]: *** [libglib-2.0.la] Error 1
make[4]: Leaving directory `/root/glib-2.38.0/glib'
make[3]: *** [install-recursive] Error 1
make[3]: Leaving directory `/root/glib-2.38.0/glib'
make[2]: *** [install] Error 2
make[2]: Leaving directory `/root/glib-2.38.0/glib'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/root/glib-2.38.0'
make: *** [install] Error 2
How can I troubleshoot this? How can I overcome this issue?
After hitting this same error on Solaris 10 01/13 and not needing dtrace support, I solved this in configure by adding --disable-dtrace.
I had the exact same problem, and located your posting after
giving the error message to a search engine. Alas, no one
had answered you, so I had no choice but to troubleshoot the
problem myself.
In my case, the problem was an old version of dtrace. I updated
the package containing /usr/bin/dtrace (which, in my case, was
systemtap-sdt-devel) and then dtrace created a proper glib_probes.lo
file.
Having solved the problem for myself, it then became my duty to
tell you how I had done so, and answer your unanswered question.
This I have now done.

unable to infer compiler target triple for clang

I have modified the clang. It was working properly. But then I had some git related issues so I cleaned the git and checked out again. Now when I try to run make clean in clang I am getting the following error. How can I fix this?
#A set of warnings here
make[5]: Entering directory `/home/test/llvm/projects/compiler-rt'
make/platform/clang_linux.mk:16: *** "unable to infer compiler target triple for clang". Stop.
make[5]: Leaving directory `/home/test/llvm/projects/compiler-rt'
make[4]: *** [CleanRuntimeLibraries] Error 2
make[4]: Leaving directory `/home/test/llvm/tools/clang/runtime/compiler-rt'
make[3]: *** [compiler-rt/.makeclean] Error 2
make[3]: Leaving directory `/home/test/llvm/tools/clang/runtime'
make[2]: *** [clean] Error 1
make[2]: Leaving directory `/home/test/llvm/tools/clang'
make[1]: *** [clang/.makeclean] Error 2
make[1]: Leaving directory `/home/test/llvm/tools'
make: *** [clean] Error 1
I had this problem, and solved it. My problem was the link for clang failed (error 9) because I didn't have enough memory. It needs about 4 gig of memory to link, and I only had 3.5 total real memory and swap available.
Look just before these errors and possibly, you'll see that the link for clang failed.
ls the clang executable at {your build directory}/Debug+Asserts/bin/clang mine was zero bytes (because of link failure).
It then generated the "unable to infer compiler target triple" because it didn't have a clang to execute.
My solution was to create a swap file (because I didn't have any space to expand my swap partition) following the instructions at geek swap definition
I solved this error by setting the LD_LIBRARY_PATH environment variable correctly. At first, I set it without the lib64.
I installed llvm on my $HOME/local so, the correct LD_LIBRARY_PATH would be.
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH”:$HOME/local/lib:$HOME/local/lib64

Resources