On Tuesday 12 January 2010 17:49:25 Damian Weber wrote:
> Hi, all,
>
> I've got a strange SIGABRT issue with kcheckpass.
> Of course, kcheckpass is not contained in the base
> system, yet I write to this list since the base system
> could be able to help with tracking this down.
> (kcheckpass is c
On Friday 25 May 2007 00:46:09 JoaoBR wrote:
> On Thursday 24 May 2007 17:19:00 Andy Fawcett wrote:
> > ping# uname -a
> > FreeBSD ping.int.athame.co.uk 6.2-STABLE FreeBSD 6.2-STABLE #0: Wed May
> > 23 15:19:22 EEST 2007
> > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/P
and use
> usb mem chips and kick atapicam out of the kernel
ping# uname -a
FreeBSD ping.int.athame.co.uk 6.2-STABLE FreeBSD 6.2-STABLE #0: Wed May 23
15:19:22 EEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PING
amd64
(compiled from sources updated immediately before the build
x11/kde3 (kde-3.5.6)
Unfortunately, you've not pasted the important part, which is the part that
actually shows the error in kdepim3. This would have come just before
the "Stop in /usr/ports/deskutils/kdepim3." message above.
The
On Sunday 18 February 2007 16:32, Ariff Abdullah wrote:
> On Sun, 18 Feb 2007 14:28:54 +0200
>
> Andy Fawcett <[EMAIL PROTECTED]> wrote:
> > On Sunday 18 February 2007 11:04, Jack L. wrote:
> > > It fails to compile with the gcc version that comes with FreeBSD 6
>
d64 when gcc 4.1 is used. I guess a
simple fix for the port would be to update the USE_GCC version to a value
known to work (4.1 and 4.2 from ports are ok, no idea about 4.0).
Hopefully someone more familiar with the compiler suites would be able to fix
the system compilers.
Andy
> On
I'm not sure this should be a ports PR, maybe it should go to the compiler
suite?
Andy
--
Andy Fawcett | [EMAIL PROTECTED]
| [EMAIL PROTECTED]
"In an open world without walls and fences, | [EMAIL P
).
At least with a vanilla install of 5.3, I had no problem going directly
to 6.0.
This was an extremely basic install, and I only did it because I lost my
6.0-R cd :)
A.
--
Andy Fawcett | [EMAIL PROTECTED]
Argh! Correction below.
On Thursday 17 November 2005 00:02, Andy Fawcett wrote:
> On Wednesday 16 November 2005 23:26, Dejan Lesjak wrote:
> > On Wednesday 16 of November 2005 04:26, James Long wrote:
> > > After hours of head-banging over the past couple of days,
> > &g
es into the same place.
Please remove them first with pkg_delete(1).
*** Error code 1
Again, please note that xterm conflicts with the version of the clients
it is supposed to work with. This is repeatable on 2 systems I have
tried so far, 5.4-RELEASE/i386 and 6.0-STABLE/amd64.
A.
problems.
On the other hand, 4.x (I think it was 4.9, but I really cannot remember
for sure) crapped all over one box so hard I refuse to ever use it
again.
A.
--
Andy Fawcett | [EMAIL PROTECTED]
| [EMAIL PRO
cted. The system is 5.4-PRERELEASE/amd64]
I have 5.4-PRE on my work amd64 box (kernel/world built a few days ago) and
I'm running KDE from ports in it without apparent problems.
A.
--
Andy Fawcett | [EMAIL PROTECTED]
e sure you rebuild devel/qmake before building qt
This is because it is the config defined by qmake
(actually /usr/local/share/qt/mkspecs/freebsd-g++/qmake.conf) that defines
what thread library to use in building qt.
A.
--
Andy Fawcett
13 matches
Mail list logo
