February 2010 - macports-tickets - lists.macosforge.org

[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

[MacPorts] #15432: Update mod_security
by MacPorts 23 Nov '13

23 Nov '13

#15432: Update mod_security -----------------------------------+---------------------------------------- Reporter: webmaster(a)lifedit.com | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: High | Milestone: Port Updates Component: ports | Version: 1.6.0 Keywords: mod_security | -----------------------------------+---------------------------------------- Hi ... I would like to see an update to the latest release of mod_security for Apache. Current MacPort version is 1.8.6 (http://trac.macports.org/browser/trunk/dports/www/mod_security/Portfile) and the official project website (http://www.modsecurity.org) currently shows version 2.5.6 to download (http://www.modsecurity.org/download/direct.html) So I think it would be great if this one could be updated soon if possible. Thanks! -- Ticket URL: <http://trac.macports.org/ticket/15432> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 9

[MacPorts] #17155: avr-gdb-6.71 broken / fails to read symbols from elf files
by MacPorts 21 Nov '13

21 Nov '13

#17155: avr-gdb-6.71 broken / fails to read symbols from elf files --------------------------------------------+------------------------------- Reporter: moritz.fischer(a)student.kit.edu | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: elf32-avr, symbols, elf, bfd | Port: avr-gdb --------------------------------------------+------------------------------- Although it seems to build perfectly ok, avr-gdb is not able to read debugging symbols from elf files. I tried switching to gdb-6.8 with the same effect. I found out that if built by hand with same ./configure parameters it works just fine, but using the port somehow elfread.o doesn't get linked in. Somehow the configure scripts seem to fail. The Problem is afaik related to bfd's elf support: "checking for ELF support in BFD... no" if compiled by port, whereas ELF support is detected when build by hand. -- Ticket URL: <http://trac.macports.org/ticket/17155> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 1

[MacPorts] #18361: LaunchDaemon script
by MacPorts 13 Nov '13

13 Nov '13

#18361: LaunchDaemon script ----------------------------------+----------------------------------------- Reporter: yaohua2000@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Port Requests Component: ports | Version: 1.7.0 Keywords: | Port: tor ----------------------------------+----------------------------------------- The port "tor" need a LaunchDaemon. -- Ticket URL: <http://trac.macports.org/ticket/18361> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 9

[MacPorts] #23143: Add ActiveMQ to Macports.
by MacPorts 12 Nov '13

12 Nov '13

#23143: Add ActiveMQ to Macports. --------------------------------------+------------------------------------- Reporter: brian.gupta@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.2 Keywords: | Port: --------------------------------------+------------------------------------- Could we get this Apache Project message queuing server software added to MacPorts.. http://activemq.apache.org/ The latest version, 5.3, can be downloaded here: http://activemq.apache.org/activemq-530-release.html Please let me know if you have any questions, or need any help. -- Ticket URL: <http://trac.macports.org/ticket/23143> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 9

[MacPorts] #18881: AFFLIB / FUSE
by MacPorts 12 Nov '13

12 Nov '13

#18881: AFFLIB / FUSE -----------------------------------+---------------------------------------- Reporter: macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: AFFLIB FUSE | Port: AFFLIB -----------------------------------+---------------------------------------- Would it be possible to get the FUSE variant of AFFLIB working? I'm attempting to use "affuse" from that package and get an error that FUSE isn't installed. Web support indicates that the FUSE developer files need to be installed before we complie AFFLIB. I edited the AFFLIB Portfile to enable the FUSE variant, and installed. I get the following output: {{{ configure: FUSE requested checking fuse.h usability... no checking fuse.h presence... no checking for fuse.h... no configure: fuse.h not found; Disabling FUSE support. }}} I do have MacFuse 1.7.1 installed, and fuse.h is in /opt/local/include. I'm willing to do legwork to get it going but am at the end of my current capabilities. Thanks. -- Ticket URL: <http://trac.macports.org/ticket/18881> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #17540: poppler conflicts with xpdf
by MacPorts 12 Nov '13

12 Nov '13

#17540: poppler conflicts with xpdf ----------------------------+----------------------------------------------- Reporter: gale@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: | Port: ----------------------------+----------------------------------------------- poppler 0.10.1 cannot be installed simultaneously with xpdf 3.02 because there are many files that both ports try to install. poppler advertises itself as "based on the xpdf code base". If so, it should depend on xpdf instead of installing some of xpdf's files itself. Better yet, create an xpdf-tools port that contains the files common to both. The list of conflicting files is: /opt/local/bin/pdffonts /opt/local/bin/pdfimages /opt/local/bin/pdfinfo /opt/local/bin/pdftoppm /opt/local/bin/pdftops /opt/local/bin/pdftotext /opt/local/share/man/man1/pdffonts.1.gz /opt/local/share/man/man1/pdfimages.1.gz /opt/local/share/man/man1/pdfinfo.1.gz /opt/local/share/man/man1/pdftoppm.1.gz /opt/local/share/man/man1/pdftops.1.gz /opt/local/share/man/man1/pdftotext.1.gz -- Ticket URL: <http://trac.macports.org/ticket/17540> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 28

[MacPorts] #20027: perl5.8 build failure
by MacPorts 12 Nov '13

12 Nov '13

#20027: perl5.8 build failure -----------------------------+---------------------------------------------- Reporter: uttam@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.7.1 Keywords: | Port: -----------------------------+---------------------------------------------- When I tried to "sudo port install wine", it gave an error that 'perl5.8' build failed. The output is attached with the attachment. Versions of: Mac OS X: 10.5.7 Macports: 1.710 Xcode: 3.1.2 -- Ticket URL: <http://trac.macports.org/ticket/20027> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 10

[MacPorts] #20111: "Function declaration isn't a prototype" in Erlang
by MacPorts 04 Nov '13

04 Nov '13

#20111: "Function declaration isn't a prototype" in Erlang ----------------------------------+----------------------------------------- Reporter: jadenb1729@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.7.1 Keywords: | Port: ----------------------------------+----------------------------------------- When I try to install Erlang R13B01 using Macports 1.710 on Mac OS X.4.11 PPC (darwin 8 ppc), I get (after some successful compilation) the attached error message. I successfully installed Erlang R12B-5_1 (a long time ago). -- Ticket URL: <http://trac.macports.org/ticket/20111> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 9

[MacPorts] #22785: Missing dylibs for Erlang
by MacPorts 04 Nov '13

04 Nov '13

#22785: Missing dylibs for Erlang --------------------------------+------------------------------------------- Reporter: conradwt@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.1 Keywords: snow leopard | Port: erlang --------------------------------+------------------------------------------- I noticed after building the current release of Erlang: port install erlang @R13B02_3+darwin_10+ssl That it doesn't appear to build the dynamic librarie (i.e. .dylib) files. -- Ticket URL: <http://trac.macports.org/ticket/22785> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6