Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#49209 closed defect (fixed)

qt3: can't find freetype 2.6.1 headers

Reported by: andy@… Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: ports Version: 2.3.4
Keywords: Cc:
Port: qt3

Description (last modified by mf2k (Frank Schima))

Two issues:

  1. The mirrors don't appear to have a valid copy of qt-x11-free-3.3.8.tar.bz2. The first three servers apparently timeout, and the fourth gives an HTML response.

I was able to get around this by copying the file from another computer on which I installed qt3 about a year ago.

  1. The "Building qt3" returns an error. Relevant lines from the build log are:
:info:build + ./configure '-I$(QTDIR)/include' '-L$(QTDIR)/lib' -I/opt/local/include -L/opt/local/lib -lresolv -buildkey qt3-jaguar -platform darwin-g++ -xplatform darwin-g++ -prefix /opt/local/lib/qt3 -docdir /opt/local/share/doc/qt3 -headerdir /opt/local/include/qt3 -libdir /opt/local/lib -release -shared -no-exceptions -thread -cups -stl -qt-gif -plugin-imgfmt-png -plugin-imgfmt-jpeg -plugin-imgfmt-mng -system-libpng -system-libjpeg -system-zlib -largefile -sm -xinerama -xrender -xft -xkb -plugin-sql-sqlite -no-sql-ibase -no-sql-mysql -no-sql-odbc -no-sql-psql
:info:build Xft support cannot be enabled due to functionality tests!
:info:build  Turn on verbose messaging (-v) to ./configure to see the final report.
:info:build  If you believe this message is in error you may use the continue
:info:build  switch (-continue) to ./configure to continue.
:info:build Command failed: cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_qt3/qt3/work/qt-x11-free-3.3.8 && ./CompileScript.sh
:info:build Exit code: 101
:error:build org.macports.build for port qt3 returned: command execution failed

Change History (10)

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

Priority: HighNormal

The Priority field is for use by Macports team members only.

comment:2 Changed 9 years ago by mf2k (Frank Schima)

Description: modified (diff)

In the future, please use WikiFormatting

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

Please attach the main.log file. However, I'm not surprised qt3 doesn't build; it's ancient. Do you really need it? qt4-mac and qt5-mac are the current versions.

comment:4 Changed 9 years ago by andy@…

I don't need qt3 itself, but qt3 is a prerequisite for xxdiff -- a neat tool for graphically showing diffs and merging over an X11 connection.

The problem was that qt3 was expecting to find all of the freetype headers in /opt/include/freetype2/, when in the latest freetype port they are in /opt/include/freetype2/freetype/. Without hacking through the compilation scripts, I found an effective kluge:

cd /opt/include/freetype2
sudo ln -s freetype/*.h .

This allows qt3 to compile, and I've confirmed xxdiff works.

comment:5 in reply to:  description ; Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Owner: changed from macports-tickets@… to ryandesign@…
Status: newassigned

Replying to andy@…:

  1. The mirrors don't appear to have a valid copy of qt-x11-free-3.3.8.tar.bz2. The first three servers apparently timeout,

I have updated the homepage and master_sites of the port in r141226.

and the fourth gives an HTML response.

In fact, three servers give an HTML response, and they're all MacPorts mirrors: the one in Australia (aarnet.au.distfiles.macports.org), the one in Germany (nue.de.distfiles.macports.org), and the one in the UK (mse.uk.distfiles.macports.org). These web servers are misconfigured. I have reported the misconfiguration to the administrators of those servers; hopefully they will fix the problem.

comment:6 in reply to:  4 ; Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Replying to andy@…:

The problem was that qt3 was expecting to find all of the freetype headers in /opt/include/freetype2/, when in the latest freetype port they are in /opt/include/freetype2/freetype/.

Ah yes, the headers did change location somewhat recently. That might be easy to fix in qt3.

Without hacking through the compilation scripts, I found an effective kluge:

cd /opt/include/freetype2
sudo ln -s freetype/*.h .

This allows qt3 to compile, and I've confirmed xxdiff works.

I'm glad you found a workaround, but you should undo these changes to prevent future problems.

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

Resolution: fixed
Status: assignedclosed
Summary: Problem with QT3qt3: can't find freetype 2.6.1 headers

Replying to ryandesign@…:

Replying to andy@…:

The problem was that qt3 was expecting to find all of the freetype headers in /opt/include/freetype2/, when in the latest freetype port they are in /opt/include/freetype2/freetype/.

Ah yes, the headers did change location somewhat recently. That might be easy to fix in qt3.

Actually, wow, the freetype developers changed the header location once before, in freetype 2.5.1, and I fixed that in #41970. And now in freetype 2.6.1 the headers have mostly moved back, so the fix is to remove the previous fix, which I've now done in r141232.

comment:8 in reply to:  5 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Replying to ryandesign@…:

In fact, three servers give an HTML response, and they're all MacPorts mirrors: the one in Australia (aarnet.au.distfiles.macports.org), the one in Germany (nue.de.distfiles.macports.org), and the one in the UK (mse.uk.distfiles.macports.org). These web servers are misconfigured. I have reported the misconfiguration to the administrators of those servers; hopefully they will fix the problem.

The German and UK servers have been fixed.

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

The administrator of the Australian server has not yet responded, but a separate ticket has been filed for that issue: #49416.

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

This problem with the Australian server appears to be resolved, though there is another similar issue still unresolved which is tracked in #49416.

Note: See TracTickets for help on using tickets.