March 2011 - macports-tickets - lists.macosforge.org

[MacPorts] #25695: Freetype 2.4.0 renders much worse than 2.3.12
by MacPorts 03 Dec '13

03 Dec '13

#25695: Freetype 2.4.0 renders much worse than 2.3.12 --------------------------------------+------------------------------------- Reporter: Peter_Dyballa@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: | Port: --------------------------------------+------------------------------------- In GNU Emacs 22.3 the font to write the texts in the menu bar and the menus' entries renders really badly now while before it looked OK. Right now I can't proof this because port does not let me build freetype @2.3.12_0 – another bug? -- Ticket URL: <http://trac.macports.org/ticket/25695> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #28338: kdebase4 @4.6.0 - KDE applications don't start
by MacPorts 30 Nov '13

30 Nov '13

#28338: kdebase4 @4.6.0 - KDE applications don't start -----------------------------------------------+---------------------------- Reporter: habmalnefrage@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: KDE4, kdebase, dolphin, konqueror | Port: kdebase4 -----------------------------------------------+---------------------------- Hi, I'm using Snow Leopard and tried to install kdebase4 to use Dolphin. The installation succeeded without errors. But when I try to start any KDE4 application from the terminal window, nothing happens. The same issue occurs when started via the X11-Symbol in the dock (that was started via startx in the terminal window). When I call the applications from Finder, a program icon jumps in the dock up and down for a while, but after that the icon's context menu shows, that the program doesn't answer. I already followed the usual 'sudo chown -R ...' and 'launchctl...' instructions, with no success. After having read some similar tickets I haven't found out a solution yet and hope, you can help. -- Ticket URL: <https://trac.macports.org/ticket/28338> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 15

[MacPorts] #26019: qtoctave-mac 0.9.1 conflicts with libquicktime
by MacPorts 28 Nov '13

28 Nov '13

#26019: qtoctave-mac 0.9.1 conflicts with libquicktime ------------------------------------+--------------------------------------- Reporter: michaelld@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: conflict | Port: qtoctave-mac, libquicktime ------------------------------------+--------------------------------------- just 1 file: ${prefix}/bin/qtinfo, which doesn't seem critical to either. See ticket #22139 for a possible solution, fixing libquicktime's binaries by prepending 'l' to those without it. -- Ticket URL: <http://trac.macports.org/ticket/26019> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #23846: octave 3.2.3 call of imread crashed octave
by MacPorts 28 Nov '13

28 Nov '13

#23846: octave 3.2.3 call of imread crashed octave -------------------------------------------+-------------------------------- Reporter: hans-juergen.greif@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.2 Keywords: | Port: -------------------------------------------+-------------------------------- Hello, octave:4> A=imread("Gears3.tiff"); Assertion failed: (semaphore_info != (SemaphoreInfo *) NULL), function LockSemaphoreInfo, file magick/semaphore.c, line 525. panic: Abort trap -- stopping myself... Abort trap tiffinfo Gears3.tiff TIFF Directory at offset 0x1d296 (119446) Image Width: 380 Image Length: 380 Resolution: 1, 1 (unitless) Bits/Sample: 8 Sample Format: unsigned integer Compression Scheme: LZW Photometric Interpretation: RGB color Orientation: row 0 top, col 0 lhs Samples/Pixel: 3 Planar Configuration: single image plane Software: Pixie MatrixWorldToScreen: 1.995447,-1.011418,0.237759,0.237759,-0.451741,-1.418443,-0.903482,-0.903482,-1.072726,-1.517127,0.356638,0.356638,21.029737,21.029734,42.059479,42.059479 MatrixWorldToCamera: 0.832050,0.501162,0.237759,0.000000,0.000000,0.428625,-0.903482,0.000000,-0.554700,0.751743,0.356638,0.000000,-0.000001,0.000003,42.059479,1.000000 Predictor: horizontal differencing 2 (0x2) -- Ticket URL: <http://trac.macports.org/ticket/23846> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 8

[MacPorts] #24476: octave-3.2.3 crashes in eigs (arpack)
by MacPorts 28 Nov '13

28 Nov '13

#24476: octave-3.2.3 crashes in eigs (arpack) -------------------------------------+-------------------------------------- Reporter: jarno.rajahalme@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.2 Keywords: | Port: octave -------------------------------------+-------------------------------------- On OSX 10.6.3 (and likely earlier), running a 64-bit kernel, have not tested with 32-bit. Octave 3.2.3 causes a segmentation fault when complex numbers are used with eigs(). within octave, type octave:1> test eigs panic: Segmentation fault -- stopping myself... Segmentation fault $ The reason for this is that the macports arpack package, that octave depends on, is compiled with options incompatible with the octave, and other fortran compiled dependencies of octave. Either the dependency should be removed (as it is useless as is), or arpack needs to be updated. -- Ticket URL: <http://trac.macports.org/ticket/24476> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6

[MacPorts] #24860: 'quit' and 'exit' do not work well for octave
by MacPorts 28 Nov '13

28 Nov '13

#24860: 'quit' and 'exit' do not work well for octave ----------------------------+----------------------------------------------- Reporter: qchen3@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.2 Keywords: quit, exit | Port: octave ----------------------------+----------------------------------------------- I found it is always painful to quit or exit octave, current 3.2.4, as well as 3.2.3. Up quitting or exiting, it will give me the following messages: ********************************************* octave:1> quit panic: Segmentation fault -- stopping myself... attempting to save variables to `octave-core'... save to `octave-core' complete Segmentation fault ********************************************* Ctr-D, quit, exit behave the same way, that is, give me the same error messages. -- Ticket URL: <http://trac.macports.org/ticket/24860> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #24861: Octave 3.2.4, unable to close figures
by MacPorts 28 Nov '13

28 Nov '13

#24861: Octave 3.2.4, unable to close figures ----------------------------+----------------------------------------------- Reporter: qchen3@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.2 Keywords: close | Port: octave ----------------------------+----------------------------------------------- The command 'close' or 'close all' do not work to close the figure windows. My OS is snow leopard 10.6.3. Hardware is macbook pro. -- Ticket URL: <http://trac.macports.org/ticket/24861> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #27020: octave-graceplot fails to build
by MacPorts 28 Nov '13

28 Nov '13

#27020: octave-graceplot fails to build ----------------------------------+----------------------------------------- Reporter: obed_sands@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: | Port: octave-graceplot ----------------------------------+----------------------------------------- looks like building the octfile for __grcmd__.cc fails due to some undeclared variables -- Ticket URL: <https://trac.macports.org/ticket/27020> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #26340: Cannot install octave packages
by MacPorts 28 Nov '13

28 Nov '13

#26340: Cannot install octave packages ------------------------------------+--------------------------------------- Reporter: matthias@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 1.9.1 Keywords: octave | Port: All octave packages (I did not try all, but many) ------------------------------------+--------------------------------------- If I try to install octave packages (e.g. octave-strings), I get the following: --------------------------------- sudo port install octave-strings Password: ---> Computing dependencies for octave-strings ---> Staging octave-strings into destroot Error: Target org.macports.destroot returned: error renaming "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_ports_math_octave- strings/work/destroot/opt/local/share/octave/octave_packages": no such file or directory Log for octave-strings is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_ports_math_octave-strings/main.log Error: Status 1 encountered during processing. To report a bug, see <http://guide.macports.org/#project.tickets> --------------------------------- I have no clue what's going on, but I believe something is not configured the way it should be (either with Octave itself, or with the packages). -- Ticket URL: <http://trac.macports.org/ticket/26340> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6

[MacPorts] #15653: std::locale broken in gcc
by MacPorts 27 Nov '13

27 Nov '13

#15653: std::locale broken in gcc --------------------------------+------------------------------------------- Reporter: dirk(a)code-shop.com | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Keywords: | --------------------------------+------------------------------------------- When compiling the following code: #include <locale> #include <iostream> #include <exception> #include <clocale> void try_c_locale(const char* locale_name) { if( std::setlocale(LC_ALL, locale_name) == NULL ) printf("Failed to setlocale(LC_ALL, \"%s\")\n", locale_name); else printf("Succeeded in calling setlocale(LC_ALL, \"%s\")\n", locale_name); } void try_cpp_locale(const char* locale_name) { try { std::locale my_locale(locale_name); } catch(std::exception& e) { printf("Failed ctor for std::locale with \"%s\": %s\n", locale_name, e.what()); return; } printf("Succeeded ctor for std::locale with \"%s\"\n", locale_name); } int main(void) { // Some locales from "locale -a" on my OS X system, here is proof // that these locales do exist on my system. Take my word for it // that "locale -a" also shows these locales existing on my linux // system as well. // // rutski@imac:~$ locale -a | tail -n 2 // C // POSIX // rutski@imac:~$ locale -a | grep en_US // en_US // en_US.ISO8859-1 // en_US.ISO8859-15 // en_US.US-ASCII // en_US.UTF-8 // rutski@imac:~$ locale -a | grep pl_PL // pl_PL // pl_PL.ISO8859-2 // pl_PL.UTF-8 // rutski@imac:~$ const char* test_locales[] = { "C", "POSIX", "en_US", "en_US.UTF-8", "pl_PL", "pl_PL.ISO8859-2" }; printf("Trying c locales...\n"); for(size_t x = 0; x < sizeof(test_locales)/sizeof(char*); x++) try_c_locale(test_locales[x]); printf("\n"); printf("Trying C++ locales...\n"); for(size_t x = 0; x < sizeof(test_locales)/sizeof(char*); x++) try_cpp_locale(test_locales[x]); } the output clearly states there is something wrong: Trying c locales... Succeeded in calling setlocale(LC_ALL, "C") Succeeded in calling setlocale(LC_ALL, "POSIX") Succeeded in calling setlocale(LC_ALL, "en_US") Succeeded in calling setlocale(LC_ALL, "en_US.UTF-8") Succeeded in calling setlocale(LC_ALL, "pl_PL") Succeeded in calling setlocale(LC_ALL, "pl_PL.ISO8859-2") Trying C++ locales... Succeeded ctor for std::locale with "C" Succeeded ctor for std::locale with "POSIX" Failed ctor for std::locale with "en_US": locale::facet::_S_create_c_locale name not valid Failed ctor for std::locale with "en_US.UTF-8": locale::facet::_S_create_c_locale name not valid Failed ctor for std::locale with "pl_PL": locale::facet::_S_create_c_locale name not valid Failed ctor for std::locale with "pl_PL.ISO8859-2": locale::facet::_S_create_c_locale name not valid a google serach delivers this: http://groups.google.com/group/gnu.gcc.help/browse_thread/thread/99d874aed6… appearantly, a --enable-clocale to configure might do something however, macport's configure stage does not allow for adding options (or I could not find it) * could this be fixed in gcc? (in libstdc++) * could this be added to macport (adding extra configure options) -- Ticket URL: <http://trac.macports.org/ticket/15653> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5