php-5.2.6 on rhel4
June 26, 2008 on 8:36 pm | In ramblings | No Commentsbuilding php-5.2.6 to our specifications on rhel4 gave me a little trouble, so i thought i’d write up the process here.
build environment: vanilla rhel 4.4/i386 install. httpd-2.0.52, apr- and apr-util-0.9.4.
prerequisites: most of the install- and build requirements are included in rhel, except for pcre and pcre-devel. i grabbed the pcre-7.3 src.rpm from our fedora mirror, compiled and installed.
the mysql AB client gave us some surprises. it installs its own, bundled version of zlib among other things, and i found that php-5.2.6 won’t (for me, anyway) install against the mysql-5.0.51a client or the mysql-5.0.45 client. i had planned on updating the mysql client installs on our web nodes, but i wound up dropping my build box back to mysql-5.0.27. voila, function ‘adler32′ not supported’ errors all gone!
build: i grabbed the php-5.2.6 src rpm from our fedora mirror and installed it.
here is a link to the .spec file i used. i basically commented out the packages not offered under rhel4 (libmcrypt, mhash, libtidy) and the packages we won’t need (mssql, freetds).
i had been working as an unprivileged user privileged with sudo, but php-5.2.6 won’t compile for gcc3, so i was lazy, su’ed, exported CC=gcc4, and continued on as root:
$ rpmbuild -bp /usr/src/redhat/SPECS/php.spec
(satisfy dependencies here)
$ rpmbuild -ba –target=i686 /usr/src/redhat/SPECS/php.spec
i recommend comparing the stock 5.2.6 php.ini against your current php.ini, as there are some new stanzas, some removed, etc. of note is the new allow_url_include directive, which is not in the php.ini file, and defaults to off. this means that any include() statements that attempt to load a url will instead throw an error. we researched this for a bit and discussed the pros and cons of leaving allow_url_include’s set to its default of off versus the disruption it would cause in our contributors’ sites. we decided to leave it off globally, but allow it, per-directory, by request.
in discovering allow_url_include we viewed many of our contributors’ sites today under 5.2.6, and generally found that wordpress, mediawiki, and other software packages that adhere to ‘best practices’ were fine, while older, home-rolled php scripts threw some errors.
work for UNC? here’s how to view your paystub.
June 6, 2008 on 7:47 am | In ramblings, tech stoof | 1 CommentUNC recently stopped sending out paper paystubs, a move which my inner environmentally conscious earth child wholly supports. however, the paystub notification e-mails from finance decline to include a link to the electronic paystubs for security reasons. my co-worker became quite grouchy whilst trying to find his paystub this morning. so, as a service to the UNC community, i am posting instructions for viewing one’s paystub should one work for UNC.
- browse to http://my.unc.edu and login with your OnYEN
- staff: click on the ’staff’ tab. others: i hope you have a tab!
- click ‘See your paystub’, then allow pop-ups and click it again.
- log in with your OnYEN again. welcome to the Payroll Services Pay Stub Application.
- choose a pay period, and click ‘Display Pay Stub’
- allow pop-ups and click ‘Display Pay Stub’ again. whistles will toot and gears will whir, and if you’re running Windows, your browser will present your paystub. if you’re not running Windows, your browser will present a file called ‘displayPayStub.do’ and ask what to do with it.
- save ‘displayPayStub.do’ and rename it to something like paystub-yyyymmdd, changing the extension to ‘.pdf’ so that your computer will know how to open it. my co-worker did a Google search for ‘.do extension’ but Google tried to sell him weave. honest.
best of luck!
Powered by WordPress with Pool theme design by Borja Fernandez.
Entries and comments feeds.
Valid XHTML and CSS. ^Top^