Synopsis: devel/qt4-uic etc. error: ÂThe specified system/compiler is not
supportedÂ
Responsible-Changed-From-To: freebsd-ports-bugs->kde
Responsible-Changed-By: edwin
Responsible-Changed-When: Wed Apr 8 00:20:22 UTC 2009
Responsible-Changed-Why:
Over to maintainer (via the GNATS Auto Assign T
> SOLUTION 1:
> Disable libiconv support altogether. This, I believe, is a viable solution
> since Windows does not have iconv and we should be using whatever fallback
> it does. This should result in no loss of functionality.
This is what I am doing for non-port builds of 4.5.0. It's also what'
On Tue, 7 Apr 2009 11:03:23 +0400
Max Brazhnikov wrote:
> is this MAKE_JOBS_SAFE or QAT failure?
Seems to be MAKE_JOBS_SAFE, it build once OK, then it failed, now it
built OK.
--
IOnut - Un^d^dregistered ;) FreeBSD "user"
"Intellectual Property" is nowhere near as valuable as "Intellect"
On Tuesday 07 April 2009 07:25:16 David Johnson wrote:
> I played around with this, rebuilding libiconv after gettext, but to no
> effect. Oh well, it was worth a shot...
I've managed to get Qt 4.5 to behave well with libiconv. It was a bit of a
cheat though. There is also another solution.
On Fri, Apr 3, 2009 at 9:35 PM, Daichi GOTO wrote:
> Hi amarok lovers ;)
>
> Anyone could use iPod with Amarok2?
> Still I cannot get it.
>
I've only tried this with one device so far (a second generation
Shuffle) and it looks like I was stymied by the fact that the GEOM
label had a space in it.
is this MAKE_JOBS_SAFE or QAT failure?
On Вторник 07 апреля 2009, q...@freebsd.org wrote:
> The Restless Daemon identified a makefile error while trying to build:
> kdebase-workspace-4.2.2 maintained by k...@freebsd.org
> Makefile ident: $FreeBSD: ports/x11/kdebase4-workspace/Makefile,v 1.218
>
