RE: cygwin-1.3.11-3: still cannot compile perl-5.8

RE: cygwin-1.3.11-3: still cannot compile perl-5.8

[Green, Paul]

PerlLIO_link runs through a bunch of macros and ends up calling the POSIX
link function (hard links).  Note that Configure only detects whether or not
you have a link() function available to be called; it never actually calls
it to see if it is operational. On operating systems where link() returns
ENOSYS every time it is called, you must add a line to the hints file that
sets d_link=undef.  (See hints/vos.sh, because the VOS system is one that
provides a dummy link() function that always returns ENOSYS).  Configure
will print a silly WHOA message about the discrepancy between the hint (no
link) and the libraries (link is there), but you can just ignore it.

PG

> -----Original Message-----
> From: Gerrit P. Haase [mailto:gp@familiehaase.de]
> Sent: Tuesday, June 25, 2002 3:45 PM
> To: Christopher Faylor
> Cc: perl5-porters@perl.org
> Subject: Re: cygwin-1.3.11-3: still cannot compile perl-5.8
> 
> 
> Hallo Christopher,
> 
> Am Dienstag, 25. Juni 2002 um 20:51 schriebst du:
> 
> >>>>Still having problems compiling the Perl RC2.
> >>>>It works well to build RC2 with the cygwin-1.3.11-1 testrelease.
> >>>>Now that 1.3.11-3 is not a test release I need someone to verify
> >>>>at another box that this is not a basically problem with my setup.
> >>>>Everything works well up to then point miniperl is used to:
> >>>>
> >>>>make[1]: Entering directory 
> `/sourcecode/perl/perl58/buildperl/x2p'
> >>>>../miniperl -I../lib s2p.PL
> >>>>Signal 11
> >>>>make[1]: *** [s2p] Error 139
> >>>>make[1]: Leaving directory `/sourcecode/perl/perl58/buildperl/x2p'
> >>>>make: *** [x2p/s2p] Error 2
> >>>>
> >>>>$ cat miniperl.exe.stackdump
> >>>>Exception: STATUS_ACCESS_VIOLATION at eip=77F34AC4
> >>>>eax=00000000 ebx=00233378 ecx=FFFFFFFF edx=FFFFFFFF 
> esi=0000000C edi=0000000C
> >>>>ebp=0022F3C0 esp=0022F394 
> program=d:\sourcecode\perl\perl58\buildperl\miniperl.exe
> >>>>cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
> >>>>Stack trace:
> >>>>Frame     Function  Args
> >>>>0022F3C0  77F34AC4  (00000000, 00000000, 0000000C, FFFFFFFF)
> >>>>0022FCE0  6107120A  (0A0B0AB4, 0A0BA5C8, 0022FD20, 00477B6A)
> >>>>0022FD20  0049262F  (0A010450, 61681570, 0022FD70, 00435D46)
> >>>>0022FD50  0048990D  (0A010450, 0A018010, 0A019818, 00000001)
> >>>>0022FD80  00415671  (0A010450, 00000001, 0022FE98, 004531B3)
> >>>>0022FEB0  00415343  (0A010450, 00000001, 0022FEE0, 00401069)
> >>>>0022FEE0  004010D7  (00000003, 61681570, 0A010278, 77F75B75)
> >>>>0022FF30  61005A9E  (00000008, FFFFFFFE, 000000E0, 610C08A0)
> >>>>0022FF90  61005D28  (00000000, 00000000, 00000246, 8011748B)
> >>>>0022FFB0  004BE312  (00401040, 037F0009, 0022FFF0, 77F1B9EA)
> >>>>0022FFC0  0040103C  (0022E640, 6104BD1C, 7FFDF000, 7FFDF000)
> >>>>0022FFF0  77F1B9EA  (00401000, 00000000, 000000B0, 00000100)
> >>>>End of stack trace
> >>
> >>> Seems like running miniperl in gdb would be instructive.  
> You'd need to
> >>> have debugging symbols in miniperl, of course.
> >>
> >>> I used to debug stuff like this all of the time when I 
> was maintaining
> >>> perl for cygwin.
> >>
> >>(gdb) run -Ilib utils/c2ph.PL
> >>Starting program: 
> /sourcecode/perl/perl58/buildperl/miniperl.exe -Ilib utils/c2ph.PL
> >>
> >>Program received signal SIGSEGV, Segmentation fault.
> >>0x77f34ac4 in _libkernel32_a_iname ()
> >>
> >>(gdb) bt
> >>#0  0x77f34ac4 in _libkernel32_a_iname ()
> >>#1  0xffffffff in ?? ()
> >>#2  0x6107120a in _libkernel32_a_iname ()
> >>#3  0x0049cfcf in Perl_pp_link (my_perl=0xa013cf0) at pp_sys.c:3556
> >                    ^^^^^^^^^^^                         ^^^^^^^^^^^^^
> 
> > What function is this calling?
> 
> PP(pp_link)
> {
> #ifdef HAS_LINK
>     dSP; dTARGET;
>     STRLEN n_a;
>     char *tmps2 = POPpx;
>     char *tmps = SvPV(TOPs, n_a);
>     TAINT_PROPER("link");
>     SETi( PerlLIO_link(tmps, tmps2) >= 0 ); <----3556
>     RETURN;
> #else
>     DIE(aTHX_ PL_no_func, "link");
> #endif
> }
> 
> iperlsys.h:
> #define PerlLIO_link(oldname, newname)                        
>           \
>         (*PL_LIO->pLink)(PL_LIO, (oldname), (newname))
> 
> pp.h:
> #define SETi(i)         STMT_START { sv_setiv(TARG, (IV)(i)); 
> SETTARG; } STMT_END
> 
> 
> -- 
> "All faults& bugs are mine - Robert"
>     from squid/acinclude.m4,   Sun Apr 21 05:21:21 2002
> 

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin-1.3.11-3: still cannot compile perl-5.8

[Gerrit P. Haase]

Hallo Paul,

Am Dienstag, 25. Juni 2002 um 23:18 schriebst du:

> PerlLIO_link runs through a bunch of macros and ends up calling the POSIX
> link function (hard links).  Note that Configure only detects whether or not
> you have a link() function available to be called; it never actually calls
> it to see if it is operational. On operating systems where link() returns
> ENOSYS every time it is called, you must add a line to the hints file that
> sets d_link=undef.  (See hints/vos.sh, because the VOS system is one that
> provides a dummy link() function that always returns ENOSYS).  Configure
> will print a silly WHOA message about the discrepancy between the hint (no
> link) and the libraries (link is there), but you can just ignore it.

Many thanks for the clarification, actually Cygwin has link() but it
seems to be broken in the current release.


Gerrit
-- 
=^..^=


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin-1.3.11-3: still cannot compile perl-5.8

[Christopher Faylor]

On Tue, Jun 25, 2002 at 11:35:10PM +0200, Gerrit P. Haase wrote:
>Am Dienstag, 25. Juni 2002 um 23:18 schriebst du:
>>PerlLIO_link runs through a bunch of macros and ends up calling the
>>POSIX link function (hard links).  Note that Configure only detects
>>whether or not you have a link() function available to be called; it
>>never actually calls it to see if it is operational.  On operating
>>systems where link() returns ENOSYS every time it is called, you must
>>add a line to the hints file that sets d_link=undef.  (See
>>hints/vos.sh, because the VOS system is one that provides a dummy
>>link() function that always returns ENOSYS).  Configure will print a
>>silly WHOA message about the discrepancy between the hint (no link) and
>>the libraries (link is there), but you can just ignore it.
>
>Many thanks for the clarification, actually Cygwin has link() but it
>seems to be broken in the current release.

No, it's not that simple.  If it was, the problem would be fixed now.
'ln' works fine.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin-1.3.11-3: still cannot compile perl-5.8

[Christopher Faylor]

On Tue, Jun 25, 2002 at 11:29:47PM +0200, Gerrit P. Haase wrote:
>Am Dienstag, 25. Juni 2002 um 22:47 schriebst du:
>>Actually, Gerrit, now that I think of it, you won't be able to do much
>>with a debugging cygwin DLL without the cygwin sources.
>
>>Could you send me the miniperl.exe via private mail instead?  bzip2'ed,
>>please.  I'll try to debug things from that direction.
>
>Yes, miniperl with symbols is on the way.

Thanks.  Actually link() *was* broken on systems that didn't support
CreateHardLink.  That's why I didn't notice it.

I'm rebuilding a snapshot now.  It should be fixed there.

Thanks for providing me with the information that I needed to track
this down.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin-1.3.11-3: still cannot compile perl-5.8

[Gerrit P. Haase]

Hallo Christopher,

Am Dienstag, 25. Juni 2002 um 22:47 schriebst du:

> Actually, Gerrit, now that I think of it, you won't be able to do much
> with a debugging cygwin DLL without the cygwin sources.

> Could you send me the miniperl.exe via private mail instead?  bzip2'ed,
> please.  I'll try to debug things from that direction.

Yes, miniperl with symbols is on the way.

Modules are in my binary package, at
http://koeln.convey.de/cywgin/perl/perl-5.8.0-RC2-1.tar.bz2
or:
http://today.clemson.edu/cygwin/perl/perl-5.8.0-RC2-1.tar.bz2

Sources:
http://koeln.convey.de/cywgin/perl/perl-5.8.0-RC2-1-src.tar.bz2
or:
http://today.clemson.edu/cygwin/perl/perl-5.8.0-RC2-1-src.tar.bz2


Gerrit
-- 
"All faults& bugs are mine - Robert"
    from squid/acinclude.m4,   Sun Apr 21 05:21:21 2002


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin-1.3.11-3: still cannot compile perl-5.8

[Christopher Faylor]

Actually, Gerrit, now that I think of it, you won't be able to do much
with a debugging cygwin DLL without the cygwin sources.

Could you send me the miniperl.exe via private mail instead?  bzip2'ed,
please.  I'll try to debug things from that direction.

cgf

On Tue, Jun 25, 2002 at 04:39:44PM -0400, Christopher Faylor wrote:
>On Tue, Jun 25, 2002 at 10:11:30PM +0200, Gerrit P. Haase wrote:
>>Hallo Christopher,
>>
>>> Do you have a debugging DLL handy or can I send you one?  If you set a
>>> breakpoint in _link in the cygwin DLL and single step along until it
>>> dies, it should be instructive.
>>
>>> Also does the latest snapshot behave any differently?
>>
>>I'll recompile miniperl now.
>>And yes, please send a dbugging cygwin dll;)
>
>On its way.
>
>Thanks.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin-1.3.11-3: still cannot compile perl-5.8

[Christopher Faylor]

On Tue, Jun 25, 2002 at 10:11:30PM +0200, Gerrit P. Haase wrote:
>Hallo Christopher,
>
>> Do you have a debugging DLL handy or can I send you one?  If you set a
>> breakpoint in _link in the cygwin DLL and single step along until it
>> dies, it should be instructive.
>
>> Also does the latest snapshot behave any differently?
>
>I'll recompile miniperl now.
>And yes, please send a dbugging cygwin dll;)

On its way.

Thanks.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin-1.3.11-3: still cannot compile perl-5.8

[Gerrit P. Haase]

Hallo Christopher,

> Do you have a debugging DLL handy or can I send you one?  If you set a
> breakpoint in _link in the cygwin DLL and single step along until it
> dies, it should be instructive.

> Also does the latest snapshot behave any differently?

I'll recompile miniperl now.
And yes, please send a dbugging cygwin dll;)


Gerrit
-- 
=^..^=


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin-1.3.11-3: still cannot compile perl-5.8

[Gerrit P. Haase]

Hallo Christopher,

Am Dienstag, 25. Juni 2002 um 21:51 schriebst du:

> On Tue, Jun 25, 2002 at 09:44:33PM +0200, Gerrit P. Haase wrote:
>>>>(gdb) bt
>>>>#0  0x77f34ac4 in _libkernel32_a_iname ()
>>>>#1  0xffffffff in ?? ()
>>>>#2  0x6107120a in _libkernel32_a_iname ()
>>>>#3  0x0049cfcf in Perl_pp_link (my_perl=0xa013cf0) at pp_sys.c:3556
>>>                    ^^^^^^^^^^^                         ^^^^^^^^^^^^^
>>
>>> What function is this calling?
>>
>>PP(pp_link)
>>{
>>#ifdef HAS_LINK
>>    dSP; dTARGET;
>>    STRLEN n_a;
>>    char *tmps2 = POPpx;
>>    char *tmps = SvPV(TOPs, n_a);
>>    TAINT_PROPER("link");
>>    SETi( PerlLIO_link(tmps, tmps2) >= 0 ); <----3556
>>    RETURN;
>>#else
>>    DIE(aTHX_ PL_no_func, "link");
>>#endif
>>}
>>
>>iperlsys.h:
>>#define PerlLIO_link(oldname, newname)                                  \
>>        (*PL_LIO->pLink)(PL_LIO, (oldname), (newname))
>>
>>pp.h:
>>#define SETi(i)         STMT_START { sv_setiv(TARG, (IV)(i)); SETTARG; } STMT_END

> So, that confirms that it is dying in the link() call even though the
> location from your stack dump doesn't make sense (not your fault).

> Do you have a debugging DLL handy or can I send you one?  If you set a
> breakpoint in _link in the cygwin DLL and single step along until it
> dies, it should be instructive.

No I have no debugging cygwin dll here right now.

> Also does the latest snapshot behave any differently?

I havn't recompiled wwith the snapshot, but just using the snapshot
with the prvious compiled perl gives also a crash.

-- 
=^..^=


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin-1.3.11-3: still cannot compile perl-5.8

[Christopher Faylor]

On Tue, Jun 25, 2002 at 09:44:33PM +0200, Gerrit P. Haase wrote:
>>>(gdb) bt
>>>#0  0x77f34ac4 in _libkernel32_a_iname ()
>>>#1  0xffffffff in ?? ()
>>>#2  0x6107120a in _libkernel32_a_iname ()
>>>#3  0x0049cfcf in Perl_pp_link (my_perl=0xa013cf0) at pp_sys.c:3556
>>                    ^^^^^^^^^^^                         ^^^^^^^^^^^^^
>
>> What function is this calling?
>
>PP(pp_link)
>{
>#ifdef HAS_LINK
>    dSP; dTARGET;
>    STRLEN n_a;
>    char *tmps2 = POPpx;
>    char *tmps = SvPV(TOPs, n_a);
>    TAINT_PROPER("link");
>    SETi( PerlLIO_link(tmps, tmps2) >= 0 ); <----3556
>    RETURN;
>#else
>    DIE(aTHX_ PL_no_func, "link");
>#endif
>}
>
>iperlsys.h:
>#define PerlLIO_link(oldname, newname)                                  \
>        (*PL_LIO->pLink)(PL_LIO, (oldname), (newname))
>
>pp.h:
>#define SETi(i)         STMT_START { sv_setiv(TARG, (IV)(i)); SETTARG; } STMT_END

So, that confirms that it is dying in the link() call even though the
location from your stack dump doesn't make sense (not your fault).

Do you have a debugging DLL handy or can I send you one?  If you set a
breakpoint in _link in the cygwin DLL and single step along until it
dies, it should be instructive.

Also does the latest snapshot behave any differently?

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin-1.3.11-3: still cannot compile perl-5.8

[Gerrit P. Haase]

Hallo Christopher,

Am Dienstag, 25. Juni 2002 um 20:51 schriebst du:

>>>>Still having problems compiling the Perl RC2.
>>>>It works well to build RC2 with the cygwin-1.3.11-1 testrelease.
>>>>Now that 1.3.11-3 is not a test release I need someone to verify
>>>>at another box that this is not a basically problem with my setup.
>>>>Everything works well up to then point miniperl is used to:
>>>>
>>>>make[1]: Entering directory `/sourcecode/perl/perl58/buildperl/x2p'
>>>>../miniperl -I../lib s2p.PL
>>>>Signal 11
>>>>make[1]: *** [s2p] Error 139
>>>>make[1]: Leaving directory `/sourcecode/perl/perl58/buildperl/x2p'
>>>>make: *** [x2p/s2p] Error 2
>>>>
>>>>$ cat miniperl.exe.stackdump
>>>>Exception: STATUS_ACCESS_VIOLATION at eip=77F34AC4
>>>>eax=00000000 ebx=00233378 ecx=FFFFFFFF edx=FFFFFFFF esi=0000000C edi=0000000C
>>>>ebp=0022F3C0 esp=0022F394 program=d:\sourcecode\perl\perl58\buildperl\miniperl.exe
>>>>cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
>>>>Stack trace:
>>>>Frame     Function  Args
>>>>0022F3C0  77F34AC4  (00000000, 00000000, 0000000C, FFFFFFFF)
>>>>0022FCE0  6107120A  (0A0B0AB4, 0A0BA5C8, 0022FD20, 00477B6A)
>>>>0022FD20  0049262F  (0A010450, 61681570, 0022FD70, 00435D46)
>>>>0022FD50  0048990D  (0A010450, 0A018010, 0A019818, 00000001)
>>>>0022FD80  00415671  (0A010450, 00000001, 0022FE98, 004531B3)
>>>>0022FEB0  00415343  (0A010450, 00000001, 0022FEE0, 00401069)
>>>>0022FEE0  004010D7  (00000003, 61681570, 0A010278, 77F75B75)
>>>>0022FF30  61005A9E  (00000008, FFFFFFFE, 000000E0, 610C08A0)
>>>>0022FF90  61005D28  (00000000, 00000000, 00000246, 8011748B)
>>>>0022FFB0  004BE312  (00401040, 037F0009, 0022FFF0, 77F1B9EA)
>>>>0022FFC0  0040103C  (0022E640, 6104BD1C, 7FFDF000, 7FFDF000)
>>>>0022FFF0  77F1B9EA  (00401000, 00000000, 000000B0, 00000100)
>>>>End of stack trace
>>
>>> Seems like running miniperl in gdb would be instructive.  You'd need to
>>> have debugging symbols in miniperl, of course.
>>
>>> I used to debug stuff like this all of the time when I was maintaining
>>> perl for cygwin.
>>
>>(gdb) run -Ilib utils/c2ph.PL
>>Starting program: /sourcecode/perl/perl58/buildperl/miniperl.exe -Ilib utils/c2ph.PL
>>
>>Program received signal SIGSEGV, Segmentation fault.
>>0x77f34ac4 in _libkernel32_a_iname ()
>>
>>(gdb) bt
>>#0  0x77f34ac4 in _libkernel32_a_iname ()
>>#1  0xffffffff in ?? ()
>>#2  0x6107120a in _libkernel32_a_iname ()
>>#3  0x0049cfcf in Perl_pp_link (my_perl=0xa013cf0) at pp_sys.c:3556
>                    ^^^^^^^^^^^                         ^^^^^^^^^^^^^

> What function is this calling?

PP(pp_link)
{
#ifdef HAS_LINK
    dSP; dTARGET;
    STRLEN n_a;
    char *tmps2 = POPpx;
    char *tmps = SvPV(TOPs, n_a);
    TAINT_PROPER("link");
    SETi( PerlLIO_link(tmps, tmps2) >= 0 ); <----3556
    RETURN;
#else
    DIE(aTHX_ PL_no_func, "link");
#endif
}

iperlsys.h:
#define PerlLIO_link(oldname, newname)                                  \
        (*PL_LIO->pLink)(PL_LIO, (oldname), (newname))

pp.h:
#define SETi(i)         STMT_START { sv_setiv(TARG, (IV)(i)); SETTARG; } STMT_END


-- 
"All faults& bugs are mine - Robert"
    from squid/acinclude.m4,   Sun Apr 21 05:21:21 2002


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin-1.3.11-3: still cannot compile perl-5.8

[Christopher Faylor]

On Tue, Jun 25, 2002 at 07:20:52PM +0200, Gerrit P. Haase wrote:
>Hallo Christopher,
>
>Am Dienstag, 25. Juni 2002 um 06:36 schriebst du:
>
>> On Tue, Jun 25, 2002 at 06:24:43AM +0200, Gerrit P. Haase wrote:
>>>Hallo,
>>>
>>>Still having problems compiling the Perl RC2.
>>>It works well to build RC2 with the cygwin-1.3.11-1 testrelease.
>>>Now that 1.3.11-3 is not a test release I need someone to verify
>>>at another box that this is not a basically problem with my setup.
>>>Everything works well up to then point miniperl is used to:
>>>
>>>make[1]: Entering directory `/sourcecode/perl/perl58/buildperl/x2p'
>>>../miniperl -I../lib s2p.PL
>>>Signal 11
>>>make[1]: *** [s2p] Error 139
>>>make[1]: Leaving directory `/sourcecode/perl/perl58/buildperl/x2p'
>>>make: *** [x2p/s2p] Error 2
>>>
>>>$ cat miniperl.exe.stackdump
>>>Exception: STATUS_ACCESS_VIOLATION at eip=77F34AC4
>>>eax=00000000 ebx=00233378 ecx=FFFFFFFF edx=FFFFFFFF esi=0000000C edi=0000000C
>>>ebp=0022F3C0 esp=0022F394 program=d:\sourcecode\perl\perl58\buildperl\miniperl.exe
>>>cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
>>>Stack trace:
>>>Frame     Function  Args
>>>0022F3C0  77F34AC4  (00000000, 00000000, 0000000C, FFFFFFFF)
>>>0022FCE0  6107120A  (0A0B0AB4, 0A0BA5C8, 0022FD20, 00477B6A)
>>>0022FD20  0049262F  (0A010450, 61681570, 0022FD70, 00435D46)
>>>0022FD50  0048990D  (0A010450, 0A018010, 0A019818, 00000001)
>>>0022FD80  00415671  (0A010450, 00000001, 0022FE98, 004531B3)
>>>0022FEB0  00415343  (0A010450, 00000001, 0022FEE0, 00401069)
>>>0022FEE0  004010D7  (00000003, 61681570, 0A010278, 77F75B75)
>>>0022FF30  61005A9E  (00000008, FFFFFFFE, 000000E0, 610C08A0)
>>>0022FF90  61005D28  (00000000, 00000000, 00000246, 8011748B)
>>>0022FFB0  004BE312  (00401040, 037F0009, 0022FFF0, 77F1B9EA)
>>>0022FFC0  0040103C  (0022E640, 6104BD1C, 7FFDF000, 7FFDF000)
>>>0022FFF0  77F1B9EA  (00401000, 00000000, 000000B0, 00000100)
>>>End of stack trace
>
>> Seems like running miniperl in gdb would be instructive.  You'd need to
>> have debugging symbols in miniperl, of course.
>
>> I used to debug stuff like this all of the time when I was maintaining
>> perl for cygwin.
>
>(gdb) run -Ilib utils/c2ph.PL
>Starting program: /sourcecode/perl/perl58/buildperl/miniperl.exe -Ilib utils/c2ph.PL
>
>Program received signal SIGSEGV, Segmentation fault.
>0x77f34ac4 in _libkernel32_a_iname ()
>
>(gdb) bt
>#0  0x77f34ac4 in _libkernel32_a_iname ()
>#1  0xffffffff in ?? ()
>#2  0x6107120a in _libkernel32_a_iname ()
>#3  0x0049cfcf in Perl_pp_link (my_perl=0xa013cf0) at pp_sys.c:3556
                   ^^^^^^^^^^^                         ^^^^^^^^^^^^^

What function is this calling?

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin-1.3.11-3: still cannot compile perl-5.8

[Gerrit P. Haase]

Hallo Christopher,

Am Dienstag, 25. Juni 2002 um 06:36 schriebst du:

> On Tue, Jun 25, 2002 at 06:24:43AM +0200, Gerrit P. Haase wrote:
>>Hallo,
>>
>>Still having problems compiling the Perl RC2.
>>It works well to build RC2 with the cygwin-1.3.11-1 testrelease.
>>Now that 1.3.11-3 is not a test release I need someone to verify
>>at another box that this is not a basically problem with my setup.
>>Everything works well up to then point miniperl is used to:
>>
>>make[1]: Entering directory `/sourcecode/perl/perl58/buildperl/x2p'
>>../miniperl -I../lib s2p.PL
>>Signal 11
>>make[1]: *** [s2p] Error 139
>>make[1]: Leaving directory `/sourcecode/perl/perl58/buildperl/x2p'
>>make: *** [x2p/s2p] Error 2
>>
>>$ cat miniperl.exe.stackdump
>>Exception: STATUS_ACCESS_VIOLATION at eip=77F34AC4
>>eax=00000000 ebx=00233378 ecx=FFFFFFFF edx=FFFFFFFF esi=0000000C edi=0000000C
>>ebp=0022F3C0 esp=0022F394 program=d:\sourcecode\perl\perl58\buildperl\miniperl.exe
>>cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
>>Stack trace:
>>Frame     Function  Args
>>0022F3C0  77F34AC4  (00000000, 00000000, 0000000C, FFFFFFFF)
>>0022FCE0  6107120A  (0A0B0AB4, 0A0BA5C8, 0022FD20, 00477B6A)
>>0022FD20  0049262F  (0A010450, 61681570, 0022FD70, 00435D46)
>>0022FD50  0048990D  (0A010450, 0A018010, 0A019818, 00000001)
>>0022FD80  00415671  (0A010450, 00000001, 0022FE98, 004531B3)
>>0022FEB0  00415343  (0A010450, 00000001, 0022FEE0, 00401069)
>>0022FEE0  004010D7  (00000003, 61681570, 0A010278, 77F75B75)
>>0022FF30  61005A9E  (00000008, FFFFFFFE, 000000E0, 610C08A0)
>>0022FF90  61005D28  (00000000, 00000000, 00000246, 8011748B)
>>0022FFB0  004BE312  (00401040, 037F0009, 0022FFF0, 77F1B9EA)
>>0022FFC0  0040103C  (0022E640, 6104BD1C, 7FFDF000, 7FFDF000)
>>0022FFF0  77F1B9EA  (00401000, 00000000, 000000B0, 00000100)
>>End of stack trace

> Seems like running miniperl in gdb would be instructive.  You'd need to
> have debugging symbols in miniperl, of course.

> I used to debug stuff like this all of the time when I was maintaining
> perl for cygwin.

(gdb) run -Ilib utils/c2ph.PL
Starting program: /sourcecode/perl/perl58/buildperl/miniperl.exe -Ilib utils/c2ph.PL

Program received signal SIGSEGV, Segmentation fault.
0x77f34ac4 in _libkernel32_a_iname ()

(gdb) bt
#0  0x77f34ac4 in _libkernel32_a_iname ()
#1  0xffffffff in ?? ()
#2  0x6107120a in _libkernel32_a_iname ()
#3  0x0049cfcf in Perl_pp_link (my_perl=0xa013cf0) at pp_sys.c:3556
#4  0x004450fd in Perl_runops_debug (my_perl=0xa013cf0) at dump.c:1398
#5  0x0041635d in S_run_body (my_perl=0xa013cf0, oldscope=1) at perl.c:1681
#6  0x00415f5f in perl_run (my_perl=0xa013cf0) at perl.c:1600
#7  0x004010d7 in main (argc=3, argv=0xa013cc0, env=0xa011de8)
    at miniperlmain.c:85
#8  0x61005a9e in _libkernel32_a_iname ()
#9  0x61005d28 in _libkernel32_a_iname ()
#10 0x004d0342 in cygwin_crt0 ()
#11 0x0040103c in mainCRTStartup ()
#12 0x77f1b9ea in _libkernel32_a_iname ()
(gdb) 


Gerrit

-- 
"All faults& bugs are mine - Robert"
    from squid/acinclude.m4,   Sun Apr 21 05:21:21 2002


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin-1.3.11-3: still cannot compile perl-5.8

[Charles Wilson]

Christopher Faylor wrote:


> Actually, it didn't originally contain ndbm.h and I regenned it within
> minutes of the db.h discussion so that later versions no longer contain
> db.h either.
> 
> I know I probably should have made the package 1.3.11-4 but I couldn't
> bring myself to do this for one include file.
> 
> So there was just a small window where db.h was available.


Ah!  Good to know -- thanks for fixing the problem, Chris.

--Chuck



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin-1.3.11-3: still cannot compile perl-5.8

[Charles Wilson]

Christopher Faylor wrote:


> Actually, it didn't originally contain ndbm.h and I regenned it within
> minutes of the db.h discussion so that later versions no longer contain
> db.h either.
> 
> I know I probably should have made the package 1.3.11-4 but I couldn't
> bring myself to do this for one include file.
> 
> So there was just a small window where db.h was available.


Ah!  Good to know -- thanks for fixing the problem, Chris.

--Chuck




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin-1.3.11-3: still cannot compile perl-5.8

[Christopher Faylor]

On Tue, Jun 25, 2002 at 06:46:38AM +0200, Gerrit P. Haase wrote:
>> Hallo,
>
>> Still having problems compiling the Perl RC2.
>> It works well to build RC2 with the cygwin-1.3.11-1 testrelease.
>> Now that 1.3.11-3 is not a test release I need someone to verify
>> at another box that this is not a basically problem with my setup.
>
>BTW, cygwin-1.3.11-3 includes two header files:
>/usr/include/db.h & /usr/include/ndbm.h which are conflicting with
>already installed headers (gdbm & bdb), so make sure to install the
>gdbm and bdb packages again after installing cygwin, will cause no
>problems since the according functions are not exported from
>cygwin.dll.

Actually, it didn't originally contain ndbm.h and I regenned it within
minutes of the db.h discussion so that later versions no longer contain
db.h either.

I know I probably should have made the package 1.3.11-4 but I couldn't
bring myself to do this for one include file.

So there was just a small window where db.h was available.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin-1.3.11-3: still cannot compile perl-5.8

[Gerrit P. Haase]

> Hallo,

> Still having problems compiling the Perl RC2.
> It works well to build RC2 with the cygwin-1.3.11-1 testrelease.
> Now that 1.3.11-3 is not a test release I need someone to verify
> at another box that this is not a basically problem with my setup.

BTW, cygwin-1.3.11-3 includes two header files:
/usr/include/db.h & /usr/include/ndbm.h which are conflicting with
already installed headers (gdbm & bdb), so make sure to install the
gdbm and bdb packages again after installing cygwin, will cause no
problems since the according functions are not exported from
cygwin.dll.

> Everything works well up to then point miniperl is used to:

> make[1]: Entering directory `/sourcecode/perl/perl58/buildperl/x2p'
> ../miniperl -I../lib s2p.PL
> Signal 11
> make[1]: *** [s2p] Error 139
> make[1]: Leaving directory `/sourcecode/perl/perl58/buildperl/x2p'
> make: *** [x2p/s2p] Error 2

> $ cat miniperl.exe.stackdump
> Exception: STATUS_ACCESS_VIOLATION at eip=77F34AC4
> eax=00000000 ebx=00233378 ecx=FFFFFFFF edx=FFFFFFFF esi=0000000C edi=0000000C
> ebp=0022F3C0 esp=0022F394 program=d:\sourcecode\perl\perl58\buildperl\miniperl.exe
> cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
> Stack trace:
> Frame     Function  Args
> 0022F3C0  77F34AC4  (00000000, 00000000, 0000000C, FFFFFFFF)
> 0022FCE0  6107120A  (0A0B0AB4, 0A0BA5C8, 0022FD20, 00477B6A)
> 0022FD20  0049262F  (0A010450, 61681570, 0022FD70, 00435D46)
> 0022FD50  0048990D  (0A010450, 0A018010, 0A019818, 00000001)
> 0022FD80  00415671  (0A010450, 00000001, 0022FE98, 004531B3)
> 0022FEB0  00415343  (0A010450, 00000001, 0022FEE0, 00401069)
> 0022FEE0  004010D7  (00000003, 61681570, 0A010278, 77F75B75)
> 0022FF30  61005A9E  (00000008, FFFFFFFE, 000000E0, 610C08A0)
> 0022FF90  61005D28  (00000000, 00000000, 00000246, 8011748B)
> 0022FFB0  004BE312  (00401040, 037F0009, 0022FFF0, 77F1B9EA)
> 0022FFC0  0040103C  (0022E640, 6104BD1C, 7FFDF000, 7FFDF000)
> 0022FFF0  77F1B9EA  (00401000, 00000000, 000000B0, 00000100)
> End of stack trace

  
> Interesting is that compiling the source works fine, building the dll
> works fine, if I use the new perl instead of miniperl I get also the
> crash:
> $ ../perl -I../lib s2p.PL
> Extracting s2p (with variable substitutions)
> Linking s2p to psed.
> Segmentation fault (core dumped)

> $ cat perl.exe.stackdump
> Exception: STATUS_ACCESS_VIOLATION at eip=77F34AC4
> eax=00000000 ebx=002337C0 ecx=FFFFFFFF edx=FFFFFFFF esi=0000000C edi=0000000C
> ebp=0022F3C0 esp=0022F394 program=d:\sourcecode\perl\perl58\buildperl\perl.exe
> cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
> Stack trace:
> Frame     Function  Args
> 0022F3C0  77F34AC4  (00000000, 00000000, 0000000C, FFFFFFFF)
> 0022FCE0  6107120A  (101A0438, 101AA6B8, 0022FD20, 10083F1A)
> 0022FD20  1008D45F  (10100440, 61681C80, 0022FD70, 10049D56)
> 0022FD50  1005759D  (10100440, 10108010, 10109818, 00000001)
> 0022FD80  100040A1  (10100440, 00000001, 0022FE98, 10009143)
> 0022FEB0  10003D73  (10100440, 00000001, 0022FEE0, 0040106A)
> 0022FEE0  004010DB  (00000003, 61681C80, 10100278, 0022FF14)
> 0022FF30  61005A9E  (610C095C, FFFFFFFE, 000000E8, 610C08A0)
> 0022FF90  61005D28  (00000000, 00000000, 00000246, 8011748B)
> 0022FFB0  00401F72  (00401040, 037F0009, 0022FFF0, 77F1B9EA)
> 0022FFC0  0040103C  (0022E440, 0022E3D2, 7FFDF000, 7FFDF000)
> 0022FFF0  77F1B9EA  (00401000, 00000000, 000000B0, 00000100)
> End of stack trace


> $ ./perl -Ilib -V
> Summary of my perl5 (revision 5.0 version 8 subversion 0) configuration:
>   Platform:
>     osname=cygwin, osvers=1.3.11(0.5332), archname=cygwin-multi-64int
>     uname='cygwin_nt-4.0 loreley 1.3.11(0.5332) 2002-06-23 22:31 i686 unknown '
>     config_args='-de -Dmksymlinks -Dusemultiplicity -Duse64bitint -Doptimize=-O2'
>     hint=recommended, useposix=true, d_sigaction=define
>     usethreads=undef use5005threads=undef useithreads=undef usemultiplicity=define
>     useperlio=define d_sfio=undef uselargefiles=define usesocks=undef
>     use64bitint=define use64bitall=undef uselongdouble=undef
>     usemymalloc=y, bincompat5005=undef
>   Compiler:
>     cc='gcc', ccflags ='-DPERL_USE_SAFE_PUTENV -fno-strict-aliasing -I/usr/local/include',
>     optimize='-O2',
>     cppflags='-DPERL_USE_SAFE_PUTENV -fno-strict-aliasing -I/usr/local/include'
>     ccversion='', gccversion='2.95.3-5 (cygwin special)', gccosandvers=''
>     intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=12345678
>     d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12
>     ivtype='long long', ivsize=8, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=4
>     alignbytes=8, prototype=define
>   Linker and Libraries:
>     ld='ld2', ldflags =' -L/usr/local/lib'
>     libpth=/usr/local/lib /usr/lib /lib
>     libs=-lgdbm -ldb -lcrypt -lutil
>     perllibs=-lcrypt -lutil
>     libc=/usr/lib/libc.a, so=dll, useshrplib=true, libperl=libperl.a
>     gnulibc_version=''
>   Dynamic Linking:
>     dlsrc=dl_dlopen.xs, dlext=dll, d_dlsymun=undef, ccdlflags=' '
>     cccdlflags=' ', lddlflags=' -L/usr/local/lib'


> Characteristics of this binary (from libperl): 
>   Compile-time options: MULTIPLICITY USE_64_BIT_INT USE_LARGE_FILES PERL_IMPLICIT_CONTEXT
>   Built under cygwin
>   Compiled at Jun 25 2002 00:32:35
>   %ENV:
>     CYGWIN="ntsec binmode tty nowinsymlinks"
>   @INC:
>     lib
>     /usr/lib/perl5/5.8.0/cygwin-multi-64int
>     /usr/lib/perl5/5.8.0
>     /usr/lib/perl5/site_perl/5.8.0/cygwin-multi-64int
>     /usr/lib/perl5/site_perl/5.8.0
>     /usr/lib/perl5/site_perl
>     .


> Gerrit



-- 
=^..^=


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin-1.3.11-3: still cannot compile perl-5.8

[Christopher Faylor]

On Tue, Jun 25, 2002 at 06:24:43AM +0200, Gerrit P. Haase wrote:
>Hallo,
>
>Still having problems compiling the Perl RC2.
>It works well to build RC2 with the cygwin-1.3.11-1 testrelease.
>Now that 1.3.11-3 is not a test release I need someone to verify
>at another box that this is not a basically problem with my setup.
>Everything works well up to then point miniperl is used to:
>
>make[1]: Entering directory `/sourcecode/perl/perl58/buildperl/x2p'
>../miniperl -I../lib s2p.PL
>Signal 11
>make[1]: *** [s2p] Error 139
>make[1]: Leaving directory `/sourcecode/perl/perl58/buildperl/x2p'
>make: *** [x2p/s2p] Error 2
>
>$ cat miniperl.exe.stackdump
>Exception: STATUS_ACCESS_VIOLATION at eip=77F34AC4
>eax=00000000 ebx=00233378 ecx=FFFFFFFF edx=FFFFFFFF esi=0000000C edi=0000000C
>ebp=0022F3C0 esp=0022F394 program=d:\sourcecode\perl\perl58\buildperl\miniperl.exe
>cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
>Stack trace:
>Frame     Function  Args
>0022F3C0  77F34AC4  (00000000, 00000000, 0000000C, FFFFFFFF)
>0022FCE0  6107120A  (0A0B0AB4, 0A0BA5C8, 0022FD20, 00477B6A)
>0022FD20  0049262F  (0A010450, 61681570, 0022FD70, 00435D46)
>0022FD50  0048990D  (0A010450, 0A018010, 0A019818, 00000001)
>0022FD80  00415671  (0A010450, 00000001, 0022FE98, 004531B3)
>0022FEB0  00415343  (0A010450, 00000001, 0022FEE0, 00401069)
>0022FEE0  004010D7  (00000003, 61681570, 0A010278, 77F75B75)
>0022FF30  61005A9E  (00000008, FFFFFFFE, 000000E0, 610C08A0)
>0022FF90  61005D28  (00000000, 00000000, 00000246, 8011748B)
>0022FFB0  004BE312  (00401040, 037F0009, 0022FFF0, 77F1B9EA)
>0022FFC0  0040103C  (0022E640, 6104BD1C, 7FFDF000, 7FFDF000)
>0022FFF0  77F1B9EA  (00401000, 00000000, 000000B0, 00000100)
>End of stack trace

Seems like running miniperl in gdb would be instructive.  You'd need to
have debugging symbols in miniperl, of course.

I used to debug stuff like this all of the time when I was maintaining
perl for cygwin.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

cygwin-1.3.11-3: still cannot compile perl-5.8

[Gerrit P. Haase]

Hallo,

Still having problems compiling the Perl RC2.
It works well to build RC2 with the cygwin-1.3.11-1 testrelease.
Now that 1.3.11-3 is not a test release I need someone to verify
at another box that this is not a basically problem with my setup.
Everything works well up to then point miniperl is used to:

make[1]: Entering directory `/sourcecode/perl/perl58/buildperl/x2p'
../miniperl -I../lib s2p.PL
Signal 11
make[1]: *** [s2p] Error 139
make[1]: Leaving directory `/sourcecode/perl/perl58/buildperl/x2p'
make: *** [x2p/s2p] Error 2

$ cat miniperl.exe.stackdump
Exception: STATUS_ACCESS_VIOLATION at eip=77F34AC4
eax=00000000 ebx=00233378 ecx=FFFFFFFF edx=FFFFFFFF esi=0000000C edi=0000000C
ebp=0022F3C0 esp=0022F394 program=d:\sourcecode\perl\perl58\buildperl\miniperl.exe
cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
Stack trace:
Frame     Function  Args
0022F3C0  77F34AC4  (00000000, 00000000, 0000000C, FFFFFFFF)
0022FCE0  6107120A  (0A0B0AB4, 0A0BA5C8, 0022FD20, 00477B6A)
0022FD20  0049262F  (0A010450, 61681570, 0022FD70, 00435D46)
0022FD50  0048990D  (0A010450, 0A018010, 0A019818, 00000001)
0022FD80  00415671  (0A010450, 00000001, 0022FE98, 004531B3)
0022FEB0  00415343  (0A010450, 00000001, 0022FEE0, 00401069)
0022FEE0  004010D7  (00000003, 61681570, 0A010278, 77F75B75)
0022FF30  61005A9E  (00000008, FFFFFFFE, 000000E0, 610C08A0)
0022FF90  61005D28  (00000000, 00000000, 00000246, 8011748B)
0022FFB0  004BE312  (00401040, 037F0009, 0022FFF0, 77F1B9EA)
0022FFC0  0040103C  (0022E640, 6104BD1C, 7FFDF000, 7FFDF000)
0022FFF0  77F1B9EA  (00401000, 00000000, 000000B0, 00000100)
End of stack trace

  
Interesting is that compiling the source works fine, building the dll
works fine, if I use the new perl instead of miniperl I get also the
crash:
$ ../perl -I../lib s2p.PL
Extracting s2p (with variable substitutions)
Linking s2p to psed.
Segmentation fault (core dumped)

$ cat perl.exe.stackdump
Exception: STATUS_ACCESS_VIOLATION at eip=77F34AC4
eax=00000000 ebx=002337C0 ecx=FFFFFFFF edx=FFFFFFFF esi=0000000C edi=0000000C
ebp=0022F3C0 esp=0022F394 program=d:\sourcecode\perl\perl58\buildperl\perl.exe
cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
Stack trace:
Frame     Function  Args
0022F3C0  77F34AC4  (00000000, 00000000, 0000000C, FFFFFFFF)
0022FCE0  6107120A  (101A0438, 101AA6B8, 0022FD20, 10083F1A)
0022FD20  1008D45F  (10100440, 61681C80, 0022FD70, 10049D56)
0022FD50  1005759D  (10100440, 10108010, 10109818, 00000001)
0022FD80  100040A1  (10100440, 00000001, 0022FE98, 10009143)
0022FEB0  10003D73  (10100440, 00000001, 0022FEE0, 0040106A)
0022FEE0  004010DB  (00000003, 61681C80, 10100278, 0022FF14)
0022FF30  61005A9E  (610C095C, FFFFFFFE, 000000E8, 610C08A0)
0022FF90  61005D28  (00000000, 00000000, 00000246, 8011748B)
0022FFB0  00401F72  (00401040, 037F0009, 0022FFF0, 77F1B9EA)
0022FFC0  0040103C  (0022E440, 0022E3D2, 7FFDF000, 7FFDF000)
0022FFF0  77F1B9EA  (00401000, 00000000, 000000B0, 00000100)
End of stack trace


$ ./perl -Ilib -V
Summary of my perl5 (revision 5.0 version 8 subversion 0) configuration:
  Platform:
    osname=cygwin, osvers=1.3.11(0.5332), archname=cygwin-multi-64int
    uname='cygwin_nt-4.0 loreley 1.3.11(0.5332) 2002-06-23 22:31 i686 unknown '
    config_args='-de -Dmksymlinks -Dusemultiplicity -Duse64bitint -Doptimize=-O2'
    hint=recommended, useposix=true, d_sigaction=define
    usethreads=undef use5005threads=undef useithreads=undef usemultiplicity=define
    useperlio=define d_sfio=undef uselargefiles=define usesocks=undef
    use64bitint=define use64bitall=undef uselongdouble=undef
    usemymalloc=y, bincompat5005=undef
  Compiler:
    cc='gcc', ccflags ='-DPERL_USE_SAFE_PUTENV -fno-strict-aliasing -I/usr/local/include',
    optimize='-O2',
    cppflags='-DPERL_USE_SAFE_PUTENV -fno-strict-aliasing -I/usr/local/include'
    ccversion='', gccversion='2.95.3-5 (cygwin special)', gccosandvers=''
    intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=12345678
    d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12
    ivtype='long long', ivsize=8, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=4
    alignbytes=8, prototype=define
  Linker and Libraries:
    ld='ld2', ldflags =' -L/usr/local/lib'
    libpth=/usr/local/lib /usr/lib /lib
    libs=-lgdbm -ldb -lcrypt -lutil
    perllibs=-lcrypt -lutil
    libc=/usr/lib/libc.a, so=dll, useshrplib=true, libperl=libperl.a
    gnulibc_version=''
  Dynamic Linking:
    dlsrc=dl_dlopen.xs, dlext=dll, d_dlsymun=undef, ccdlflags=' '
    cccdlflags=' ', lddlflags=' -L/usr/local/lib'


Characteristics of this binary (from libperl): 
  Compile-time options: MULTIPLICITY USE_64_BIT_INT USE_LARGE_FILES PERL_IMPLICIT_CONTEXT
  Built under cygwin
  Compiled at Jun 25 2002 00:32:35
  %ENV:
    CYGWIN="ntsec binmode tty nowinsymlinks"
  @INC:
    lib
    /usr/lib/perl5/5.8.0/cygwin-multi-64int
    /usr/lib/perl5/5.8.0
    /usr/lib/perl5/site_perl/5.8.0/cygwin-multi-64int
    /usr/lib/perl5/site_perl/5.8.0
    /usr/lib/perl5/site_perl
    .


Gerrit
-- 
=^..^=


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/