Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

Pike 7.2 on FreeBSD 5.3/Sparc64
by Xavier Beaudouin 10 Nov '04

10 Nov '04

Hello there, I have the following error when compiling pike 7.2.570 on freebsd sparc64 : Compiling peep_t.c /usr/ports/lang/pike72/work/pike-7.2.570/src/smartlink cc -I. -I/usr/ports/lang/pike72/work/pike-7.2.570/src -I/usr/local/include -I/usr/ports/lang/pike72/work/pike-7.2.570/src -O -pthread -R/usr/local/lib -L/usr/local/lib -rdynamic language.o security.o bignum.o interpret.o constants.o cpp.o fdlib.o cyclic.o array.o backend.o callback.o encode.o docode.o dynamic_buffer.o dynamic_load.o error.o fd_control.o fsort.o gc.o hashtable.o lex.o multiset.o signal_handler.o pike_search.o pike_types.o main.o mapping.o pike_memory.o module.o module_support.o object.o opcodes.o operators.o port.o program.o rusage.o stralloc.o stuff.o threads.o version.o queue.o builtin.o svalue.o las_t.o builtin_functions_t.o peep_t.o `cat modules/linker_options` -lm -lcrypt -o tpike svalue.o(.text+0x23bc): In function `is_lt': : undefined reference to `_Qp_cmp' svalue.o(.text+0x2428): In function `is_lt': : undefined reference to `_Qp_cmp' svalue.o(.text+0x28a0): In function `is_lt': : undefined reference to `_Qp_cmp' gmake[3]: *** [tpike-real] Error 1 gmake[3]: Leaving directory `/usr/ports/lang/pike72/work/pike-7.2.570/src' gmake[2]: *** [/usr/ports/lang/pike72/work/pike-7.2.570/src/tpike] Error 2 gmake[2]: Leaving directory `/usr/ports/lang/pike72/work/pike-7.2.570/src' gmake[1]: *** [pike] Error 2 gmake[1]: Leaving directory `/usr/ports/lang/pike72/work/pike-7.2.570/src' Can you tell me where is this comming from ? FYI : bash-2.05b# uname -a FreeBSD ws02.local.oav.net 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Mon Nov 8 09:50:23 CET 2004 root@ws02.local.oav.net:/usr/src/sys/sparc64/compile/WPHP01 sparc64 bash-2.05b# gcc -v Using built-in specs. Configured with: FreeBSD/sparc64 system compiler Thread model: posix gcc version 3.4.2 [FreeBSD] 20040728 /Xavier -- Xavier Beaudouin - Unix System Administrator & Projects Leader. President of Kazar Organization : http://www.kazar.net/ Please visit http://caudium.net/, home of Caudium & Camas projects

3 7

MinGW
by Martin Nilsson (DivX Networks) ＠ Pike (-) developers forum 09 Nov '04

09 Nov '04

I'm working a bit with getting Pike to compile with MinGW. In pike_threadlib, when using NT_THREADS there is no th_kill. How solve that?

6 6

pow
by Mirar ＠ Pike developers forum 09 Nov '04

09 Nov '04

Is this the expected result? | > 17->pow(0.5); | (41) Result: 1 If it is, can someone explain why? Also note that | > 17->_sqrt(); | (38) Result: 4 works nicely. (I wanted a generic integer root, square, cube or nth.)

2 4

Pike 7.6.24 & FreeBSD 5.3 / Sparc64
by Xavier Beaudouin 08 Nov '04

08 Nov '04

Hello, As for 7.2 compilation on Pike under FreeBSD Sparc 64 give such returns=20= : WARNING: Compiler failure! Trying without optimization! {standard input}: Assembler messages: {standard input}:9741: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:9763: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:9765: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:9779: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:9781: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:9803: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:9805: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:9819: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:9821: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10063: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10065: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10087: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10089: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10103: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10105: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10127: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10129: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10143: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10145: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10410: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10432: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10434: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10448: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10450: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10472: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10474: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10488: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10490: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10729: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10751: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10753: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10767: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10769: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10791: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10793: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10807: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] {standard input}:10809: Error: Illegal operands: There are only 32=20 single precision f registers; [0-31] Compilation command was: /usr/ports/lang/pike76/work/Pike-v7.6.24/src/smartlink cc -I.=20 -I/usr/ports/lang/pike76/work/Pike-v7.6.24/src/modules/Image=20 -I/usr/ports/lang/pike76/work/Pike-v7.6.24/src=20 -I/usr/ports/lang/pike76/work/Pike-v7.6.24/src =20 -I/usr/ports/lang/pike76/work/Pike-v7.6.24/src/bundles/include=20 -I/usr/local/include -DHAVE_CONFIG_H -O -pipe -ffast-math=20 -fomit-frame-pointer =20 -I/usr/ports/lang/pike76/work/Pike-v7.6.24/src/bundles/include=20 -I/usr/local/include -c search.c -o search.o gmake[2]: *** [search.o] Error 1 gmake[2]: Leaving directory=20 `/usr/ports/lang/pike76/work/Pike-v7.6.24/src/modules/Image' gmake[1]: *** [Image] Error 1 gmake[1]: Leaving directory=20 `/usr/ports/lang/pike76/work/Pike-v7.6.24/src/modules' gmake: *** [module_objects] Error 1 *** Error code 2 Stop in /usr/ports/lang/pike76. bash-2.05b# uname -a FreeBSD ws02.local.oav.net 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Mon Nov =20= 8 09:50:23 CET 2004 =20 root@ws02.local.oav.net:/usr/src/sys/sparc64/compile/WPHP01 sparc64 bash-2.05b# gcc -v Using built-in specs. Configured with: FreeBSD/sparc64 system compiler Thread model: posix gcc version 3.4.2 [FreeBSD] 20040728 bash-2.05b# -- Xavier Beaudouin - Unix System Administrator & Projects Leader. President of Kazar Organization : http://www.kazar.net/ Please visit http://caudium.net/, home of Caudium & Camas projects

2 1

C function
by Martin Nilsson (DivX Networks) ＠ Pike (-) developers forum 07 Nov '04

07 Nov '04

Is there anything like push_efun(f_map); ?

1 0

bugtracker for Pike
by Alexander Demenshin 05 Nov '04

05 Nov '04

Hi, Just in case - I did setup Mantis to aid bug reporting, tracking etc. It's located at: http://pike.strongfire.net/bts/ Anonymous access (report/view only) is enabled, account registration too. If anybody thinks this might be useful (I believe it is, since currently we have no real bug-tracking system), please, sign-in, then we can annouce this on the site and in pike-users ML so it can be used. Obviously, all current cvs-commiters will get "manager" status on project Pike (just inform me when you register there), or any other projects they want to manage and/or track there - I am open to suggestions. I am sorry that Mantis is not written in Pike, but it is simple to use and powerful enough, it can be used now and it will simplify (hopefully) life of those who hunt bugs :) If nobody is interested - well, I'll use it for my own projects only :) Regards, /Al

3 6

Re: string_to_utf8() behavior on non-wide strings
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 04 Nov '04

04 Nov '04

Also, things like the SQLite module could check the actual datatype to figure out what to do. In my version of the Oracle module (I don't know if it works the same in the new one), I used (<"foo">) and "foo" to differentiate BLOBs (which are octet sequences) from strings (which are character sequences), since Oracle had very firm opinions on what a character is.

2 2

Re: string_to_utf8() behavior on non-wide strings
by Per Hedbor () ＠ Pike (-) developers forum 04 Nov '04

04 Nov '04

And regexps are usually far slower than search. Not that I doubt the conversion step takes time.

1 0

call by reference
by Peter Lundqvist (disjunkt) ＠ Pike (-) developers forum 03 Nov '04

03 Nov '04

I was under the impression that call by reference was default in pike, but it seems I've lived a lie. Is there a way to write void foo(string s) { s=s+"!"; } void main() { string a = "Hello World"; foo(a); write(a+"\n"); } without returning a string from foo?

5 5

call by reference
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 03 Nov '04

03 Nov '04

As response to your question, you'll have to do something like this: void foo(array(string) s) { s[0]=s[0]+"!"; } void main() { array(string) a = ({"Hello World"}); foo(a); write(a[0]+"\n"); } I've thought about adding pointers to the language - see lyskom message 10034173 and comment tree. Still think it's a cool idea, but I don't know when I'll get around actually doing something about it. / Martin Stjernholm, Roxen IS Previous text: >12527661 2004-11-03 20:00 /1 lines/ Peter Lundqvist (disjunkt) >Recipients: Pike (-) help >Comment to 12527655 >Subject: call by reference >-------------------------------------------------------------------- >I got that ;) > >(12527661) /Peter Lundqvist (disjunkt) /---------------------------- >

1 0

Jump to page:

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