I would like to start using this new feature, but the 2.0b12 kist has not
been built yet.  I got the latest sources from
http://cvs.apache.org/snapshots/embperl/, but had trouble running the XS
scripts.  Has anyone seen this problem?  Any suggestions?

> perl xsbuilder/source_scan.pl -- seems to run fine

> xsbuilder/xs_generate.pl -- lots or warnings such as:
struct tAppConfig...
WARNING: pPool not in mapfile
WARNING: bUseEnv not in mapfile
WARNING: bUseRedirectEnv not in mapfile

and finally:

Can't locate object method "new_podtemplate" via package "Embperl::WrapXS"
at
/home/drayner/perllib/lib/perl5/site_perl/5.8.0/ExtUtils/XSBuilder/WrapXS.pm
line 1586.

Going ahead and build Embper fails:

> perl Makefile.PL
Warning: the following files are missing in your kit:
        Config.pod
        META.yml
        xs/Embperl/App/App.xs
        xs/Embperl/App/Config/Config.xs
        xs/Embperl/App/Config/Makefile.PL
        xs/Embperl/App/Makefile.PL
        xs/Embperl/Component/Component.xs
        xs/Embperl/Component/Config/Config.xs
        xs/Embperl/Component/Config/Makefile.PL
        xs/Embperl/Component/Makefile.PL
        xs/Embperl/Component/Output/Makefile.PL
        xs/Embperl/Component/Output/Output.xs
        xs/Embperl/Component/Param/Makefile.PL
        xs/Embperl/Component/Param/Param.xs
        xs/Embperl/Makefile.PL
        xs/Embperl/Req/Config/Config.xs
        xs/Embperl/Req/Config/Makefile.PL
        xs/Embperl/Req/Makefile.PL
        xs/Embperl/Req/Param/Makefile.PL
        xs/Embperl/Req/Param/Param.xs
        xs/Embperl/Req/Req.xs
        xs/Embperl/Thread/Makefile.PL
        xs/Embperl/Thread/Thread.xs
        xs/Makefile.PL
Please inform the author.


Thanks and regards,

Doug Rayner
Senior System Architect
Savicom: Next Generation eMail Marketing
http://www.savicom.net
(415) 617-9006

----- Original Message ----- 
From: "Gerald Richter" <[EMAIL PROTECTED]>
To: "Doug Rayner" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, April 20, 2004 8:43 PM
Subject: Re: Access to CGI object (was: Use Embperl 2.0 or 1.3.6? (was:
Change in behavior of <TH> in 2.0?))


> >
> > Were you able to develop the final solution to this?  Is the CGI
> > object now available from the request object?  If so, would it be in
> > the latest distribution kit yet?
> >
>
> It's now finaly part of the request object, you can get it via
>
> $epreq -> param -> cgi
>
> Currently it's only in the CVS version. It will released in 2.0b12
>
> Gerald
>
>
> > Thanks and regards,
> >
> > Doug Rayner
> > Senior System Architect
> > Savicom: Next Generation eMail Marketing
> > http://www.savicom.net
> > (415) 617-9006
> >
> > ----- Original Message -----
> > From: "Gerald Richter" <[EMAIL PROTECTED]>
> > To: "Doug Rayner" <[EMAIL PROTECTED]>
> > Cc: <[EMAIL PROTECTED]>
> > Sent: Monday, March 08, 2004 11:24 AM
> > Subject: Re: Access to CGI object (was: Use Embperl 2.0 or 1.3.6?
> > (was: Change in behavior of <TH> in 2.0?))
> >
> >
> >> Doug Rayner wrote:
> >>> Gerald;
> >>>
> >>> Are you open to suggestions for changes to Embperl 2.0 at this
> >>> point?
> >>>
> >>
> >> I am always open to suggestion, also I will main do bugfixing before
> >> the final 2.0 release
> >>
> >>> We would like to get access to the temporary files behind the file
> >>> handles provided for file uploads.  We would need access to the CGI
> >>> object used in the function get_multipart_formdata() in Embperl.pm.
> >>> Unfortunately, the object reference for the CGI object is in a my
> >>> variable and goes out of scope as soon as the function exits.  It
> >>> would be nice if this object reference could stay in scope and
> >>> accessble to the template throughout the whole request.  It could be
> >>> added to the %fdat hash, or put in some other global variable.
> >>>
> >>> Any thoughts on this?  We would prefer not to hack the distributed
> >>> sources for Embperl to accomplish this.  A supported method for
> >>> accomplishing this would be much preferable.
> >>>
> >>>
> >>
> >> The latest CVS version adds the CGI object as
> >>
> >> $fdatsplit{___CGI___}
> >>
> >> because CGI 3.01+ deletes the temp file as soon as it goes out of
> >> scope, so I have to keep the object.
> >>
> >> But be warned this is undocumented yet and is likely to change in
> >> favor for a real Embperl request method.
> >>
> >> Gerald
> >>
> >> P.S. Please send such mails to the Embperl mailing list
> >>
> >>
>
>> -------------------------------------------------------------------------
> -
> >> - Gerald Richter            ecos electronic communication services
> >> gmbh IT-Securitylösungen * Webapplikationen mit
> >> Apache/Perl/mod_perl/Embperl
> >>
> >> Post:       Tulpenstrasse 5          D-55276 Dienheim b. Mainz
> >> E-Mail:     [EMAIL PROTECTED]          Voice:   +49 6133 939-122
> >> WWW:        http://www.ecos.de/      Fax:     +49 6133 939-333
>
>> -------------------------------------------------------------------------
> -
> >> - Besuchen Sie uns auf der CeBIT (18. - 24. März 2004)
> >> Halle 6 Stand B38-452
> >>
> >> ECOS BB-5000 Firewall- und IT-Security Appliance: www.bb-5000.info
>
>> -------------------------------------------------------------------------
> -
> >> -
>
> --------------------------------------------------------------------------
-
> Gerald Richter            ecos electronic communication services gmbh
> IT-Securitylösungen * Webapplikationen mit Apache/Perl/mod_perl/Embperl
>
> Post:       Tulpenstrasse 5          D-55276 Dienheim b. Mainz
> E-Mail:     [EMAIL PROTECTED]          Voice:   +49 6133 939-122
> WWW:        http://www.ecos.de/      Fax:     +49 6133 939-333
> --------------------------------------------------------------------------
-
> Besuchen Sie uns auf der KOMCOM 2004 in Mannheim
> 25. bis 27. Mai 2004  Stand K11a   www.komcom.de
>
> ECOS BB-5000 Firewall- und IT-Security Appliance: www.bb-5000.info
> --------------------------------------------------------------------------
-
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to