Bug 662538 – sci-libs/udunits-2.2.20 : * Currently no working fortran compiler is available (see /var/tmp/portage/sci-libs/udunits-2.2.20/temp/_fortran_compile_test.log for information)

• Status: CONFIRMED
• Product: Gentoo Linux

[Description Toralf Förster 2018-07-31 17:04:33 UTC]

 * ERROR: sci-libs/udunits-2.2.20::gentoo failed (setup phase):
 *   Currently no working fortran compiler is available (see /var/tmp/portage/sci-libs/udunits-2.2.20/temp/_fortran_compile_test.log for information)
 * 

  -------------------------------------------------------------------

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 17.0-systemd_libressl_20180727-201601

  -------------------------------------------------------------------

gcc-config -l:
 [1] x86_64-pc-linux-gnu-7.3.0
 [2] x86_64-pc-linux-gnu-7.3.1 *

Available Python interpreters, in order of preference:
  [1]   python3.5
  [2]   python3.6 (fallback)
  [3]   python2.7 (fallback)
Available Ruby profiles:
  [1]   ruby23 (with Rubygems) *



emerge -qpv sci-libs/udunits
[ebuild  N    ] sci-libs/udunits-2.2.20  USE="-static-libs"

[Comment 1 Toralf Förster 2018-07-31 17:04:37 UTC]

Created attachment 541892 [details]
emerge-info.txt

[Comment 2 Toralf Förster 2018-07-31 17:04:40 UTC]

Created attachment 541894 [details]
die.env

[Comment 3 Toralf Förster 2018-07-31 17:04:43 UTC]

Created attachment 541896 [details]
emerge-history.txt

[Comment 4 Toralf Förster 2018-07-31 17:04:46 UTC]

Created attachment 541898 [details]
etc.portage.tbz2

[Comment 5 Toralf Förster 2018-07-31 17:04:49 UTC]

Created attachment 541900 [details]
logs.tbz2

[Comment 6 Toralf Förster 2018-07-31 17:04:52 UTC]

Created attachment 541902 [details]
sci-libs:udunits-2.2.20:20180731-091311.log

[Comment 7 Toralf Förster 2018-07-31 17:06:32 UTC]

Because this warning is new at the tinderbox - IIRC - and b/c it happenes only at one image I'm just curious, why it happened today at about 2 dozen different packages.