curl/types.h got removed in this release. It was empty for a long time (since 2004) but is still included in at least 2 packages.
media-libs/raptor (bug 376001)
Created attachment 280639 [details]
here is the faillog
+ www-client/firefox-5.0-r2 (and btw, shouldn't the ebuild know that firefox's ./configure probes the system for curl?)
(In reply to comment #1)
> + www-client/firefox-5.0-r2 (and btw, shouldn't the ebuild know that firefox's
> ./configure probes the system for curl?)
Could you open a separate bug please? I am looking at the fix and will comment on the new bug. Please make it block this bug. Thx
tangogps and foxtrotgps are also looking for it.
gimp is also looking for it.
x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -pthread -DQT_SHARED -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng14 -I/usr/include/qt4 -I/usr/include/qt4/QtGui -I/usr/include/libdrm -I/usr/include/qt4/QtCore -I/usr/include -DGIMP_DISABLE_DEPRECATED -DGDK_MULTIHEAD_SAFE -DGTK_MULTIHEAD_SAFE -O2 -march=native -pipe -fomit-frame-pointer -floop-interchange -floop-strip-mine -floop-block -Wall -Wdeclaration-after-statement -Wmissing-prototypes -Wmissing-declarations -Winit-self -Wpointer-arith -Wold-style-definition -MT uri-backend-libcurl.o -MD -MP -MF .deps/uri-backend-libcurl.Tpo -c -o uri-backend-libcurl.o uri-backend-libcurl.c
uri-backend-libcurl.c:27:24: erreur fatale: curl/types.h : Aucun fichier ou dossier de ce type
To both of you, Miguel and Cyril, and anyone else who thinks about posting to this bug: This is a tracker, that means _no_ reports at all in this bug.
Please file a new bug instead and make it block this one. It's impossible to track failures and fixes in just one bug.
Curl maintainers, please either pmask >=curl-7.21.7 or readd types.h in curl-7.21.7-r3. This update broke too much stuff all over the tree.
The fix is simple, everyone not fixing this in <24h is just lazy. Also, .7 is a security bump.
(In reply to comment #7)
> The fix is simple, everyone not fixing this in <24h is just lazy. Also, .7
> is a security bump.
@Christoph. This bug looks like its resolved. Should it be closed? (Trying to pick up from where you left off here)
Sorry, missed your comment. Guess this can be closed, yeah.