public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Crute <mcrute@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] PHP5 Quick Question
Date: Tue, 2 Aug 2005 11:39:50 -0400	[thread overview]
Message-ID: <558b73fb05080208393ab06c2c@mail.gmail.com> (raw)
In-Reply-To: <20050802173009.0612f2aa.hilse@web.de>

[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]

Well grepping that file is a nice trick that I didnt know. Thanks! Thats 
what I needed to know.

-Mike

On 8/2/05, Hans-Werner Hilse <hilse@web.de> wrote:
> 
> Hi,
> 
> On Tue, 2 Aug 2005 10:32:21 -0400
> Michael Crute <mcrute@gmail.com> wrote:
> 
> > Is there a way to build the php 5 extensions (I.E. GD, mysql, etc) as
> > external libraries instead of compiling it all into the core? I assume 
> this
> > is the sharedext flag but I want to make sure before I go try it and 
> muck
> > things up.
> 
> $ grep sharedext /usr/portage/profiles/use.desc
> sharedext - Adds support for building shared extensions in php
> 
> sounds good, doesn't it ;-)?
> 
> Regarding the "gd-external" A. Khattri mentioned, I think this is to
> make php use a separately compiled (by emerging it as a dependency) GD
> lib instead of using the sources that php has integrated.
> 
> -hwh
> --
> gentoo-user@gentoo.org mailing list
> 
> 


-- 
________________________________
Michael E. Crute
Software Developer
SoftGroup Development Corporation

"In a world without walls and fences, who needs windows and gates?"

[-- Attachment #2: Type: text/html, Size: 1552 bytes --]

      reply	other threads:[~2005-08-02 15:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-02 14:32 [gentoo-user] PHP5 Quick Question Michael Crute
2005-08-02 14:47 ` A. Khattri
2005-08-02 15:21   ` Michael Crute
2005-08-02 15:30 ` Hans-Werner Hilse
2005-08-02 15:39   ` Michael Crute [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=558b73fb05080208393ab06c2c@mail.gmail.com \
    --to=mcrute@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox