On Tue, Apr 17, 2007 at 04:33:55PM +0200, Michael Nottebrock wrote:
> > I dimly remember seeing that before - I don't think Qt/qmake can actually
> > handle a PREFIX-move cleanly and once the prefix has changed, it has to be
> > deinstalled *before* rebuilding it, or else this will happen.
>
> Si
On Tue, Apr 17, 2007 at 09:22:58PM +0200, Dejan Lesjak wrote:
> On Tuesday 17 April 2007 20:58:42 Michael Nottebrock wrote:
> > On Tuesday, 17. April 2007, Dejan Lesjak wrote:
> > > On Tuesday 17 of April 2007, Michael Nottebrock wrote:
> > > > On Tuesday, 17. April 2007, Michael Nottebrock wrote:
On Tue, Apr 17, 2007 at 08:58:42PM +0200, Michael Nottebrock wrote:
> > Would bumping revision of qmake and qt be enough or were you thinking of
> > something more aggressive?
>
> No - I'm guessing the problem is that qmake generates wrong dependencies in
> Makefiles when it configures Qt with a
FYI; can you please investigate and/or report to the developers? If
you are already aware of this problem but do not yet have a fix,
please mark the port BROKEN in the appropriate case, so that users do
not unexpectedly encounter it.
See http://pointyhat.freebsd.org for the full log.
Thanks,
Kri
qt needs to be patched to look in ${LOCALBASE} for the X libraries
instead of assuming they are in /usr/X11R6. Can someone look at this
ASAP?
Kris
===> Patching for qt-3.3.8_3
===> Applying FreeBSD patches for qt-3.3.8_3
===> qt-3.3.8_3 depends on executable in : qmake - found
===> qt-3.3.
On Sat, May 05, 2007 at 12:36:49PM -0400, Kris Kennaway wrote:
> qt needs to be patched to look in ${LOCALBASE} for the X libraries
> instead of assuming they are in /usr/X11R6. Can someone look at this
> ASAP?
>
> Kris
This appears to come from qmake.
Kris
>
> ===>
On Sat, May 05, 2007 at 12:53:51PM -0400, Kris Kennaway wrote:
> On Sat, May 05, 2007 at 12:36:49PM -0400, Kris Kennaway wrote:
> > qt needs to be patched to look in ${LOCALBASE} for the X libraries
> > instead of assuming they are in /usr/X11R6. Can someone look at this
> >
On Tue, May 08, 2007 at 05:00:24PM +0200, Michael Nottebrock wrote:
> > Michael, if you are convinced, the bump is needed, please, do the honors...
>
> I think it will be done for us once the X11R7 import happens.
That's correct, we have bumped the revision in the git repo which will
be merged b
On Sat, May 12, 2007 at 11:04:58AM +0200, Michael Nottebrock wrote:
> On Friday, 11. May 2007, Kris Kennaway wrote:
> > cd src && make -f Makefile
> > /usr/local/bin/qmake-qt4 -spec /usr/local/share/qt4/mkspecs/freebsd-g++
> > -unix -o Makefile src.pro
>
> Th
On Mon, May 14, 2007 at 06:41:08AM +0200, Michael Nottebrock wrote:
> Kris Kennaway schrieb:
> > On Sat, May 12, 2007 at 11:04:58AM +0200, Michael Nottebrock wrote:
> >
> >> On Friday, 11. May 2007, Kris Kennaway wrote:
> >>
> >>> cd src &
FYI; can you please investigate and/or report to the developers? If
you are already aware of this problem but do not yet have a fix,
please mark the port BROKEN in the appropriate case, so that users do
not unexpectedly encounter it.
See http://pointyhat.freebsd.org for the full log.
Thanks,
Kri
Some change to current broke this, don't know who is responsible
- Forwarded message from User Ports-i386 <[EMAIL PROTECTED]> -
X-Original-To: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
X-Original-To: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
Date: Wed, 13 Jun 2007 15:11:14
FYI; can you please investigate and/or report to the developers? If
you are already aware of this problem but do not yet have a fix,
please mark the port BROKEN in the appropriate case, so that users do
not unexpectedly encounter it.
See http://pointyhat.freebsd.org for the full log.
Thanks,
Kri
FYI; can you please investigate and/or report to the developers? If
you are already aware of this problem but do not yet have a fix,
please mark the port BROKEN in the appropriate case, so that users do
not unexpectedly encounter it.
See http://pointyhat.freebsd.org for the full log.
Thanks,
Kri
FYI; can you please investigate and/or report to the developers? If
you are already aware of this problem but do not yet have a fix,
please mark the port BROKEN in the appropriate case, so that users do
not unexpectedly encounter it.
See http://pointyhat.freebsd.org for the full log.
Thanks,
Kri
FYI; can you please investigate and/or report to the developers? If
you are already aware of this problem but do not yet have a fix,
please mark the port BROKEN in the appropriate case, so that users do
not unexpectedly encounter it.
See http://pointyhat.freebsd.org for the full log.
Thanks,
Kri
Dear maintainer,
With 7.0-RELEASE coming we need to start working on bringing the ports
collection into better shape, and you can do your part by helping to
fix or annotate as BROKEN the ports that you maintain.
Could you please submit a PR either marking this port BROKEN on the
appropriate platf
Dear maintainer,
With 7.0-RELEASE coming we need to start working on bringing the ports
collection into better shape, and you can do your part by helping to
fix or annotate as BROKEN the ports that you maintain.
Could you please submit a PR either marking this port BROKEN on the
appropriate platf
Tilman Linneweh wrote:
>
>
> * Mark Linimon [ Dec 26, 2007 (18:28 )]:
>
>> OpenEXR is coredumping on sparc64-6 and sparc64-7. This means that
>> kde can't
>> be built for those architectures, including for the releases. Does
>> anyone
>> have some time to investigate this? I am willing to a
Philip M. Gollucci wrote:
> o Remove 5.x support
>
> Port maintainer ([EMAIL PROTECTED]) is cc'd.
FYI, we stated in the EOL announcement that we are not doing sweeping
5.x removals right away. Please give it more time.
Kris
___
kde-freebsd mailing
The following reply was made to PR ports/124944; it has been noted by GNATS.
From: Kris Kennaway <[EMAIL PROTECTED]>
To: "Philip M. Gollucci" <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: ports/124944: [PATCH] audio/arts: Remove
21 matches
Mail list logo
