When trying to build dev-lisp/gcl-2.6.7: $ emerge -vv dev-lisp/gcl These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] dev-lisp/gcl-2.6.7 USE="X ansi dlopen doc gprof readline -custreloc -debug -emacs -tk" 0 kB Total: 1 package (1 new), Size of downloads: 0 kB >>> Verifying ebuild Manifests... >>> Emerging (1 of 1) dev-lisp/gcl-2.6.7 to / * gcl-2.6.7.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking gcl-2.6.7.tar.gz ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking gcl-2.6.7.tar.gz to /var/tmp/portage/dev-lisp/gcl-2.6.7/work * Applying 2.6.7-fix-configure.in-gentoo.patch ... [ ok ] * Applying gcl-2.6.7-fix-configure.in-bfd.patch ... [ ok ] * No configure.{ac,in} present in 'work'! * * ERROR: dev-lisp/gcl-2.6.7 failed. * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 3151: Called eautoconf * environment, line 922: Called die * The specific snippet of code: * die "No configure.{ac,in} present!"; * The die message: * No configure.{ac,in} present! * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/dev-lisp/gcl-2.6.7/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-lisp/gcl-2.6.7/temp/environment'. * ========================================== $ ls /var/tmp/portage/dev-lisp/gcl-2.6.7/work/gcl-2.6.7 AC_FD_CC RELEASE-2.6.2.html bin configure eval.html gcl1.jpg install.sh majvers misc readme.mingw AC_FD_MSG acconfig.h binutils configure-new.ac eval.tcl gcl2.jpg japitest.lsp makdefs mp unixport COPYING.LIB-2.0 add-defs clcs configure.in faq gmp.patch lsp makedefc.in o utils ChangeLog add-defs.bat cmpnew debian gcl-tk gmp3 ltconfig makefile pcl windows ChangeLog.old add-defs1 comp doc gcl.ico go ltmain.sh man readme xbin README.openbsd ansi-tests config.guess dos gcl.jpg h machine merge.c readme-bin.mingw xgcl-2 RELEASE-2.5.1 bfdtest.c config.sub elisp gcl.png info machines minvers readme.gmp
Please post your `emerge --info' too.
I got the same error: Portage 2.1.4.4 (default/linux/amd64/2008.0/desktop, gcc-4.1.2, glibc-2.6.1-r0, 2.6.26-gentoo-r1 x86_64) ================================================================= System uname: 2.6.26-gentoo-r1 x86_64 Intel(R) Core(TM)2 Duo CPU E8200 @ 2.66GHz Timestamp of tree: Thu, 04 Sep 2008 02:15:02 +0000 app-shells/bash: 3.2_p33 dev-java/java-config: 1.3.7, 2.1.6 dev-lang/python: 2.5.2-r6 dev-python/pycrypto: 2.0.1-r6 sys-apps/baselayout: 1.12.11.1 sys-apps/sandbox: 1.2.18.1-r2 sys-devel/autoconf: 2.13, 2.61-r2 sys-devel/automake: 1.5, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.1 sys-devel/binutils: 2.18-r3 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.26 virtual/os-headers: 2.6.23-r3 ACCEPT_KEYWORDS="amd64" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=nocona -O2" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c /etc/udev/rules.d" CXXFLAGS="-march=nocona -O2" DISTDIR="/usr/portage/distfiles" EMERGE_DEFAULT_OPTS="--deep --with-bdeps y" FEATURES="distlocks metadata-transfer nodoc noinfo parallel-fetch sandbox sfperms strict unemerge-orphans unmerge-orphans userfetch" GENTOO_MIRRORS="http://mirror.gentoo.no/ ftp://trumpetti.atm.tut.fi/gentoo http://gentoo.oregonstate.edu http://www.ibiblio.org/pub/Linux/distributions/gentoo" LDFLAGS="-Wl,-O1" LINGUAS="en en_US" MAKEOPTS="-j3 -s" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://lestat/gentoo-portage" USE="X acl acpi alsa amd64 asf bash-completion berkdb bluetooth branding bzip2 cairo cdr cli cracklib crypt dbus dri dv dvd dvdr dvdread dvi edl eds encode evo fam firefox flac fortran gif gnome gpm gsm gstreamer gtk hal iconv ilbc imlib isdnlog jpeg kde libnotify mad midi mikmod mmx mozilla mp3 mpeg mpeg2 mplayer mudflap multilib mythtv ncurses nls nothemes nptl nptlonly nsplugin nvidia offensive ogg oggvorbis opengl openmp oss pam pcre pdf perl pic png ppds pppd python qt3 qt3support qt4 quicktime rar readline reflection sdl session spell spl sse sse2 ssl startup-notification svg sysfs tcpd theora tiff truetype unicode usb userlocales vorbis wma x264 xanim xorg xulrunner xv xvid xvmc zlib" ALSA_CARDS="hda-intel" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="mouse keyboard" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en en_US" USERLAND="GNU" VIDEO_CARDS="nvidia" Unset: CPPFLAGS, CTARGET, FFLAGS, INSTALL_MASK, LANG, LC_ALL, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
Created attachment 164608 [details] Emerge build log
...and this is my row in /etc/portage/package.use: dev-lisp/gcl X readline -ansi -custreloc -debug -dlopen -doc emacs -gprof -tk
As far as I can see, there is an ebuild error in gcl-2.6.7.ebuild .. You need to change the src_unpack section of your ebuild to something like: src_unpack() { unpack ${A} sed -e "s/gcl-doc/${PF}/g" "${S}"/info/makefile > "${T}"/makefile mv "${T}"/makefile "${S}"/info/makefile epatch "${FILESDIR}"/${PV}-fix-configure.in-gentoo.patch epatch "${FILESDIR}"/${P}-fix-configure.in-bfd.patch local pwd1="${pwd}" ## You can choose any local variable you like ## cd "${S}" ## The Source dir needs to be set, before calling eautoconf ## eautoconf || die cd "${pwd1}" ## Return to previous directory ## } Dont 4get to run 'ebuild gcl-2.6.7.ebuild manifest' in /usr/portage/dev-lisp/gcl afterwards. that should do it.. I hope. If it does, please mark this bug as resolved and notify upstream so they'll fix the ebuild file.
Thanks for replying! (= I added the three lines you suggested, but this time it seems to hang a ways into the configure phase: # Subconfigure of BFD done # ------------------------ # checking for long... yes checking size of long... 8 checking sizeof struct contblock... 16 checking endian.h usability... yes checking endian.h presence... yes checking for endian.h... yes checking "endianness"... little checking for sbrk... yes checking for randomized sbrk... yes checking for randomized brk remedy... After googling a bit I found this: http://bugs.gentoo.org/show_bug.cgi?id=186926 One solution seems to be to disable heap randomization in the kernel. During runtime this will suffice: echo 1 > /proc/sys/kernel/randomize_va_space With your changes and this, the ebuild compiles fine. Perhaps upstream can have a look at axiom? Have any pointers on how to notify upstream?
gr8! then u have a dirty solution for this bug, which is ok for now.. u can mark it as resolved. calling the upstream devs of gcl might be useless, since u need to contact the guy who compiled the gcl-2.6.7 package which might be a gentoo-dev (not from the gcl team). So maybe it's best to contact gentoo-portage devs. they should know what to do with it. you can find a list of the devs at: http://www.gentoo.org/proj/en/portage/index.xml.
Ok, great stuff. I guess then UPSTREAM is the correct resolv status. However, since I'm not the original reporter, I'm not able to resolv. I'll contact one of the devs for advice.
Yotam: Did you mean that I should adress one of the developers listed in the link you pasted? I tried that and he took offense =(. I don't get it. This bug is assigned to common-lisp. Isn't that the group that handles the ebuilds? Same as the maintainers? I have enough info to create a patch at this time. Where do I send it?
I perhaps you menat this url? http://www.gentoo.org/proj/en/lisp/common-lisp/index.xml They're probably reached at common-lisp@gentoo.org, no?
Patches should be posted here, preferably.
Created attachment 166418 [details, diff] Patch to make this ebuild compile. This patch is verified to make the ebuild compile on the setup previously described in this bugzilla.
Created attachment 166420 [details, diff] Patch to make this ebuild compile. This patch is verified to make the ebuild compile on the setup previously described in this bugzilla.
I will resolve this bug, when I have a working internet connection.
I had the same problem. The patch fixed it. Here's hoping it'll be merged into the portage tree soon. Thanks for the patch! :)
*** Bug 248521 has been marked as a duplicate of this bug. ***
I had the same problem; I had apply BOTH suggestions to fix it (src_unpack at comment 5 and pkg_setup at comment 13) and it now compiles. Preceding message in this bug dates four months. Is there a specific reason why not committing the patches to the tree?
Isn't that what the patch does? Both src_unpack and pkg_setup? I've been guessing that they didn't have the time to apply the patch and commit.
Is this relevant for (~)2.6.7-r3?
comment 18. You are right, in fact I applied the suggestions in order of reading of comments by direct editing of the ebuild and my eyes missed the second part of the patch. Sorry for the confusion. (In reply to comment #19) > Is this relevant for (~)2.6.7-r3? 2.6.7-r1 -> fail 2.6.7-r2 -> success 2.6.7-r3 -> success I guess one should stabilize either of the working ebuilds.
RESOLVED WONTFIX. This package is masked for many months. We may make an attempt to revive it, but not in the near future. You're free to reopen if you want. But as Marijn says: # Marijn Schouten <hkBst at gentoo dot org> (29 Jul 2009) # Masked for increasingly many problems. Upstream is flaky and hasn't released since 2005. # Maxima is the only consumer and can be built with sbcl or clisp. # Hopefully upstream will do a release that we can add to revive this package. dev-lisp/gcl
