grant beattie | 1 Jan 08:58 2004
Picon

Re: 2 questions because of FreeBSD pkgsrc trouble

On Wed, Dec 31, 2003 at 05:29:16PM +0100, Michal Pasternak wrote:

> On FreeBSD:
> 
> 1) www/mozilla builds and instals okay, but it doesnt include Personal 
>    Security Manager -- eg. no https:// protocol in it. 
>    
>    Does a generic build of www/mozilla on NetBSD include https:// ?

yes, it does.

I think this problem is the result of mozilla being unable to find
libssl3.so, or libssl3.so unable to find it's required shared libs.

check out mozilla/patches/patch-ab and patch-bo, which might need
tweaking for FreeBSD (iirc, the NetBSD runtime linker passes the
rpath down to shared libraries, where FreeBSD's doesn't).

grant.

Berndt Josef Wulf | 1 Jan 12:49 2004
Picon

kdevelop-2.1.5 for KDE3


G'day,

I've noticed a few oddities as of late with kdevelop and seek confirmation 
from other kdevelop users in the NetBSD community before commencing a hunt 
for a fix. 

1.) KDevelop will hang when enabling automatic code completion and argument 
hints soon after expire of the preselected delay time.

2.) KDevelop refuses to find the kdelibs documentation. Updating and 
rebuilding the documentation tree as suggested by the error message emitted 
by the setup dialog doesn't remedy the problem.

3.) Internal debugger doesn't work reliably disregarding break points at times

4.) Clicking on compiler error message will not jump to the line the source 
code.

These functions worked with previous versions of KDE2.x and perhaps early 
versions of KDE3.x, which makes me suspect that KDevelop-2.1.5 may nolonger 
compatible and work with later versions of KDE3.x.

Any constructive comments are most welcome and appreciated.

cheerio Berndt
--

-- 
Name	: Berndt Josef Wulf		| +++ With BSD on Packet Radio +++
E-Mail	: wulf at ping dot net dot au	|    tfkiss, tnt, dpbox, wampes
ICQ	: 18196098			|  VK5ABN, Nairne, South Australia 
(Continue reading)

Gavan Fantom | 1 Jan 13:39 2004

Re: USE_SASL is too general?

On Wed, 31 Dec 2003, Adam C. Migus wrote:

> You can complain about poorly designed software all you like.  If the
> pkg_ utilities implemented cycle detection in the least and correction
> in the ideal this problem would be solved.

There is code to detect cycles in bsd.pkg.mk.

--

-- 
Gillette - the best a man can forget

Greg Troxel | 1 Jan 18:19 2004
Picon

Re: Ruminations on pkg_chk...

  >1. In FreeBSD ports, one can install multiple versions of a package.
  >   When starting to use portupgrade, we usually find that there are
  >   multiple versions of a lot of libraries, with many files claimed by
  >   multiple packages.
  >
  How?  I've used FreeBSD ports for years and have never seen this...
  Care to elaborate?  The multiple versions of libraries are usually
  tucked away in lib/compat after an upgrade to insure packages continue
  to work after upgrades, as you point out below.

I'm not talking about lib/compat, but libraries provided by ports.
With pkgsrc, a pkg conflicts with older versions of itself, so doing a
'make install' fails if an older version is installed.  With ports, at
least in the past, the second copy would be installed and registered.

This can happen by doing a 'make package' of port A, which depends on
libfoo.  Version 1.0 of libfoo gets installed.  Wait 3 months and cvs
update.  Do 'make package' of port B, which also requires libfoo, but
now the libfoo Makefile says 1.1 is current and needed, so libfoo 1.1
gets installed.  I have seen this multiple times, and when starting to
use portupgrade many such situations needed to be cleaned up.

To check that this behavior still occurs, I went to a FreeBSD box
running 4.9-RC with ports from November 5.  glib-1.2.8 was installed.
I went to devel/glib12 and did 'make package'.  Now glib-1.2.8 and
glib-1.2.10_10 are both installed.  I deleted glib-1.2.8, which
complained about files not matching the MD5 checksum.  I delete
glib-1.2.10_10, which complained about
/usr/local/share/aclocal/glib.m4 not exising (probably because it was
deleted by 1.2.8).
(Continue reading)

Brian A. Seklecki | 1 Jan 20:23 2004

Re: 2 questions because of FreeBSD pkgsrc trouble

On Wed, 2003-12-31 at 16:29, Michal Pasternak wrote:
> On FreeBSD:
> 
> 1) www/mozilla builds and instals okay, but it doesnt i
> nclude Personal 
>    Security Manager -- eg. no https:// protocol in it. 
>    
>    Does a generic build of www/mozilla on NetBSD include https:// ?

Yes, the Makefile includes CONFIGURED_ARGS+= --enable-crypto

Check your
pkgsrc/www/mozilla/work/mozilla-1.5.1/config.{cache,log,status}

Most i386 users are better off using alternatives now, anyway.

> 
> 2) x11/qt3-libs -- and kdelibs3, which depend on it -- don't do antialiasing.
>    (gtk2 has it). I tried many things -- no success, no antialiased fonts

For anti-aliased fonts see:

http://www.netbsd.org/Documentation/x/#anti_aliased

>    in my beloved KDE. I think it is a building problem.
>    
>    On FreeBSD libqt-mt.so is linked with: (see below). Should it do
>    antialiasing with such set of libraries? If it doesn't -- which library
>    qt3 depends on should I check?
>    
(Continue reading)

Juan RP | 1 Jan 20:29 2004

Re: 2 questions because of FreeBSD pkgsrc trouble

On Thu, 01 Jan 2004 19:23:59 +0000
"Brian A. Seklecki" <lavalamp <at> spiritual-machines.org> wrote:

> > 2) x11/qt3-libs -- and kdelibs3, which depend on it -- don't do
> > antialiasing.
> >    (gtk2 has it). I tried many things -- no success, no antialiased fonts
> 
> For anti-aliased fonts see:
> 
> http://www.netbsd.org/Documentation/x/#anti_aliased

I don't think his problem was about configuration files or XFree86, I'm having
the same problem than Michal Pasternak in NetBSD -current, and the problem
was configure script doesn't detect the header files of freetype correctly...

--

-- 
Juan RP <juan AT xtraeme DOT unixbsd DOT org>

Michal Pasternak | 1 Jan 19:36 2004
Picon

Re: 2 questions because of FreeBSD pkgsrc trouble

Brian A. Seklecki [Thu, Jan 01, 2004 at 07:23:59PM +0000]:
> >    Does a generic build of www/mozilla on NetBSD include https:// ?
> 
> Yes, the Makefile includes CONFIGURED_ARGS+= --enable-crypto

I am not asking about the Makefile content -- I would like to know, if
_compiled_ mozilla package from pkgsrc on NetBSD can use https . That's
quite different thing :)

> Check your
> pkgsrc/www/mozilla/work/mozilla-1.5.1/config.{cache,log,status}

Nothing strange/important there. I even tried including openssl's buidlink2,
didn't help.

> > 2) x11/qt3-libs -- and kdelibs3, which depend on it -- don't do antialiasing.
> >    (gtk2 has it). I tried many things -- no success, no antialiased fonts
> 
> For anti-aliased fonts see:
> 
> http://www.netbsd.org/Documentation/x/#anti_aliased

That was already included by "I tried many things" ;]

--

-- 
Michal Pasternak :: http://pasternak.w.lub.pl :: http://winsrc.sf.net

Brian A. Seklecki | 1 Jan 20:54 2004

Re: 2 questions because of FreeBSD pkgsrc trouble

On Thu, 2004-01-01 at 19:29, Juan RP wrote:
> On Thu, 01 Jan 2004 19:23:59 +0000
> "Brian A. Seklecki" <lavalamp <at> spiritual-machines.org> wrote:
> 
> > > 2) x11/qt3-libs -- and kdelibs3, which depend on it -- don't do
> > > antialiasing.
> > >    (gtk2 has it). I tried many things -- no success, no antialiased fonts

Right, if gtk2/glib2 functions, then via process of elimination you can
rule out your X11 / Fonts as the problem. 

> > 
> > For anti-aliased fonts see:
> > 
> > http://www.netbsd.org/Documentation/x/#anti_aliased
> 
> I don't think his problem was about configuration files or XFree86, I'm having
> the same problem than Michal Pasternak in NetBSD -current, and the problem
> was configure script doesn't detect the header files of freetype correctly...

That reminds me of KDE3's gnu autconfigure scripts not detecting our
Xinerama properly.

-lava

Adam C. Migus | 1 Jan 21:11 2004

Re: Ruminations on pkg_chk...

Greg Troxel wrote:

>  >1. In FreeBSD ports, one can install multiple versions of a package.
>  >   When starting to use portupgrade, we usually find that there are
>  >   multiple versions of a lot of libraries, with many files claimed by
>  >   multiple packages.
>  >
>  How?  I've used FreeBSD ports for years and have never seen this...
>  Care to elaborate?  The multiple versions of libraries are usually
>  tucked away in lib/compat after an upgrade to insure packages continue
>  to work after upgrades, as you point out below.
>
>I'm not talking about lib/compat, but libraries provided by ports.
>With pkgsrc, a pkg conflicts with older versions of itself, so doing a
>'make install' fails if an older version is installed.  With ports, at
>least in the past, the second copy would be installed and registered.
>
>This can happen by doing a 'make package' of port A, which depends on
>libfoo.  Version 1.0 of libfoo gets installed.  Wait 3 months and cvs
>update.  Do 'make package' of port B, which also requires libfoo, but
>now the libfoo Makefile says 1.1 is current and needed, so libfoo 1.1
>gets installed.  I have seen this multiple times, and when starting to
>use portupgrade many such situations needed to be cleaned up.
>
>To check that this behavior still occurs, I went to a FreeBSD box
>running 4.9-RC with ports from November 5.  glib-1.2.8 was installed.
>I went to devel/glib12 and did 'make package'.  Now glib-1.2.8 and
>glib-1.2.10_10 are both installed.  I deleted glib-1.2.8, which
>complained about files not matching the MD5 checksum.  I delete
>glib-1.2.10_10, which complained about
(Continue reading)

Mirko Thiesen | 1 Jan 23:20 2004
Picon

Re: VTunD not doing anything

On Mon, 29 Dec 2003, Mirko Thiesen wrote:

> Now everything works - except VTunD (vtun-2.6nb3). It did compile and
> install sucessfully, however, it simply does not do anything. The tun
> device interfaces don't come up automatically after rebooting (after being
> created at some stage of the boot process). If I "ifconfig tunX up" them
> manually, nothing happens.

As Christoph Badura and Michael van Elst - thanks to both of them! -
pointed out, the solution was the recently changed authentication scheme
of VTunD. The system on the other side is running FreeBSD, and updating
VTunD on that system using the FreeBSD ports collection did not help.
Obviously, VTunD 2.6 is not the same as VTunD 2.6 -- 2.6 from PkgSrc
incorporates the changes from OpenFortress.NL and should be some kind of
pre-3.0 whereas 2.6 from FreeBSD ports really is 2.6.

Applying the patch from the distfiles directory on the FreeBSD machine
helped and made the tunnel working again.

Thanks again to Michael van Elst and Christoph Badura!

Bye, K&K,
T-Zee

PS: A Happy New Year, by the way!
--

-- 
thiesi <at> NetWork23.Sytes.NET ---- NetBSD: Power to the people!
Tel.: ++49-(0)171-416 05 09 -- Fax: ++49-(0)171-134 16 05 09
Mirko Thiesen, P.O. Box 26 03 54, D-13413 Berlin, W. Germany
             "We're with you all the way, mostly"
(Continue reading)


Gmane