| Summary: | gtk+-2.4.1 and glib-2.4.1 released | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jason Oliveira <mushroomblue> |
| Component: | New packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | sbh, ticho |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://www.gtk.org | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | patch for gtk+-2.4.1 (against 2.4.0-r1) | ||
|
Description
Jason Oliveira
2004-05-03 14:25:49 UTC
glib compiles fine, but with gtk+, the gtk+-2.4.0-uimanager-zero-becomes-null.patch fails. commented out, and compiled with no issues. The "uimanager-zero-becomes-null" patch is not needed in 2.4.1 anymore, as the issue it patches has been fixed upstream. (http://bugzilla.gnome.org/attachment.cgi?id=26513&action=view) well, that would certainly explain why the patch failed. :) Ok, I can now confirm that both gtk+ 2.4.1 and glib 2.4.1 emerge cleanly. Glib: just a version bump Gtk+: version bump and removed one patch Patch for gtk+ ebuild attached. Created attachment 30684 [details, diff]
patch for gtk+-2.4.1 (against 2.4.0-r1)
This was diff-ed against gtk+-2.4.0-r1.ebuild
dev-libs/glib-2.4.1 failed: checking for C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details. configure:2642: gcc -march=pentium4 -O3 -pipe conftest.c >&5 /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.3/../../../../i686-pc-linux-gnu/bin/ld: u nrecognized option '--as-needed' /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.3/../../../../i686-pc-linux-gnu/bin/ld: u se the --help option for usage information collect2: ld returned 1 exit status configure:2645: $? = 1 configure: failed program was ... open a _new_ bug for a _new_ problem please.. don't litter other bugs with your problem that just happens to involve the same package. Anyway, a quick search would probably have yielded #49363 . The initial bug here got fixed a few days ago btw, forgot to close. |