WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: unable to compile  (Read 2087 times)

Offline jls

  • Hero Member
  • *****
  • Posts: 2133
unable to compile
« on: June 14, 2016, 12:45:16 AM »
Hi
I'm trying to compile but I got errors:
Code: [Select]
jls@box:~/Scrivania/rage$ ./autogen.sh
Running aclocal...
Running autoheader...
Running autoconf...
Running libtoolize...
Running automake...
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/home/jls/Scrivania/rage':
configure: error: C compiler cannot create executables
See `config.log' for more details

config.log is attached.
Thanks
dCore user

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9659
Re: unable to compile
« Reply #1 on: June 14, 2016, 10:51:24 AM »
I need to update the gcc related startup scripts, will do that.

Offline jls

  • Hero Member
  • *****
  • Posts: 2133
Re: unable to compile
« Reply #2 on: June 14, 2016, 11:46:30 AM »
Thank you Jason
dCore user

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9659
Re: unable to compile
« Reply #3 on: June 14, 2016, 05:40:48 PM »
Updated the startup scripts to apply to the newer gcc, g++, etc versions in dCore-xenial and dCore-wily.  Right now running a "make all" build on the Linux kernel 4.2.9 in dCore-xenial and all is working as expected.  Let me know if there are still issues.

Offline jls

  • Hero Member
  • *****
  • Posts: 2133
Re: unable to compile
« Reply #4 on: June 15, 2016, 01:08:09 AM »
Hi.
I was trying to compile under trusty.
dCore user

Offline jls

  • Hero Member
  • *****
  • Posts: 2133
Re: unable to compile
« Reply #5 on: June 15, 2016, 10:13:52 AM »
Hi still same errors under trusty, haven't tried others
dCore user

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9659
Re: unable to compile
« Reply #6 on: June 18, 2016, 09:30:20 PM »
I am compiling the 3.16.6 linux kernel with "make all" successfully on dCore-trusty with build-essential installed.  The name and the version of the source  and a link to it you are trying to build would be helpful so I can try and reproduce.  I have made startup script adjustments today, so an update of existing SCEs and another attempt may work. 

Offline jls

  • Hero Member
  • *****
  • Posts: 2133
Re: unable to compile
« Reply #7 on: June 23, 2016, 05:32:57 AM »
Hi
https://git.enlightenment.org/devs/jayji/email.git/
for example.
Actually my goal is to build enlightenment, since the niko2040 ppa is no more up to date.
dCore user

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9659
Re: unable to compile
« Reply #8 on: June 23, 2016, 09:34:40 AM »
On dCore-trusty, below is what I get with that source, it stops where there are the E dependencies that need installing first.  So the build process itself is working in dCore-trusty.


Code: [Select]
root@box:/home/jason/email# ./autogen.sh
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force --warnings=all,error -I m4
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize --copy --force
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
autoreconf: running: /usr/bin/autoconf --force --warnings=all,error
autoreconf: running: /usr/bin/autoheader --force --warnings=all,error
autoreconf: running: automake --add-missing --copy --force-missing --warnings=all,error
configure.ac:40: installing './ar-lib'
configure.ac:40: installing './compile'
configure.ac:43: installing './config.guess'
configure.ac:43: installing './config.sub'
configure.ac:37: installing './install-sh'
configure.ac:37: installing './missing'
src/bin/email/Makefile.am: installing './depcomp'
parallel-tests: installing './test-driver'
autoreconf: Leaving directory `.'
cmp: config.cache-env: No such file or directory
Cleaning configure cache...
configure: creating cache config.cache
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking for ar... ar
checking the archiver (ar) interface... ar
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert i686-pc-linux-gnu file names to i686-pc-linux-gnu format... func_convert_file_noop
checking how to convert i686-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: Initialized email (0.0.99) development=227
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking whether gcc understands -c and -o together... (cached) yes
checking dependency style of gcc... (cached) gcc3
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for doxygen... no
WARNING:
The doxygen program was not found in your execute
You may have doxygen installed somewhere not covered by your path.

If this is the case make sure you have the packages installed, AND
that the doxygen program is in your execute path (see your
shell manual page on setting the $PATH environment variable), OR
alternatively, specify the program to use with --with-doxygen.
configure: WARNING: Warning: no doxygen detected. Documentation will not be built
checking for EFL... no
configure: error: Package requirements (
   eina       >= 1.17.99
   eet        >= 1.17.99
   evas       >= 1.17.99
   ecore      >= 1.17.99
   ecore-file >= 1.17.99
   ecore-con  >= 1.17.99
   edje       >= 1.17.99
   eo         >= 1.17.99
) were not met:

No package 'eina' found
No package 'eet' found
No package 'evas' found
No package 'ecore' found
No package 'ecore-file' found
No package 'ecore-con' found
No package 'edje' found
No package 'eo' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables EFL_CFLAGS
and EFL_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
root@box:/home/jason/email#


Offline jls

  • Hero Member
  • *****
  • Posts: 2133
Re: unable to compile
« Reply #9 on: June 23, 2016, 09:43:18 AM »
I've installed build-essential, libtool and sed, but still error
dCore user

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9659
Re: unable to compile
« Reply #10 on: June 23, 2016, 09:45:30 AM »
Is all SCEs that are loaded up to date? 

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9659
Re: unable to compile
« Reply #11 on: June 23, 2016, 09:55:31 AM »
I added libtool and sed to build-essential's deps now.

Offline jls

  • Hero Member
  • *****
  • Posts: 2133
Re: unable to compile
« Reply #12 on: June 23, 2016, 11:09:22 AM »
Which pkg should be up-to-date? As for build essential, it was reimported just before the tests.
I've to add that there are the trusty-backports under my debextra folder
« Last Edit: June 23, 2016, 11:15:16 AM by jls »
dCore user

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9659
Re: unable to compile
« Reply #13 on: June 23, 2016, 11:23:07 AM »
Any SCE that is being loaded needs to be up to date as I have made some changes in the startup scripts of the gcc related packages.  And not having these changes in your local SCEs may be the problem. 

Offline jls

  • Hero Member
  • *****
  • Posts: 2133
Re: unable to compile
« Reply #14 on: June 26, 2016, 05:11:24 AM »
Hi
Re-importing build-essential without my debextra dir make the compiler work:
below is my debextra:
Code: [Select]
jls@box:~$ cat /opt/debextra/*
http://ppa.launchpad.net/enlightenment-git/ppa/ubuntu trusty main
http://ppa.launchpad.net/niko2040/e19/ubuntu trusty main
 http://ppa.launchpad.net/ferramroberto/lffl/ubuntu trusty main http://dl.google.com/linux/talkplugin/deb/ stable main
http://ppa.launchpad.net/libreoffice/ppa/ubuntu trusty main
http://ppa.launchpad.net/igesef/liferea/ubuntu trusty mainhttp://ppa.launchpad.net/pidgin-developers/ppa/ubuntu trusty main
http://ftp5.gwdg.de/pub/opensuse/repositories/home:/jgeboski/xUbuntu_14.04 ./
http://ppa.launchpad.net/transmissionbt/ppa/ubuntu trusty main http://archive.canonical.com/ubuntu/ trusty partner
http://packages.bodhilinux.com/bodhi trusty main
http://ubuntu.mirror.garr.it/mirrors/ubuntu-archive/ trusty-updates main
http://ubuntu.mirror.garr.it/mirrors/ubuntu-archive/ trusty-updates multiverse
http://ubuntu.mirror.garr.it/mirrors/ubuntu-archive/ trusty-updates restricted
http://ubuntu.mirror.garr.it/mirrors/ubuntu-archive/ trusty-updates universe
http://ubuntu.mirror.garr.it/mirrors/ubuntu-archive/ trusty-backports main
http://ubuntu.mirror.garr.it/mirrors/ubuntu-archive/ trusty-backports multiverse
http://ubuntu.mirror.garr.it/mirrors/ubuntu-archive/ trusty-backports restricted
http://ubuntu.mirror.garr.it/mirrors/ubuntu-archive/ trusty-backports universe
jls@box:~$



ps. I think there is some problem on my system:

Code: [Select]

jls@box:~$ sudo /opt/bootlocal.sh
sudo: /opt/bootlocal.sh: command not found
jls@box:~$ sudo sh /opt/bootlocal.sh
jls@box:~$ head /opt/bootlocal.sh
#!/bin/busybox ash
# put other system startup commands here

TCUSER=$(cat /etc/sysconfig/tcuser)


[ $(hostname) = "vesa" ]  && cp /etc/X11/xorg-vesa.conf /etc/X11/xorg.conf

sudo rm -f /opt/debextra/*
VERSION=`version|awk -F : '{ print $1 }' |awk -F - '{ print $2 }'`
jls@box:~$
dCore user