On Tue, May 17, 2011 at 11:28 PM, Mike Jakubik
wrote:
> It's fairly simple, ill have to see how mod_ajp works and test it in our
> staging environment first. However anyone else that uses mod_jk will run
> in to this eventually, guess i should contact the apache team
> responsible for the two.
>
On Tue, 17 May 2011 21:46:14 +0200
Alexander Leidinger wrote:
> On Tue, 17 May 2011 09:01:41 -0700 "Kevin Oberman"
> wrote:
>
>
> > Please put the information in this message (or at least most of it)
> > into ports/UPDATING so a few less people running old kernels will be
> > bitten by the ins
On all of my FreeBSD 9.0-CURRENT/amd64 boxes LibreOffice 3.3.X crashes
after starting and dumping core with signal 8. The boxes are all FreeBSD
9.0-CURRENT/amd64, the most recent version. The ports are up to date, I
also tried to recompile every necessary port without success.
On all FreeBSD 9
on 18/05/2011 12:10 O. Hartmann said the following:
> ---
> Oh dear - something failed during the build - sorry !
> For more help with debugging build errors, please see the section in:
> http://wiki.documentf
On Mon, May 16, 2011 at 1:02 PM, Jerry wrote:
> I am proposing a new one:
>
> x - expired
> This report is over 2 years old. If no one has bothered to fix it
> by now, then in all probability no one will.
Not gonna happen, for reasons that have been mentioned previously.
If you feel a PR
For a couple of days I have not been able to upgrade apr1. It dies
with libtool that I've also rebuilt.
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for library containing strerror... none required
checking whether system uses EBCDIC...
Quoting eculp :
For a couple of days I have not been able to upgrade apr1. It dies
with libtool that I've also rebuilt.
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for library containing strerror... none required
checking whether sys
Hi,
While troubleshooting my problem with apr 1.4.4 and mod_jk i discovered
from upstream (devs on apr maillist) that there is a regression in this
version, reverting the port to a previous version might be a good idea
while a fix is created.
http://mail-archives.apache.org/mod_mbox/apr-dev/20110
I have the system FreeBSD 9.0-CURRENT #0 r222032 amd64
Port devel/libdispatch well constructed and works, why he:
libdispatch-174 is marked as broken: does not link on 9.X. ?
.if ${OSVERSION} >= 90 && ${ARCH} == "amd64"
BROKEN= does not link on 9.X
.endif
Thanks!
On 2011-05-18 20:57, eculp wrote:
> Quoting eculp :
>
>> For a couple of days I have not been able to upgrade apr1. It dies with
>> libtool that I've also rebuilt.
>>
>> checking for minix/config.h... no
>> checking whether it is safe to define __EXTENSIONS__... yes
>> checking for library contai
Hello,
I see the following error during the build:
dbdimp.c: In function 'mysql_db_FETCH_attrib':
dbdimp.c:2447: error: 'sv_undef' undeclared (first use in this function)
% uname -a
FreeBSD awarnach.mathstat.dal.ca 8.0-RELEASE-p4 FreeBSD 8.0-RELEASE-p4
#0: Mon Jul 12 20:55:11 UTC 2010
r...@amd64
I posted the other day about an issue I was having working around a
distribution CGI when adding a patch to a port. Thanks to a suggestion from
Matthew Seaman that problem is solved, but I seem to have bumped up against
another. It seems that I can't find a way to make applying the patch optio
Following up my own post. Bleargh.
On 2011/05/18, at 17:29, Matthew Pounsett wrote:
> .if defined(FOO)
> PATCH_SITES= http://location.site.com/path/
> PATCHFILES= port-${PORTVERSION}.patch
> PATCH_DIST_STRIP= -p1
> .endif
I should note that I have actually been doing this using '.i
On 18/05/2011 22:29, Matthew Pounsett wrote:
> I've added a new option (call it 'FOO') to the OPTIONS definition,
> and I'm attempting to add something like this directly below MASTER_SITES
> near the top of the Makefile:
>
> .if defined(FOO)
> PATCH_SITES= http://location.site.com/path/
> PA
On 05/18/2011 15:10, Matthew Seaman wrote:
# Testing both WITH_ and WITHOUT_ is a good idea...
I'm not sure why you would need to test both, unless it's to catch wacky
stuff coming in from the environment?
The usual way is to test the opposite of the default. So for default on
you would tes
On 18/05/2011 23:17, Doug Barton wrote:
> On 05/18/2011 15:10, Matthew Seaman wrote:
>> # Testing both WITH_ and WITHOUT_ is a good idea...
>
> I'm not sure why you would need to test both, unless it's to catch wacky
> stuff coming in from the environment?
That's one reason. Another is that it m
Quoting Olli Hauer :
On 2011-05-18 20:57, eculp wrote:
Quoting eculp :
For a couple of days I have not been able to upgrade apr1. It dies with
libtool that I've also rebuilt.
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for library c
Based on the responses here it sounds like I've been doing nothing wrong so I
played around a bit more. I guess in my testing there must've been some
combination of things I didn't get right... I did a bunch more testing and
eventually I made it work doing exactly what I've been doing, except
On May 18, 2011, at 17:44 , eculp wrote:
> checking whether it is safe to define __EXTENSIONS__... yes
> checking for library containing strerror... none required
> checking whether system uses EBCDIC... no
> performing libtool configuration...
> ./configure: 9904: Syntax error: word unexpected (e
19 matches
Mail list logo
