Problem in finishing Phase 7 about ewxb-gcc-cross-compiler-builder HOT 4 CLOSED

Your host and target is x86_64?Do you need a cross-compiler then?

Which command in phase 7 fails? Paste the full output from the scrip at
some pastebin :)

On Nov 25, 2014 11:21 PM, "Srini Brahmaroutu" [email protected]
wrote:

I am trying to build the tool chain to compile GO 1.3.3 on x86_64 with
target set to x86_64 and I am running into issues with step 7. Following is
the error message.

/root/src/x86_64-unknown-linux-gnu_gcc_build/tools/x86_64-unknown-linux-gnu/lib/../lib64/libstdc++.
so.6.0.21-gdb.py is not an ELF file

Things I changed are
+export TARGET="x86_64-unknown-linux-gnu"
+export LINUX_ARCH="x86_64"

+#export GCCV=gcc-4.9.0
+export GCCV=gccgo

-export LINUXV=linux-2.6.31.14 (MAY BE NOT NEEDED)
+export LINUXV=linux-3.13

—
Reply to this email directly or view it on GitHub
#1.

from ewxb-gcc-cross-compiler-builder.

Reason I do the target the same system is to test first. I know that .py file issue is a known issue but I am not sure how to circumvent the issue. Hopefully the below output is good for you to analyze.

libtool: install: /usr/bin/install -c .libs/libitm.lai /root/src/x86_64-unknown-linux-gnu_gcc_build/tools/x86_64-unknown-linux-gnu/lib/../lib64/libitm.la
libtool: install: /usr/bin/install -c .libs/libitm.a /root/src/x86_64-unknown-linux-gnu_gcc_build/tools/x86_64-unknown-linux-gnu/lib/../lib64/libitm.a
libtool: install: chmod 644 /root/src/x86_64-unknown-linux-gnu_gcc_build/tools/x86_64-unknown-linux-gnu/lib/../lib64/libitm.a
libtool: install: /root/src/x86_64-unknown-linux-gnu_gcc_build/tools/x86_64-unknown-linux-gnu/bin/ranlib /root/src/x86_64-unknown-linux-gnu_gcc_build/tools/x86_64-unknown-linux-gnu/lib/../lib64/libitm.a
libtool: finish: PATH="/root/src/x86_64-unknown-linux-gnu_gcc_build/tools/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/local/go/bin:/root/go/bin:/home/ewxb_gcc_cross-compiler_builder:/sbin" ldconfig -n /root/src/x86_64-unknown-linux-gnu_gcc_build/tools/x86_64-unknown-linux-gnu/lib/../lib64
/sbin/ldconfig.real: /root/src/x86_64-unknown-linux-gnu_gcc_build/tools/x86_64-unknown-linux-gnu/lib/../lib64/libstdc++.so.6.0.21-gdb.py is not an ELF file - it has the wrong magic bytes at the start.

Libraries have been installed in:
/root/src/x86_64-unknown-linux-gnu_gcc_build/tools/x86_64-unknown-linux-gnu/lib/../lib64

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:

• add LIBDIR to the `LD_LIBRARY_PATH' environment variable
  during execution
• add LIBDIR to the `LD_RUN_PATH' environment variable
  during linking
• use the `-Wl,-rpath -Wl,LIBDIR' linker flag
• have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for

more information, such as the ld(1) and ld.so(8) manual pages.

test -z "/root/src/x86_64-unknown-linux-gnu_gcc_build/tools/share/info" || /bin/mkdir -p "/root/src/x86_64-unknown-linux-gnu_gcc_build/tools/share/info"
install-info --info-dir='/root/src/x86_64-unknown-linux-gnu_gcc_build/tools/share/info' '/root/src/x86_64-unknown-linux-gnu_gcc_build/tools/share/info/libitm.info'
This is not dpkg install-info anymore, but GNU install-info
See the man page for ginstall-info for command line arguments
install-info: No such file or directory for /root/src/x86_64-unknown-linux-gnu_gcc_build/tools/share/info/libitm.info
make[4]: Leaving directory /root/src/x86_64-unknown-linux-gnu_gcc_build/obj/gcc3/x86_64-unknown-linux-gnu/libitm' make[3]: Leaving directory/root/src/x86_64-unknown-linux-gnu_gcc_build/obj/gcc3/x86_64-unknown-linux-gnu/libitm'
make[2]: Leaving directory /root/src/x86_64-unknown-linux-gnu_gcc_build/obj/gcc3/x86_64-unknown-linux-gnu/libitm' make[1]: Leaving directory/root/src/x86_64-unknown-linux-gnu_gcc_build/obj/gcc3'
ln: './as' and './as' are the same file

from ewxb-gcc-cross-compiler-builder.

Are you sure this is an error? What happens next, does ewxb continue to build?

If I Google on the message it seems to be something you can ignore
https://gcc.gnu.org/ml/gcc-help/2014-08/msg00053.html

from ewxb-gcc-cross-compiler-builder.

I'll close this as the conversation did not continue.

from ewxb-gcc-cross-compiler-builder.