[lug] PHP3 compile and rusage (the fix)

John Starkey jstarkey at advancecreations.com
Mon Jan 8 18:16:14 MST 2001


Thanks Chip. Your suggestion led me to the fix.

I was enabling mysql when compiling php3 and was pointing it to the
symlink. www.mysql.org (I think) said to symlink from /usr/local/mysql to
the mysql compiled source dir. I guess php's compile wasn't following the
link so it didn't see the mysql includes.

I tried your suggestion of cp'ing the php3 binaries to the local machine
but couldn't compile it in apache because of the dir structure. That's
what made me think of it.

Thanks again,

John

On Mon, 8 Jan 2001, Atkinson, Chip wrote:

> Yeah, just ftp the executable files themselves, don't bother with the built
> but not installed directories.  
> 
> Here are at least two ways of a recursive touch:
> find . -exec touch {} \;
> find . -print | xargs touch
> 
> Note that if you have weird file names, you'll need to look into -print0
> 
> Chip
> 
> > -----Original Message-----
> > From: John Starkey [mailto:jstarkey at advancecreations.com]
> > Sent: Monday, January 08, 2001 1:03 PM
> > To: 'lug at lug.boulder.co.us'
> > Subject: RE: [lug] PHP3 compile and rusage
> > 
> > 
> > I tried doing make on the other machine and make install on 
> > the local box,
> > yesterday. I rec'd a clock skew (no wonder I'm always late :} 
> > ) and some
> > other errors. Do you know of a way to use touch recursively? 
> > I didn't see
> > anything in man touch that'd work.
> > 
> > I'll try using the completed code though. Thanks. I can't see 
> > myself going
> > thru the C code. I've got too much going on to even attempt to figure
> > that out. If this doesn't work I'll have to use the remote 
> > until I know
> > enough to understand/fix this problem. 
> > 
> > Thanks again,
> > 
> > John
> > 
> > On Mon, 8 Jan 2001, Atkinson, Chip wrote:
> > 
> > > John,
> > > 
> > > Here's an idea for you -- take the compiled code from one 
> > of your machines
> > > as well as php.ini from those machines and just copy it to your home
> > > machine.  That's the easiest and cheapest, but if you must 
> > get it to compile
> > > on your machine, you will probably have to slug through the 
> > whole thing an
> > > inch at a time.  To do that, I'd find what is not defined 
> > and where it is.
> > > If it's nowhere to be found, you may not have installed 
> > that particular
> > > package.  Then it starts getting fugly. :-)
> > > 
> > > Chip
> > > 
> > > > -----Original Message-----
> > > > From: John Starkey [mailto:jstarkey at advancecreations.com]
> > > > Sent: Monday, January 08, 2001 12:37 PM
> > > > To: 'lug at lug.boulder.co.us'
> > > > Subject: RE: [lug] PHP3 compile and rusage
> > > > 
> > > > 
> > > > Chip thanks a lot for the reply. I've spent a total of 16 
> > > > hours on this. I
> > > > see the same problem all over the boards, everyone has a 
> > > > suggestion/fix
> > > > but none of them apply. 
> > > > 
> > > > I do have a machine that works fine. It's a stock install 
> > of RH6.2,
> > > > unscathed by me:}. But my home machine just won't compile. For the
> > > > archives and anyone else, there's a faq that addresses this 
> > > > issue as well
> > > > as a lot of discussion on this in the php.net mail 
> > archives. But it's
> > > > definately an "I broke my linux box" issue from what i can tell.
> > > > 
> > > > > Are there any other errors?  rusage is a structure in 
> > > > system header files.
> > > > > See getrlimit(2).  One thing that I found when building PHP 
> > > > on machines here
> > > > > is that the linux boxes as installed were missing include 
> > > > files, or links to
> > > > 
> > > > No other errors.
> > > > 
> > > > Yea. I upgraded to glibc-2.1.3, reconfiged my 2.3.9 kernel 
> > > > and symlinked
> > > > to the linux dir and the asm dir from /usr/include, I tried, 
> > > > as one person
> > > > suggested, adding a CFLAG='-02 -DHAVE_SYS_RESOURCE_H' env 
> > > > variable, but
> > > > this is already a flag in everything up to and including the 
> > > > microtime.c
> > > > line anyway. I uncommented all the RLIM_INFINITY lines in my 
> > > > resource.h.
> > > > And a few other things that I can't remember I'm sure.
> > > > 
> > > > > Clean the distribution directory out again (make clean usually)
> > > > > Re-run configure
> > > > > run make
> > > > 
> > > > Also need to delete the config.cache.
> > > > 
> > > > > watch the error messages for include files not being found. 
> > > >  Find the files,
> > > > > usually under /usr/src/linux and put symlinks in 
> > > > /usr/include that point to
> > > > > the files that reside under /usr/src/linux/...
> > > > 
> > > > I don't see any errors for includes not found (or atleast not 
> > > > blantenly
> > > > saying so.) This error doesn't even make mention. Just says the
> > > > function/microtime.c storage size og "usg" isn't known. (I 
> > > > guess usg is in
> > > > an include somewhere?)
> > > > 
> > > > Maybe I missed something here. I did a make menu config in 
> > > > the 2.3.9 dir,
> > > > and accepted the defaults. Then did a make. After that I 
> > > > symlinked from
> > > > /usr/include/linux to /usr/src/linux/include/linux and from
> > > > /usr/include/asm to /usr/src/linux/include/asm-i386. 
> > > > 
> > > > This is crazy. I don't have a problem with anything else 
> > compiling.
> > > > 
> > > > Thanks,
> > > > 
> > > > john
> > > > 
> > > > 
> > > > _______________________________________________
> > > > Web Page:  http://lug.boulder.co.us
> > > > Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> > > > 
> > > 
> > > _______________________________________________
> > > Web Page:  http://lug.boulder.co.us
> > > Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> > > 
> > 
> > 
> > _______________________________________________
> > Web Page:  http://lug.boulder.co.us
> > Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> > 
> 
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> 





More information about the LUG mailing list