CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: b...@cvs.openbsd.org2012/12/09 01:23:31 Modified files: devel/boost: Makefile distinfo Log message: Mostly cosmetic tweaking and sync distinfo. ok ajacoutot@
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2012/12/09 06:21:43 Modified files: telephony/asterisk: Tag: OPENBSD_5_2 Makefile distinfo telephony/asterisk/patches: Tag: OPENBSD_5_2 patch-channels_chan_unistim_c patch-main_features_c Log message: Update Asterisk in 5.2-stable to 1.8.18.1, various fixes including deadlocks, crashes, thread and memory leaks and heap corruption.
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2012/12/09 07:17:41 Modified files: . : INDEX Log message: sync; 7843. 1255(+), 1146(-)
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: r...@cvs.openbsd.org2012/12/09 15:05:25 Modified files: www/awstats: Makefile www/awstats/pkg: README Log message: - set NO_REGRESS=Yes - mark as arch independed - make the pre-configure/do-install blocks more compact using vars - adjust paths in docs/*.html too to reflect the installation - mention in README, that the default config works for localhost httpd out of the box and how to access the reports - bump REVISION feedback from and ok kirby@, sthen@
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: ajacou...@cvs.openbsd.org 2012/12/10 00:16:39 Modified files: devel/pango/patches: patch-pango_pango-font_h Log message: Committed upstream.
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: ajacou...@cvs.openbsd.org 2012/12/10 00:20:29 Modified files: mail/gmime : Makefile distinfo Log message: Minor update to gmime-2.6.13.
How to size /usr/ports? And is libreoffice for 5.2 known to be broken?
I did a pkg_add for Libreoffice on 5.2 stable and when I run libreoffice I get errors about a size mismatch in libstdc++ and the screen is not painted properly. I tried to build the port but I don't have enough space allocated. Is libreoffice known to be broken on AMD64 5.2-stable? How much space should I allocate to /usr/ports to be able to build anything in the tree at this point? Looking at the man page for ports and bsd.port.mk I am not sure whether moving the work directory elsewhere (I have plenty of space in var) would work or whether everything needs to be in one tree. Thanks. /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04
Re: How to size /usr/ports? And is libreoffice for 5.2 known to be broken?
On 2012/12/09 08:37, John Long wrote: I did a pkg_add for Libreoffice on 5.2 stable and when I run libreoffice I get errors about a size mismatch in libstdc++ and the screen is not painted properly. I tried to build the port but I don't have enough space allocated. The size mismatch errors are because there is a mixture of libraries using C++ which are compiled with GCC 4.2.1 from base, and the main program which is compiled with GCC 4.6.3 from ports. This is not really a great situation but to fix it basically means everything c++ (ports/X) would need to be compiled with ports GCC. Is libreoffice known to be broken on AMD64 5.2-stable? I don't have anything running 5.2 at present (everything's -current here) but in practice libreoffice (and chrome which has the same problem) does usually run OK so I *think* the screen not being painted properly is probably not related to the conflicting symbols which trigger the size mismatch. How much space should I allocate to /usr/ports to be able to build anything in the tree at this point? Looking at the man page for ports and bsd.port.mk I am not sure whether moving the work directory elsewhere (I have plenty of space in var) would work or whether everything needs to be in one tree. You can happily use a work directory outside of /usr/ports; set WRKOBJDIR in /etc/mk.conf. I do this on pretty much every machine I build ports on (the default auto-partitioning layout is geared towards people using packages rather than building from ports). However: I don't think a self-built libreoffice is likely to work any better, and building it is rather painful. Probably better to look around and see what more information you can find about what's happening. Describing the screen painting problem might be useful (i.e. what you do, what you see). And there are other things you can try - is it tied to a specific window manager, for example?
Re: How to size /usr/ports? And is libreoffice for 5.2 known to be broken?
Thanks for the explanations Stuart. I didn't look into the problem too much before trying to build the port because I figured it might be a problem with the package. After your reply I realize this is a tough situation. Is libreoffice known to be broken on AMD64 5.2-stable? I don't have anything running 5.2 at present (everything's -current here) but in practice libreoffice (and chrome which has the same problem) does usually run OK so I *think* the screen not being painted properly is probably not related to the conflicting symbols which trigger the size mismatch. Looks like the libreoffice version numbers on current and stable differ quite a bit so I'm not sure if we can draw any conclusions based on what works in current. It would be helpful to know if anybody else is running it without issues in stable on AMD64 though. How much space should I allocate to /usr/ports to be able to build anything in the tree at this point? Looking at the man page for ports and bsd.port.mk I am not sure whether moving the work directory elsewhere (I have plenty of space in var) would work or whether everything needs to be in one tree. You can happily use a work directory outside of /usr/ports; set WRKOBJDIR in /etc/mk.conf. I do this on pretty much every machine I build ports on (the default auto-partitioning layout is geared towards people using packages rather than building from ports). I never take the auto layout either but in the past 5G ports has been plenty. I didn't build any behemoths like libreoffice obviously! Thanks for confirming WRKOBJDIR will do the trick. I was about to try it but wasn't sure I understood the man page warnings about stuff out of tree not building correctly 100% of the time, given this port was already questionable to begin with. I didn't want to introduce any other source of possible screwups while attempting to get a good copy. However: I don't think a self-built libreoffice is likely to work any better, and building it is rather painful. This makes sense after your explanation above. Probably better to look around and see what more information you can find about what's happening. Describing the screen painting problem might be useful (i.e. what you do, what you see). And there are other things you can try - is it tied to a specific window manager, for example? Basically when it starts up it leaves a major U-shaped space on the screen unpainted. Whatever was there before shows up and doesn't get covered by libreoffice. At first I thought it was the splash screen like OO used to have but that is square, not this bizarre T shape. I was able to do some things like open a new document but it was not operating like my old OO normally did, some things were just weird. It feels sick, something is definitely not right. Since I figured the package was broken I didn't pay too much attention to the details and from experience it seems like if a port is broken the answer is to run -current anyway so I figured if it was broken it wasn't going to be useful to give too much detail on it. Maybe I am wrong but that's what I have seen in the past on the mailing list. I just converted my main desktop to OpenBSD because I was so happy with it on my Loongson. I used OpenBSD years ago and drifted away from it because I was multibooting too many OS but came back recently because of the quality and because I needed something to run on a Loongson box. After that I figured it was time to reduce the number of OS I have running here and I am not happy with the directions Linux is going in and the other BSD projects seem to be struggling so OpenBSD won. I am not bashing any of those projects since I have used them all productively in the past and appreciate all the work that goes into them but everybody has his own preferences right? I do want to say thank you again to all the OpenBSD people because you put out a great OS and I can see people really pay attention to detail and usually give a damn and take it hard if something isn't right. The flaming can suck but on the other hand bullshit is significantly reduced and quality stays up. Anyway I had no way to test ahead of time to see if the apps I need will work since this is a one-off box with el-cheapo components, couldn't emulate it on qemu or vbox etc. so I just winged it. I'm going to see if I have better luck with the last release of OO on another system that libreoffice isn't available for. At this point I need to be able to edit some old doc. If you think the port from current will build and run on stable I have no problem trying it. This box runs pretty good (takes like 45/30 minutes to build userland/xenocara) and it's no problem to build big ports now that you said I can move the work directory. Thanks alot for your reply. /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \
Re: How to size /usr/ports? And is libreoffice for 5.2 known to be broken?
On Sun, Dec 09, 2012 at 12:30:38PM +, Stuart Henderson wrote: Probably better to look around and see what more information you can find about what's happening. Describing the screen painting problem might be useful (i.e. what you do, what you see). I've been having problems with fonts in libreoffice lately. Not sure what's causing it. Here's what it looks like: http://stsp.name/images/libreoffice-fonts.jpg Anyone else seeing this?
Re: How to size /usr/ports? And is libreoffice for 5.2 known to be broken?
On Sun, Dec 09, 2012 at 02:16:21PM +0100, Stefan Sperling wrote: On Sun, Dec 09, 2012 at 12:30:38PM +, Stuart Henderson wrote: Probably better to look around and see what more information you can find about what's happening. Describing the screen painting problem might be useful (i.e. what you do, what you see). I've been having problems with fonts in libreoffice lately. Not sure what's causing it. Here's what it looks like: http://stsp.name/images/libreoffice-fonts.jpg Anyone else seeing this? What hardware (graphics card driver) are you using ? -- Matthieu Herrb
Re: How to size /usr/ports? And is libreoffice for 5.2 known to be broken?
How much space should I allocate to /usr/ports to be able to build anything in the tree at this point? Looking at the man page for ports and bsd.port.mk I am not sure whether moving the work directory elsewhere (I have plenty of space in var) would work or whether everything needs to be in one tree. if you are building ports it is also important to 1) bump your /usr/local from the default 10g to atleast 20g, i think i have set it to 60g so i can hold the entire ports tree. 2) have /usr/ports/pobj or WRKOBJDIR on a separate partition, so you can just newfs it before building huge ports. 3) bump datasize limits in /etc/login.conf to 2G. Mozilla firefox and some other ports need upto 1.5 G to link. 4) watch /usr/ports/distfiles like a hawk, and delete old stuff from there. 5) enable ccache in /etc/mk.conf to speed up repetitive compiles. 6) man dpb building libre-office is painful, it takes hours and hours (i think it takes 6-12 hours on this box) even on a fast quad core ivy bridge xeon. this box builds userland in 14 mins.you would probably take around 18 hrs-32 hrs. just FYI.
Re: UPDATE: TeX Live 2012
On Fri, Nov 16, 2012 at 01:00:29AM +, Edd Barrett wrote: On Thu, Nov 15, 2012 at 11:16:41AM +, Stuart Henderson wrote: Using the patch provided by sthen, it doesn't build for me on amd64: http://junkpile.org/tl.diff.2 - texlive-base builds on -current now (following the changes to make to preserve whitespace). Ah, I was about to post a simialr diff. Yeh, we figured out that the recent make changes hosed my comments. When testing, can people please test the upgrade too. Works for me (tm), but i would like to be sure that I did not miss anything. I've been using this for various LaTeX work on both i386 and amd64 for a while now. No visible issue. ok matthieu@ -- Matthieu Herrb
Re: How to size /usr/ports? And is libreoffice for 5.2 known to be broken?
On Sun, Dec 09, 2012 at 07:39:38AM -0600, Amit Kulkarni wrote: How much space should I allocate to /usr/ports to be able to build anything in the tree at this point? Looking at the man page for ports and bsd.port.mk I am not sure whether moving the work directory elsewhere (I have plenty of space in var) would work or whether everything needs to be in one tree. if you are building ports it is also important to 1) bump your /usr/local from the default 10g to atleast 20g, i think i have set it to 60g so i can hold the entire ports tree. 2) have /usr/ports/pobj or WRKOBJDIR on a separate partition, so you can just newfs it before building huge ports. 3) bump datasize limits in /etc/login.conf to 2G. Mozilla firefox and some other ports need upto 1.5 G to link. 4) watch /usr/ports/distfiles like a hawk, and delete old stuff from there. 5) enable ccache in /etc/mk.conf to speed up repetitive compiles. 6) man dpb Thanks alot. I don't think I will be bulk building anytime soon but I will keep your email around. Good info. building libre-office is painful, it takes hours and hours (i think it takes 6-12 hours on this box) even on a fast quad core ivy bridge xeon. this box builds userland in 14 mins.you would probably take around 18 hrs-32 hrs. just FYI. Wow! -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04
Re: How to size /usr/ports? And is libreoffice for 5.2 known to be broken?
On Sun, Dec 09, 2012 at 02:32:14PM +0100, Matthieu Herrb wrote: On Sun, Dec 09, 2012 at 02:16:21PM +0100, Stefan Sperling wrote: On Sun, Dec 09, 2012 at 12:30:38PM +, Stuart Henderson wrote: Probably better to look around and see what more information you can find about what's happening. Describing the screen painting problem might be useful (i.e. what you do, what you see). I've been having problems with fonts in libreoffice lately. Not sure what's causing it. Here's what it looks like: http://stsp.name/images/libreoffice-fonts.jpg Anyone else seeing this? What hardware (graphics card driver) are you using ? It's an Intel Pineview GM. Full dmesg and X log below. (Nevermind the athn debug stuff in dmesg. The kernel contains some WIP patches for the athn, it's an unsupported chip.) OpenBSD 5.2-current (GENERIC.MP) #351: Fri Dec 7 22:58:29 CET 2012 s...@byrne.stsp.name:/usr/src/sys/arch/i386/compile/GENERIC.MP RTC BIOS diagnostic error 80clock_battery cpu0: Intel(R) Atom(TM) CPU N435 @ 1.33GHz (GenuineIntel 686-class) 1.34 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,LAHF,PERF real mem = 2134695936 (2035MB) avail mem = 2088824832 (1992MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 10/21/11, BIOS32 rev. 0 @ 0xef735, SMBIOS rev. 2.6 @ 0xe5830 (33 entries) bios0: vendor INSYDE version V1.15 date 10/21/2011 bios0: Packard Bell dot s acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET APIC MCFG SLIC BOOT SSDT SSDT SSDT WDAT acpi0: wakeup devices P32_(S4) UHC1(S3) UHC2(S3) UHC3(S3) UHC4(S3) ECHI(S3) EXP1(S4) EXP2(S3) EXP3(S3) EXP4(S3) AZAL(S4) MODM(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 166MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Atom(TM) CPU N435 @ 1.33GHz (GenuineIntel 686-class) 1.34 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,LAHF,PERF ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 4 acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 4 (P32_) acpiprt2 at acpi0: bus 1 (EXP1) acpiprt3 at acpi0: bus 2 (EXP2) acpiprt4 at acpi0: bus 3 (EXP3) acpiprt5 at acpi0: bus -1 (EXP4) acpiec0 at acpi0 acpicpu0 at acpi0: C2, C1, PSS acpicpu1 at acpi0: C2, C1, PSS acpitz0 at acpi0: critical temperature is 98 degC acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: SLPB acpibtn2 at acpi0: LID_ acpiac0 at acpi0: AC unit offline acpibat0 at acpi0: BAT1 model AL10B31 serial 2883 type LION oem SANYO acpivideo0 at acpi0: GFX0 acpivout0 at acpivideo0: DD02 bios0: ROM list: 0xc/0xda00! 0xcda00/0x1000 cpu0: Enhanced SpeedStep 1331 MHz: speeds: 1333, 1000 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel Pineview DMI rev 0x00 vga1 at pci0 dev 2 function 0 Intel Pineview Video rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) intagp0 at vga1 agp0 at intagp0: aperture at 0x8000, size 0x1000 inteldrm0 at vga1: apic 4 int 16 drm0 at inteldrm0 Intel Pineview Video rev 0x00 at pci0 dev 2 function 1 not configured azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x02: msi azalia0: codecs: Realtek ALC269 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x02: apic 4 int 16 pci1 at ppb0 bus 1 re0 at pci1 dev 0 function 0 Realtek 8101E rev 0x05: RTL8105E (0x4080), apic 4 int 16, address 04:7d:7b:21:ad:9d ukphy0 at re0 phy 7: Generic IEEE 802.3u media interface, rev. 2: OUI 0x000732, model 0x0008 ppb1 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x02: apic 4 int 17 pci2 at ppb1 bus 2 athn0 at pci2 dev 0 function 0 Atheros AR9485 rev 0x01: apic 4 int 17 ROM block 0: alg=3 ref=2 len=256 ROM chunk @2/6 ROM chunk @28/1 ROM chunk @32/4 ROM chunk @40/3 ROM chunk @46/3 ROM chunk @73/6 ROM chunk @106/8 ROM chunk @124/1 ROM chunk @140/4 ROM chunk @147/3 ROM chunk @153/3 ROM chunk @196/1 ROM chunk @206/20 ROM chunk @229/11 ROM chunk @243/11 ROM chunk @257/11 ROM chunk @271/11 ROM chunk @285/11 ROM chunk @299/11 ROM chunk @324/1 ROM chunk @328/9 ROM chunk @344/9 ROM chunk @356/62 found RF switch connected to GPIO pin 7 128 key cache entries using closed loop power control txchainmask=0x1 rxchainmask=0x1 athn0: AR9485 rev 1 (1T1R), ROM rev 0, address 74:de:2b:ee:dd:3e ppb2 at pci0 dev 28 function 2 Intel 82801GB PCIE rev 0x02: apic 4 int 18 pci3 at ppb2 bus 3 rtsx0 at pci3 dev 0 function 0 Realtek RTS5209 Card Reader rev 0x01:
Re: How to size /usr/ports? And is libreoffice for 5.2 known to be broken?
Sorry I've not got time for a detailed answer to the whole mail right now, but updating one port to -current without also updating dependencies is often going to fail (especially for things like this which have many dep's). Since 5.2 there has been quite a lot of cleanup of system headers, so various ports have had workarounds removed so they're unlikely to build on 5.2 without a lot of extra work. This is why developers will often recommend just moving to -current; and that way if the problem still exists, you will be running the same OS/package version that others can easily obtain themselves making it easier to work on a fix. On OpenBSD -current always ought to be (and in general is) at least as reliable as -stable (and often more so). The naming -stable is intended to imply stable api / very conservative changes only rather than stable as in reliable. This is not necessarily the same meanings as given to the words in some other OS. Things I'd point out, - if this was an upgrade rather than new installation, make sure all packages were upgraded together; mixing and matching between versions rarely works well - the symptoms might suggest some kind of X/display driver type of problem, so more information about hardware (dmesg) might be helpful
Re: How to size /usr/ports? And is libreoffice for 5.2 known to be broken?
On Sun, Dec 09, 2012 at 02:01:21PM +, Stuart Henderson wrote: Sorry I've not got time for a detailed answer to the whole mail right now, but updating one port to -current without also updating dependencies is often going to fail (especially for things like this which have many dep's). I realize the probability of success is inversely proportional to the number of deps. Recently I did get gdb 7.5 working on mips64el stable after I mentioned gdb losing its mind unwinding the stack and somebody mentioned 7.5 works. Luckily the port from current builds cleanly. Since 5.2 there has been quite a lot of cleanup of system headers, so various ports have had workarounds removed so they're unlikely to build on 5.2 without a lot of extra work. This is why developers will often recommend just moving to -current; and that way if the problem still exists, you will be running the same OS/package version that others can easily obtain themselves making it easier to work on a fix. I do run current on Loongson because I'm not using it constantly and can afford to monkey around with it occasionally but on this box I don't want to have to upgrade if I can avoid it, until 5.3 comes out. At this point I'm trying to set up all the stuff I need and then just use it. On OpenBSD -current always ought to be (and in general is) at least as reliable as -stable (and often more so). The naming -stable is intended to imply stable api / very conservative changes only rather than stable as in reliable. This is not necessarily the same meanings as given to the words in some other OS. Thanks, I realize that too. I look at it as the difference between changing as little as possible and low admin cost on a stable system while still having an excellent upgrade and patching path, with current being a state of the art system but one that requires frequent upgrades if anything goes wrong. I want to get this particular box doing what I want then to spend as little time managing it as possible. Things I'd point out, - if this was an upgrade rather than new installation, make sure all packages were upgraded together; mixing and matching between versions rarely works well It is a new 5.2 install. - the symptoms might suggest some kind of X/display driver type of problem, so more information about hardware (dmesg) might be helpful I don't think so since everything else works flawlessly as usual. I just installed OO on a Solaris box and it gets me past this issue so I'll wait for 5.3 to come out and then try libreoffice again. Thanks alot for taking the time to explain things. /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04
Re: Importing supercollider-3.6.1 and about boost
On Sun, 9 Dec 2012 08:02:01 -0600, Amit Kulkarni wrote: Mark as BROKEN-hppa, triggers an ICE in src/tr1/assoc_laguerre.cpp, apparently related the switch to PIE and the fact that boost uses precompiled .gch headers. This is no longer true since base gcc is now compiled as non-PIE. Someone should remove the BROKEN marker ...
Re: new: net/bitcoin
On Sat, 26 May 2012 15:44:31 +0200, Pascal Stumpf wrote: Bitcoin is an experimental new digital currency that enables instant payments to anyone, anywhere in the world. Bitcoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Bitcoin is also the name of the open source software which enables the use of this currency. Of course, mining is not very efficient on OpenBSD, but it is still useful to manage your wallet, make transactions etc. Updated port attached (0.7.1), latest update done by Alex Bula. ok? bitcoin.tgz Description: bitcoin.tgz
Re: new: net/bitcoin
On Sun, Dec 09, 2012 at 05:09:56PM +0100, Pascal Stumpf wrote: [...] ok? There seems to be one superflouus file, patches/patch-srd_db.cpp.org. Can't say anything else yet, it's still building. -- Gregor Best
Re: Importing supercollider-3.6.1 and about boost
2012/12/8 Abel Abraham Camarillo Ojeda acam...@verlet.org: I'm trying to import supercollider-3.6.1 into our ports system, but it needs devel/boost at least 1.50.0 I'm looking into how to update it but I saw a lot of messages lately about devel/boost problems with PIE or something like that is devel/boost that hard to update?, I guess that even if I update it I will need to be sure if nothing get break by that... There's a particular reason because it haven't been updated? Do you really want to give boost for supercollider just before Doomsday? -- WBR, Vadim Zhukov
new: net/tinc
Hi ports@, I am trying to create a port for the tinc VPN daemon. Attached are my efforts this far, but they are not yet perfect. tinc.conf.5 contains syntax errors which I was unable to fix. Mandoc complains FATAL: child violates parent syntax if anyone could give me a hint on how to fix that, I'd be happy to submit a fully working port. -- Gregor Best net-tinc.tbz Description: Binary data
Re: Importing supercollider-3.6.1 and about boost
With boost-1.52.0 from jasperla/openbsd-wip supercollider-3.6.1 builds fine, I needed to make some patches for it to build, I'm sending them upstream, but I still have lots of runtime errors, will work with upstream on that. Thanks. On Sat, Dec 8, 2012 at 9:23 AM, Amit Kulkarni amitk...@gmail.com wrote: I'm trying to import supercollider-3.6.1 into our ports system, but it needs devel/boost at least 1.50.0 I'm looking into how to update it but I saw a lot of messages lately about devel/boost problems with PIE or something like that where did you see PIE problems? please point it out. is devel/boost that hard to update?, I guess that even if I update it I will need to be sure if nothing get break by that... There's a particular reason because it haven't been updated? see https://github.com/jasperla/openbsd-wip/tree/master/devel/boost databases/mongodb doesn't work (it might get looked at this month) and games/pokerth needs to be updated (i will do it soon...). I have updated other boost-affected ports in wip... you can test boost 1.52.0 and report here if you find any problems.
Re: Importing supercollider-3.6.1 and about boost
On Sun, Dec 09, 2012 at 03:30:49PM +0100, Pascal Stumpf wrote: On Sun, 9 Dec 2012 08:02:01 -0600, Amit Kulkarni wrote: Mark as BROKEN-hppa, triggers an ICE in src/tr1/assoc_laguerre.cpp, apparently related the switch to PIE and the fact that boost uses precompiled .gch headers. This is no longer true since base gcc is now compiled as non-PIE. Someone should remove the BROKEN marker ... Well if somone with an hppa system can double check it builds OK then I'd love to do so. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Re: new: net/tinc
On 2012/12/09 22:16, Gregor Best wrote: Hi ports@, I am trying to create a port for the tinc VPN daemon. Attached are my efforts this far, but they are not yet perfect. tinc.conf.5 contains syntax errors which I was unable to fix. Mandoc complains FATAL: child violates parent syntax if anyone could give me a hint on how to fix that, I'd be happy to submit a fully working port. -- Gregor Best USE_GROFF=Yes
Re: new: net/tinc
On Sun, Dec 09, 2012 at 11:08:02PM +, Stuart Henderson wrote: [...] USE_GROFF=Yes [...] An updated port is attached. Should I write an introductory paragpraph like the other New: foo/bar mails do for other ports? -- Gregor Best net-tinc.tbz Description: Binary data
Re: UPDATE: sysutils/runit 2.1.1 rc.d script
Hi,
runsvdir and runit-init work fine so far on i386 (-current), even if
I find it weird that upstream goes back to /service - I just symlinked
/service to /var/service, the ''install -d /service'' step in rc_pre()
does respect that.
etc/openbsd/3 would obviously need patching to work properly out of the
box (it calls sv(8) while this one isn't in PATH); perl -pie can help
but caring about this could be interpreted as remplacing init with
runit is supported, so... :)
Attached is a lightly tested patch to handle ctrlaltdel. The OpenBSD
kernel sends pid 1 SIGUSR1, not SIGINT, the patch basically makes runit
consider both as equivalent; that is different from the way our init
handles them but that's good enough at least for my use case. It would
of course need more tweaking before being sent upstream.
--
Jérémie Courrèges-Anglas
GPG Key fingerprint: 61DB D9A0 00A4 67CF 2A90 8961 6191 8FBF 06A1 1494
diff -pruN /usr/ports/sysutils/runit/patches/patch-src_runit_c /usr/ports/mystuff/sysutils/runit/patches/patch-src_runit_c
--- /usr/ports/sysutils/runit/patches/patch-src_runit_c Thu Jan 1 01:00:00 1970
+++ /usr/ports/mystuff/sysutils/runit/patches/patch-src_runit_c Mon Dec 10 04:03:46 2012
@@ -0,0 +1,38 @@
+$OpenBSD$
+Add SIGUSR1 support.
+--- src/runit.c.orig Sun Dec 9 19:35:19 2012
src/runit.c Sun Dec 9 19:38:42 2012
+@@ -66,6 +66,8 @@ int main (int argc, const char * const *argv, char * c
+ sig_block(sig_hangup);
+ sig_block(sig_int);
+ sig_catch(sig_int, sig_int_handler);
++ sig_block(sig_usr1);
++ sig_catch(sig_usr1, sig_int_handler);
+ sig_block(sig_pipe);
+ sig_block(sig_term);
+
+@@ -129,6 +131,8 @@ int main (int argc, const char * const *argv, char * c
+ sig_unblock(sig_hangup);
+ sig_unblock(sig_int);
+ sig_uncatch(sig_int);
++ sig_unblock(sig_usr1);
++ sig_uncatch(sig_usr1);
+ sig_unblock(sig_pipe);
+ sig_unblock(sig_term);
+
+@@ -145,6 +149,7 @@ int main (int argc, const char * const *argv, char * c
+ sig_unblock(sig_child);
+ sig_unblock(sig_cont);
+ sig_unblock(sig_int);
++ sig_unblock(sig_usr1);
+ #ifdef IOPAUSE_POLL
+ poll(x, 1, 14000);
+ #else
+@@ -156,6 +161,7 @@ int main (int argc, const char * const *argv, char * c
+ sig_block(sig_cont);
+ sig_block(sig_child);
+ sig_block(sig_int);
++ sig_block(sig_usr1);
+
+ while (read(selfpipe[0], ch, 1) == 1) {}
+ while ((child =wait_nohang(wstat)) 0)
diff -pruN /usr/ports/sysutils/runit/patches/patch-src_sig_c /usr/ports/mystuff/sysutils/runit/patches/patch-src_sig_c
--- /usr/ports/sysutils/runit/patches/patch-src_sig_c Thu Jan 1 01:00:00 1970
+++ /usr/ports/mystuff/sysutils/runit/patches/patch-src_sig_c Mon Dec 10 04:03:58 2012
@@ -0,0 +1,12 @@
+$OpenBSD$
+Add SIGUSR1 support.
+--- src/sig.c.orig Sun Oct 4 22:44:02 2009
src/sig.c Sun Dec 9 19:31:42 2012
+@@ -10,6 +10,7 @@ int sig_hangup = SIGHUP;
+ int sig_int = SIGINT;
+ int sig_pipe = SIGPIPE;
+ int sig_term = SIGTERM;
++int sig_usr1 = SIGUSR1;
+
+ void (*sig_defaulthandler)() = SIG_DFL;
+ void (*sig_ignorehandler)() = SIG_IGN;
diff -pruN /usr/ports/sysutils/runit/patches/patch-src_sig_h /usr/ports/mystuff/sysutils/runit/patches/patch-src_sig_h
--- /usr/ports/sysutils/runit/patches/patch-src_sig_h Thu Jan 1 01:00:00 1970
+++ /usr/ports/mystuff/sysutils/runit/patches/patch-src_sig_h Mon Dec 10 04:04:04 2012
@@ -0,0 +1,12 @@
+$OpenBSD$
+Add SIGUSR1 support.
+--- src/sig.h.orig Sun Dec 9 19:48:13 2012
src/sig.h Sun Dec 9 19:48:04 2012
+@@ -10,6 +10,7 @@ extern int sig_hangup;
+ extern int sig_int;
+ extern int sig_pipe;
+ extern int sig_term;
++extern int sig_usr1;
+
+ extern void (*sig_defaulthandler)();
+ extern void (*sig_ignorehandler)();
