Forums

Skip to content

Advanced search
  • Quick links
    • Unanswered topics
    • Active topics
    • Search
  • FAQ
  • Login
  • Register
  • Board index Assistance Portage & Programming
  • Search

dev-lisp/ecl-24.5.10 won't install

Problems with emerge or ebuilds? Have a basic programming question about C, PHP, Perl, BASH or something else?
Post Reply
Advanced search
4 posts • Page 1 of 1
Author
Message
juniper
l33t
l33t
User avatar
Posts: 986
Joined: Fri Oct 22, 2004 12:03 am
Location: we the north

dev-lisp/ecl-24.5.10 won't install

  • Quote

Post by juniper » Sun Jan 25, 2026 6:58 pm

Hello all,

I don't actually care about this package but it is being pulled in by something else i want to install.

Here is the error just before emerging craps out.

Code: Select all

make[4]: Entering directory '/var/tmp/portage/dev-lisp/ecl-24.5.10/work/ecl-24.5.10/build/libffi'
 /bin/mkdir -p '/var/tmp/portage/dev-lisp/ecl-24.5.10/work/ecl-24.5.10/build/pkgconfig'
 /bin/mkdir -p '/var/tmp/portage/dev-lisp/ecl-24.5.10/work/ecl-24.5.10/build'
 /usr/lib/portage/python3.13/ebuild-helpers/xattr/install -c -m 644 libffi.pc '/var/tmp/portage/dev-lisp/ecl-24.5.10/work/ecl-24.5.10/build/pkgconfig'
 /bin/sh ./libtool   --mode=install /usr/lib/portage/python3.13/ebuild-helpers/xattr/install -c   libffi.la '/var/tmp/portage/dev-lisp/ecl-24.5.10/work/ecl-24.5.10/build'
libtool: install: /usr/lib/portage/python3.13/ebuild-helpers/xattr/install -c .libs/libffi.lai /var/tmp/portage/dev-lisp/ecl-24.5.10/work/ecl-24.5.10/build/libffi.la
libtool: install: /usr/lib/portage/python3.13/ebuild-helpers/xattr/install -c .libs/libffi.a /var/tmp/portage/dev-lisp/ecl-24.5.10/work/ecl-24.5.10/build/libffi.a
libtool: install: chmod 644 /var/tmp/portage/dev-lisp/ecl-24.5.10/work/ecl-24.5.10/build/libffi.a
libtool: install: x86_64-pc-linux-gnu-ranlib /var/tmp/portage/dev-lisp/ecl-24.5.10/work/ecl-24.5.10/build/libffi.a
libtool: finish: PATH="/usr/lib/portage/python3.13/ebuild-helpers/xattr:/usr/lib/portage/python3.13/ebuild-helpers:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/
lib/llvm/21/bin:/sbin" ldconfig -n /var/tmp/portage/dev-lisp/ecl-24.5.10/work/ecl-24.5.10/build
----------------------------------------------------------------------
Libraries have been installed in:
   /var/tmp/portage/dev-lisp/ecl-24.5.10/work/ecl-24.5.10/build

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the '-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the 'LD_LIBRARY_PATH' environment variable
     during execution
   - add LIBDIR to the 'LD_RUN_PATH' environment variable
     during linking
   - use the '-Wl,-rpath -Wl,LIBDIR' linker flag
   - have your system administrator add LIBDIR to '/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
make[4]: Leaving directory '/var/tmp/portage/dev-lisp/ecl-24.5.10/work/ecl-24.5.10/build/libffi'
make[3]: Leaving directory '/var/tmp/portage/dev-lisp/ecl-24.5.10/work/ecl-24.5.10/build/libffi'
make[2]: Leaving directory '/var/tmp/portage/dev-lisp/ecl-24.5.10/work/ecl-24.5.10/build/libffi'
Building libeclmin.a...
make[2]: Entering directory '/var/tmp/portage/dev-lisp/ecl-24.5.10/work/ecl-24.5.10/build/c'
/var/tmp/portage/dev-lisp/ecl-24.5.10/work/ecl-24.5.10/src/c/dpp.c:112:13: error: ‘bool’ cannot be defined via ‘typedef’
  112 | typedef int bool;
      |             ^~~~
/var/tmp/portage/dev-lisp/ecl-24.5.10/work/ecl-24.5.10/src/c/dpp.c:112:13: note: ‘bool’ is a keyword with ‘-std=c23’ onwards
/var/tmp/portage/dev-lisp/ecl-24.5.10/work/ecl-24.5.10/src/c/dpp.c:112:1: warning: useless type name in empty declaration
  112 | typedef int bool;
      | ^~~~~~~
make[2]: *** [Makefile:114: dpp] Error 1
make[2]: Leaving directory '/var/tmp/portage/dev-lisp/ecl-24.5.10/work/ecl-24.5.10/build/c'
make[1]: *** [Makefile:132: libeclmin.a] Error 2
make[1]: *** Waiting for unfinished jobs....
macros.txi:135: warning: redefining Texinfo language command: @seealso
manual.txi:29: warning: @noindent is useless inside of a paragraph
manual.txi:31: warning: @noindent is useless inside of a paragraph
characters.txi:12: warning: node name with index entries should not contain `. '
make[3]: Leaving directory '/var/tmp/portage/dev-lisp/ecl-24.5.10/work/ecl-24.5.10/build/doc/manual'
make[2]: Leaving directory '/var/tmp/portage/dev-lisp/ecl-24.5.10/work/ecl-24.5.10/build/doc'
make[1]: Leaving directory '/var/tmp/portage/dev-lisp/ecl-24.5.10/work/ecl-24.5.10/build'
make: *** [Makefile:65: all] Error 2
 * ERROR: dev-lisp/ecl-24.5.10::gentoo failed (compile phase):
 *   emake failed
 *
 * If you need support, post the output of `emerge --info '=dev-lisp/ecl-24.5.10::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=dev-lisp/ecl-24.5.10::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/dev-lisp/ecl-24.5.10/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-lisp/ecl-24.5.10/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-lisp/ecl-24.5.10/work/ecl-24.5.10'
 * S: '/var/tmp/portage/dev-lisp/ecl-24.5.10/work/ecl-24.5.10'

>>> Failed to emerge dev-lisp/ecl-24.5.10, Log file:

>>>  '/var/tmp/portage/dev-lisp/ecl-24.5.10/temp/build.log'

 * Messages for package dev-lisp/ecl-24.5.10:

 * ERROR: dev-lisp/ecl-24.5.10::gentoo failed (compile phase):
 *   emake failed
 * If you need support, post the output of `emerge --info '=dev-lisp/ecl-24.5.10::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=dev-lisp/ecl-24.5.10::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/dev-lisp/ecl-24.5.10/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-lisp/ecl-24.5.10/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-lisp/ecl-24.5.10/work/ecl-24.5.10'
 * S: '/var/tmp/portage/dev-lisp/ecl-24.5.10/work/ecl-24.5.10'

and here is the output of emerge --info '=dev-lisp/ecl-24.5.10::gentoo'
Top
Hu
Administrator
Administrator
Posts: 24380
Joined: Tue Mar 06, 2007 5:38 am

  • Quote

Post by Hu » Sun Jan 25, 2026 7:48 pm

You are using gcc-15. Per https://gcc.gnu.org/gcc-15/porting_to.html:

Code: Select all

 GCC 15 changes the default language version for C compilation from -std=gnu17 to -std=gnu23. If your code relies on older versions of the C standard, you will need to either add -std= to your build flags, or port your code to C23. C23 brings the following changes:

...

New keywords

C23 added various new keywords, including bool, true, false, nullptr, and thread_local. Code that uses these for identifiers will need changing. For example typedef int bool; will fail with:


<source>:1:13: error: 'bool' cannot be defined via 'typedef'
    1 | typedef int bool;
      |             ^~~~
<source>:1:13: note: 'bool' is a keyword with '-std=c23' onwards
<source>:1:1: warning: useless type name in empty declaration
    1 | typedef int bool;
      | ^~~~~~~
This looks like exactly your problem. As a workaround, compile the code with an older C standard. Long term, this code needs to be fixed.
Top
juniper
l33t
l33t
User avatar
Posts: 986
Joined: Fri Oct 22, 2004 12:03 am
Location: we the north

  • Quote

Post by juniper » Sun Jan 25, 2026 9:07 pm

Indeed. I suspected that might be the problem, so I was in the middle of emerging gcc:14 as you replied.

I am on gcc:15, but that is the current stable gcc.

Anyway, I emerged ecl with gcc 14 and it worked. I am trying to install sagemath (from an overlay) and it pulls in maxima which is pulling in ecl. ecl is in the main gentoo tree, so I assume it will be updated to use gcc 15 at some point.

In any case, I compiled ecl with gcc. I will resume compilation of the rest with gcc 15.
Top
GDH-gentoo
Advocate
Advocate
User avatar
Posts: 2110
Joined: Sat Jul 20, 2019 7:02 pm
Location: South America

  • Quote

Post by GDH-gentoo » Mon Jan 26, 2026 1:03 am

This error seems to be the one filed as bug #945043.
NeddySeagoon wrote:I'm not a witch, I'm a retired electronics engineer :)
Ionen wrote:As a packager I just don't want things to get messier with weird build systems and multiple toolchains requirements though :)
Top
Post Reply

4 posts • Page 1 of 1

Return to “Portage & Programming”

Jump to
  • Assistance
  • ↳   News & Announcements
  • ↳   Frequently Asked Questions
  • ↳   Installing Gentoo
  • ↳   Multimedia
  • ↳   Desktop Environments
  • ↳   Networking & Security
  • ↳   Kernel & Hardware
  • ↳   Portage & Programming
  • ↳   Gamers & Players
  • ↳   Other Things Gentoo
  • ↳   Unsupported Software
  • Discussion & Documentation
  • ↳   Documentation, Tips & Tricks
  • ↳   Gentoo Chat
  • ↳   Gentoo Forums Feedback
  • ↳   Duplicate Threads
  • International Gentoo Users
  • ↳   中文 (Chinese)
  • ↳   Dutch
  • ↳   Finnish
  • ↳   French
  • ↳   Deutsches Forum (German)
  • ↳   Diskussionsforum
  • ↳   Deutsche Dokumentation
  • ↳   Greek
  • ↳   Forum italiano (Italian)
  • ↳   Forum di discussione italiano
  • ↳   Risorse italiane (documentazione e tools)
  • ↳   Polskie forum (Polish)
  • ↳   Instalacja i sprzęt
  • ↳   Polish OTW
  • ↳   Portuguese
  • ↳   Documentação, Ferramentas e Dicas
  • ↳   Russian
  • ↳   Scandinavian
  • ↳   Spanish
  • ↳   Other Languages
  • Architectures & Platforms
  • ↳   Gentoo on ARM
  • ↳   Gentoo on PPC
  • ↳   Gentoo on Sparc
  • ↳   Gentoo on Alternative Architectures
  • ↳   Gentoo on AMD64
  • ↳   Gentoo for Mac OS X (Portage for Mac OS X)
  • Board index
  • All times are UTC
  • Delete cookies

© 2001–2026 Gentoo Foundation, Inc.

Powered by phpBB® Forum Software © phpBB Limited

Privacy Policy