Richard Lynch kirjoitti:
This didn't compute. Halt on option that is enabled by default but
isn't
available?? huh?
Joe Sixpack or Betty Buick goes to compile PHP.
They do something not unlike:
/configure --enable-jpeg
This causes a notice of unknown option now..since that option does not exi
On Tue, July 17, 2007 4:03 pm, Jani Taskinen wrote:
>> Now if we could just get configure to HALT when an option that is
>> enabled by default but is specified on the command line as well
>> isn't
>> available, so users aren't confused by it continuing to build
>> something they didn't ask for in t
Arnold Daniels kirjoitti:
Anyway, I only mend to say that building pecl packages in the PHP distro
isn't so rare as just claimed. So it would be nice if this nifty feature
would also work for added packages.
It works for everything but phpize'd builds.
If you find out that some extension in pe
Hi,
I understand, but Yahoo is huge. We are not... Saying that it is
standard practice for ISP's is perhaps (ehh for sure) a bit of an
overstatement, since I only have contact with other small hosting
providers like us.
For us making packages actually takes up a significant amount of time,
Rasmus Lerdorf kirjoitti:
Jani Taskinen wrote:
Only side-effect is that any 3rd party extension which happens to use
the AC_ARG_* macros will cause it to report those as "unknown". But
perhaps it's time to be update.. ;)
*cough* APC *cough*
But this check isn't in a phpize-generated configure
Richard Lynch kirjoitti:
Maybe this check should be in a phpize-generated configure script, so
that new extensions will have it built-in?
I left it out intentionally from phpize. It is just a notice but I rather not
see any bug reports about 3rd party stuff. :)
MANY bug reports and build is
On Tue, July 17, 2007 3:04 pm, Gwynne Raskind wrote:
>>> Only side-effect is that any 3rd party extension which happens to
>>> use
>>> the AC_ARG_* macros will cause it to report those as "unknown". But
>>> perhaps it's time to be update.. ;)
>>>
>>> *cough* APC *cough*
>> But this check isn't in a
Arnold Daniels wrote:
> Hi Rasmus,
>
> I hope you've got a lot of fingers on your hand, because we do this as well.
>
> All servers are updated with an apt script and our private repository.
> It's easier to manage a single php package on all servers, that 14
> different packages. Each time PHP u
Hi Rasmus,
I hope you've got a lot of fingers on your hand, because we do this as well.
All servers are updated with an apt script and our private repository.
It's easier to manage a single php package on all servers, that 14
different packages. Each time PHP updates we take the newest package
Gwynne Raskind wrote:
> On Jul 17, 2007, at 3:44 PM, Rasmus Lerdorf wrote:
Hey Jani, nice job on the unknown configure options check. I saw the
commit go through a couple of days ago, and today it got me to clean up
an ancient build script I have been using for ages when it gave me
On Jul 17, 2007, at 3:44 PM, Rasmus Lerdorf wrote:
Hey Jani, nice job on the unknown configure options check. I saw
the
commit go through a couple of days ago, and today it got me to
clean up
an ancient build script I have been using for ages when it gave
me this:
Notice: Following unknow
Rasmus Lerdorf kirjoitti:
Hey Jani, nice job on the unknown configure options check. I saw the
commit go through a couple of days ago, and today it got me to clean up
an ancient build script I have been using for ages when it gave me this:
Notice: Following unknown configure options were used:
Jani Taskinen wrote:
> Rasmus Lerdorf kirjoitti:
>> Hey Jani, nice job on the unknown configure options check. I saw the
>> commit go through a couple of days ago, and today it got me to clean up
>> an ancient build script I have been using for ages when it gave me this:
>>
>> Notice: Following un
On 17.07.2007 22:00, Rasmus Lerdorf wrote:
Hey Jani, nice job on the unknown configure options check.
Yeah, it's really nice.
It also helped me to locate minor error in oci8/config.m4 =)
Thanks, Jani.
I saw the commit go through a couple of days ago, and today it got me to clean
up
an anc
Hey Jani, nice job on the unknown configure options check. I saw the
commit go through a couple of days ago, and today it got me to clean up
an ancient build script I have been using for ages when it gave me this:
Notice: Following unknown configure options were used:
--with-pdflib=/usr/local
--
15 matches
Mail list logo
