May 2015 - macports-tickets - lists.macosforge.org

[MacPorts] #46202: Undefined symbols for architecture x86_64 on Yosemite
by MacPorts 30 Jul '15

30 Jul '15

#46202: Undefined symbols for architecture x86_64 on Yosemite ------------------------+-------------------------------- Reporter: nmsnoopy@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.3.3 Keywords: linker | Port: log4cpp ------------------------+-------------------------------- hello, First of all thanks a lot to have solved my first ticket : #46178, I resintalled from scratch gcc48 and now gcc48 works. The problem I have now(and from the beginning in fact) is a linking problem on Yosemite. Here below I added a simple code using the log4cpp library which fails at the link level. I have only installed the gcc48, log4cpp and boost ports (Note that the same program does not fail on Mavericks). Thanks to help me on this. The link error is: {{{ > g++ -o test4 test4.cpp -L/opt/local/lib -llog4cpp Undefined symbols for architecture x86_64: "log4cpp::OstreamAppender::OstreamAppender(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::basic_ostream<char, std::char_traits<char> >*)", referenced from: _main in cc8Xtd0v.o ld: symbol(s) not found for architecture x86_64 collect2: error: ld returned 1 exit status }}} The example code: {{{ #include "log4cpp/Category.hh" #include "log4cpp/Appender.hh" #include "log4cpp/OstreamAppender.hh" int main(int argc, char** argv) { log4cpp::Appender *appender1 = new log4cpp::OstreamAppender("console", &std::cout); return 0; } }}} -- Ticket URL: <https://trac.macports.org/ticket/46202> MacPorts <https://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #47835: bibtex2html - Installation error
by MacPorts 28 Jul '15

28 Jul '15

#47835: bibtex2html - Installation error ----------------------------+-------------------------------- Reporter: jursonovicst@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: ----------------------------+-------------------------------- bibtex2html cannot be compiled, becase required font files are missing. Could you please update the dependent packages and add texlive-fonts- recommended, which will install the required fonts, please? KR Tamás -- Ticket URL: <https://trac.macports.org/ticket/47835> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #45842: netpbm build failure/linker error with +universal on Yosemite 10.10
by MacPorts 28 Jul '15

28 Jul '15

#45842: netpbm build failure/linker error with +universal on Yosemite 10.10 -------------------------+-------------------------------- Reporter: d_blatner@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.2 Keywords: | Port: -------------------------+-------------------------------- See Log-File -- Ticket URL: <https://trac.macports.org/ticket/45842> MacPorts <https://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #46183: okular @4.13.3_0 Cannot open files directly from the command line
by MacPorts 23 Jul '15

23 Jul '15

#46183: okular @4.13.3_0 Cannot open files directly from the command line ---------------------------+-------------------------------- Reporter: dsfrancis03@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: Okular ---------------------------+-------------------------------- Hello, I have a Late 2008 15" Macbook Pro. I recently installed Yosemite (clean install) on my Macbook and also installed kde4-kile through macports 2.3.3. The installations of all the related ports seemed fine except for two ports, okular @4.13.3_0 and kde4-kile @2.1.3_1. In this post, I'd like to discuss my problem regarding okular. If I open okular first and then open a file from File - Open menu, then okular opens the file with no problem. However, if I try to open a file using okular from kile, or if I try to open a file using okular from the command line (e.g, '/Applications/MacPorts/KDE4/okular.app/Contents/MacOS/okular abc.pdf'), then okular fails to open the file. Here is the error message: {{{ okular(609)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: okular(609)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: okular(609)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: okular(609)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: okular(609)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: KCrash: Application 'okular' crashing... KCrash: Attempting to start directly KCrash failed to exec(), errno = 2 }}} And, here are more about okular: {{{ $ /Applications/MacPorts/KDE4/okular.app/Contents/MacOS/okular --version Qt: 4.8.6 KDE Development Platform: 4.13.3 Okular: 0.19.3 }}} Please help me solve this issue and let me know if more information is needed. I have another issue regarding kile, which doesn't open a file by drag- and-drop, and I'll probably open a new ticket later. But, before I open a new ticket, if anyone is familiar with this issue, please advise. -- Ticket URL: <https://trac.macports.org/ticket/46183> MacPorts <https://www.macports.org/> Ports system for OS X

1 10

[MacPorts] #47681: `hg status' crashes on newly created repository
by MacPorts 22 Jul '15

22 Jul '15

#47681: `hg status' crashes on newly created repository --------------------------+-------------------------------- Reporter: veedeehjay@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: mercurial --------------------------+-------------------------------- this happens with mercurial(a)3.3.3 under OSX 10.10.3. the following should reproducibly crash if the `hggit'` is requested in `~/.hgrc` {{{ mkdir new cd new hg init hg status }}} with the message: {{{ ** unknown exception encountered, please report by visiting ** http://mercurial.selenic.com/wiki/BugTracker ** Python 2.7.9 (default, Dec 13 2014, 15:13:49) [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.56)] ** Mercurial Distributed SCM (version 3.3.3) ** Extensions loaded: convert, rebase, fetch, graphlog, extdiff, hgk, color, hgsubversion, hggit, churn, pager, strip, mq, transplant Traceback (most recent call last): File "/opt/local/bin/hg", line 43, in <module> ... LOTS MORE ... File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/mercurial/scmutil.py", line 1105, in finddirs pos = path.rfind('/') AttributeError: 'tuple' object has no attribute 'rfind' }}} two observations: 1. without the `hggit` extension the problem goes away here 2. using the `mercurial-devel` instead of the`mercurial` port also makes the problem go away even in the presence of `hggit`. whether it's a problem of mercurial or the `py-hggit` port I canot say... -- Ticket URL: <https://trac.macports.org/ticket/47681> MacPorts <https://www.macports.org/> Ports system for OS X

1 8

[MacPorts] #47604: watchman builds with datatype mismatch in clang
by MacPorts 22 Jul '15

22 Jul '15

#47604: watchman builds with datatype mismatch in clang -----------------------+-------------------------------- Reporter: siulung@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: -----------------------+-------------------------------- $ sudo port install watchman ---> Computing dependencies for watchman ---> Fetching archive for watchman ---> Attempting to fetch watchman-3.1_0+universal.darwin_14.i386-x86_64.tbz2 from http://packages.macports.org/watchman [...] Error: org.macports.build for port watchman returned: command execution failed Please see the log file for port watchman for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_watchman/watchman/main.log :info:build watcher/fsevents.c:133:67: error: values of type 'FSEventStreamEventFlags' should not be used as format arguments; add an explicit cast to 'unsigned int' instead [-Werror,-Wformat] :info:build w_log(W_LOG_DBG, "fse_thread: add %s %" PRIx32 "\n", pathbuf, evt->flags); :info:build ~~~ ^~~~~~~~~~ :info:build (unsigned int) :info:build 1 error generated. -- Ticket URL: <https://trac.macports.org/ticket/47604> MacPorts <https://www.macports.org/> Ports system for OS X

1 5

[MacPorts] #45556: alliance @5.0-20110203_2 (science) build failure
by MacPorts 21 Jul '15

21 Jul '15

#45556: alliance @5.0-20110203_2 (science) build failure ----------------------------+-------------------------------- Reporter: gayubaassane@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.2 Keywords: | Port: alliance ----------------------------+-------------------------------- I'm using the mac os X yosemite -- Ticket URL: <https://trac.macports.org/ticket/45556> MacPorts <https://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #46114: please include drawstuff library in devel/ode
by MacPorts 18 Jul '15

18 Jul '15

#46114: please include drawstuff library in devel/ode --------------------------+-------------------------------- Reporter: mescalinum@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: devel/ode --------------------------+-------------------------------- The package ode ships with a library for drawing simulation, called 'drawstuff'. The ode port does not compile or install this library. Could you please add it (perhaps via a port variant, for those who do not want it)? -- Ticket URL: <https://trac.macports.org/ticket/46114> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #47901: port:cmake+docs+gui: build documentation in Qt help/Assistant format
by MacPorts 17 Jul '15

17 Jul '15

#47901: port:cmake+docs+gui: build documentation in Qt help/Assistant format -------------------------+-------------------------------- Reporter: rjvbertin@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch | Port: cmake -------------------------+-------------------------------- cmake uses sphinx to generate its documentation, which means a `.qch` version can be made for use with Qt's Assistant. I propose to do this automatically when combining `+docs` with `+gui` and `+python34` . The latter condition is because Python 2.7 appears to crash when building the documentation; I have not checked if this also occurs without building the documentation in Qt format. (That does not seem impossible because the .qch file is generated from the HTML documentation, and appears to be built in the destroot step while the crash occurs during the build phase.) I've also removed my -bundle patch, which turned out not to be a good idea (as I already signalled a while ago). -- Ticket URL: <https://trac.macports.org/ticket/47901> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #47904: cmake @3.2.2_0: variants are a confusing mess
by MacPorts 16 Jul '15

16 Jul '15

#47904: cmake @3.2.2_0: variants are a confusing mess ----------------------+------------------------- Reporter: larryv@… | Owner: michaelld@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: cmake ----------------------+------------------------- I won’t mince words: `cmake`’s variants make no sense. Half of them only exist if one of the other half are selected. This is not discoverable at all, and I suspect most users only realize that they had a choice after they install `cmake`. ---- Say I want to install CMake. {{{ % port variants cmake cmake has the variants: docs: Build documentation: HTML and manpages gui: Build Qt-based cmake-gui universal: Build for multiple architectures }}} Looks like I have three choices. Cool. I decide to build cmake-gui and the documentation. {{{ % sudo port install cmake +docs +gui ---> Computing dependencies for cmake The following dependencies will be installed: dbus lcms libmng py27-alabaster py27-babel py27-docutils py27-jinja2 py27-pygments py27-roman py27-six py27-snowballstemmer py27-sphinx py27-sphinx_rtd_theme py27-tz python27 qt4-mac sphinx_select Continue? [Y/n]: }}} Eh. Maybe I already have Python 3.4 installed, and I’d rather not install Python 2.7, but it doesn’t look like I have a choice, so I’ll just go with it. But the `+gui` variant seems to require `qt4-mac`. What if I have `qt5-mac` installed? Those conflict, so I guess I’ll just go without the GUI. Except that that wasn’t necessary at all. Turns out I do have choices, but they’re utterly undiscoverable. I’d have to check the list variants //after already selecting a variant//, which is something I never think to do. {{{ % port variants cmake +docs +gui cmake has the variants: +docs: Build documentation: HTML and manpages +gui: Build Qt-based cmake-gui [+]python27: Build documentation using Sphinx from Python 2.7 * conflicts with python34 python34: Build documentation using Sphinx from Python 3.4 * conflicts with python27 [+]qt4: Build Qt GUI using Qt4 * conflicts with qt5 qt5: Build Qt GUI using Qt5 * conflicts with qt4 universal: Build for multiple architectures }}} `cmake` should eliminate this weird two-level thing and instead present all its variants up front. Something like this. {{{ % port variants cmake cmake has the variants: docs_py27: Build HTML docs and manpages using Sphinx from Python 2.7 * conflicts with docs_py34 docs_py34: Build HTML docs and manpages using Sphinx from Python 3.4 * conflicts with docs_py27 gui_qt4: Build cmake-gui with Qt4 * conflicts with gui_qt5 gui_qt5: Build cmake-gui with Qt5 * conflicts with gui_qt4 universal: Build for multiple architectures }}} ---- No patch to offer, I’m afraid. Sorry for the anticlimax. Feel free to let this lie fallow until I whip up something. -- Ticket URL: <https://trac.macports.org/ticket/47904> MacPorts <https://www.macports.org/> Ports system for OS X

1 3