Pike-devel

pike-devel@lists.lysator.liu.se

1 participants
3045 discussions

Bug in aclocal.m4?
by Pontus Östlund 16 Mar '18

16 Mar '18

I found the following in aclocal.m4 if test "x$enable_binary" = "no"; then Allthough I'm lamer in comparison to most developers, in my world that can never evaluate to true. It's been like that since 2002-01-27. I have no idea what the code folloing the statement does in practice though. And then I saw the following in configure.in # Do the below even when --disable-binary is used, since we need a # real $CPP, and AC_PROG_CPP wants AC_PROG_CC to be called earlier. # $CC will be overridden with a dummy later on. # MY_AC_PROG_CC # The above has problems if the smartlink binary is removed. /grubba Which seems somewhat related? Now, I have no idea what this code does so maybe there's nothing to bother about. But from a glance it looked somewhat suspicious so I though I'd report it. Regards ----------------------------- Pontus Östlund Developer • Roxen AB +46 70-662 81 69 www.roxen.com <http://www.roxen.com/> | twitter.com/roxen <https://twitter.com/roxen>

2 1

8.0 and precompiled pike files...
by Stephen R. van den Berg 07 Mar '18

07 Mar '18

The current git version of 8.0, but it has been this way for at least the past two months, works fine for me as long as I remove all *.o files from the installed version. If I do not do that, it crashes right away with a segmentation fault. It does not matter if I compile it with gcc 6, 7 or 8. Same result. Is that just on my system, or is this a generic .o file dumping problem in pike 8.0? I regularly compile with: --with-cdebug --without-rtldebug --without-valgrind --with-double-precision --with-long-int --disable-noopty-retry --with-machine-code --without-portable-bytecode -g -O2 on an amd64 linux system (devel2, to be exact, from pikefarm). -- Stephen.

1 2

Type warnings on 8.0?
by Stephen R. van den Berg 15 Feb '18

15 Feb '18

lib/modules/__builtin.pmod/Nettle.pmod/Hash.pike:446: Warning: Not a valid object type. lib/modules/__builtin.pmod/Nettle.pmod/Hash.pike:446: Warning: Expected: function(void | mixed ... : object) | object | program. lib/modules/__builtin.pmod/Nettle.pmod/Hash.pike:446: Warning: Got : mixed. lib/modules/__builtin.pmod/Nettle.pmod/Hash.pike:532: Warning: Invalid type. lib/modules/__builtin.pmod/Nettle.pmod/Hash.pike:532: Warning: Expected: function(void | mixed ... : object) | object | program | type(mixed). lib/modules/__builtin.pmod/Nettle.pmod/Hash.pike:532: Warning: Got : mixed. lib/modules/__builtin.pmod/Nettle.pmod/Hash.pike:593: Warning: Invalid type. lib/modules/__builtin.pmod/Nettle.pmod/Hash.pike:593: Warning: Expected: function(void | mixed ... : object) | object | program | type(mixed). lib/modules/__builtin.pmod/Nettle.pmod/Hash.pike:593: Warning: Got : mixed. I tried parsing the code, but the solution is non-obvious (at least to me). -- Stephen.

2 2

cp is different from rm/mv
by Stephen R. van den Berg 12 Feb '18

12 Feb '18

The reason why rm and mv are are first class citizens is because they correspond to libc/system calls (unlink and rename). "cp" has no libc/system call equivalent. commit 76dc18c99a3b30f91d5f3a7007b972081af9bc09 Author: Martin Nilsson <nilsson(a)fastmail.com> Date: Fri Feb 9 19:24:29 2018 +0100 Put cp() in the global scope, as rm() and mv() are already there. So polluting the global namespace with cp is not necessarily a logical step. -- Stephen.

4 3

Doc fixes and @namespace removal
by Stephen R. van den Berg 08 Feb '18

08 Feb '18

Could someone please take a look at: commit a05ef1359a8c06e6f63ccd5ac8086d2c21823a2e (HEAD -> 8.1, origin/8.1, devel/8.1) Author: Stephen R. van den Berg <srb(a)cuci.nl> Date: Thu Feb 8 13:44:04 2018 +0100 Fix typos and docs. lib/master.pike.in | 24 +----------------------- lib/modules/Crypto.pmod/RC4.pmod | 2 +- lib/modules/Crypto.pmod/module.pmod | 2 +- lib/modules/Tools.pmod/Hilfe.pmod | 10 +++++----- src/sprintf.c | 2 +- src/string_builder.cmod | 3 +++ 6 files changed, 12 insertions(+), 31 deletions(-) I kicked out some @namespace and @endnamespace directives that autodoc complained about. I'm unsure if simply removing them had the desired effect. -- Stephen.

2 2

Protocols.DNS.server anyone used it in a DNS server?
by Stephen R. van den Berg 08 Feb '18

08 Feb '18

Has anyone ever used Protocols.DNS.server in an application (to implement a mini-DNS server)? Is the code available? -- Stephen.

3 3

Re: Pull request - jemalloc
by Tomasz Jamroszczak 07 Feb '18

07 Feb '18

On Tue, 06 Feb 2018 14:58:02 +0100, Peter Bortas @ Pike developers forum <10353(a)lyskom.lysator.liu.se> wrote: > Right, then I have no general complaints left (if the USE_JEMALLOC > thing Nilsson pointed out is cleared up). This looks localized > enough that it shouldn't break anything. OK, I'll modify the pull request soon after a few more compilations. > I'm curious what benchmarks have been run with this. Do you have any > before and after comparisons for this Tomasz? From cursory testing of Opera Mini transcoder where both Pike and Presto web browser engine using jemalloc on several machines for a few days I can see 15% - 20% smaller memory footprint at the cost of bigger CPU usage. But there's a lot of moving parts so these numbers should not be trusted. I'll have sound numbers in a week. -- Best Regards Tomasz Jamroszczak

2 2

MPI breaks on SunOS
by Stephen R. van den Berg 06 Feb '18

06 Feb '18

In case nobody noticed, Pikefarm seems to break on SunOS because it tries to compile in MPI without proper libs. -- Stephen.

6 6

Pull request - jemalloc
by Tomasz Jamroszczak 06 Feb '18

06 Feb '18

Hi. I'm first time poster. I'm working for Opera Software and I'm developing Opera Mini server, which involves quite a lot of Pike. I've added handling of jemalloc to Pike build and I'd like to upstream it to Pike repository. What's the procedure (a "pull request") to proceed with the change? -- Best Regards Tomasz Jamroszczak

5 7

Re: Pull request - jemalloc
by Tomasz Jamroszczak 06 Feb '18

06 Feb '18

On Tue, 06 Feb 2018 14:48:01 +0100, Martin Nilsson (Coppermist) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > Perhaps I'm missing something, but you are testing for > jemalloc/jemalloc.h in configure, but then include it regardless of > the result. Right. I think the src/global.h should read: #if defined(USE_JEMALLOC) && defined(HAVE_JEMALLOC_JEMALLOC_H) -- Best Regards Tomasz Jamroszczak

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pike-devel