Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#41042 closed defect (invalid)

openmotif on mavericks does not build

Reported by: fabian@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.2.1
Keywords: mavericks Cc: josephwinston (Joseph Winston), ryandesign (Ryan Schmidt), jean-daniel.pauget@…
Port: openmotif

Description

$ uname -a
Darwin palmtree 13.0.0 Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64 x86_64

$ port version
Version: 2.2.1

$ sudo port clean openmotif
--->  Cleaning openmotif

$ sudo port install openmotif
--->  Computing dependencies for openmotif
--->  Cleaning openmotif
--->  Updating database of binaries: 100.0%
--->  Scanning binaries for linking errors: 100.0%
--->  No broken files found.

$ sudo port upgrade outdated
--->  Fetching archive for openmotif
--->  Attempting to fetch openmotif-2.3.4_1.darwin_13.x86_64.tbz2 from http://packages.macports.org/openmotif
--->  Attempting to fetch openmotif-2.3.4_1.darwin_13.x86_64.tbz2 from http://lil.fr.packages.macports.org/openmotif
--->  Attempting to fetch openmotif-2.3.4_1.darwin_13.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/openmotif
--->  Computing dependencies for openmotif
--->  Fetching distfiles for openmotif
--->  Verifying checksums for openmotif
--->  Extracting openmotif
--->  Applying patches to openmotif
--->  Configuring openmotif
--->  Building openmotif
Error: org.macports.build for port openmotif returned: command execution failed
Please see the log file for port openmotif for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_openmotif/openmotif/main.log
Error: Unable to upgrade port: 1
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets

I will append main.log

Attachments (2)

main.log (803.8 KB) - added by fabian@… 7 years ago.
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_openmotif/openmotif/main.log
freshinstall-main.log (875.3 KB) - added by jean-daniel.pauget@… 7 years ago.

Download all attachments as: .zip

Change History (12)

Changed 7 years ago by fabian@…

Attachment: main.log added

/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_openmotif/openmotif/main.log

comment:1 Changed 7 years ago by mf2k (Frank Schima)

Keywords: mavericks added; openmotif removed

comment:2 Changed 7 years ago by ryandesign (Ryan Schmidt)

Summary: openmotiv on mavericks does not buildopenmotif on mavericks does not build

openmotif builds fine for me on Mavericks. Have you installed Xcode 5.0.1 and installed the command line tool by running xcode-select --install?

comment:3 Changed 7 years ago by fabian@…

Thanks ryan. To be sure I just redownloaded the command line tools for 10.9 from developer.apple.com and reinstalled them. xcode-select --install fails with a network error, it seems that this is a common problem. Unfortunately reinstalling the command line tools didn't fix the problem. I have Xcode 5.1 installed. I also tried cleaning the port (and even port clean all) without success. I don't have time right now to dig deeper into this and since it's working on a new/clean box I guess the bug can be closed, even though I can't recall fancy experiments that I've done that could have somehow "poisoned" the box.

I am trying (for comparison) on a brand new mac to install open motif with macports. It works just fine there, so the machine where I'm having problem must be in a bad state.

comment:4 Changed 7 years ago by josephwinston (Joseph Winston)

Cc: josephwinston@… added

Cc Me!

comment:5 Changed 7 years ago by ryandesign (Ryan Schmidt)

Cc: ryandesign@… added

I've rebuilt openmotif a few times, trying to get my environment as similar to yours as possible, and I've gotten to the point where our configure and build phases produce identical log output, right up to the point where mine continues while yours fails with

:info:build Severe: internal error - submit defect report
:info:build make[3]: *** [xmanimate.uid] Error 1

This is an openmotif error message, so I suppose it's the developers of openmotif to whom you have to submit that report.

Before doing so, I'd just ask you to verify that you did follow the migration instructions when upgrading to Mavericks.

comment:6 Changed 7 years ago by fabian@…

Thanks for pointing me to the wiki, I didn't expect that it was required to reinstall everything as if from scratch. After that Openmotif builds. It would probably be a good idea that when Macports detects that the version of the OS changed, it points the user to that twiki. Since a port selfupdate worked and most (for me at least all except Openmotif) ports kept working I was assuming that I am on the right track, but as it turns out I was completely wrong.

comment:7 in reply to:  6 Changed 7 years ago by ryandesign (Ryan Schmidt)

Resolution: invalid
Status: newclosed

Replying to fabian@…:

It would probably be a good idea that when Macports detects that the version of the OS changed, it points the user to that twiki.

I would like that, but at present I don't think MacPorts keeps track of what version of OS X it was last used with, so it can't tell when that has changed.

comment:8 in reply to:  5 Changed 7 years ago by jean-daniel.pauget@…

Replying to ryandesign@…:

I've rebuilt openmotif a few times, trying to get my environment as similar to yours as possible, and I've gotten to the point where our configure and build phases produce identical log output, right up to the point where mine continues while yours fails with

:info:build Severe: internal error - submit defect report
:info:build make[3]: *** [xmanimate.uid] Error 1

This is an openmotif error message, so I suppose it's the developers of openmotif to whom you have to submit that report.

Before doing so, I'd just ask you to verify that you did follow the migration instructions when upgrading to Mavericks.

I'm afraid I have a very close trouble with a fresh install, i.e. :

I rename /opt/local out of the way and also /Applications/Macports/Python...

I install macport 2.2.1-10.9

port install openmotif reaches an internal error : (end of main.log)

:info:build make[3]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_openmotif/openmotif/work/motif-2.3.4/demos/programs/getsubres'
:info:build Making all in hellomotif
:info:build make[3]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_openmotif/openmotif/work/motif-2.3.4/demos/programs/hellomotif'
:info:build /usr/bin/clang -DHAVE_CONFIG_H -I. -I../../../include -I../../../lib/Xm -I./../../../lib -I../../../lib -I/opt/local/include   -I/opt/local/include -I/opt/local/include  -pipe -Os -arch x86_64 -Wall -g -fno-strict-aliasing -Wno-unused -Wno-comment -fno-tree-ter -I/opt/local/include -I/opt/local/include/freetype2 -I/opt/local/include -I/opt/local/include/freetype2 -I/opt/local/include    -MT hellomotif.o -MD -MP -MF .deps/hellomotif.Tpo -c -o hellomotif.o hellomotif.c
:info:build clang: warning: argument unused during compilation: '-fno-tree-ter'
:info:build mv -f .deps/hellomotif.Tpo .deps/hellomotif.Po
:info:build /bin/sh ../../../libtool  --tag=CC   --mode=link /usr/bin/clang  -pipe -Os -arch x86_64 -Wall -g -fno-strict-aliasing -Wno-unused -Wno-comment -fno-tree-ter -I/opt/local/include -I/opt/local/include/freetype2 -I/opt/local/include -I/opt/local/include/freetype2 -I/opt/local/include     -L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 -o hellomotif hellomotif.o ../../../lib/Xm/libXm.la ../../../lib/Mrm/libMrm.la -lXp -liconv  -L/opt/local/lib -lXft -lXrender -L/opt/local/lib -lXft  -ljpeg -lpng
:info:build libtool: link: /usr/bin/clang -pipe -Os -arch x86_64 -Wall -g -fno-strict-aliasing -Wno-unused -Wno-comment -fno-tree-ter -I/opt/local/include -I/opt/local/include/freetype2 -I/opt/local/include -I/opt/local/include/freetype2 -I/opt/local/include -Wl,-headerpad_max_install_names -arch x86_64 -o .libs/hellomotif hellomotif.o  -L/opt/local/lib ../../../lib/Xm/.libs/libXm.dylib ../../../lib/Mrm/.libs/libMrm.dylib /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_openmotif/openmotif/work/motif-2.3.4/lib/Xm/.libs/libXm.dylib -lXmu -lXext -lXt -lSM -lICE -lX11 -lXp -liconv -lXrender -lXft -ljpeg -lpng
:info:build ../../../clients/uil/uil -o hellomotif.uid hellomotif.uil -I./../../../clients/uil -I../../../clients/uil
:info:build
:info:build Severe: internal error - submit defect report
:info:build make[3]: *** [hellomotif.uid] Error 1
:info:build make[3]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_openmotif/openmotif/work/motif-2.3.4/demos/programs/hellomotif'

what could I've done wrong ?

Last edited 7 years ago by jean-daniel.pauget@… (previous) (diff)

Changed 7 years ago by jean-daniel.pauget@…

Attachment: freshinstall-main.log added

comment:9 Changed 7 years ago by ryandesign (Ryan Schmidt)

Cc: jean-daniel.pauget@… added

Have you installed Xcode 5.0.2 (e.g. from the Mac App Store) and its command line tools (e.g. by running xcode-select --install)?

comment:10 in reply to:  9 Changed 7 years ago by jean-daniel.pauget@…

Replying to ryandesign@…:

Have you installed Xcode 5.0.2 (e.g. from the Mac App Store) and its command line tools (e.g. by running xcode-select --install)?

I could not properly perform the Xcode-select --install after the Xcode-5.0.2 upgrade, but as all other ports installed correctly I assumed that was a recent change in xcode.

now that you insisted on that, I manage to have a proper Xcode-select --install after fully restarting the machine (!) ... before that, that command would simply display its help !

okay now it does build, thanks !

Note: See TracTickets for help on using tickets.