You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by Noam Solomon <no...@socketnet.com> on 2002/11/19 18:07:11 UTC

am i heading for disaster... ?

In the process of building apache_1.3.27 / mod_perl 1.3.27 / openssl0.9.6g / mod_ssl mod_ssl-2.8.12-1.3.27 on a Solaris OS 2 UltraSparc, with Perl 5.8, the apache make failed because of an undefined "url_delims".  I was using the method where you build mod_ssl, then build mod_perl, then configure apache, loading mod_perl statically.

Anyway, I poked around and found that indeed the uri_delims.h file in src/main was empty!  So still in src/main, I manually ran "gcc gen_uri_delims.c", then ran "a.out > uri_delims.h" to regenerate that header file, and got this.

  /* this file is automatically generated by gen_uri_delims, do not edit */
  static const unsigned char uri_delims[256] = {
      T_NUL,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
      0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,T_HASH,0,0,0,0,
      0,0,0,0,0,0,0,T_SLASH,0,0,0,0,0,0,0,0,0,0,T_COLON,0,
      0,0,0,T_QUESTION,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
      0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
      0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
      0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
      0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
      0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
      0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
      0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
      0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
      0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
  };

Then when I ran make again, everything was hunky-dory.  Now what I want to know is, why would this have happened in the first place?  Is it a sign that something is fundamentally wrong with the build, but I just haven't seen it yet?  Or should I just breathe easy and hope for the best?




Re: am i heading for disaster... ?

Posted by Noam Solomon <no...@socketnet.com>.
I definitely didn't run out of disk space, so it must have been something
else.  There were a number of funky things that happened over the course of
the build.  The first time around, I made mod_perl, then made mod_ssl, and
had an error about util.o being out of sync with mod_ssl, so then I ran the
mod_perl make a second time, without cleaning first.  Maybe the file got
erased in the process.  The next time I ran apache make, I had a linker
error and had to set LD_LIBRARY_PATH explicitly to correct it.  Maybe I
needed to do the same while building mod_perl.

But, knock on wood, the server hasn't choked yet, or behaved weirdly.  Guess
I'll find out when it goes into production...

Thanks

----- Original Message -----
From: "Stas Bekman" <st...@stason.org>
To: "Noam Solomon" <no...@socketnet.com>
Cc: <mo...@perl.apache.org>
Sent: Wednesday, November 20, 2002 12:39 PM
Subject: Re: am i heading for disaster... ?


> Noam Solomon wrote:
> > In the process of building apache_1.3.27 / mod_perl 1.3.27 /
> > openssl0.9.6g / mod_ssl mod_ssl-2.8.12-1.3.27 on a Solaris OS 2
> > UltraSparc, with Perl 5.8, the apache make failed because of an
> > undefined "url_delims".  I was using the method where you build mod_ssl,
> > then build mod_perl, then configure apache, loading mod_perl statically.
> >
> > Anyway, I poked around and found that indeed the uri_delims.h file in
> > src/main was empty!  So still in src/main, I manually ran "gcc
> > gen_uri_delims.c", then ran "a.out > uri_delims.h" to regenerate that
> > header file, and got this.
> >
> >
> >     /* this file is automatically generated by gen_uri_delims, do not
> >     edit */
> >     static const unsigned char uri_delims[256] = {
> >         T_NUL,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
> >         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,T_HASH,0,0,0,0,
> >         0,0,0,0,0,0,0,T_SLASH,0,0,0,0,0,0,0,0,0,0,T_COLON,0,
> >         0,0,0,T_QUESTION,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
> >         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
> >         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
> >         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
> >         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
> >         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
> >         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
> >         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
> >         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
> >         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
> >     };
> >
> > Then when I ran make again, everything was hunky-dory.  Now what I want
> > to know is, why would this have happened in the first place?  Is it a
> > sign that something is fundamentally wrong with the build, but I just
> > haven't seen it yet?  Or should I just breathe easy and hope for the
best?
>
> I doubt this has anything to do with mod_perl. The build hasn't changed
> in years, so it must be some external glitch. For example you might have
> run out of disk space, so when it was writing the file it was zeroed.
>
>
> --
>
>
> _____________________________________________________________________
> Stas Bekman             JAm_pH      --   Just Another mod_perl Hacker
> http://stason.org/      mod_perl Guide   http://perl.apache.org/guide
> mailto:stas@stason.org  http://ticketmaster.com http://apacheweek.com
> http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
>
>
>


Re: am i heading for disaster... ?

Posted by Stas Bekman <st...@stason.org>.
Noam Solomon wrote:
> In the process of building apache_1.3.27 / mod_perl 1.3.27 / 
> openssl0.9.6g / mod_ssl mod_ssl-2.8.12-1.3.27 on a Solaris OS 2 
> UltraSparc, with Perl 5.8, the apache make failed because of an 
> undefined "url_delims".  I was using the method where you build mod_ssl, 
> then build mod_perl, then configure apache, loading mod_perl statically.
>  
> Anyway, I poked around and found that indeed the uri_delims.h file in 
> src/main was empty!  So still in src/main, I manually ran "gcc 
> gen_uri_delims.c", then ran "a.out > uri_delims.h" to regenerate that 
> header file, and got this.
>  
> 
>     /* this file is automatically generated by gen_uri_delims, do not
>     edit */
>     static const unsigned char uri_delims[256] = {
>         T_NUL,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
>         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,T_HASH,0,0,0,0,
>         0,0,0,0,0,0,0,T_SLASH,0,0,0,0,0,0,0,0,0,0,T_COLON,0,
>         0,0,0,T_QUESTION,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
>         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
>         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
>         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
>         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
>         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
>         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
>         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
>         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
>         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
>     };
> 
> Then when I ran make again, everything was hunky-dory.  Now what I want 
> to know is, why would this have happened in the first place?  Is it a 
> sign that something is fundamentally wrong with the build, but I just 
> haven't seen it yet?  Or should I just breathe easy and hope for the best?

I doubt this has anything to do with mod_perl. The build hasn't changed 
in years, so it must be some external glitch. For example you might have 
run out of disk space, so when it was writing the file it was zeroed.


-- 


_____________________________________________________________________
Stas Bekman             JAm_pH      --   Just Another mod_perl Hacker
http://stason.org/      mod_perl Guide   http://perl.apache.org/guide
mailto:stas@stason.org  http://ticketmaster.com http://apacheweek.com
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/