Bugzilla Bug 152727

I have f2c installed in my box but the GNU Octave ebuild 2.1.73 still complains
that it needs a fortran compiler from GCC.
I used to compile octave with f2c instead of g77 and it always worked fine.

(In reply to comment #0)
> I have f2c installed in my box but the GNU Octave ebuild 2.1.73 still complains
> that it needs a fortran compiler from GCC.
> I used to compile octave with f2c instead of g77 and it always worked fine.
> 

We need your emerge --info please. If you are using gcc-4.x I don't think
f2c will work anymore and you will need gfortran.

Best,
Markus

# emerge --info
Portage 2.1.2_rc1 (default-linux/ppc/ppc32/2006.1/G3, gcc-4.1.1, glibc-2.4-r4,
2.6.18-gentoo ppc)
=================================================================
System uname: 2.6.18-gentoo ppc 750FX
Gentoo Base System version 1.12.5
Last Sync: Sat, 28 Oct 2006 07:50:01 +0000
app-admin/eselect-compiler: [Not Present]
dev-java/java-config: 1.3.7, 2.0.30
dev-lang/python:     2.4.3-r4
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     [Not Present]
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.18.1
sys-devel/autoconf:  2.13, 2.60
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
sys-devel/binutils:  2.17
sys-devel/gcc-config: 1.3.14
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.17-r1
ACCEPT_KEYWORDS="ppc ~ppc"
AUTOCLEAN="yes"
CBUILD="powerpc-unknown-linux-gnu"
CFLAGS="-O3 -pipe -mcpu=G3 -fno-strict-aliasing"
CHOST="powerpc-unknown-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config
/usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf
/etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c"
CXXFLAGS="-O3 -pipe -mcpu=G3 -fno-strict-aliasing"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks metadata-transfer parallel-fetch sandbox sfperms
strict"
GENTOO_MIRRORS="http://mirror.cse.unsw.edu.au/pub/gentoo
http://ftp.swin.edu.au/gentoo"
LINGUAS="en en_US en_GB en_AU"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress
--force --whole-file --delete --delete-after --stats --timeout=180
--exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/portage-overlay"
SYNC="rsync://rsync.au.gentoo.org/gentoo-portage"
USE="ppc X a52 aac acl alsa apache2 arts berkdb bonobo bzip2 c++ cairo cdr cli
cracklib crypt cups dbus djvu dlloader dri dts dv dvd dvdr eds elibc_glibc
emboss encode exif ffmpeg firefox flac gdbm gif gmp gnutls gtkhtml hal howl
iconv idn ieee1394 input_devices_evdev input_devices_keyboard
input_devices_mouse ipv6 isdnlog jpeg jpeg2k kde kernel_linux lcms libg++
libwww linguas_en linguas_en_AU linguas_en_GB linguas_en_US mad matroska mikmod
mime mmap mng modplug mp3 mpeg mpeg4 musicbrainz ncurses nls nptl nptlonly ogg
openexr opengl pam pcre png pnp pppd python qt qt3 qt4 quicktime readline
reflection ruby sasl sdl session speex spell spl ssl subversion svg sysfs
theora threads tiff truetype truetype-fonts type1-fonts udev unicode usb
userland_GNU userlocales utf8 vhosts video_cards_dummy video_cards_fbdev
video_cards_radeon vorbis wifi xinerama xml xorg xv xvid zeroconf zlib"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS,
PORTAGE_RSYNC_EXTRA_OPTS

Yes am I using gcc 4.1, but the gcc bugzilla has no reports of f2c bugs.
Why is f2c not supposed to work with gcc 4?

(In reply to comment #3)
> Yes am I using gcc 4.1, but the gcc bugzilla has no reports of f2c bugs.
> Why is f2c not supposed to work with gcc 4?
> 

My bad, I got confused and f2c should work, of course :)
Could you please post your config.log!

I just had a quick look at octave's configure and it looks
like f2c detection fails since it tries to link against
libf2c.so instead of the static lib.

I'll see if there is an easy fix for that, otherwise we should
probably file a bug upstream.

Thanks,
Markus

Created an attachment (id=100936) [details]
allow f2c as compiler

Created an attachment (id=100937) [details]
fix f2c detection and linkage in octave's configure

Could you please try the above two patches and see if it compiles
through with f2c!

Thanks,
Markus

I tried your two patches and octave compiled fine. I did some tests and it
seems to work properly.

Thanks!

I've merged everything and the new revision, aka octave 2.1.73-r1,
has f2c enabled. Thanks for testing.

Best,
Markus