This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-1559782072-1198636212=:28008
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE



-Jaime Fournier
ober@LinBSD.org
ober@NetBSD.org


On Tue, 25 Dec 2007, [UTF-8] C=C3=A9sar Catri=C3=A1n Carre=C3=B1o wrote:

> Date: Tue, 25 Dec 2007 22:22:53 -0300
> From: "[UTF-8] C=C3=A9sar Catri=C3=A1n Carre=C3=B1o" <ccatrian@eml.cc>
> To: current-users@NetBSD.org
> Cc: Bernd Ernesti <netbsd@lists.veego.de>
> Subject: Re: Problem compiling perl in current
>=20
> On Tue, 25 Dec 2007 22:42:05 +0100
> Bernd Ernesti <netbsd@lists.veego.de> wrote:
>
>> On Tue, Dec 25, 2007 at 06:29:28PM -0300, C=C3=A9sar Catri=C3=A1n Carre=
=C3=B1o wrote:
>>>> [1]   Bad system call         ./try
>>>> The program compiled OK, but exited with status 140.
>>>> (The supplied flags or libraries might be incorrect.)
>>>>
>>>> You have a problem.  Shall I abort Configure [y]
>>>> Ok.  Stopping Configure.
>>>> ---
>>>>
>>>> By using NetBSD 4.99.34 to compile (without pkg_comp), works just fine=
=2E
>>>
>>> Tested against 4.99.44, perl fails to build against threads.
>>
>> I had no problem to do a normal pkgsrc build for perl with 4.99.44 on i3=
86
>> and you test program works too (this time with 4.99.45):
>>
>> : cc -o try -O2 -pthread -I/usr/include -fno-strict-aliasing -pipe -Wdec=
laration-after-statement -I/usr/pkg/include -L/usr/pkg/lib try.c -lcrypt -l=
pthread
>> : ./try
>> Ok
>> :
>>
>> Are you sure that your system is ok, like ram, or did you use some custo=
m
>> compile flags?
>>
>> Bernd
>>
>
> I collected some dump of this stuff:
>
> 23818      1 try      CALL  rasctl(0xbbbb99c4,5,0)
> 23818      1 try      RET   rasctl 0
> 23818      1 try      CALL  _lwp_unpark_all(0,0,0)
> 23818      1 try      RET   _lwp_unpark_all 1024/0x400
> 23818      1 try      CALL  __sysctl
> (0xbfbfebc0,2,0xbfbfec18,0xbfbfec1c,0,0) 23818      1 try      RET
> __sysctl 0 23818      1 try      CALL  getrlimit(3,0xbfbfec48)
> 23818      1 try      RET   getrlimit 0
> 23818      1 try      CALL  __sysctl
> (0xbfbfeba0,2,0xbfbfebf8,0xbfbfebfc,0,0) 23818      1 try      RET
> __sysctl 0 23818      1 try      CALL  mprotect(0xbfa01000,0x1000,0)
> 23818      1 try      RET   mprotect 0
> 23818      1 try      CALL  _lwp_self
> 23818      1 try      RET   _lwp_self 1
> 23818      1 try      CALL  _lwp_ctl
> 23818      1 try      RET   _lwp_ctl -1 errno 78 Function not
> implemented 23818      1 try      PSIG  SIGSYS SIG_DFL
>
> So this may be caused because I'm still using a 4.99.34 kernel. So I'll
> compile a new one to run the chroot and try again soon.
>
> Thanks
> --
> C=C3=A9sar Catri=C3=A1n Carre=C3=B1o
>

I found the same problem on zaurus when my userland was older than my=20
kernel.
Once I upgraded my userland I did not see this issue.

--0-1559782072-1198636212=:28008--