Displaying 4 results from an estimated 4 matches for "ac_no_execut".
2004 Nov 22
0
[LLVMdev] Link tests are not allowed after GCC_NO_EXECUTABLES
On Sat, 20 Nov 2004, Henrik Bach wrote:
> I can't figure what this means:
> ------------------
> ...
> checking for g++ that supports -ffunction-sections -fdata-sections... no
> checking for sin in -lm... configure: error: Link tests are not allowed
> after GCC_NO_EXECUTABLES.
> make: *** [configure-target-libstdc++-v3] Error 1
> ------------------
I've never seen
2005 Jan 13
0
[LLVMdev] Link tests are not allowed after GCC_NO_EXECUTABLES
Hi,
John Chriswell wrote:
>You might want to google for AC_NO_EXECUTABLES. It's an autoconf test that
>generates the >behavior you describe. Apparently the GCC folks wrote a new
>version of the macro due to the >above behavior.
As suggested, I googled and found this interesting answer for above error
and behavior:
http://www.mail-archive.com/g...
2004 Nov 20
3
[LLVMdev] Link tests are not allowed after GCC_NO_EXECUTABLES
Hi,
I can't figure what this means:
------------------
...
checking for g++ that supports -ffunction-sections -fdata-sections... no
checking for sin in -lm... configure: error: Link tests are not allowed
after GCC_NO_EXECUTABLES.
make: *** [configure-target-libstdc++-v3] Error 1
------------------
Henrik.
=============================================================
Henrik Bach
Open Source
2020 Nov 06
1
Building an LLVM cross-compiler
...uot;libc"'s headers,
then build the mingw equivalent of the libc.
Here, the "libc" consists of import libraries (that are generated from
symbol listings using llvm-dlltool) and static libraries, so libclang_rt
isn't needed yet. (The autoconf scripts for these bits define
AC_NO_EXECUTABLES, which avoids bailing out due to the compiler not being
able to link an executable.)
After this step, I build the compiler-rt builtins, and this is configured
with -DCMAKE_C_COMPILER_WORKS=1 to (iirc) make it not bail out even though
the toolchain still can't link anything. After build...