http://permalink.gmane.org/gmane.os.netbsd.devel.pkgsrc.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.os.netbsd.devel.pkgsrc.user/18138 <pre>Hello. I need help. I want to compile pkgsrc/devel/pkg-config on NetBSD-current. But I saw error and cannot create it. anyone else?? HEO SeonMeyong. ===== Environment:NetBSD-current Platform: NetBSD-amd64 uname: NetBSD hostname 6.99.20 NetBSD 6.99.20 (GENERIC) #0: Fri May 24 14:43:12 JST 2013 Binary: nyftp HEAD 05/22 binary. /etc/mk.conf is not set. Errors: =&gt; Bootstrap dependency digest&gt;=20010302: found digest-20121220 ===&gt; Checking for vulnerabilities in pkg-config-0.28 =&gt; Checksum SHA1 OK for pkg-config-0.28.tar.gz =&gt; Checksum RMD160 OK for pkg-config-0.28.tar.gz ===&gt; Installing dependencies for pkg-config-0.28 =&gt; Tool dependency libtool-base&gt;=2.2.6bnb3: found libtool-base-2.4.2nb2 ===&gt; Overriding tools for pkg-config-0.28 ===&gt; Extracting for pkg-config-0.28 ===&gt; Patching for pkg-config-0.28 =&gt; Applying pkgsrc patches for pkg-config-0.28 ===&gt; Creating toolchain wrappers for pkg-config-0.28 ===&gt; Configuring for pkg-config-0.28 =&gt; Modifying GNU configure scripts to avoid --recheck =&gt; Replacing config-</pre> HEO SeonMeyong 2013-05-24T08:17:19 http://permalink.gmane.org/gmane.os.netbsd.devel.pkgsrc.user/18137 <pre>Hi there, I am looking for a packet filter for netbsd 4.0 that can help with the isc.org ANY attack. The latest package tree does not have ³wip/iptables² in it and I am having trouble locating it on ftp.netbsd.org. I am thinking from reading that ipf does not have that functionality of limiting requests in a certain amount of time. What do some of you use? Or where do I find iptables? Thanks (again), Frank Frank DeChellis President, Internet Access Worldwide Welland, Ontario, Canada www.iaw.com </pre> Frank DeChellis 2013-05-24T02:51:37 http://permalink.gmane.org/gmane.os.netbsd.devel.pkgsrc.user/18136 <pre>Worked perfect. Thanks for your help. On 13-05-15 2:21 PM, "Jeremy C. Reed" &lt;reed&lt; at &gt;reedmedia.net&gt; wrote: Frank DeChellis President, Internet Access Worldwide Welland, Ontario, Canada www.iaw.com </pre> Frank DeChellis 2013-05-24T02:29:10 http://permalink.gmane.org/gmane.os.netbsd.devel.pkgsrc.user/18135 <pre> lipsum.ps is a postscript file generated by groff on another system. I can tell that it's valid because it opens in gs on that other system and even opens correctly on the OS X machine in Preview. ghostscript-fonts is installed as usual. All gs operations seem to break with this same type of error. Louis </pre> Louis Guillaume 2013-05-22T04:30:00 http://permalink.gmane.org/gmane.os.netbsd.devel.pkgsrc.user/18134 <pre>Hi, I did similar but not the same thing, but no problem here. OS: 10.6.0 Would you let me know how to generate lipsum.ps ? I don't check for the ghostscrit-fonts listed in last part of this mail, which happened to be installed for may previous necessity. d187&lt; at &gt;makoto 23:30:26/130521(..print/ghostscript-agpl)% grep X11 /usr/pkg/etc/mk.conf #X11_TYPE=native BUILTIN_X11_TYPE.native= Darwin getting lipsum.ps ----(test-lipsum.tex) ------- \documentclass{jarticle} \usepackage{lipsum} \begin{document} hoge \lipsum \lipsum[3-56] \end{document} -------------- platex test-lipsum.tex dvips test-lipsum.dvi d187&lt; at &gt;makoto 23:33:13/130521(~)% gs test-lipsum.ps GPL Ghostscript 9.07 (2013-02-14) Copyright (C) 2012 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Warning: the map file cidfmap was not found. d187&lt; at &gt;makoto 23:34:57/130521(~)% pkg_info |grep ghost ghostscript-agpl-9.07nb1 Postscript interpreter ghostscript-fonts-8.11nb3 Postscr</pre> Makoto Fujiwara 2013-05-21T14:40:16 http://permalink.gmane.org/gmane.os.netbsd.devel.pkgsrc.user/18133 <pre>Please update dvtm to v0.9, it was updated in March: http://lists.suckless.org/dev/1304/15112.html Thank you for your time. </pre> Christopher Hobbs 2013-05-21T03:17:15 http://permalink.gmane.org/gmane.os.netbsd.devel.pkgsrc.user/18132 <pre>Hi, I recently updated my OS X packages with the pkgsrc-2013Q1 release. This update saw the change from "ghostscript" to "ghostscript-agpl". I don't know if that has any bearing on this issue. The machine on which this was built is running OS X 10.8 (Mountain Lion). It seems that Ghostscript can't find fonts. For example: --- 8&lt; --- $ gs lipsum.ps GPL Ghostscript 9.07 (2013-02-14) Copyright (C) 2012 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Loading NimbusMonL-Regu font from %rom%Resource/Font/NimbusMonL-Regu... Error: /undefined in /findfont Operand stack: Courier&lt; at &gt;0 --nostringval-- Courier Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1900 1 3 %oparray_pop 1899 1 3 %oparray_pop 1883 1 3 %oparray_pop 1771 1 3 %oparray_pop --nostring</pre> Louis Guillaume 2013-05-20T18:15:29 http://permalink.gmane.org/gmane.os.netbsd.devel.pkgsrc.user/18131 <pre> GCC 4.5 is not enough, actually. 4.6 is the least acceptable version, if we're talking about Fortran dialect in current use. I have to point out that GCC 4.7 didn't build for me on 6.1 RCn for different reason until pkgsrcCon when it built the first time at all. I had problems building pkgsrc GCC 4.7 on Debian/Ubuntu systems after that time. Then this is the same old problem with official bulk builds. NetBSD 6.0 builds should be thrown away in favour of 6.1 or 6.0.2 at least until we get enough power to support it. My point is that if we're going to solve problems around Fortran by forcing everyone to use modern dialect, we should solve underlying problems first. Currently, there's a lot of packages that rely on F77 directly or indirectly. When combined with our insistance on using libtool it causes a lot of breakage. I don't know how to deal with it, since most reasons lie in social problems: - NetBSD developers resist shipping Fortran compiler; - NetBSD developers resist building packages on reaso</pre> Aleksej Saushev 2013-05-19T12:01:51 http://permalink.gmane.org/gmane.os.netbsd.devel.pkgsrc.user/18130 <pre> Well, the base system contains one: "gcc (NetBSD nb2 20110806) 4.5.3" The gcc47 package fails with /usr/include/x86/lock.h: Assembler messages: /usr/include/x86/lock.h:108: Error: bad register name `%sil' This is described in PR 45673 and fixed in -current, and has been pulled up to 6.0.2 and 6.1, so this is basically fixed at least for current and 6.x. Thomas </pre> Thomas Klausner 2013-05-19T09:26:05 http://permalink.gmane.org/gmane.os.netbsd.devel.pkgsrc.user/18129 <pre>from Jukka Ruohonen: and Jimmy Johansson: Current branch of pkgsrc is just as stable as quarterly. Stability issue is packages. Other package managers/frameworks such as FreeBSD ports, portage (Gentoo Linux) and Arch Linux (pacman and the Arch Build System) are all kept current. But the newer modular-xorg is highly experimental on NetBSD pkgsrc and FreeBSD ports; I believe is better on Linux. I wanted to upgrade xorg-modular installation on USB sticks (NetBSD) with pkgsrc tree and work directories on hard drive (FreeBSD UFS2/ffsv2 partition), but now I see maybe I shouldn't rush into it. Tom </pre> Thomas Mueller 2013-05-19T09:00:12 http://permalink.gmane.org/gmane.os.netbsd.devel.pkgsrc.user/18128 <pre> Ah, if I comment out ",osmesa" then I get much further, but it's still broken. </pre> Hisashi T Fujinaka 2013-05-19T00:03:19 http://permalink.gmane.org/gmane.os.netbsd.devel.pkgsrc.user/18127 <pre>With current sources, MesaLib doesn't appear to build. option.mk doesn't make that much sense to me. There's no dependency on libdrm but it appears to find an old version somewhere once I comment out the first error (in the log I'm attaching). </pre> Hisashi T Fujinaka 2013-05-18T23:57:17 http://permalink.gmane.org/gmane.os.netbsd.devel.pkgsrc.user/18126 <pre> Hello, Just in case anyone wonders what the problem with post-1977 Fortran is, here is the explanation: Manuel Bouyer &lt;bouyer&lt; at &gt;antioche.eu.org&gt; writes: We don't have _any_ reliably building modern compiler on NetBSD currently. lang/g95 is problematic too (it doesn't build on linux, for instance). </pre> Aleksej Saushev 2013-05-18T20:14:25 http://permalink.gmane.org/gmane.os.netbsd.devel.pkgsrc.user/18125 <pre> Herzlichen Dank, Leider verlassen Sie unseren Newsletter, sie wurden wie von Ihnen gewünscht bei unserem Newsletter abgemeldet! Diese Mail dient zu Ihrer Bestätigung! </pre> Newsletter Information 2013-05-18T15:19:05 http://permalink.gmane.org/gmane.os.netbsd.devel.pkgsrc.user/18124 <pre> Comparatively speaking, yes. It doesn't. If you set PKGSRC_FORTRAN to g95, you get it for both. Would be wrong. Joerg </pre> Joerg Sonnenberger 2013-05-18T07:44:22 http://permalink.gmane.org/gmane.os.netbsd.devel.pkgsrc.user/18122 <pre>Getting laid has never been easier. Join now. http://dir.brinstanroom.com yvyasz </pre> root< at >bricheolet.com 2013-05-17T17:54:00 http://permalink.gmane.org/gmane.os.netbsd.devel.pkgsrc.user/18121 <pre>Hi, From: Joerg Sonnenberger &lt;joerg&lt; at &gt;britannica.bec.de&gt;, Date: Sat, 18 May 2013 01:10:04 +0200 Do you want to say f2c is light package, and g95 is heavy package? I have thought when USE_LANGUAGES=fortran, g95 should be used, and when USE_LANGUAGES=fortran77, f2c should be used. But according to joerg&lt; at &gt;, fortran77 and fortran cannot coexist as pkgsrc compiler, because ABI incompatibility. My understanding is right? If fortran77 and fortran cannot coexist as pkgsrc compiler, when f2c is default fortran compiler, USE_LANGUAGES=fortran should not invoke g95. By the way, I have thought fc2 is only supports fortran77, but in pkgsrc/mk/compiler/f2c.mk, LANGUAGES.f2c=fortran fortran77 is defined. Is this correct? -- Ryo ONODERA // ryo_on&lt; at &gt;yk.rim.or.jp PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB FD1B F404 27FA C7D1 15F3 </pre> Ryo ONODERA 2013-05-18T00:08:25 http://permalink.gmane.org/gmane.os.netbsd.devel.pkgsrc.user/18120 <pre> Until recently, requiring a separate compiler would have been way too heavy for something like devel/libtool-base, which is needed by almost anything else. Now that Fortran is split off, the situation is much less dramatic. If someone really only wants to use Fortran77, f2c is good enough, but given e.g. the inability to build R with it, I find that a bad default choice. Joerg </pre> Joerg Sonnenberger 2013-05-17T23:10:04 http://permalink.gmane.org/gmane.os.netbsd.devel.pkgsrc.user/18118 <pre>Hi, From: Joerg Sonnenberger &lt;joerg&lt; at &gt;britannica.bec.de&gt;, Date: Thu, 16 May 2013 00:29:34 +0200 If fortran and fortran77 should use same compiler, what is the mean of having separate compiler options, fortran and fortran77. -- Ryo ONODERA // ryo_on&lt; at &gt;yk.rim.or.jp PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB FD1B F404 27FA C7D1 15F3 </pre> Ryo ONODERA 2013-05-17T22:49:39 http://permalink.gmane.org/gmane.os.netbsd.devel.pkgsrc.user/18117 <pre> My bad, I wasn't aware of that, thanks for the pointer. ------------------------------------------------------------------ Emile `iMil' Heitor .°. &lt;imil&lt; at &gt;{home.imil.net,NetBSD.org,gcu.info}&gt; _ | http://imil.net | ASCII ribbon campaign ( ) | http://www.NetBSD.org | - against HTML email X | http://gcu.info | &amp; vCards / \ </pre> iMil 2013-05-17T13:41:04 http://permalink.gmane.org/gmane.os.netbsd.devel.pkgsrc.user/18116 <pre>JFYI: pkg_install had been resolved the issue over 4 years ago. http://mail-index.netbsd.org/pkgsrc-changes/2009/02/13/msg018399.html On Fri, 17 May 2013 15:24:35 +0900, iMil &lt;imil&lt; at &gt;home.imil.net&gt; wrote: </pre> OBATA Akio 2013-05-17T06:45:15 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.os.netbsd.devel.pkgsrc.user