1 |
Another thing to add to this, pear does not appear to compile with |
2 |
the apache build. |
3 |
|
4 |
I have this in my /etc/portage/package.use: dev-lang/php apache2 |
5 |
sockets mysql mysqli cli xml xsl pcre pdo-external session sqlite |
6 |
curl gd iconv jpeg pcntl pear png posix soap snmp ssl zlib bzip2 |
7 |
bcmath ctype calendar curlwrappers gdbm exif dbm unicode |
8 |
|
9 |
According to this url: http://gentoo-wiki.com/HOWTO_PHP_5_with_PEAR |
10 |
all that pear needs in order to compile are the following USE flags: |
11 |
cli pcre xml zlib. Maybe I'm a little out of it, but if you use the |
12 |
ebuild command does it use /etc/portage/package.use or is that only |
13 |
for emerge? |
14 |
|
15 |
|
16 |
On Sep 26, 2006, at 3:31 PM, nate wrote: |
17 |
|
18 |
> I'm not sure if this is the proper list, if it is not I apologize |
19 |
> and if someone could tell me which I should use it would be |
20 |
> appreciated. |
21 |
> |
22 |
> I'm having a few issues, and I'm not exactly sure where these are |
23 |
> exactly. |
24 |
> |
25 |
> First off I built a custom apache-2.0.58 ebuild from the one in the |
26 |
> portage tree. It seems to have compiled just fine, and reads all |
27 |
> of our previous apache configs, it even loads up php just fine and |
28 |
> dandy. The reason for this custom build was we needed a specific |
29 |
> layout that we have created, which was used during the compiling of |
30 |
> apache. |
31 |
> |
32 |
> Next onto php. Since our application relies heavily on php for the |
33 |
> back end we have several patches that we have created, as well as |
34 |
> needing very specific things done in the ./configure portion of |
35 |
> compiling. The patches applied just fine, I looked for the lines |
36 |
> that were changed in the source code while it was compiling and |
37 |
> they did change. The ./configure that I put inside /usr/portage/ |
38 |
> eclass/depend.apache also ran with no problems. |
39 |
> |
40 |
> My php.ini location was specified in two locations, first with -- |
41 |
> with-config-file-path=/etc/apache as well as modifying |
42 |
> PHP_INI_DIR="/etc/apache/" in /usr/portage/eclass/php5_1- |
43 |
> sapi.eclass, though a php -i still shows the default location for |
44 |
> the gentoo build at /etc/php/apache2-php5/php.ini. I know it's |
45 |
> silly to require our php.ini to be in /etc/apache, but currently |
46 |
> that's where a *lot* of code looks for that file, symbolic links |
47 |
> cause issues so the file must reside there. |
48 |
> |
49 |
> Finally libphp5.so does not seem to compile *at all.* This is |
50 |
> troublesome considering I am compiling with the apache support |
51 |
> enabled. Without that I won't be able to use php scripts through |
52 |
> apache, any idea why that doesn't exist? |
53 |
> -- |
54 |
> gentoo-user@g.o mailing list |
55 |
|
56 |
|
57 |
-- |
58 |
gentoo-user@g.o mailing list |