[OpenIndiana-discuss] /usr/bin/vi* and large files.
trying to open a large file with vi/vim (oi_151a4), the editor behaves like opening a new file. moreThan2G.foo [New File] could this be the same issue like tail is not largefile aware https://www.illumos.org/issues/2717 Btw: Is vim a part of illumos-userland or openindiana? Uwe ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Which compiler to use for Perl modules?
Hello, I need to install a few Perl modules on one of my OpenIndiana boxes (oi151a4), Digest::MD4 for example. Unfortunately the usual way of installation (perl Makefile.PL ; make ; ...) doesn't work because the created Makefiles are configured for the Sun/Solaris Studio compiler. How to proceed now? Download Oracle's Solaris Studio compiler or modify the Makefiles to use gcc instead of cc? Which compiler was used for buidling perl? Thank you very much for your help in advance. Regards, Henner ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Which compiler to use for Perl modules?
not perfect, but you might be able to get the installed perl to compile by doing the following: cd /usr/perl5 cp ./5.10.0/lib/i86pc-solaris-64int/Config.pm ./5.10.0/lib/i86pc-solaris-64int/Config.pm.bak cp ./5.10.0/lib/Sun/Solaris/PerlGcc/Config.pm ./5.10.0/lib/i86pc-solaris-64int/Config.pm fix ./5.10.0/lib/i86pc-solaris-64int/Config_heavy.pl: change KPIC - fPIC change optimize='-O2 -fno-strict-aliasing' change ld='gcc' Jon On 24 May 2012 12:43, Henner Gratz h...@uni-bremen.de wrote: Hello, I need to install a few Perl modules on one of my OpenIndiana boxes (oi151a4), Digest::MD4 for example. Unfortunately the usual way of installation (perl Makefile.PL ; make ; ...) doesn't work because the created Makefiles are configured for the Sun/Solaris Studio compiler. How to proceed now? Download Oracle's Solaris Studio compiler or modify the Makefiles to use gcc instead of cc? Which compiler was used for buidling perl? Thank you very much for your help in advance. Regards, Henner ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Which compiler to use for Perl modules?
Hello Jon! Thank you very much for your fast reply. I appreciate it very much. Patching the Config module is much better than modifying every makefile. And the best is: It works! Best regards, Henner On 24 May 2012 11:55 UTC, Jonathan Adams wrote: not perfect, but you might be able to get the installed perl to compile by doing the following: cd /usr/perl5 cp ./5.10.0/lib/i86pc-solaris-64int/Config.pm ./5.10.0/lib/i86pc-solaris-64int/Config.pm.bak cp ./5.10.0/lib/Sun/Solaris/PerlGcc/Config.pm ./5.10.0/lib/i86pc-solaris-64int/Config.pm fix ./5.10.0/lib/i86pc-solaris-64int/Config_heavy.pl: change KPIC - fPIC change optimize='-O2 -fno-strict-aliasing' change ld='gcc' Jon On 24 May 2012 12:43, Henner Gratzhpg at uni-bremen.de http://openindiana.org/mailman/listinfo/openindiana-discuss wrote: / Hello, / / / / I need to install a few Perl modules on one of my OpenIndiana boxes / / (oi151a4), / / Digest::MD4 for example. Unfortunately the usual way of installation (perl / / Makefile.PL ; / / make ; ...) doesn't work because the created Makefiles are configured for / / the / / Sun/Solaris Studio compiler. How to proceed now? Download Oracle's Solaris / / Studio / / compiler or modify the Makefiles to use gcc instead of cc? Which compiler / / was used / / for buidling perl? / / / /Thank you very much for your help in advance. / / / / / / Regards, / / / / Henner / / / ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Which compiler to use for Perl modules?
On Thu, 24 May 2012, Henner Gratz wrote: I need to install a few Perl modules on one of my OpenIndiana boxes (oi151a4), Digest::MD4 for example. Unfortunately the usual way of installation (perl Makefile.PL ; make ; ...) doesn't work because the created Makefiles are configured for the Sun/Solaris Studio compiler. How to proceed now? Download Oracle's Solaris Studio compiler or modify the Makefiles to use gcc instead of cc? Which compiler was used for buidling perl? The perfect solution is to always install Perl modules using the compiler used to build Perl. Perl remembers all the nuances involved with the compiler used when Perl was built and replays these options when modules are built. This behavior is a long-standing problem with Perl. Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] problem route traceroute pkg.openindiana.orgon 109.71.206.26
HI Mike logs show takes place during the fall in the direction of routing packets in this problem - to most difficult session with the site router D-LINK DIR-100 192.168.0.1 My Dynamic IP 109.71.206.26 May/24/2012 21:59:42 [FW] **Drop Packet** IP/TCP 90.156.201.97:80-192.168.0.100:40245 May/24/2012 21:59:41 [FW] **Drop Packet** IP/TCP 91.218.229.12:80-192.168.0.100:57776 May/24/2012 21:59:40 [FW] **Drop Packet** IP/TCP 91.218.229.12:80-192.168.0.100:34479 May/24/2012 21:59:37 [FW] **Drop Packet** IP/TCP 90.156.201.97:80-192.168.0.100:40245 May/24/2012 21:59:37 [HTTP] logout (192.168.0.101) May/24/2012 21:59:29 [FW] **Drop Packet** IP/UDP 10.2.34.25:68-255.255.255.255:67 May/24/2012 21:59:24 [FW] **Drop Packet** IP/UDP 10.2.34.237:51636-10.2.34.255:1947 May/24/2012 21:59:17 [FW] **Drop Packet** IP/TCP 91.218.229.12:80-192.168.0.100:34479 May/24/2012 21:59:17 [FW] **Drop Packet** IP/UDP 10.2.34.9:68-255.255.255.255:67 May/24/2012 21:59:17 [FW] **Drop Packet** IP/TCP 91.218.229.12:80-192.168.0.100:57776 May/24/2012 21:59:17 [FW] **Drop Packet** IP/UDP 10.2.34.239:1027-10.2.34.255:1947 May/24/2012 21:59:13 [FW] **Drop Packet** IP/UDP 217.19.124.200:1027-255.255.255.255:1947 May/24/2012 21:58:52 [FW] **Drop Packet** IP/TCP 91.218.229.12:80-192.168.0.100:57776 May/24/2012 21:58:52 [FW] **Drop Packet** IP/TCP 91.218.229.12:80-192.168.0.100:34479 May/24/2012 21:58:48 [FW] **Drop Packet** IP/TCP 90.156.201.97:80-192.168.0.100:40245 May/24/2012 21:58:42 [FW] **Drop Packet** IP/UDP 0.0.0.0:68-255.255.255.255:67 May/24/2012 21:58:42 [FW] **Drop Packet** IP/UDP 10.2.34.237:51636-10.2.34.255:1947 May/24/2012 21:58:42 [FW] **Drop Packet** IP/TCP 90.156.201.97:80-192.168.0.100:40245 May/24/2012 21:58:41 [FW] **Drop Packet** IP/UDP 0.0.0.0:68-255.255.255.255:67 May/24/2012 21:58:41 [FW] **Drop Packet** IP/TCP 91.218.229.12:80-192.168.0.100:34479 May/24/2012 21:49:08 [FW] **Drop Packet** IP/TCP 90.156.201.99:80-192.168.0.100:48925 May/24/2012 21:49:07 [FW] **Drop Packet** IP/TCP 90.156.201.115:80-192.168.0.100:53217 May/24/2012 21:49:07 [FW] **Drop Packet** IP/TCP 90.156.201.13:80-192.168.0.100:46880 May/24/2012 21:49:06 [FW] **Drop Packet** IP/TCP 90.156.201.48:80-192.168.0.100:43573 May/24/2012 21:49:05 [FW] **Drop Packet** IP/TCP 90.156.201.99:80-192.168.0.100:48925 May/24/2012 21:49:05 [FW] **Drop Packet** IP/UDP 10.2.34.23:68-255.255.255.255:67 May/24/2012 21:49:04 [FW] **Drop Packet** IP/TCP 90.156.201.115:80-192.168.0.100:53217 May/24/2012 21:49:04 [FW] **Drop Packet** IP/TCP 90.156.201.13:80-192.168.0.100:46880 May/24/2012 21:49:01 [FW] **Drop Packet** IP/UDP 0.0.0.0:68-255.255.255.255:67 May/24/2012 21:49:00 [FW] **Drop Packet** IP/UDP 10.2.34.58:68-255.255.255.255:67 May/24/2012 21:48:57 [FW] **Drop Packet** IP/UDP 10.2.34.58:68-255.255.255.255:67 May/24/2012 21:48:51 [FW] **Drop Packet** IP/UDP 0.0.0.0:68-255.255.255.255:67 May/24/2012 21:48:50 [FW] **Drop Packet** IP/UDP 0.0.0.0:68-255.255.255.255:67 May/24/2012 21:48:46 [FW] **Drop Packet** IP/UDP 10.2.34.237:51636-10.2.34.255:1947 May/24/2012 21:48:37 [FW] **Drop Packet** IP/UDP 10.2.34.239:1027-10.2.34.255:1947 May/24/2012 21:48:33 [FW] **Drop Packet** IP/UDP 0.0.0.0:68-255.255.255.255:67 May/24/2012 21:48:33 [FW] **Drop Packet** IP/TCP 90.156.201.48:80-192.168.0.100:43573 May/24/2012 21:48:33 [FW] **Drop Packet** IP/UDP 217.19.124.200:1027-255.255.255.255:1947 May/24/2012 21:48:32 [FW] **Drop Packet** IP/TCP 90.156.201.99:80-192.168.0.100:48925 May/24/2012 21:48:31 [FW] **Drop Packet** IP/TCP 90.156.201.115:80-192.168.0.100:53217 Mike La Spina писал 2012-05-20 03:17: Arhipkin, Did you try traceroute -I pkg.openindiana.org Many
Re: [OpenIndiana-discuss] OpenOffice come back with 3.4 release
Perhaps someone more directly involved with the illumos based gcc work could enlighten the Apache team a bit... Message original Sujet: Re: OpenSolaris/Illumos intel GCC port Date : Thu, 24 May 2012 22:13:11 -0500 De : Pedro Giffuni p...@apache.org Répondre à : ooo-...@incubator.apache.org Pour : ooo-...@incubator.apache.org Copie à : Rich Reynolds r...@redstar-assoc.com Groupes de discussion: gmane.comp.apache.incubator.ooo.devel Références : 4fbede69.2090...@redstar-assoc.com On 05/24/12 20:20, Rich Reynolds wrote: hi all - anyone know of the above port happening? rich I don't think so. My understanding is that gcc was never well supported on Solaris. We have seen reports of success (after minor changes) with Sun's compiler though. Cheers, Pedro. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
