Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#38048 closed defect (fixed)

kdelibs3 won't build because of wrong autoconf version

Reported by: tehcog (tehcog) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.1.3
Keywords: Cc: wulfgang@…, mkae (Marko Käning), michael.bessolov@…, rlhamil, FlorianFranzen@…, arkonan (Alexandra Ellwood), takekawa@…, cooljeanius (Eric Gallager), ryandesign (Ryan Carsten Schmidt)
Port: kdelibs3

Description

kdelibs3 won't build on MacPorts base version 2.1.3, Snowleopard 10.6.8 Please see attached file.

Attachments (2)

kdelibs3_Debug.txt (11.2 KB) - added by tehcog (tehcog) 11 years ago.
debug log
main.log (289.6 KB) - added by wulfgang@… 11 years ago.
kdelibs3 main.log

Download all attachments as: .zip

Change History (23)

Changed 11 years ago by tehcog (tehcog)

Attachment: kdelibs3_Debug.txt added

debug log

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

Cc: nomaintainer@… removed

It is not useful to Cc nomaintainer.

It is more helpful if you attach the main.log file.

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

The log already attached is sufficient; it says:

error: Autoconf version 2.65 or higher is required

So, kdelibs3's dependency on port:autoconf263 seems incorrect.

What happens if you install the autoconf port? Or is it already installed?

comment:3 in reply to:  2 Changed 11 years ago by tehcog (tehcog)

Replying to ryandesign@…: . .

So, kdelibs3's dependency on port:autoconf263 seems incorrect.

What happens if you install the autoconf port? Or is it already installed?

Thanks for your assistance in this matter. I have:

The following ports are currently installed:
  autoconf @2.68_2
  autoconf @2.69_0 (active)
  autoconf263 @2.63_0 (active)

Am I missing something here?

Last edited 11 years ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)

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

Nope; the kdelibs3 port is simply programmed to explicitly use autoconf263. That appears to be wrong and should be fixed.

comment:5 Changed 11 years ago by jmroot (Joshua Root)

Given that it built fine before, it seems more likely that not also depending on an autoconf263-compatible automake is the problem.

comment:6 Changed 11 years ago by wulfgang@…

Cc: wulfgang@… added

Cc Me!

comment:7 Changed 11 years ago by mkae (Marko Käning)

Cc: mk@… added

Cc Me!

comment:8 Changed 11 years ago by michael.bessolov@…

Cc: michael.bessolov@… added

Cc Me!

comment:9 Changed 11 years ago by rlhamil

Cc: rlhamil@… added

Cc Me!

comment:10 Changed 11 years ago by FlorianFranzen@…

Cc: FlorianFranzen@… added

Cc Me!

comment:11 Changed 11 years ago by arkonan (Alexandra Ellwood)

Cc: lxs@… added

Cc Me!

comment:12 Changed 11 years ago by takekawa@…

It could be fixed by using automake-17 and aclocal-17.

--- Portfile~	2013-03-18 18:43:12.000000000 +0900
+++ Portfile	2013-03-18 18:44:08.000000000 +0900
@@ -33,6 +33,7 @@
 dist_subdir             kde3
 
 depends_build           port:autoconf263 \
+                        port:automake17 \
                         port:automake \
                         port:pkgconfig \
                         port:unsermake
@@ -132,7 +133,7 @@
 use_configure           no
 
 use_parallel_build      yes
-build.env               MAKEFLAGS="-j${build.jobs}" AUTOCONF=autoconf263 \
+build.env               MAKEFLAGS="-j${build.jobs}" AUTOCONF=autoconf263 AUTOMAKE=automake-17 ACLOCAL=aclocal-17 \
                         CC=${configure.cc} CXX=${configure.cxx}
 build.cmd               ./CompileScript.sh

comment:13 Changed 11 years ago by takekawa@…

Cc: takekawa@… added

Cc Me!

comment:14 Changed 11 years ago by mkae (Marko Käning)

Indeed it builds fine again with the above patch! :-)

Committed as r104164.

Last edited 11 years ago by mkae (Marko Käning) (previous) (diff)

comment:15 Changed 11 years ago by mkae (Marko Käning)

Resolution: fixed
Status: newclosed

comment:16 Changed 11 years ago by jmroot (Joshua Root)

Should it really depend on both automake and automake17?

Changed 11 years ago by wulfgang@…

Attachment: main.log added

kdelibs3 main.log

comment:17 Changed 11 years ago by wulfgang@…

Resolution: fixed
Status: closedreopened

I am using the most recent version of XCode and Macports, and I am still having trouble to compile.

I ran

sudo port clean kdelibs3
sudo port install kdelibs3

which triggered an install of automake17. This install was successful, but kdelibs3 failed:

:info:build In file included from /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_kdelibs3/kdelibs3/work/kdelibs-3.5.10/kdecore/krootprop.cpp:20:
:info:build In file included from /opt/local/lib/qt3/include/qwidget.h:42:
:info:build In file included from /opt/local/lib/qt3/include/qwindowdefs.h:44:
:info:build /opt/local/lib/qt3/include/qstring.h:898:44: warning: operands of ? are integers of different signs: 'uint' (aka 'unsigned int') and 'int' [-Wsign-compare]
:info:build     return insertHelper( index, s, pos==-1 ? s.size() : pos );
:info:build                                            ^ ~~~~~~~~   ~~~
:info:build /opt/local/lib/qt3/include/qstring.h:920:45: warning: operands of ? are integers of different signs: 'uint' (aka 'unsigned int') and 'int' [-Wsign-compare]
:info:build     return operatorPlusEqHelper( s, pos==-1 ? s.size() : pos );
:info:build                                             ^ ~~~~~~~~   ~~~
:info:build 2 warnings generated.
:info:build kdelibs3-3.5.10-16 make failed!
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_kdelibs3/kdelibs3/work/kdelibs-3.5.10" && ./CompileScript.sh all 
:info:build Exit code: 1

There are many more error messages that seem similar (problems with operators etc.). See the attached log for details.

comment:18 in reply to:  17 Changed 11 years ago by FlorianFranzen@…

Replying to wulfgang@…:

There are many more error messages that seem similar (problems with operators etc.). See the attached log for details.

These warnings are actually not the problem. The actual problem you encounter is:

:info:build Undefined symbols for architecture x86_64:
:info:build   "QPtrList<DCOPClientTransaction>::deleteItem(void*)", referenced from:
:info:build       vtable for QPtrList<DCOPClientTransaction> in libDCOP.4.2.0.dylib-master.o
:info:build ld: symbol(s) not found for architecture x86_64
:info:build clang: error: linker command failed with exit code 1 (use -v to see invocation)
:info:build Error creating ./dcop/libDCOP.la. Exit status 1.

Do you happen to have a second, no mac ports version of qt3 installed?

You probably have run a selfupdate (sudo port selfupdate) prior to building?

Can you supply us with more information about the version of OS X you are using?

comment:19 Changed 11 years ago by cooljeanius (Eric Gallager)

Cc: egall@… added

Cc Me!

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

Keywords: autoconf removed
Resolution: fixed
Status: reopenedclosed
Summary: kdelibs3 won't build on MacPorts base version 2.1.3, Snowleopard 10.6.8kdelibs3 won't build because of wrong autoconf version

This is a new problem now, for which there should be a new ticket, please. And in fact there already is: #38876

comment:21 in reply to:  16 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added

Replying to jmr@…:

Should it really depend on both automake and automake17?

Removed automake dependency in r106068.

Note: See TracTickets for help on using tickets.