To be blunt... No. I don't mind giving the occasional bit of advice or throwing an occasional comment into a forum thread but I'm not prepared to offer one on one personal support. Especially as I'm not familiar with your specific Operating System version.
To be honest, it's highly unlikely that you will be the first person to build the required libraries on OS X 10.5, so when you encounter errors just fire up your favorite web search engine and search for the error. You'll most likely find at least one other person that has encountered the error before and with any luck they'll have documented a fix or someone else will have detailed a fix.
Just download the source packages you need, within each package there will generally be an 'INSTALL' or 'README' file which details basic steps required to build the package/library. Follow the instructions, note down any errors if you encounter them and go search the web for a potential fix. Note, the most common error durng configure is 'can't find xxx library' which should be self explanatory.
To give you a rough idea of what you may be letting yourself in for, have a look at this thread....
viewtopic.php?f=31&t=39385&p=208672
... although *please note*, do not follow the guides in that thread word for word, the guide was written quite some time ago for OS X 10.2 and as such will probably not be correct for 10.5
From my own experiences of building on MAC OS X there are two common problems...
1. Linking seems to be a bit of voodoo, most likely issues due to my unfamiliarity of the underlying OS X build system so to avoid many potential headaches install libraries somewhere that the linker will find them (most libraires/packages default to /usr/local which should be fine).
2. Official Apple binaries tend to include executable code for all 4 of it's architectures, a standard 'configure' and 'make' will produce binaries for a single architecture only however, when these binaries are used in conjunction with Apple's official binaries it can lead to problems and failures. A classic example is if you compile your own Apache PHP module then have Apple's official Apache release load your PHP module it generally fails. Things may have changed so this may be a non-issue now and there are various options to get round this if it's still a problem.