Summary: | Grace 5.1.14 configure: error: M*tif has not been found | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Faustin Roman <faustinroman> |
Component: | Current packages | Assignee: | Donnie Berkholz (RETIRED) <dberkholz> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | graphics+disabled, lanius, sci |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Grace config.log
emerge motif-config emerge openmotif emerge openmotif (cont.) emerge grace Grace config.log |
Description
Faustin Roman
2005-03-11 01:34:28 UTC
*** Bug 84824 has been marked as a duplicate of this bug. *** *** Bug 84822 has been marked as a duplicate of this bug. *** *** Bug 84825 has been marked as a duplicate of this bug. *** Lay off the refreshes/submits please... :) sorry... first time bug commiter...;) not a problem. Might want to attach the config.log :) Created attachment 53165 [details]
Grace config.log
configure:8002: gcc -o conftest -O2 -march=pentium4 -fomit-frame-pointer conftest.c -ldnet -lm 1>&5 /usr/lib/gcc/i686-pc-linux-gnu/3.4.3-20050110/../../../../i686-pc-linux-gnu/bin/ld: cannot find -ldnet Donnie: Ok, looks like the libdnet dep is missing. But about the Motif problem, that seems to be motif-config related. At least I can't reproduce it (and I still don't use motif-config). Shot too fast regarding dnet... checking for dnet_ntoa in -ldnet... no checking for dnet_ntoa in -ldnet_stub... no and configure continues happily. The comments in the configure script also look like it's not necessary. Bah. HEre's a happier version. configure:8756: gcc -o conftest -O2 -march=pentium4 -fomit-frame-pointer conftest.c -lXm -lXpm -lXp -lXmu -lXt -lXext -lX11 -lSM -lICE 1>&5 configure:8739:22: Xm/XmAll.h: No such file or directory remerge motif-config,openmotif and the grace Created attachment 53237 [details]
emerge motif-config
Created attachment 53238 [details]
emerge openmotif
Created attachment 53239 [details]
emerge openmotif (cont.)
Created attachment 53240 [details]
emerge grace
Created attachment 53241 [details]
Grace config.log
is there something that I'm doing wrong?
1) emerge --sync 2) emerge motif-config openmotif 3) emerge grace checking for a Motif >= 1002 compatible API... no configure: error: M*tif has not been found !!! Please attach the config.log to your bug report: !!! /var/tmp/portage/grace-5.1.14/work/grace-5.1.14/config.log !!! ERROR: media-gfx/grace-5.1.14 failed. !!! Function econf, Line 485, Exitcode 0 !!! econf failed !!! If you need support, post the topmost build error, NOT this status message. Is there something that I'm doing wrong? It seems is not grace broken or openmotif but motif-config because Grace compiles with lesstif also, but I couldn't make it work with it. I've unmerged lesstif and applyed the workaround described here(Bug 84243 motif-config installs incorrect includes - http://bugs.gentoo.org/show_bug.cgi?id=84243): "I ran 'motif-config --uninstall openmotif-2.2', manually removed /usr/include/{Xm,uil,Mrm} and ran 'motif-config --install openmotif-2.2'" Now emerging grace works. I got the same problem here, but (re)-emerging / unmerging lead always to the same error-messages. I changed into the work-directory and did ./configure manually with no option and it worked. So I would say this is a bug in the ebuild of grace and no openmotif/motif-config issue. Although USE-FLAGS are set to "+fftw +jpeg +netcdf +pdflib +png" I get checking for netCDF API version >= 3.0... no --> support for netCDF is disabled checking for FFTW library >= 2.1.3... no --> using legacy unoptimized FFT code checking for zlib >= 1.0.3... no checking for IJG JPEG software >= 61... no --> JPEG backend is disabled checking for libpng >= 0.9.6... no --> PNG backend is disabled checking for libtiff >= 19960307... no checking for PDFlib >= 4.0.3... no --> PDF driver is disabled in addition to the motif-error, but a simple manual ./configure finds every lib... that's funny: just tried something new: after configuring manually, i tried to emerge grace (which configured grace again) and it succeeded. just double-checked. |