The C compiler identification is unknown (Solved)

kabbalah · 2016-02-06 04:29:01

Can not build from aur I get this error

==> Extrayendo las fuentes…
  -> Extrayendo qtspell-0.7.4.tar.xz con bsdtar
==> Iniciando build()…
-- The C compiler identification is unknown
-- The CXX compiler identification is GNU 5.3.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- broken
CMake Error at /usr/share/cmake-3.4/Modules/CMakeTestCCompiler.cmake:61 (message):
  The C compiler "/usr/bin/cc" is not able to compile a simple test program.

  It fails with the following output:

   Change Dir: /tmp/yaourt-tmp-julio/aur-qtspell/src/qtspell-0.7.4/build/CMakeFiles/CMakeTmp

  

  Run Build Command:"/usr/bin/make" "cmTC_10faa/fast"

  /usr/bin/make -f CMakeFiles/cmTC_10faa.dir/build.make
  CMakeFiles/cmTC_10faa.dir/build

  make[1]: se entra en el directorio
  '/tmp/yaourt-tmp-julio/aur-qtspell/src/qtspell-0.7.4/build/CMakeFiles/CMakeTmp'


  Building C object CMakeFiles/cmTC_10faa.dir/testCCompiler.c.o

  /usr/bin/cc -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong
  --param=ssp-buffer-size4 -o CMakeFiles/cmTC_10faa.dir/testCCompiler.c.o -c
  /tmp/yaourt-tmp-julio/aur-qtspell/src/qtspell-0.7.4/build/CMakeFiles/CMakeTmp/testCCompiler.c


  cc1: error: ssp-buffer-size4: los argumentos --param deben ser de la forma
  NOMBRE=VALOR

  CMakeFiles/cmTC_10faa.dir/build.make:65: fallo en las instrucciones para el
  objetivo 'CMakeFiles/cmTC_10faa.dir/testCCompiler.c.o'

  make[1]: *** [CMakeFiles/cmTC_10faa.dir/testCCompiler.c.o] Error 1

  make[1]: se sale del directorio
  '/tmp/yaourt-tmp-julio/aur-qtspell/src/qtspell-0.7.4/build/CMakeFiles/CMakeTmp'


  Makefile:126: fallo en las instrucciones para el objetivo 'cmTC_10faa/fast'

  make: *** [cmTC_10faa/fast] Error 2

  

  

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:4 (PROJECT)


-- Configuring incomplete, errors occurred!
See also "/tmp/yaourt-tmp-julio/aur-qtspell/src/qtspell-0.7.4/build/CMakeFiles/CMakeOutput.log".
See also "/tmp/yaourt-tmp-julio/aur-qtspell/src/qtspell-0.7.4/build/CMakeFiles/CMakeError.log".

I have installed Arch Linux x64

Any idea

Last edited by kabbalah (2016-02-06 22:19:03)

jasonwryan · 2016-02-06 04:40:26

kabbalah wrote:

-- Check for working C compiler: /usr/bin/cc -- broken

Any idea

Yeah: that doesn't look too good...

Joel · 2016-02-06 05:10:20

I just test qtspell aur package and compiles as expected:

==> Validando los archivos source con sha256sums…
    qtspell-0.7.4.tar.xz ... Aprobado
==> Extrayendo las fuentes…
  -> Extrayendo qtspell-0.7.4.tar.xz con bsdtar
==> Iniciando build()…
-- The C compiler identification is GNU 5.3.0
-- The CXX compiler identification is GNU 5.3.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29") 
-- Checking for module 'enchant'
--   Found enchant, version 1.6.0
-- Looking for Q_WS_X11
-- Looking for Q_WS_X11 - found
-- Looking for Q_WS_WIN
-- Looking for Q_WS_WIN - not found
-- Looking for Q_WS_QWS
-- Looking for Q_WS_QWS - not found
-- Looking for Q_WS_MAC
-- Looking for Q_WS_MAC - not found
-- Found Qt4: /usr/bin/qmake-qt4 (found version "4.8.7") 
-- Could NOT find Doxygen (missing:  DOXYGEN_EXECUTABLE) 
-- Configuring done
-- Generating done
-- Build files have been written to: /....

the obvious, did you have base-devel installed?

Trilby · 2016-02-06 05:12:15

Please post output in English. In this case, though, it doesn't take any of my Spanish training to see what this message is saying:

cc1: error: ssp-buffer-size4: los argumentos --param deben ser de la forma
  NOMBRE=VALOR

Translation: fix the typo in your makepkg.conf

x33a · 2016-02-06 05:24:19

Moving to "Newbie Corner".

kabbalah · 2016-02-06 14:48:22

Base devel is the first thing that is installed #pacstrap / mnt based base-devel

Trilby · 2016-02-06 16:00:54

So that's a yes? We don't know what you installed. But here it is clear that the compiler is present. But there is a typo in your CFLAGS. Fix the typo.

kabbalah · 2016-02-06 17:16:15

If I install base and base-devel first. Now I post my COMPILE FLAGS

#########################################################################
# ARCHITECTURE, COMPILE FLAGS
#########################################################################
#
CARCH="x86_64"
CHOST="x86_64-unknown-linux-gnu"

#-- Compiler and Linker Flags
# -march (or -mcpu) builds exclusively for an architecture
# -mtune optimizes for an architecture, but builds for whole processor family
CPPFLAGS="-D_FORTIFY_SOURCE=2"
CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size4"
CXXFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4"
LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro"
#-- Make Flags: change this for DistCC/SMP systems
#MAKEFLAGS="-j2"
#-- Debugging flags
DEBUG_CFLAGS="-g -fvar-tracking-assignments"
DEBUG_CXXFLAGS="-g -fvar-tracking-assignments"

I do not know how to do what says Trilby

Last edited by kabbalah (2016-02-06 17:19:29)

Scimmia · 2016-02-06 17:23:11

Trilby nailed it. Have you not been merging your .pacnew files? Or just merging them badly? See https://projects.archlinux.org/svntogit … ges/pacman

Trilby · 2016-02-06 18:16:14

Change ssp-buffer-size4 to ssp-buffer-size=4 (or just remove it).

kabbalah · 2016-02-06 18:31:28

In this page copy this code and change this in my makepkg, and it worked for me

https://wiki.manjaro.org/index.php?title=Makepkg

#########################################################################
# ARCHITECTURE, COMPILE FLAGS
#########################################################################
#
CARCH="x86_64"
CHOST="x86_64-unknown-linux-gnu"

#-- Exclusive: will only run on x86_64
# -march (or -mcpu) builds exclusively for an architecture
# -mtune optimizes for an architecture, but builds for whole processor family
CPPFLAGS="-D_FORTIFY_SOURCE=2"
CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4"
CXXFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4"
LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro"
#-- Make Flags: change this for DistCC/SMP systems
#MAKEFLAGS="-j2"

Thank all

Last edited by kabbalah (2016-02-06 18:32:40)

Scimmia · 2016-02-06 19:23:05

So what is the point of --param=ssp-buffer-size=4? If you're going to move away from the defaults, you should know why.

kabbalah · 2016-02-06 22:21:09

No, I do not know why but eventually worked for me and I could compile from AUR

Trilby · 2016-02-06 22:56:25

It "works" because you fixed the typo. "--param=ssp-buffer-size=4" is an option that gcc understands, "--param=ssp-buffer-size4" is giberish. Scimmia's question was why you have that option included at all, it is not in the default makepkg.conf (it previously was which is most likely why you have it).

Arch Linux

#1 2016-02-06 04:29:01

The C compiler identification is unknown (Solved)

#2 2016-02-06 04:40:26

Re: The C compiler identification is unknown (Solved)

#3 2016-02-06 05:10:20

Re: The C compiler identification is unknown (Solved)

#4 2016-02-06 05:12:15

Re: The C compiler identification is unknown (Solved)

#5 2016-02-06 05:24:19

Re: The C compiler identification is unknown (Solved)

#6 2016-02-06 14:48:22

Re: The C compiler identification is unknown (Solved)

#7 2016-02-06 16:00:54

Re: The C compiler identification is unknown (Solved)

#8 2016-02-06 17:16:15

Re: The C compiler identification is unknown (Solved)

#9 2016-02-06 17:23:11

Re: The C compiler identification is unknown (Solved)

#10 2016-02-06 18:16:14

Re: The C compiler identification is unknown (Solved)

#11 2016-02-06 18:31:28

Re: The C compiler identification is unknown (Solved)

#12 2016-02-06 19:23:05

Re: The C compiler identification is unknown (Solved)

#13 2016-02-06 22:21:09

Re: The C compiler identification is unknown (Solved)

#14 2016-02-06 22:56:25

Re: The C compiler identification is unknown (Solved)

Board footer