Bug 32834 – Compiling openmotif-2.2.2-r1 fails with errors

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Thomas Schweikle 2003-11-05 16:57:25 UTC]

This is for openmotive-2.2.2-r1. It gives this error while compiling:

make[3]: *** [send.o] Error 1
make[3]: Leaving directory `/var/tmp/portage/openmotif-2.2.2-r1/work/openMotif-2.2.2/clients/mwm/WmW
smLib'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/openmotif-2.2.2-r1/work/openMotif-2.2.2/clients/mwm'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/openmotif-2.2.2-r1/work/openMotif-2.2.2/clients'
make: *** [all-recursive] Error 1

!!! ERROR: x11-libs/openmotif-2.2.2-r1 failed.
!!! Function src_compile, Line 38, Exitcode 2
!!! make failed

The error did not vanish within a 10 days period and an "emerge sync".

[Comment 1 Heinrich Wendel (RETIRED) 2003-11-06 11:47:23 UTC]

please post a complete log of the merge process and 'emerge info'

[Comment 2 Thomas Schweikle 2003-11-06 13:35:41 UTC]

Created attachment 20354 [details]
Log from "emerge openmotif"

Compressed log from commands
- emerge openmotif
- emerge info

as requested

[Comment 3 Thomas Schweikle 2003-11-06 13:39:02 UTC]

complete list of commands used to create the log:
emerge sync
emerge openmotiv > openmotif-emerge.log 2>&1
emerge info > openmotif-info.log 2>&1
tar -cvzf openmotif-emerge.tar.gz openmotif-emerge.log openmotif-info.log

[Comment 4 Heinrich Wendel (RETIRED) 2003-11-09 05:19:13 UTC]

do you have lesstif installed? if remove it, install openmotif and then reinstall
it

[Comment 5 Thomas Schweikle 2003-11-10 00:22:05 UTC]

openmotif-2.2.2-r1 is compiling now. Could we have a warning about lesstif
interfering with openmotif? And it must be removed before emerging openmotif,
then emerging lesstif again (to keep some other applications working)?

[Comment 6 Heinrich Wendel (RETIRED) 2003-11-13 05:24:22 UTC]

added a message when make fails :)

[Comment 7 Heinrich Wendel (RETIRED) 2003-12-29 04:52:13 UTC]

*** Bug 36709 has been marked as a duplicate of this bug. ***