Date: Tue, 08 May 2018 02:11:32 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 227918] [PATCH] remove exists check for CROSS_BINUTILS_PREFIX for external clang builds on secondary arches Message-ID: <bug-227918-227-kRuhHF2YRs@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-227918-227@https.bugs.freebsd.org/bugzilla/> References: <bug-227918-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227918 --- Comment #7 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Mark Millard from comment #6) The WITHOUT_LIB32=3D based build completed. So it looks to me like the -B handling logic in the build environment for FreeBSD may need some work for lib32 capable contexts for cross-toolchain builds. I'll note that gcc/g++ reports for its -B option: QUOTE `-B' prefixes that effectively specify directory names also apply to librar= ies in the linker, because the compiler translates these options into `-L' opti= ons for the linker. They also apply to includes files in the preprocessor, beca= use the compiler translates these options into `-isystem' options for the preprocessor. In this case, the compiler appends `include' to the prefix. END QUOTE This would make using a non-directory different than pointing -B to a directory, at least for gcc/g++ cross tools. But I did not find any wording about the handling of multiple -B's on the command line. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-227918-227-kRuhHF2YRs>