Re: [kde-freebsd] KDE4 libssl conflicts

2008-08-12 Thread Andy Fawcett
On Tuesday 12 August 2008 12:43:37 Warren Liddell wrote:
> > You've got a mix of older and newer library versions, which makes
> > me think that you are trying to do a partial upgrade of your ports
> > after upgrading the FreeBSD base system to a newer version.  You
> > really need to rebuild all ports when doing that, or else you'll
> > run into issues.
> >
> > However, the specific problem you mention should have been resolved
> > by this change here:
> >
> >http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/126410
> >
> > ...so please double-check that your ports tree has been updated to
> > get this fix.
> >
> > Regards,
>
> I did recently upgrade my base system from 6.3-STABLE to 7.0-STABLE,
> however, i just re-ran a csup and ran portupgrade an tried a re-build
> of KDE4 with the same error output.

You need to clean out the 6.3 versions of various libs/binaries.

See the delete-old and delete-old-libs targets on /usr/src/Makefile


-- 
Andy Fawcett | [EMAIL PROTECTED]
 | [EMAIL PROTECTED]
"In an open world without walls and fences,  | [EMAIL PROTECTED]
  we wouldn't need Windows and Gates."  -- anon  | [EMAIL PROTECTED]

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: X fails after upgrade to xorg-7.2; FreeBSD AMD64 w/ Radeon 9600 Pro

2007-06-19 Thread Andy Fawcett
On Wednesday 20 June 2007 05:30:19 Mark Kirkwood wrote:
> Byron Campbell wrote:
> > Xorg -configure now reports:
> >
> > (++) Using config file: "/root/xorg.conf.new"
> > (WW) RADEON: No matching Device section for instance (BusID
> > PCI:1:0:1) found
> > (**) RADEON(0): RADEONPreInit
> >
> > Manually doing the config by running xorgcfg -textmode gives a
> > different BusID in the xorg.conf file --> BusID PCI:1:0:0
>
> FWIW on the PCI busids:
>
> PCI:1:0:0 is the primary port of your card, PCI:1:0:1 is the secondary -
> the warning is just because 'Xorg -configure' does not create a setup
> for dual monitors.
>
> For the rest, well done on getting rid of the undefined symbols... shame
> it still does not work. Good luck for the reinstall!

One thing that *might* make a difference could be the drm stuff. I have it 
built into my kernel, you might be (auto)loading it as modules.

Relevant lines from my kernel config:

device  radeondrm
device  drm

Could be worth trying, if you don't already have it.

-- 
Andy Fawcett | [EMAIL PROTECTED]
 | [EMAIL PROTECTED]
"In an open world without walls and fences,  | [EMAIL PROTECTED]
  we wouldn't need Windows and Gates."  -- anon  | [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: X fails after upgrade to xorg-7.2; FreeBSD AMD64 w/ Radeon 9600 Pro

2007-06-19 Thread Andy Fawcett
On Tuesday 19 June 2007 02:52:55 Mark Kirkwood wrote:
> Byron Campbell wrote:
> > On Sunday 17 June 2007 10:23:19 pm Mark Kirkwood wrote:
> >> AFAICS the symbol is defined in:
> >>
> >> /usr/local/lib/xorg/modules/drivers/ati_drv.so
> >>
> >> e.g:
> >>
> >> $ nm ati_drv.so|grep ATIMemoryTypeNames_88800CX
> >> b5c0 D ATIMemoryTypeNames_88800CX
> >>
> >> What does it show on your system (I'm wondering if your ati
> >> drivers have not been upgraded properly).
> >
> > Ah, good point. The output here is:
> >
> > 00e940 D ATIMemoryTypeNames_88800CX
>
> Well - seems to be defined there hmmm. not sure why you are
> getting 'undefined symbol' in atimisc_drv.so in that case. I am
> wondering if the problem is tied up with amd64 specifically -
> hopefully someone else will have some ideas :-).
>
> In the meantime you could hack your xorg.conf to use 'vesa' driver
> and see if you can actually startup X - try adding modeline settings
> in there for your monitor if you still get 'out of range' (tho I must
> say I've *never* needed to put them in with Xorg...).
>
> Also worth trying might be borrowing a DVI cable (assuming your
> monitor has a DVI input) and seeing if X works with it connected
> instead of the VGA one.

I'm running the same board (Neo2-F) and card (9600) versions on amd64 at 
home, but with a CRT. When I get home this evening I will mail my 
xorg.conf to Byron directly to see if it helps.

Andy


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: [kde-freebsd] KDE 3.2 + startx errors (dcopserver)

2004-02-15 Thread Andy Fawcett
On Sunday 15 February 2004 11:19, Bryan Cassidy wrote:
> I am running FreeBSD 4.9 and have just installed KDE 3.2 from the
> ports without any errors. I know for a fact I have X configured so it
> couldnt be that. I added exec startkde to my .xinitrc file and ran
> 'startx' and I get the following
>
> There was an error setting up inter-process communications for KDE.
> The message returned by the system was:
>
> could not read network connection list
> /home/usr/.DCOPserver_bsdjunky.homeunix.org__0
>
> Please check that the dcopserver program is running.
>
> Second error I get is
>
> Will not save configuration
> Configuration file "/home/usr/.kde/share/config/kwinrc" not writable
>
> Configuration file "/home/usr/.kde/share/config/kdeglobals" not
> writable
>
> Please contact your system admin.
>
>  I have tried running 'dcopserver' as usr and as root with no
> success. Any help would be appreciated.

As root:
chown -R youruser:yourgroup /home/usr/.kde
should fix it.

If not, you need to check the permissions of those files, and ensure 
they are:

-rw--- youruser yourgroup

A.

-- 
Andy Fawcett | [EMAIL PROTECTED]
 | [EMAIL PROTECTED]
"In an open world without walls and fences,  | [EMAIL PROTECTED]
  we wouldn't need Windows and Gates."  -- anon  | [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: [kde-freebsd]

2003-08-20 Thread Andy Fawcett
On Thursday 21 August 2003 05:01, Rob Lahaye wrote:

> > Why didn't you use the port? ( /usr/ports/print/lyx ). It usually
> > takes care of these problems.
>
> No it doesn't; the lyx port has the same problem!
> I compiled LyX 1.3.2 from ports as "make WITH_QT=yes", to build
> LyX/Qt.

FWIW, the lyx port (with Qt enabled) is working fine for me, on 5.1R and 
up to date KDE/Qt installed.

Of course, this may be a 4.x issue, and I don't have a 4.x system to 
test on.

Andy

-- 
Andy Fawcett | [EMAIL PROTECTED]
 | [EMAIL PROTECTED]
"In an open world without walls and fences,  | [EMAIL PROTECTED]
  we wouldn't need Windows and Gates."  -- anon  | [EMAIL PROTECTED]

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: [kde-freebsd] can't compile kde3.1.2

2003-07-23 Thread Andy Fawcett
On Wednesday 23 July 2003 05:48, Antoine Solomon wrote:
> I am having problems building and installing kde3.1.2 from the ports
> collection Here is the error that I get
>
> checking for libXext... no
> ===>  Script "configure" failed unexpectedly.
>   Please report the problem to [EMAIL PROTECTED] [maintainer] and
> attach the "/usr/ports/x11/kdelibs3/work/kdelibs-3.1.2/config.log"
> including the output of the failure of your make command. Also, it
> might be a good idea to provide an overview of all packages installed
> on your system (e.g. an `ls /var/db/pkg`).
> *** Error code 1
>
> Stop in /usr/ports/x11/kdelibs3.

Okay, as Kris pointed out, there's not enough info to go on here...

However, remove the existing arts package, as it's very outdated, and 
could potentially cause a build problem.

Do that, try another kdelibs build, and if you still run into the same 
problem please follow the instructions that the build system gives you.

A.

-- 
Andy Fawcett | [EMAIL PROTECTED]
 | [EMAIL PROTECTED]
"In an open world without walls and fences,  | [EMAIL PROTECTED]
  we wouldn't need Windows and Gates."  -- anon  | [EMAIL PROTECTED]

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"