kdebase3 patch failure

[patrick.gill@…]

I cannot install kdebase3 on Ma 10.6.8 because the file "/System/Library/Frameworks/Tcl.framework/Versions/8.5/Resources/tclIndex" is missing. This file seems to be missing for others and causes trouble in several other tickets too, but I thought reporting it here would be helpful.

To replicate the problem, follow sample output with MacPorts 2.0.3 and OS X 10.6.8:

$ sudo port install koffice
--->  Computing dependencies for koffice
--->  Dependencies to be installed: kdebase3 lcms libexif libwpd libgsf gconf dbus-glib dbus gtk-doc docbook-xml docbook-xml-4.1.2 xmlcatmgr docbook-xml-4.2 docbook-xml-4.3 docbook-xml-4.4 docbook-xml-4.5 docbook-xml-5.0 docbook-xsl docbook-xsl gnome-doc-utils intltool gnome-common p5.12-getopt-long p5.12-pathtools p5.12-scalar-list-utils p5.12-xml-parser intltool iso-codes rarian getopt gtk2 atk gdk-pixbuf2 pango cairo libpixman xorg-xcb-util shared-mime-info orbit2 libidl policykit eggdbus gnome-vfs desktop-file-utils popt gnome-mime-data libbonobo mysql5 ruby wv2
Error: Target org.macports.patch returned: shell command failed (see log for details)
Error: Failed to install kdebase3
Log for kdebase3 is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_kdebase3/kdebase3/main.log
Error: The following dependencies were not installed: kdebase3 lcms libexif libwpd libgsf gconf dbus-glib dbus gtk-doc docbook-xml docbook-xml-4.1.2 xmlcatmgr docbook-xml-4.2 docbook-xml-4.3 docbook-xml-4.4 docbook-xml-4.5 docbook-xml-5.0 docbook-xsl docbook-xsl gnome-doc-utils intltool gnome-common p5.12-getopt-long p5.12-pathtools p5.12-scalar-list-utils p5.12-xml-parser intltool iso-codes rarian getopt gtk2 atk gdk-pixbuf2 pango cairo libpixman xorg-xcb-util shared-mime-info orbit2 libidl policykit eggdbus gnome-vfs desktop-file-utils popt gnome-mime-data libbonobo mysql5 ruby wv2
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

In the log file, there will be the line:

:debug:patch couldn't open "/System/Library/Frameworks/Tcl.framework/Versions/8.5/Resources/tclIndex": no such file or directory

I think that's the culprit. I'm attaching the full log file in case.

Thanks for your help with this! It looks like I'm not the only one with trouble finding /System/Library/Frameworks/Tcl.framework/Versions/8.5/Resources/tclIndex; the directory is there, but no file.

[ryandesign (Ryan Carsten Schmidt)]

No, the tclIndex messages are irrelevant, and the log you attached is also not usable because it is not from a clean build (it contains lines "Skipping completed"). Clean and try again and attach that main.log.

sudo port clean koffice

Note there is another existing ticket about koffice not working (#29583); the koffice port is old and it would surprise me if it worked at all anymore.

[ryandesign (Ryan Carsten Schmidt)]

patrick.gill, can you please respond to the above?

[patrick.gill@…]

Thanks - the previous email hadn't gone through. Sorry for the delay.

I followed your instructions as follows:

sudo port selfupdate
sudo port clean koffice
sudo port install koffice

and got many lines of error-free output until the following:

--->  Fetching archive for koffice
--->  Attempting to fetch koffice-1.6.3_4.darwin_10.x86_64.tbz2 from http://packages.macports.org/koffice
--->  Fetching koffice
--->  Attempting to fetch koffice-1.6.3.tar.bz2 from http://mirrors.mit.edu/kde/stable/koffice-1.6.3/src/
--->  Attempting to fetch kde-admindir-790.tar.bz2 from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/koffice
--->  Verifying checksum(s) for koffice
--->  Extracting koffice
--->  Configuring koffice
--->  Building koffice
Error: Target org.macports.build returned: shell command failed (see log for details)
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

I'm going to attach the new log file; I hope that helps.

Thanks!

Patrick

[patrick.gill@…]

Newer log from failed attempt at installing koffice

[mf2k (Frank Schima)]

That's the wrong log. It's from the successful activation of gdbm.

[patrick.gill@…]

Replying to macsforever2000@…:

That's the wrong log. It's from the successful activation of gdbm.

Where should I look for the right log? The log I attached was the only log in /opt/local/var/macports/logs. Does macports have another log directory?

[mf2k (Frank Schima)]

When you install koffice, if it fails to build, the log location is printed out in Terminal.

[patrick.gill@…]

Replying to macsforever2000@…:

When you install koffice, if it fails to build, the log location is printed out in Terminal.

Unfortunately, terminal only gave me the following:

Core-3:~ patrickgill$ sudo port install koffice
--->  Computing dependencies for gdbm

*snip*

--->  Building koffice
Error: Target org.macports.build returned: shell command failed (see log for details)
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>
Core-3:~ patrickgill$ cd /opt/local

There's no filename mentioned. I ran a spotlight search for files with "log" in them in the macports directory and I got 7 files:

config 2.log
config.log
configure.log
cvs.log
make-drivers.log
make-ksqlite.log
make.log

I will attach them all; unless the log you're looking for either doesn't have "log" in the filename or isn't in the macports folder than I guess I can't help you.

[patrick.gill@…]

By the way, thanks for all your help. If this is dreary rather than interesting don't worry - koffice on a mac isn't critical for me. It would be nice, but it sounds like you're not too optimistic about it working even if this one issue is sorted out.

[mf2k (Frank Schima)]

Please do *not* attach random log files. What is the output of the following?

port version

[patrick.gill@…]

Replying to macsforever2000@…:

Please do *not* attach random log files. What is the output of the following?

port version

It's

Version: 2.0.3

[mf2k (Frank Schima)]

That's weird. It should output the log location. The general directory is /opt/local/var/macports/logs/.

[patrick.gill@…]

Replying to macsforever2000@…:

That's weird. It should output the log location. The general directory is /opt/local/var/macports/logs/.

I agree. It's weird, but the only log I have in /opt/local/var/macports/logs is main.2.log, which you said is the successful activation of gdbm. Strange.

[jmroot (Joshua Root)]

The only somewhat useful log yet attached shows kdebase3 failing to patch, so I guess we'll assume that's the problem...

[clemc@…]

I am seeing the same error 10 months later on a Lion system. I chased that error a bit, realized that kdebase3 is going to great lengths to ensure that autoconfig263 can be found. Then later in the build it's getting an *.ac file that needs 2.65 or later [standard autoconf on my system is showing 2.69 ad well has having the autoconf263 binary)

I'm very interesting in getting this to work, as my son would like to be able to run KEXI for a BSA project. KEXI is not longer distributed by itself, but rather has part of koffice - which is fine if it would install.

Any thoughts/help would be appreciated.

Thanks Clem

[clemc@…]

Trying to attach my error log, the the web server keeps getting the error bellow, contact me off line and I'll see if I can make the error log available if its of any help. Thanks,

Clem

---

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, admin@… and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

[ryandesign (Ryan Carsten Schmidt)]

Replying to clemc@…:

I am seeing the same error 10 months later on a Lion system.

Your error does not look the same; rather, it looks like #38554.

[ryandesign (Ryan Carsten Schmidt)]

Replying to macsforever2000@…:

That's weird. It should output the log location.

Yes, it is weird, but it happens sometimes. See #37093 for this and other weird misbehavior.

[ryandesign (Ryan Carsten Schmidt)]

Replying to jmr@…:

The only somewhat useful log yet attached shows kdebase3 failing to patch, so I guess we'll assume that's the problem...

The patch failure is because it was not a clean attempt, as I explained initially.

There is no actionable information in this bug report. If the original reporter is still experiencing a problem, they should "sudo port clean kdelibs3" and try again, and if it fails again, attach the main.log.

[cooljeanius (Eric Gallager)]

Cc Me!