FAQ
I'm slowly trying to get back into the swing of things after a couple of
weeks away, and I see that blead currently doesn't build on Win32 (in
debug mode at least):

..\toke.c(3209) : error C2039: 'S_pending_ident' : is not a member of
'yy_parser'
..\parser.h(23) : see declaration of 'yy_parser'
..\toke.c(4137) : error C2039: 'S_pending_ident' : is not a member of
'yy_parser'
..\parser.h(23) : see declaration of 'yy_parser'
..\toke.c(4750) : error C2039: 'S_pending_ident' : is not a member of
'yy_parser'
..\parser.h(23) : see declaration of 'yy_parser'
..\toke.c(4874) : error C2039: 'S_pending_ident' : is not a member of
'yy_parser'
..\parser.h(23) : see declaration of 'yy_parser'
..\toke.c(4908) : error C2039: 'S_pending_ident' : is not a member of
'yy_parser'
..\parser.h(23) : see declaration of 'yy_parser'
..\toke.c(6888) : error C2039: 'S_pending_ident' : is not a member of
'yy_parser'
..\parser.h(23) : see declaration of 'yy_parser'
..\toke.c(6889) : error C2039: 'S_pending_ident' : is not a member of
'yy_parser'
..\parser.h(23) : see declaration of 'yy_parser'

I haven't tried a release build yet. I would try it after a distclean,
but that doesn't work any more either...:

C:\p5p\bleadperl\win32>nmake distclean

Microsoft (R) Program Maintenance Utility Version 6.00.8168.0
Copyright (C) Microsoft Corp 1988-1998. All rights reserved.

..\miniperl.exe -I..\lib ..\uupacktool.pl -c -d .. -m
'..\miniperl.exe' is not recognized as an internal or external command,
operable program or batch file.
NMAKE : fatal error U1077: '..\miniperl.exe' : return code '0x1'
Stop.

--


------------------------------------------------
Radan Computational Ltd.

The information contained in this message and any files transmitted with it are confidential and intended for the addressee(s) only. If you have received this message in error or there are any problems, please notify the sender immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Radan Computational Ltd. The recipient(s) of this message should check it and any attached files for viruses: Radan Computational will accept no liability for any damage caused by any virus transmitted by this email.

Search Discussions

  • Steve Hay at Jan 2, 2007 at 11:44 am

    Steve Hay wrote:
    I'm slowly trying to get back into the swing of things after a couple of
    weeks away, and I see that blead currently doesn't build on Win32 (in
    debug mode at least):

    ..\toke.c(3209) : error C2039: 'S_pending_ident' : is not a member of
    'yy_parser'
    ..\parser.h(23) : see declaration of 'yy_parser' [...]
    I haven't tried a release build yet. I would try it after a distclean,
    but that doesn't work any more either...:
    The distclean silliness is now fixed by #29659, but I have the same
    toke.c compilation errors in release mode.

    --


    ------------------------------------------------
    Radan Computational Ltd.

    The information contained in this message and any files transmitted with it are confidential and intended for the addressee(s) only. If you have received this message in error or there are any problems, please notify the sender immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Radan Computational Ltd. The recipient(s) of this message should check it and any attached files for viruses: Radan Computational will accept no liability for any damage caused by any virus transmitted by this email.
  • Demerphq at Jan 2, 2007 at 11:55 am

    On 1/2/07, Steve Hay wrote:
    Steve Hay wrote:
    I'm slowly trying to get back into the swing of things after a couple of
    weeks away, and I see that blead currently doesn't build on Win32 (in
    debug mode at least):

    ..\toke.c(3209) : error C2039: 'S_pending_ident' : is not a member of
    'yy_parser'
    ..\parser.h(23) : see declaration of 'yy_parser' [...]
    I haven't tried a release build yet. I would try it after a distclean,
    but that doesn't work any more either...:
    The distclean silliness is now fixed by #29659, but I have the same
    toke.c compilation errors in release mode.
    I was wondering, would it be possible for things like the distclean to
    fallback on using real perl? At least on win32 its highly likely that
    people building a new Perl already have an installed one in the path.

    yves

    --
    perl -Mre=debug -e "/just|another|perl|hacker/"
  • Steve Hay at Jan 2, 2007 at 12:08 pm

    demerphq wrote:
    On 1/2/07, Steve Hay wrote:
    The distclean silliness is now fixed by #29659, but I have the same
    toke.c compilation errors in release mode.
    I was wondering, would it be possible for things like the distclean to
    fallback on using real perl? At least on win32 its highly likely that
    people building a new Perl already have an installed one in the path.
    I don't think that would be a good idea. I always build perl in an
    environment in which there specifically isn't any other perl on the PATH
    to avoid any possible confusion as to which perl is getting used.
    Otherwise a call to an unqualified "perl.exe" could easily do the wrong
    thing, depending on what the current directory is.

    --


    ------------------------------------------------
    Radan Computational Ltd.

    The information contained in this message and any files transmitted with it are confidential and intended for the addressee(s) only. If you have received this message in error or there are any problems, please notify the sender immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Radan Computational Ltd. The recipient(s) of this message should check it and any attached files for viruses: Radan Computational will accept no liability for any damage caused by any virus transmitted by this email.
  • Demerphq at Jan 2, 2007 at 12:30 pm

    On 1/2/07, Steve Hay wrote:
    demerphq wrote:
    On 1/2/07, Steve Hay wrote:
    The distclean silliness is now fixed by #29659, but I have the same
    toke.c compilation errors in release mode.
    I was wondering, would it be possible for things like the distclean to
    fallback on using real perl? At least on win32 its highly likely that
    people building a new Perl already have an installed one in the path.
    I don't think that would be a good idea. I always build perl in an
    environment in which there specifically isn't any other perl on the PATH
    to avoid any possible confusion as to which perl is getting used.
    Otherwise a call to an unqualified "perl.exe" could easily do the wrong
    thing, depending on what the current directory is.
    Ah I see. Ok, I depend on having another perl available in path to
    cross test with, also for stuff like regen.pl and friends.

    Yves


    --
    perl -Mre=debug -e "/just|another|perl|hacker/"
  • Dave Mitchell at Jan 2, 2007 at 2:05 pm

    On Tue, Jan 02, 2007 at 10:56:01AM +0000, Steve Hay wrote:
    I'm slowly trying to get back into the swing of things after a couple of
    weeks away, and I see that blead currently doesn't build on Win32 (in
    debug mode at least):

    ..\toke.c(3209) : error C2039: 'S_pending_ident' : is not a member of
    'yy_parser'
    Hopefully fixed by change #29660

    --
    Monto Blanco... scorchio!
  • Steve Hay at Jan 2, 2007 at 2:52 pm

    Dave Mitchell wrote:
    On Tue, Jan 02, 2007 at 10:56:01AM +0000, Steve Hay wrote:
    I'm slowly trying to get back into the swing of things after a couple of
    weeks away, and I see that blead currently doesn't build on Win32 (in
    debug mode at least):

    ..\toke.c(3209) : error C2039: 'S_pending_ident' : is not a member of
    'yy_parser'
    Hopefully fixed by change #29660
    That fixed the toke.c problem, but then I got linker errors over
    Perl_my_cxt_index and Perl_Imy_cxt_keys_ptr.

    I've applied #29661 to fix them. Hopefully it's OK, but I'm always
    uneasy about this stuff. Does it look right?

    --


    ------------------------------------------------
    Radan Computational Ltd.

    The information contained in this message and any files transmitted with it are confidential and intended for the addressee(s) only. If you have received this message in error or there are any problems, please notify the sender immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Radan Computational Ltd. The recipient(s) of this message should check it and any attached files for viruses: Radan Computational will accept no liability for any damage caused by any virus transmitted by this email.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupperl5-porters @
categoriesperl
postedJan 2, '07 at 10:57a
activeJan 2, '07 at 2:52p
posts7
users3
websiteperl.org

People

Translate

site design / logo © 2018 Grokbase