Steven M. Bellovin | 1 Apr 05:41 2008

problems building kdenetwork

I'm having trouble trying to build kdenetwork:

/usr/pkgsrc/net/kdenetwork3/work/.buildlink/include/X11/Xmd.h:152: error: confli
cting declaration 'typedef long unsigned int CARD32'
../../krfb/libvncserver/rfb.h:43: error: 'CARD32' has a previous declaration as 
'typedef unsigned int CARD32'
rfbcontroller.cc: In member function 'virtual void KNotifyEvent::exec()':

This is on a i386-4.x machine running xorg.  I refreshed pkgsrc from HEAD,
used lintpkgsrc to find out what packages were out of date, and pkgdepgraph
to generate a rebuild script.  Everything but kde3 rebuilt without
any trouble.

/usr/pkg/include/X11/Xmd.h comes from xproto, which seems to be
a dependency of kdenetwork3, though I don't see just where it's
being requested.

		--Steve Bellovin, http://www.cs.columbia.edu/~smb

OBATA Akio | 1 Apr 06:03 2008
Picon

Re: problems building kdenetwork

JFYI:Same problem is reported as PR#38227.

Chavdar Ivanov | 1 Apr 10:08 2008
Picon

Re: problems building kdenetwork

On 01/04/2008, Steven M. Bellovin <smb <at> cs.columbia.edu> wrote:
> I'm having trouble trying to build kdenetwork:
>
>  /usr/pkgsrc/net/kdenetwork3/work/.buildlink/include/X11/Xmd.h:152: error: confli
>  cting declaration 'typedef long unsigned int CARD32'
>  ../../krfb/libvncserver/rfb.h:43: error: 'CARD32' has a previous declaration as
>  'typedef unsigned int CARD32'
>  rfbcontroller.cc: In member function 'virtual void KNotifyEvent::exec()':
>

As part of a two-week-long pkg_rolling-replace I rebuild kde a few
days ago; I was just about to hit the Return key with the above when I
remembered I had the same problem; I "solved" it on the spot by
duplicating the definition in Xmd.h.

>  This is on a i386-4.x machine running xorg.  I refreshed pkgsrc from HEAD,
>  used lintpkgsrc to find out what packages were out of date, and pkgdepgraph
>  to generate a rebuild script.  Everything but kde3 rebuilt without
>  any trouble.
>
>  /usr/pkg/include/X11/Xmd.h comes from xproto, which seems to be
>  a dependency of kdenetwork3, though I don't see just where it's
>  being requested.
>
>                 --Steve Bellovin, http://www.cs.columbia.edu/~smb
>

--

-- 
----------------------------------------------------------------
/dev/random says:
(Continue reading)

Larson, Timothy E. | 2 Apr 22:25 2008

confusion regarding .include vs DEPENDS

Greetings,

When reading chapter 10 of the pkgsrc doco, I am confused about including
the buildlink3 file vs having DEPENDS in the makefile.  The doco seems to
indicate a preference to using buildlink3 files, but how do you specify a
minimum version for the dependency that way?  I don't want to force
dependencies to be updated when it's not necessary.

Thanks,
Tim

--

-- 
Tim Larson        AMT2 Unix Systems Administrator
    InterCall, a division of West Corporation

               Eschew obfuscation!
Attachment (smime.p7s): application/x-pkcs7-signature, 12 KiB
Juan RP | 2 Apr 22:31 2008
Picon

Re: confusion regarding .include vs DEPENDS

On Wed, 2 Apr 2008 15:25:48 -0500
"Larson, Timothy E." <TELarson <at> west.com> wrote:

> Greetings,
> 
> When reading chapter 10 of the pkgsrc doco, I am confused about including
> the buildlink3 file vs having DEPENDS in the makefile.  The doco seems to
> indicate a preference to using buildlink3 files, but how do you specify a
> minimum version for the dependency that way?  I don't want to force
> dependencies to be updated when it's not necessary.

The buildlink3 file has some lines to specify API and ABI minimum
versions, but if you want to specify another minimum version in a
package, you can use something like:

BUILDLINK_API_DEPENDS.foo+= foo>=2.10

--

-- 
Juan Romero Pardines - xtraeme at gmail|netbsd dot org
	The NetBSD Project

Make your own NetBSD/x86 Live CD
http://www.netbsd.org/~xtraeme/mklivecd/

Johnny C. Lam | 2 Apr 22:53 2008

Re: confusion regarding .include vs DEPENDS

Larson, Timothy E. wrote:
> When reading chapter 10 of the pkgsrc doco, I am confused about including
> the buildlink3 file vs having DEPENDS in the makefile.  The doco seems to
> indicate a preference to using buildlink3 files, but how do you specify a
> minimum version for the dependency that way?  I don't want to force
> dependencies to be updated when it's not necessary.

You want to include a dependency's buildlink3.mk files *only* if the 
package links against libraries provided by the dependency.  Otherwise, 
use DEPENDS.

See Juan's reply for how to set the version for a buildlink3.mk file.

	Cheers,

	-- Johnny C. Lam

Larson, Timothy E. | 2 Apr 23:35 2008

RE: confusion regarding .include vs DEPENDS

Johnny C. Lam <mailto:jlam <at> pkgsrc.org> wrote:
> You want to include a dependency's buildlink3.mk files *only* if the
> package links against libraries provided by the dependency. 
> Otherwise, use DEPENDS.  
> 
> See Juan's reply for how to set the version for a buildlink3.mk file.

So, when is it important to specify a version (with either method) and when
is it not?  I'm not completely sure I understand the distinction between
them (better explanation in the doco would be great), and also am still
unsure if this mistake is what caused the unwanted updating.

Tim
--

-- 
Tim Larson        AMT2 Unix Systems Administrator
    InterCall, a division of West Corporation

               Eschew obfuscation!
Attachment (smime.p7s): application/x-pkcs7-signature, 12 KiB
Alan Barrett | 3 Apr 16:35 2008

Re: confusion regarding .include vs DEPENDS

On Wed, 02 Apr 2008, Juan RP wrote:
> The buildlink3 file has some lines to specify API and ABI minimum
> versions, but if you want to specify another minimum version in a
> package, you can use something like:
> 
> BUILDLINK_API_DEPENDS.foo+= foo>=2.10

That works if you want to say "the version in the buildlink3.mk file
is too small; use this instead".  It doesn't work if you want to say
"the version in the buildlink3 file is unnecessarily large; use this
instead".

It's often the case that pkg X depends on pkg Y, and in reality X could
work with a very old version of Y, but the buildlink3.mk files say that
*anything* that depends on Y has to use a recent version of Y.

My understanding is that the versions in the buildlink3.mk files are
the way they are because of concerns about what happens to people who
install binary packages that they downloaded from somewhere.  However,
if you use pkgsrc the way I do:

	update pkgsrc;
	build and install some stuff;
	wait some days/weeks/months;
	update pkgsrc;
	build and install more stuff;

then you will often have to perform unnecessary updates.

--apb (Alan Barrett)
(Continue reading)

Joerg Sonnenberger | 3 Apr 17:52 2008
Picon

Re: confusion regarding .include vs DEPENDS

On Thu, Apr 03, 2008 at 04:35:13PM +0200, Alan Barrett wrote:
> My understanding is that the versions in the buildlink3.mk files are
> the way they are because of concerns about what happens to people who
> install binary packages that they downloaded from somewhere.

It is also one of the few ways to preserve sanity. We already have
issues with partial updates, allowing even more of that doesn't help.

Joerg

Matthias Scheler | 3 Apr 23:38 2008
Picon

Re: rtorrent & xmlrpc


On 30 Mar 2008, at 16:22, Gergo Szakal wrote:
> Has anyone considered building rtorrent with xmlrpc support or at  
> least
> adding an option for it?

Yes, I've tried. The problem is that it requires a newer version of  
"xmlrpc-c"
than the one which is currently in "pkgsrc". I tried updating the  
package
and failed because "xmlrpc-c"'s build system is a mess. It is so broken
that I haven't even managed to get the current version to build under
Mac OS X, see PR pkg/38071.

If somebody sorts out the "xmlrpc-c" package I will add "xmlrpc"  
support to
the "rtorrent" package.

	Kind regards

--

-- 
Matthias Scheler                           http://zhadum.org.uk/


Gmane