Summary: | gnome2-utils.eclass: gnome2_disable_deprecation_warning(): should not add $(NULL) to configure (was: gnome-base/nautilus-3.6.3 - ./configure: line 16204: NULL: command not found) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | iGentoo <AlphatPC> |
Component: | Eclasses | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alexander, esigra, gmt |
Priority: | Normal | Keywords: | NeedPatch |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=530490 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 262490 | ||
Attachments: |
nautilus-3.6.3-build.log
/var/tmp/portage/gnome-base/nautilus-3.6.3/work/nautilus-3.6.3/configure |
Description
iGentoo
2012-12-27 12:41:40 UTC
Created attachment 333472 [details]
/var/tmp/portage/gnome-base/nautilus-3.6.3/work/nautilus-3.6.3/configure
This is most likely caused by the eclass replacing -D*DISABLED_DEPRECATED by $(NULL) which seems inappropriate in configure. However, it does not make the build fail right ? (In reply to comment #2) > This is most likely caused by the eclass replacing -D*DISABLED_DEPRECATED by > $(NULL) which seems inappropriate in configure. > > However, it does not make the build fail right ? No, it doesn't. Thanks for the report. I've fixed the nautilus ebuild to avoid this error; but the real fix should be in gnome2-utils.eclass - we need to find a better way to handle this situation. Probably we should be using different sed commands for configure and for Makefile.in's. + 27 Dec 2012; Alexandre Rostovtsev <tetromino@gentoo.org> + nautilus-3.6.3.ebuild: + Avoid spurious "NULL: command not found" warnings (bug #448822, thanks to + Alphat-PC). Same problem with gtksourceview: ./gtksourceview-3.12.2:20141124-220501.log:./configure: line 12013: NULL: command not found ./gtksourceview-3.12.2:20141124-220501.log:./configure: line 12013: NULL: command not found ./gtksourceview-3.12.2:20141124-220501.log:./configure: line 12013: NULL: command not found ./gtksourceview-3.12.2:20141124-220501.log:./configure: line 12013: NULL: command not found ./gtksourceview-3.12.2:20141124-220501.log:./configure: line 12013: NULL: command not found vm3020 ~ # sed -n '12006,12013p' /var/tmp/portage/x11-libs/gtksourceview-3.12.2/work/gtksourceview-3.12.2/configure if test "$enable_deprecations" = "no"; then DISABLE_DEPRECATED_CFLAGS="\ $(NULL) \ $(NULL) \ $(NULL) \ $(NULL) \ $(NULL) \ -DGSEAL_ENABLE" How would $(/bin/true) work instead of $(NULL)? (In reply to Pacho Ramos from comment #6) > How would $(/bin/true) work instead of $(NULL)? It will not work in Makefiles. In configure you can just replace defines with empty string. (In reply to Alexander Tsoy from comment #7) > (In reply to Pacho Ramos from comment #6) > > How would $(/bin/true) work instead of $(NULL)? > > It will not work in Makefiles. Hmm.. no, should work, but it is hacky. :) (In reply to Alexander Tsoy from comment #8) > (In reply to Alexander Tsoy from comment #7) > > (In reply to Pacho Ramos from comment #6) > > > How would $(/bin/true) work instead of $(NULL)? > > > > It will not work in Makefiles. > > Hmm.. no, should work, but it is hacky. :) Well... but it looks like the best solution to me still :| Anyway, I don't see any damage on that $(NULL) warnings (they are not really a problem and we know where are they coming from) *** Bug 566202 has been marked as a duplicate of this bug. *** Any problem with going with $(/bin/true) finally? [master a9ceaad] eclass/gnome2-utils.eclass: prevent spurious warnings (#448822) 1 file changed, 2 insertions(+), 2 deletions(-) |