mirror of
https://code.it4i.cz/sccs/easyconfigs-it4i.git
synced 2025-04-16 11:48:06 +01:00
edafe1112d
new file: b/Bazel/CROSSTOOL.patch new file: b/Bazel/cc_configure.patch new file: l/libepoxy/libepoxy-1.4.3.eb modified: o/OpenMPI/OpenMPI-2.1.0-GCC-6.3.0-2.27.eb modified: o/OpenMPI/OpenMPI-2.1.1-GCC-7.1.0-2.28.eb new file: t/Tensorflow/Tensorflow-1.2.0-Python-3.6.1.eb new file: x/X11/X11-20160819-test.eb new file: x/X11/X11-20170314-test.eb new file: x/xf86-video-dummy/xf86-video-dummy-0.3.5.eb new file: x/xf86-video-fbdev/xf86-video-fbdev-0.4.4.eb new file: x/xorg-macros/xorg-macros-1.19.1.eb new file: x/xorg-server/xorg-server-1.19.3.eb
54 lines
2.8 KiB
Diff
54 lines
2.8 KiB
Diff
--- tools/cpp/CROSSTOOL.orig 1980-01-01 00:00:00.000000000 +0100
|
|
+++ tools/cpp/CROSSTOOL 2017-06-26 07:02:16.976232074 +0200
|
|
@@ -100,34 +100,34 @@
|
|
target_system_name: "local"
|
|
toolchain_identifier: "local_linux"
|
|
|
|
- tool_path { name: "ar" path: "/usr/bin/ar" }
|
|
- tool_path { name: "compat-ld" path: "/usr/bin/ld" }
|
|
- tool_path { name: "cpp" path: "/usr/bin/cpp" }
|
|
- tool_path { name: "dwp" path: "/usr/bin/dwp" }
|
|
- tool_path { name: "gcc" path: "/usr/bin/gcc" }
|
|
+ tool_path { name: "ar" path: "/apps/all/binutils/2.28-GCCcore-7.1.0/bin/ar" }
|
|
+ tool_path { name: "compat-ld" path: "/apps/all/binutils/2.28-GCCcore-7.1.0/bin/ld" }
|
|
+ tool_path { name: "cpp" path: "/apps/all/GCCcore/7.1.0/bin/cpp" }
|
|
+ tool_path { name: "dwp" path: "/apps/all/binutils/2.28-GCCcore-7.1.0/bin/dwp" }
|
|
+ tool_path { name: "gcc" path: "/apps/all/GCCcore/7.1.0/bin/gcc" }
|
|
cxx_flag: "-std=c++0x"
|
|
- linker_flag: "-lstdc++"
|
|
- linker_flag: "-B/usr/bin/"
|
|
+ linker_flag: "-lstdc++, -W1"
|
|
+ linker_flag: "-B/apps/all/binutils/2.28-GCCcore-7.1.0/bin"
|
|
|
|
# TODO(bazel-team): In theory, the path here ought to exactly match the path
|
|
# used by gcc. That works because bazel currently doesn't track files at
|
|
# absolute locations and has no remote execution, yet. However, this will need
|
|
# to be fixed, maybe with auto-detection?
|
|
- cxx_builtin_include_directory: "/usr/lib/gcc/"
|
|
- cxx_builtin_include_directory: "/usr/local/include"
|
|
- cxx_builtin_include_directory: "/usr/include"
|
|
- tool_path { name: "gcov" path: "/usr/bin/gcov" }
|
|
+ cxx_builtin_include_directory: "/apps/all/GCCcore/7.1.0/lib/gcc/x86_64-pc-linux-gnu/7.1.0/include"
|
|
+ cxx_builtin_include_directory: "/apps/all/GCCcore/7.1.0/lib/gcc/x86_64-pc-linux-gnu/7.1.0/include-fixed/"
|
|
+ cxx_builtin_include_directory: "/apps/all/GCCcore/7.1.0/include/c++/7.1.0"
|
|
+ tool_path { name: "gcov" path: "/apps/all/GCCcore/7.1.0/bin/gcov" }
|
|
|
|
# C(++) compiles invoke the compiler (as that is the one knowing where
|
|
# to find libraries), but we provide LD so other rules can invoke the linker.
|
|
- tool_path { name: "ld" path: "/usr/bin/ld" }
|
|
+ tool_path { name: "ld" path: "/apps/all/binutils/2.28-GCCcore-7.1.0/bin/ld" }
|
|
|
|
- tool_path { name: "nm" path: "/usr/bin/nm" }
|
|
- tool_path { name: "objcopy" path: "/usr/bin/objcopy" }
|
|
+ tool_path { name: "nm" path: "/apps/all/binutils/2.28-GCCcore-7.1.0/bin/nm" }
|
|
+ tool_path { name: "objcopy" path: "/apps/all/binutils/2.28-GCCcore-7.1.0/bin/objcopy" }
|
|
objcopy_embed_flag: "-I"
|
|
objcopy_embed_flag: "binary"
|
|
- tool_path { name: "objdump" path: "/usr/bin/objdump" }
|
|
- tool_path { name: "strip" path: "/usr/bin/strip" }
|
|
+ tool_path { name: "objdump" path: "/apps/all/binutils/2.28-GCCcore-7.1.0/bin/objdump" }
|
|
+ tool_path { name: "strip" path: "/apps/all/binutils/2.28-GCCcore-7.1.0/bin/strip" }
|
|
|
|
# Anticipated future default.
|
|
unfiltered_cxx_flag: "-no-canonical-prefixes"
|