Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 889890

Summary: x11-wm/fvwm3-1.0.4-r2 - ../.../FScreen.h: error: expected specifier-qualifier-list before TAILQ_ENTRY
Product: Gentoo Linux Reporter: Toralf Förster <toralf>
Component: Current packagesAssignee: Matt Jolly <kangie>
Status: RESOLVED FIXED    
Severity: normal CC: kangie, proxy-maint
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: emerge-info.txt
emerge-history.txt
environment
etc.clang.tar.bz2
etc.portage.tar.bz2
logs.tar.bz2
temp.tar.bz2
x11-wm:fvwm3-1.0.4-r2:20230105-200015.log

Description Toralf Förster gentoo-dev 2023-01-05 20:03:37 UTC
too long lines were shrinked:

/usr/include/librsvg-2.0/librsvg/rsvg-cairo.h:88:10: note: declared here
   88 | gboolean rsvg_handle_render_cairo (RsvgHandle *handle, cairo_t *cr);
      |          ^~~~~~~~~~~~~~~~~~~~~~~~
x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I..  -I..  -I/usr/include/freetype2 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/sysprof-4 -pthread      -I/usr/include/libpng16  -I/usr/include/librsvg-2.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/incl
x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I..  -I..  -I/usr/include/freetype2 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/sysprof-4 -pthread      -I/usr/include/libpng16  -I/usr/include/librsvg-2.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/incl
In file included from FTips.c:36:
../libs/FScreen.h:79:9: error: expected specifier-qualifier-list before TAILQ_ENTRY
   79 |         TAILQ_ENTRY(screen_info) entry;
      |         ^~~~~~~~~~~

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

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 17.1_desktop_gnome-j4_test-20230104-200049

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

GNUMAKEFLAGS="$GNUMAKEFLAGS --jobserver-style=pipe"
GNUMAKEFLAGS="$GNUMAKEFLAGS --shuffle"
gcc-config -l:
 [1] x86_64-pc-linux-gnu-12 *
clang/llvm (if any):
clang version 15.0.6
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/lib/llvm/15/bin
Configuration file: /etc/clang/clang.cfg
/usr/lib/llvm/15
15.0.6
Python 3.10.9
Available Rust versions:
  [1]   rust-bin-1.66.0 *
The following VMs are available for generation-2:
*)	Eclipse Temurin JDK 17.0.5_p8 [openjdk-bin-17]
Available Java Virtual Machines:
  [1]   openjdk-bin-17  system-vm

php cli (if any):
  [1]   php8.2 *

  HEAD of ::gentoo
commit 10b791f166e452d3e861dccf2184c50c1bde1fae
Author: Repository mirror & CI <repomirrorci@gentoo.org>
Date:   Thu Jan 5 19:17:17 2023 +0000

    2023-01-05 19:17:17 UTC

emerge -qpvO x11-wm/fvwm3
[ebuild  N    ] x11-wm/fvwm3-1.0.4-r2  USE="nls readline svg -bidi -debug -doc -go -lock -netpbm -perl -stroke -tk -vanilla" PYTHON_SINGLE_TARGET="python3_10 -python3_8 -python3_9 -python3_11"
Comment 1 Toralf Förster gentoo-dev 2023-01-05 20:03:38 UTC
Created attachment 847572 [details]
emerge-info.txt
Comment 2 Toralf Förster gentoo-dev 2023-01-05 20:03:40 UTC
Created attachment 847574 [details]
emerge-history.txt
Comment 3 Toralf Förster gentoo-dev 2023-01-05 20:03:41 UTC
Created attachment 847576 [details]
environment
Comment 4 Toralf Förster gentoo-dev 2023-01-05 20:03:42 UTC
Created attachment 847578 [details]
etc.clang.tar.bz2
Comment 5 Toralf Förster gentoo-dev 2023-01-05 20:03:43 UTC
Created attachment 847580 [details]
etc.portage.tar.bz2
Comment 6 Toralf Förster gentoo-dev 2023-01-05 20:03:44 UTC
Created attachment 847582 [details]
logs.tar.bz2
Comment 7 Toralf Förster gentoo-dev 2023-01-05 20:03:45 UTC
Created attachment 847584 [details]
temp.tar.bz2
Comment 8 Toralf Förster gentoo-dev 2023-01-05 20:03:46 UTC
Created attachment 847586 [details]
x11-wm:fvwm3-1.0.4-r2:20230105-200015.log
Comment 9 Matt Jolly gentoo-dev 2024-08-17 07:50:22 UTC
Cannot repro on 1.1.0; We're a good few releases past 1.0.4 now; I think this got fixed upstream at some point.

Major build system changes incoming; we can open a new bug if this happens in a version > 1.1.0.