Ok, I figured out how to get it right. First upgrade automake, then
upgrade autoconf, and the problem is gone.
Nicki
This message was sent using IMP, the Internet Messaging Program.
__
Tirc has not been developed for some time now. It's now considered
insecure and has already been removed from most of the other distros.
It has been flagged deprecated in our tree for awhile, so unless
someone wants to take over development and maintenance of this port
it will be deorbited Thur
Hi,
The build which triggered this email is done under tinderbox-2.4.3, on
7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly"
and ccache support, with the "official" up-to-date Ports Tree, with the
following vars set:
NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_
Hi,
The build which triggered this email is done under tinderbox-2.4.3, on
7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly"
and ccache support, with the "official" up-to-date Ports Tree, with the
following vars set:
NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_
Hi,
The build which triggered this email is done under tinderbox-2.4.3, on
7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly"
and ccache support, with the "official" up-to-date Ports Tree, with the
following vars set:
NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_
Hello,
something went wrong with the last upgrade of devel/qt4. I followed the
entry in UPDATING and made
# portupgrade -f devel/qmake4 devel/qt4-moc devel/qt4-corelib
but only devel/qmake4 was upgraded; the two others were skipped (I don't
know why). So I tried to do the portupgrade by hand but
On Wed, 27 Aug 2008 17:43:45 +0200, Karsten Rothemund wrote:
> So, these two basic packages are missing now on the system and the rest
> of the Qt- and KDE-packages cannot be upgraded.
>
> Interesting enough: on my laptop everything worked.
>
> My question: is there a chance to "repair" this withou
Hi,
The build which triggered this email is done under tinderbox-2.4.3, on
7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly"
and ccache support, with the "official" up-to-date Ports Tree, with the
following vars set:
NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_
>
> The only packages I didn't get to build were database, java and
> jhandles. If someone else could do these for me I would appreciate it.
> I also did not get octcdf to build, because it requires a newer
> version of netcdf than FreeBSD currently has in the ports.
Hi Stephen,
Thank you for yo
Alexander Barth wrote:
The only packages I didn't get to build were database, java and
jhandles. If someone else could do these for me I would appreciate it.
I also did not get octcdf to build, because it requires a newer
version of netcdf than FreeBSD currently has in the ports.
Hi Stephen,
Hi Michael,
Yes, that one works like a charm. Thanks!
Tames.
--
Tames van der Does
CCIE Security #9652
Mobile: +31 622408224
Email: [EMAIL PROTECTED]
-Original Message-
From: Michael Scholz [mailto:[EMAIL PROTECTED]
Sent: Monday, August 25, 2008 08:50 PM W. Europe Standard Time
T
Hi,
I tried to install |/www/slash, but |it stopped on mod_perl build error.
The system: freebsd 7.0 minimal install, with appache2.2.9, mysql 5.0
and php5 installed and the ports are updated.
Information on freshports.org shows that there is no maintainer for this
port and the last update
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Guoqin Ren wrote:
> Hi,
>
> I tried to install |/www/slash, but |it stopped on mod_perl build error.
>
> The system: freebsd 7.0 minimal install, with appache2.2.9, mysql 5.0
> and php5 installed and the ports are updated.
>
> Information on fresh
Greg Larkin wrote:
-BEGIN PGP SIGNED MESSAGE-
[...]
Ideally, the www/slash port should specify that it conflicts with Apache
2.x, unless it can be ported to use mod_perl2 as well as mod_perl.
Regards,
Greg
- --
Greg Larkin
Thanks Greg, dead on.
___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philip M. Gollucci wrote:
> Greg Larkin wrote:
>> -BEGIN PGP SIGNED MESSAGE-
> [...]
>
>> Ideally, the www/slash port should specify that it conflicts with Apache
>> 2.x, unless it can be ported to use mod_perl2 as well as mod_perl.
>>
>> Rega
Hi Greg,
Thanks a lot :)
I'll get Apache1.3 installed on another machine and try slash again.
Thanks,
Guoqin
On Wed, Aug 27, 2008 at 5:24 PM, Greg Larkin <[EMAIL PROTECTED]> wrote:
>
>
> Hi Guoquin,
>
> I found this documentation on
> http://www.freebsd.org/doc/en/books/handbook/networ
Le 19/08/2008 à 19:32:52-0400, Philip M. Gollucci a écrit
> Philip M. Gollucci wrote:
> > [PLEASE DROP GNATS from your replys]
> > http://tinderbox-amd64.rws/index.php?action=list_buildports&build=8-CURRENT-RT38
> >
>
> should be
> http://tinderbox-amd64.riderway.com:8080/index.php?action=list_
Albert Shih wrote:
Le 19/08/2008 à 19:32:52-0400, Philip M. Gollucci a écrit
Philip M. Gollucci wrote:
[PLEASE DROP GNATS from your replys]
http://tinderbox-amd64.rws/index.php?action=list_buildports&build=8-CURRENT-RT38
should be
http://tinderbox-amd64.riderway.com:8080/index.php?action=lis
18 matches
Mail list logo