I encountered a problem as I tried to compile hylafax with gcc 3.3.1 The hylafax configure-script has to be fixed, since gcc -v reports gcc-Version instead of gcc-version for newer versions of gcc (note the "new" capital "V") I attach the respective patch for the configure-script. Unfortunately, I don't have time yet to change the ebuild accordingly, but this should be no problem to the maintainer... ;o) Regards, Torsti :o)
Created attachment 18219 [details, diff] Patch for hylafax 4.1.7 vs. gcc 3.3.1
Thanks. Now testing...
I don't currently have another machine to bump gcc on, but I might have an alternative fix. Try the new ~x86 ebuild and let me know what happens.
Hmm, same here - I don't even have my hylafax-machine running at the moment, since I'm about to move to another town. But I'll check the new ebuild as soon as possible.
a duplicate bug with a newer hylafax version seemed to come across this old problem again, reopening to the package maintainers discretion and appending the newer bug to this original one. Alex
*** Bug 38483 has been marked as a duplicate of this bug. ***
Is this still a problem? I'm beyond the 3.3.1 version of gcc, and 4.1.8-r1 still builds fine for me. If anyone still needs the gcc Version patch, please speak up and I'll make an -r2 ebuild. Here's my build info: rama root # emerge --info Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.1) ================================================================= System uname: 2.6.1 i686 AMD Athlon(tm) XP 2000+ Gentoo Base System version 1.4.3.13 distcc 2.11.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] Autoconf: sys-devel/autoconf-2.59 Automake: sys-devel/automake-1.7.7 AUTOCLEAN="yes" CFLAGS="-march=i686 -mcpu=athlon-xp -Os -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-march=i686 -mcpu=athlon-xp -Os -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache cvs distcc sandbox userpriv usersandbox" GENTOO_MIRRORS="ftp://mirror.iawnet.sandia.gov/pub/gentoo http://gentoo.oregonstate.edu http://www.ibiblio.org/pub/Linux/distributions/gentoo http://trumpetti.atm.tut.fi/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="3dnow X aalib acl acpi alsa apm arts avi berkdb bonobo cdr crypt cups dga directfb dvd emacs encode esd evo fam fbcon foomaticdb freetype freetype2 gb gd gdbm gif gnome gpm gtk gtk2 gtkhtml imap imlib ipv6 java jpeg junit kde lame lcms ldap libg++ libwww mad mikmod mmx motif mozilla mpeg mysql ncurses nls ogg oggvorbis opengl oss pam pda pdflib perl plotutils png python qt quicktime readline samba sasl sdl slang slp spell sse ssl tcltk tcpd tetex tiff truetype vorbis x86 xml xml2 xmms xv zeo zlib"
Created attachment 27028 [details, diff] gcc version patch for hylafax 4.1.8 Since the solution with autoreconf didn't work for me, I created a new patch, ebuild and digest. (See attachments) It works well on my system with gcc-3.3.3 Exthaustive testing and check-in to the rsync tree is requested! ;o) Regards, Torsti
Created attachment 27029 [details] New ebuild file (proposed 4.1.8-r2) @package maintainers: please test it and check in, if possible Regards, Torsti
Created attachment 27030 [details] MD5 digests for 4.1.8-r2
I also got the gcc-error during emerge of hylafax-xxx-r1. My emerge --info looks pretty much the same as the one above. Then I used the three files Torsten posted and emerged from my OVERLAY. It worked flawlessly. Thanks Torsten! Ciao, S
I also got the gcc-error during emerge of hylafax-xxx-r1. My emerge --info looks pretty much the same as the one above. Then I used the three files Torsten posted and emerged from my OVERLAY. It worked flawlessly. Thanks Torsten! Ciao, Sören Lorenz
Now in portage; if someone with the problem can confirm it works for them, I'll close this sucker...
No negative feedback on this, so closing...