Starnge error

2007-12-22 Thread Jack Raats
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

While running portugrade -Na I get the following error:

  If there are vulnerabilities in these programs there may be a security
  risk to the system. FreeBSD makes no guarantee about the security of
  ports included in the Ports Collection. Please type 'make deinstall'
  to deinstall the port if this is a concern.
===>  Cleaning for compat5x-i386-5.4.0.8_9
- --->  Cleaning out obsolete shared libraries
[Updating the pkgdb  in /var/db/pkg ... - 362 packages found 
(-0 +1) . done]
Operation not permitted - /usr/local/lib/compat/pkg/libc.so.5
Operation not permitted - /usr/local/lib/compat/pkg/libc_r.so.5
Operation not permitted - /usr/local/lib/compat/pkg/libcrypt.so.2
Operation not permitted - /usr/local/lib/compat/pkg/libpthread.so.1
Operation not permitted - /usr/local/lib/compat/pkg/libthr.so.1
- --->  Upgrading 'usermin-1.310' to 'usermin-1.320' (sysutils/usermin)

What is wrong?

Jack
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32) - GPGrelay v0.959

iD8DBQFHbgr9Ph5RwW/NzC4RAh17AJwI//R7zWs3oUlMDp1SMoCMIbwYLQCgwBja
MWuaGEbeR9+wtofM+Xx4QOU=
=3nzP
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: multimedia/mplayer doesn't build (default options)

2007-12-22 Thread Tim Kellers

FreeBSD WickerBill wrote:



On Dec 22, 2007 1:37 AM, Dominic Fandrey <[EMAIL PROTECTED] 
> wrote:


I've got a solution now. After the build failed just go to your
WRKDIR and run
gmake. The build will finish just fine. I've got no idea why it
doesn't work
through the ports.
___
freebsd-ports@freebsd.org 
mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
"[EMAIL PROTECTED]
"


This worked for me

cd /usr/ports/multimedia/mplayer/work/MPlayer-1.0rc2/
gmake
cd ../..
make install

Thanks for the fix.

I don't think the make.conf file is the problem here's mine

cat /etc/make.conf
USE_QT=yes
WITH_HAL=yes
WITH_MTP=yes
X11BASE=/usr/local
$LOCALBASE=/usr/local
# added by use.perl 2007-11-07 06:52:01
PERL_VER=5.8.8
PERL_VERSION=5.8.8





--
--I'm not 'renting' my OS-- 

This worked for me (finally), too.  My /etc/make.conf:

# added by use.perl 2007-11-17 18:10:05
PERL_VER=5.8.8
PERL_VERSION=5.8.8



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


Re: multimedia/mplayer doesn't build (default options)

2007-12-22 Thread FreeBSD WickerBill
On Dec 22, 2007 1:37 AM, Dominic Fandrey <[EMAIL PROTECTED]> wrote:

> I've got a solution now. After the build failed just go to your WRKDIR and
> run
> gmake. The build will finish just fine. I've got no idea why it doesn't
> work
> through the ports.
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>

This worked for me

cd /usr/ports/multimedia/mplayer/work/MPlayer-1.0rc2/
gmake
cd ../..
make install

Thanks for the fix.

I don't think the make.conf file is the problem here's mine

cat /etc/make.conf
USE_QT=yes
WITH_HAL=yes
WITH_MTP=yes
X11BASE=/usr/local
$LOCALBASE=/usr/local
# added by use.perl 2007-11-07 06:52:01
PERL_VER=5.8.8
PERL_VERSION=5.8.8





-- 
--I'm not 'renting' my OS--
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: multimedia/mplayer doesn't build (default options)

2007-12-22 Thread Tim Kellers

Tim Kellers wrote:

Thomas Zander wrote:

On 22/12/2007, Dominic Fandrey <[EMAIL PROTECTED]> wrote:
 
I've got a solution now. After the build failed just go to your 
WRKDIR and run
gmake. The build will finish just fine. I've got no idea why it 
doesn't work

through the ports.



This is indeed strange. I still couldn't figure out how to trigger
this problem. However I have done "pkg_delete -a" on a 7.0 box and
installed all ports from scratch, including mplayer with the default
options. No problem whatsoever. It would really be helpful to know
what causes this issue.

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


  
I've been hacking around inside this problem during my downtime at 
work for days, now.  I'm trying the "gmake solution" now, but I've 
broken so many things (fontconfig, gtk1.x, gtk2.x, etc) trying to 
figure this out that I have to unbreak everything before I can see if 
using gmake in the WRKDIR fixes it for me, too.  I'll post updates as 
things become less broken.


Of all the (unsuccessful) things I was trying, running gmake wasn't 
even on my radar screen.  What made you think to try that??


Tim


Ok, things are now getting less broken for me...

By chance is anyone having this problem on a box (like mine) that was 
upgraded from 6.2 to 7.0?  The gmake solution failed for me when it 
tried to build xmms along with mplayer, with a failure in a compat lib 
that looked like something that was a holdover from my 6.2 upgrade.  I 
thought I had  run portupgrade -fa when I updated this  box (a Gateway 
laptop) when RELENG-7 was first tagged (or branched) but, obviously, I 
missed something.


More building continues...

Tim


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


Re: multimedia/mplayer doesn't build (default options)

2007-12-22 Thread Tim Kellers

Thomas Zander wrote:

On 22/12/2007, Dominic Fandrey <[EMAIL PROTECTED]> wrote:
  

I've got a solution now. After the build failed just go to your WRKDIR and run
gmake. The build will finish just fine. I've got no idea why it doesn't work
through the ports.



This is indeed strange. I still couldn't figure out how to trigger
this problem. However I have done "pkg_delete -a" on a 7.0 box and
installed all ports from scratch, including mplayer with the default
options. No problem whatsoever. It would really be helpful to know
what causes this issue.

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


  
I've been hacking around inside this problem during my downtime at work 
for days, now.  I'm trying the "gmake solution" now, but I've broken so 
many things (fontconfig, gtk1.x, gtk2.x, etc) trying to figure this out 
that I have to unbreak everything before I can see if using gmake in the 
WRKDIR fixes it for me, too.  I'll post updates as things become less 
broken.


Of all the (unsuccessful) things I was trying, running gmake wasn't even 
on my radar screen.  What made you think to try that??


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


Updating 'mail/freepops' port

2007-12-22 Thread Gerard
Evidently, the '/mail/freepops/' port does not have a maintainer. If I
knew more about it, I would attempt to do it myself; however, that
might well lead to a disaster.

Anyway, is there any chance that the port can be updated. The port
version is "0.0.99" and the official version is "0.2.6". Unfortunately,
many new modules cannot be used with this older version. In particular,
both Yahoo and Gmail are no longer accessible.

Thanks!

-- 
Gerard Seibert
[EMAIL PROTECTED]


signature.asc
Description: PGP signature


Re: multimedia/mplayer doesn't build (default options)

2007-12-22 Thread Thomas Zander
On 22/12/2007, Dominic Fandrey <[EMAIL PROTECTED]> wrote:
> I've got a solution now. After the build failed just go to your WRKDIR and run
> gmake. The build will finish just fine. I've got no idea why it doesn't work
> through the ports.

This is indeed strange. I still couldn't figure out how to trigger
this problem. However I have done "pkg_delete -a" on a 7.0 box and
installed all ports from scratch, including mplayer with the default
options. No problem whatsoever. It would really be helpful to know
what causes this issue.

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


Re: Opinion on cross-port OPTIONS CONFLICTS

2007-12-22 Thread Josh Paetzel
On Saturday 22 December 2007 03:32:56 pm Edwin Groothuis wrote:
> On Sat, Dec 22, 2007 at 11:50:53AM -0600, Josh Paetzel wrote:
> > On Friday 21 December 2007 10:33:44 pm Edwin Groothuis wrote:
> > > On Fri, Dec 21, 2007 at 09:05:18PM -0600, Josh Paetzel wrote:
> > > > > > It also doesn't work if someone runs make rmconfig, or make
> > > > > > config again and changes things after the port is installed.
> > > > > >
> > > > > > It probably doesn't work if a package was used to install either.
> > > > >
> > > > > Create a slave port audio/arts-withoutnas and let it depends on
> > > > > that one.
> > > >
> > > > I don't think that's a scalable solution.  It would create an
> > > > explosion of ports in the already taxed tree, as well as confusion as
> > > > to which port to install among the users.
> > >
> > > And what is your solution for this problem?
> >
> > My initial solution as I posted is to register the OPTIONs used to build
> > a port in /var/db/pkg
>
> And how is that going to resolve the issue earlier suggestions
> suffered from with regarding to ports which are not installed yet
> but which will be installed as a dependency of this port?
>
> Edwin

Well, my idea was you'd be able to CONFLICT based on OPTIONs set in another 
port, so at least you could die with a helpful error message if they weren't 
set properly.

-- 
Thanks,

Josh Paetzel

PGP: 8A48 EF36 5E9F 4EDA 5A8C 11B4 26F9 01F1 27AF AECB


signature.asc
Description: This is a digitally signed message part.


Re: Opinion on cross-port OPTIONS CONFLICTS

2007-12-22 Thread Edwin Groothuis
On Sat, Dec 22, 2007 at 11:50:53AM -0600, Josh Paetzel wrote:
> On Friday 21 December 2007 10:33:44 pm Edwin Groothuis wrote:
> > On Fri, Dec 21, 2007 at 09:05:18PM -0600, Josh Paetzel wrote:
> > > > > It also doesn't work if someone runs make rmconfig, or make config
> > > > > again and changes things after the port is installed.
> > > > >
> > > > > It probably doesn't work if a package was used to install either.
> > > >
> > > > Create a slave port audio/arts-withoutnas and let it depends on
> > > > that one.
> > >
> > > I don't think that's a scalable solution.  It would create an explosion
> > > of ports in the already taxed tree, as well as confusion as to which port
> > > to install among the users.
> >
> > And what is your solution for this problem?
> 
> My initial solution as I posted is to register the OPTIONs used to build a 
> port in /var/db/pkg

And how is that going to resolve the issue earlier suggestions
suffered from with regarding to ports which are not installed yet
but which will be installed as a dependency of this port?

Edwin

-- 
Edwin Groothuis  |Personal website: http://www.mavetju.org
[EMAIL PROTECTED]|  Weblog: http://www.mavetju.org/weblog/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: misc/compat5x package installs with weird messages

2007-12-22 Thread Jan Henrik Sylvester

Norikatsu Shigemura wrote:

On Fri, 14 Dec 2007 18:32:22 -0600
Stephen Montgomery-Smith <[EMAIL PROTECTED]> wrote:

My bets are on noschg flag.
Pav, you are exactly right.  I have experienced this many times myself. 
  After installing the compat5x package you need to do "chflags -R 
noschg /var/tmp/inst* && rm -rf /var/tmp/inst*" or something like that.
I think it is a bug in pkg_install, that it doesn't check for the schg 
flag being set in its temporary file area.  Or maybe it should set the 
flags in the first place.


I knew this issue.  So I fixed it with rev#1.16 on make clean.
But my work was not enough:-(.  How about following patch?


I did a portupgrade to the new version. It ended with:

===>  Cleaning for compat5x-i386-5.4.0.8_9
--->  Cleaning out obsolete shared libraries
[Updating the pkgdb  in /var/db/pkg ... - 787 packages 
found (-0 +1) . done]

Operation not permitted - /usr/local/lib/compat/pkg/libc.so.5
Operation not permitted - /usr/local/lib/compat/pkg/libc_r.so.5
Operation not permitted - /usr/local/lib/compat/pkg/libcrypt.so.2
Operation not permitted - /usr/local/lib/compat/pkg/libpthread.so.1
Operation not permitted - /usr/local/lib/compat/pkg/libthr.so.1

I do not know what was not permitted. portupgrade did backup the shared 
libs with their schg flag. Whatever should have happened then...


I guess since nothing has changed with the libs, I can safely removed 
everything from /usr/local/lib/compat/pkg/ that came from this update 
(pam_*.so.2, snmp_*.so.2, and the files mentioned in the error message). 
Is that correct?


BTW: Creating a compat5x-i386-5.4.0.8_9 package with pkg_create, 
removing it, and readding it all went without error messages.


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


Re: Opinion on cross-port OPTIONS CONFLICTS

2007-12-22 Thread Josh Paetzel
On Friday 21 December 2007 10:33:44 pm Edwin Groothuis wrote:
> On Fri, Dec 21, 2007 at 09:05:18PM -0600, Josh Paetzel wrote:
> > > > It also doesn't work if someone runs make rmconfig, or make config
> > > > again and changes things after the port is installed.
> > > >
> > > > It probably doesn't work if a package was used to install either.
> > >
> > > Create a slave port audio/arts-withoutnas and let it depends on
> > > that one.
> >
> > I don't think that's a scalable solution.  It would create an explosion
> > of ports in the already taxed tree, as well as confusion as to which port
> > to install among the users.
>
> And what is your solution for this problem?
>
> Edwin

My initial solution as I posted is to register the OPTIONs used to build a 
port in /var/db/pkg

-- 
Thanks,

Josh Paetzel

PGP: 8A48 EF36 5E9F 4EDA 5A8C 11B4 26F9 01F1 27AF AECB


signature.asc
Description: This is a digitally signed message part.


Re: pkg-config and library dependencies

2007-12-22 Thread Alexander Leidinger
Quoting Ed Schouten <[EMAIL PROTECTED]> (Sat, 22 Dec 2007 13:21:49 +0100):

> It turns out that my configure script added some unneeded -lfoo's, so I
> removed those, but there were still a lot of libraries that got added by
> pkg-config and friends. It turns out that a lot of those .pc's add
> rubbish:
[...]
> The last case is even worse. Your application will link directly against
> libthr if your use libgthread, voiding the entire idea of abstracting
> the threads library. I guess the reason they were added, is keep things
> working when compiling static binaries, because you can't recursively
> pull dependencies in that case, but that is a wrong argument, because
> you can then add the libraries to Libs.private and use
> `pkg-config --static'.

The problem is even deeper. libtool does not enable the "OS has
recursive resolver" knob on most systems. Debian has a custom patch.
The problem is, that in some cases this doesn't work. I can't remember
them, but have a look at the libtool archive, I asked there about the
problem. libtool-2 is AFAIR supposed to fix the problems.

I also asked the gome maintainers if they are interested in patches to
their libs which fix the issues you mentioned. The outcome is (and I
agree with them), that patches should go to the authors of the
problematic software first, and come into FreeBSD via regular updates
of the software in question.

I also have some patches regarding this, but they are outdated (and
just a proof of concept, as I wanted to play around with this first),
since I haven't updated to the new X.org / GNOME yet. You can find
patches at http://www.leidinger.net/FreeBSD/port-patches/, feel free to
take some and play around with them.

I would like to see that "the right thing" is done in the software
which is ported, so if someone wants to give this a high priority on
his TODO list, count me in for some help (as time permits).

Bye,
Alexander.

-- 
Ferengi Rule of Acquisition #16:
 A deal is a deal... until a better one comes along.
-- ST:DS9, "Melora"
http://www.Leidinger.net  Alexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org netchild @ FreeBSD.org  : PGP ID = 72077137
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Opinion on cross-port OPTIONS CONFLICTS

2007-12-22 Thread Pav Lucistnik
> > That's why you do slave port with an option toggled, when you need a
> > package you can depend on. OPTIONS haven't changed this aspect.
> 
> But you can't readily specify option X enabled, option Y disabled on 
> that slave port. 

You can, that's the point.

> There may come a time when it's decided to either have vanilla 
> plists and seperate one(s) with options or dont track plists for non 
> default options at all. I bet most/many non-default ports don't get 
> properly packaged anyway as it is.

Port needs to package cleanly with any combination of OPTIONS specified. If it
doesn't, it needs to be fixed.

--
Pav Lucistnik <[EMAIL PROTECTED]>
on the road via OpenWebMail

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


Re: TeTeX and TeXLive

2007-12-22 Thread Rick Voland
Ulrich Spoerlein wrote:
> On Sun, 16.12.2007 at 22:59:55 +0900, Hiroki Sato wrote:
>>  This is a progress report from the current teTeX maintainer who is
>>  trying to update TeX in the ports tree to TeXLive.  As I explained,
>>  if we go with the finer-grained package model, over 1000 ports have
>>  to be added at a time, so testing them should be done in a separate
>>  tree at least.  I hope I will be able to set up a public tree for
>>  testing and collaborative work this month...
>>
>>  Any comments are welcome.  Thanks.
> 
> As I'm not doing any work, my vote doesn't count, but please: Creating
> 2-3 *big* TeXLive ports is certainly wrong, but creating 1000 tiny ports
> is equally wrong. Think about the repo bloat and churn introduced by a
> "single" software like a LaTeX system. It will slow down everything from
> cvs checkout, to index building and pkg_info(1).
> 
> Can't you split the TeXLive Distribution up into say 12 ports? Something
> minimal that can be used by other ports to typeset documentation (how
> common is this, anyway?) and 3-4 big TeXLive ports for the typical TeX
> user.
> 
> Cheers,
> Ulrich Spoerlein



I am also only a user of TeX and friends.

May I suggest some categories for triage?


1) Simple packages like envlab and lettrine are easy to locate and
install afterwards.  So, maybe these packages (and others like
additional fonts) don't need to be in the typical TeXLive port for FreeBSD.

2) Binaries for features like xetex and ConTeXt may be difficult to
install outside the assistance of a port.  I wish recent, stable
versions of these could be included in a port, maybe the main port.

3) For now, the FreeBSD port for musixtex is incompatible with tetex.  I
wish that the various TeXLive components could be designed to be
compatible with each other so that a user could still choose to add
additional features after the initial installation.


These are only suggestions.  Thanks for your work maintaining TeX and
friends for FreeBSD.


---

Rick Voland
[EMAIL PROTECTED]

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


lang/ocaml update

2007-12-22 Thread Stanislav Sedov
Hi!

The patch attached updates lang/ocaml to 3.10.0. This version should
be almost backwards compatible with 3.09.3, but if you have time, can
you, please, check if it works for you?

If everything goes right, I'll commit if just after the slush is over.

Thanks!

-- 
Stanislav Sedov
ST4096-RIPE
Index: Makefile
===
RCS file: /work/src/fbsd-cvs/ports/lang/ocaml/Makefile,v
retrieving revision 1.59
diff -u -r1.59 Makefile
--- Makefile	19 May 2007 20:13:47 -	1.59
+++ Makefile	20 Dec 2007 21:19:02 -
@@ -6,8 +6,8 @@
 #
 
 PORTNAME=	ocaml
-PORTVERSION=	3.09.3
-PORTREVISION=	1
+PORTVERSION=	3.10.0
+PORTREVISION=	0
 CATEGORIES=	lang
 MASTER_SITES=	http://caml.inria.fr/distrib/${DISTNAME:R}/ \
 		ftp://ftp.inria.fr/INRIA/caml-light/${DISTNAME:R}/ \
@@ -89,7 +89,7 @@
 	@${REINPLACE_CMD} -E \
 		-e 's|(BYTECCCOMPOPTS[ \t]*=.*)|\1 ${CFLAGS} ${THR_CPP}|' \
 		-e 's|(NATIVECCCOMPOPTS[ \t]*=.*)|\1 ${CFLAGS} ${THR_CPP}|' \
-		-e 's|(PTHREAD_LINK[ \t]*=).*|\1 ${THR_LD}|' \
+		-e '/^PTHREAD_LINK/s,-pthread,${THR_LD},g' \
 		-e 's|gcc|${CC}|g'	\
 		${WRKSRC}/config/Makefile
 
@@ -114,9 +114,9 @@
 		"! -name .cvsignore")
 .endif
 
-.for prog in camlp4o.opt camlp4r.opt ocamlc.opt ocamldep.opt ocamldoc.opt \
+.for PROG in camlp4o.opt camlp4r.opt ocamlc.opt ocamldep.opt ocamldoc.opt \
 		ocamllex.opt ocamlopt.opt ocamlrun ocamlyacc
-	@${STRIP_CMD} ${PREFIX}/bin/${prog}
+	@${STRIP_CMD} ${PREFIX}/bin/${PROG}
 .endfor
 
 # Fix permissions for ld.conf
Index: bsd.ocaml.mk
===
RCS file: bsd.ocaml.mk
diff -N bsd.ocaml.mk
--- bsd.ocaml.mk	7 Aug 2006 06:55:27 -	1.3
+++ /dev/null	1 Jan 1970 00:00:00 -
@@ -1,195 +0,0 @@
-# ex:ts=4
-#
-# $MBSDlabs: portmk/bsd.ocaml.mk,v 1.18 2006/08/06 18:47:23 stas Exp $
-# $FreeBSD: ports/lang/ocaml/bsd.ocaml.mk,v 1.3 2006/08/07 06:55:27 itetcu Exp $
-#
-# bsd.ocaml.mk - Support for the Objective Caml language packages
-#
-# Author: Stanislav Sedov <[EMAIL PROTECTED]>
-#
-# Feel free to send any comments and suggestions to maintainer.
-#
-# Currently recognised variables are:
-#
-# USE_OCAML		-	Set if your port uses OCaml to build/install.
-# NO_OCAML_BUILDDEPENDS	-	Don't add ocamlc to BUILD|EXTRACT|PATCH_DEPENDS.
-# NO_OCAML_RUNDEPENDS	-	Don't add ocamlc to RUN_DEPENDS.
-# USE_OCAML_FINDLIB	-	Set if your port uses ocamlfind to install
-#packages. Package direcories will be
-#automatically deleted.
-# USE_OCAML_LDCONFIG	-	Set if your port installs shared libraries
-#into ocaml site-lib dir. OCaml ld.conf file
-#will be automatically processed.
-# USE_OCAML_WASH	-	Set if your port wants to automatically
-#purge shared Ocaml dirs on uninstall. It's
-#useful when installing to non-standard PREFIX
-# OCAML_PKGDIRS		-	Directories under site-lib to be processed
-#if USE_OCAML_FINDLIB specified.
-#Default: ${PORTNAME}
-# OCAML_LDLIBS		-	Directories under PREFIX to be automatically
-#added/removed from ld.conf
-#Default: ${OCAML_SITELIBDIR}/${PORTNAME}
-
-.if !defined(OCAML_include)
-
-OCAML_MAINTAINER=	[EMAIL PROTECTED]
-OCAML_include=		bsd.ocaml.mk
-
-#
-# OCaml programs location
-#
-OCAMLC?=		${LOCALBASE}/bin/ocamlc
-OCAMLC_OPT?=		${LOCALBASE}/bin/ocamlc.opt
-OCAMLCP?=		${LOCALBASE}/bin/ocamlcp
-OCAMLFIND?=		${LOCALBASE}/bin/ocamlfind
-
-#
-# OCaml library directory
-#
-OCAML_LIBDIR?=		lib/ocaml
-
-#
-# Where to install site libraries
-#
-OCAML_SITELIBDIR?=	${OCAML_LIBDIR}/site-lib
-
-#
-# OCaml compiler port dependency
-#
-OCAMLC_PORT?=		${PORTSDIR}/lang/ocaml
-OCAMLC_DEPEND?=		${OCAMLC}:${OCAMLC_PORT}
-
-#
-# OCaml package manager port dependency
-#
-OCAMLFIND_PORT?=	${PORTSDIR}/devel/ocaml-findlib
-OCAMLFIND_DEPEND?=	${OCAMLFIND}:${OCAMLFIND_PORT}
-
-#
-# Common OCaml examples and documents location
-#
-OCAML_DOCSDIR=		${PREFIX}/share/doc/ocaml
-OCAML_EXAMPLESDIR=	${PREFIX}/share/examples/ocaml
-
-#
-# Location of OCaml ld.conf file
-#
-OCAML_LDCONF?=		${OCAML_LIBDIR}/ld.conf
-
-OCAMLFIND_DESTDIR?=	${PREFIX}/${OCAML_SITELIBDIR}
-OCAMLFIND_LDCONF?=	${PREFIX}/${OCAML_LDCONF}
-
-.if defined(USE_OCAML)
-. if !defined(NO_OCAML_BUILDDEPENDS)
-EXTRACT_DEPENDS+=	${OCAMLC_DEPEND}
-PATCH_DEPENDS+=		${OCAMLC_DEPEND}
-BUILD_DEPENDS+=		${OCAMLC_DEPEND}
-. endif
-. if !defined(NO_OCAML_RUNDEPENDS)
-RUN_DEPENDS+=		${OCAMLC_DEPEND}
-. endif
-PLIST_SUB+=	OCAML_SITELIBDIR="${OCAML_SITELIBDIR}"
-.endif
-
-.if defined(USE_OCAML_FINDLIB) || defined(USE_OCAML_LDCONFIG)
-. if !target(post-install-script)
-post-install-script: ocaml-findlib ocaml-ldconfig ocaml-wash
-. endif
-.endif
-
-.if defined(USE_OCAML_FINDLIB)
-#
-# We'll additionally add ocamlfind to RUN_DEPENDS, since
-# if the port requires ocamlfind to install - it requires
-# some ocaml libraries and these libraries RUN_DEPENDS on
-# ocamlfind
-#
-BUILD_DEPENDS+=		${OCAMLFIND_DEPEND}
-RUN_DEPENDS+=		${OCAMLFIND_DEPEND}
-MAKE_ENV+=	OCAMLFIND_DESTDIR="${OCAMLFIND_DESTDIR}" \
-		OCAMLFIND_LDC

pkg-config and library dependencies

2007-12-22 Thread Ed Schouten
Hello everyone,

This morning I ran a `readelf -d' on an application that I maintain
(audio/herrie) and I saw that my application depends on a lot of
libraries that the application doesn't use anyway, but get pulled in
recursively.

If I understand correctly, this is bad behaviour. If your application
uses GNOME's GLib, it always depends on libiconv, even though you don't
call any functions in those libraries. So when libiconv's major gets
bumped, you don't need to recompile a single library, but the entire
tree of applications.

It turns out that my configure script added some unneeded -lfoo's, so I
removed those, but there were still a lot of libraries that got added by
pkg-config and friends. It turns out that a lot of those .pc's add
rubbish:

| $ pkg-config --libs libcurl
| -rpath=/usr/lib:/usr/local/lib -L/usr/local/lib -lcurl  
| $ pkg-config --libs glib-2.0
| -L/usr/local/lib -lglib-2.0 -liconv  
| $ pkg-config --libs gthread-2.0
| -pthread -L/usr/local/lib -lgthread-2.0 -lglib-2.0 -liconv  

The last case is even worse. Your application will link directly against
libthr if your use libgthread, voiding the entire idea of abstracting
the threads library. I guess the reason they were added, is keep things
working when compiling static binaries, because you can't recursively
pull dependencies in that case, but that is a wrong argument, because
you can then add the libraries to Libs.private and use
`pkg-config --static'.

I've added a bunch of patches for the ports I use for audio/herrie. I
didn't file any PR's yet, because I'd like to hear your opinions on this
matter. Are my findings correct?

-- 
 Ed Schouten <[EMAIL PROTECTED]>
 WWW: http://g-rave.nl/
--- ftp/curl/files/patch-libcurl.pc.in	1970-01-01 01:00:00.0 +0100
+++ ftp/curl/files/patch-libcurl.pc.in	2007-12-22 11:18:46.0 +0100
@@ -0,0 +1,10 @@
+--- libcurl.pc.in	2007-02-18 10:41:27.0 +0100
 libcurl.pc.in	2007-12-22 10:19:13.0 +0100
+@@ -33,6 +33,6 @@
+ URL: http://curl.haxx.se/
+ Description: Library to transfer files with ftp, http, etc.
+ Version: @VERSION@
+-Libs: -L${libdir} -lcurl @LDFLAGS@ @LIBS@
++Libs: -L${libdir} -lcurl
+ Libs.private: @LIBCURL_LIBS@ @LIBS@
+ Cflags: -I${includedir}
--- devel/glib20/files/patch-pkgconfig	1970-01-01 01:00:00.0 +0100
+++ devel/glib20/files/patch-pkgconfig	2007-12-22 13:00:56.0 +0100
@@ -0,0 +1,51 @@
+--- glib-2.0.pc.in	2007-11-24 07:41:02.0 +0100
 glib-2.0.pc.in	2007-12-22 12:59:43.0 +0100
+@@ -10,6 +10,7 @@
+ Name: GLib
+ Description: C Utility Library
+ Version: @VERSION@
+-Libs: -L${libdir} -lglib-2.0 @INTLLIBS@ @ICONV_LIBS@
++Libs: -L${libdir} -lglib-2.0
++Libs.private: @INTLLIBS@ @ICONV_LIBS@
+ Cflags: -I${includedir}/glib-2.0 -I${libdir}/glib-2.0/include 
+ 
+--- gmodule-2.0.pc.in	2007-11-24 07:41:02.0 +0100
 gmodule-2.0.pc.in	2007-12-22 12:59:43.0 +0100
+@@ -9,5 +9,6 @@
+ Description: Dynamic module loader for GLib
+ Requires: glib-2.0
+ Version: @VERSION@
+-Libs: -L${libdir} @G_MODULE_LDFLAGS@ -lgmodule-2.0 @G_MODULE_LIBS@
++Libs: -L${libdir} @G_MODULE_LDFLAGS@ -lgmodule-2.0
++Libs.private: @G_MODULE_LIBS@
+ Cflags:
+--- gmodule-export-2.0.pc.in	2007-11-24 07:41:02.0 +0100
 gmodule-export-2.0.pc.in	2007-12-22 12:59:43.0 +0100
+@@ -9,5 +9,6 @@
+ Description: Dynamic module loader for GLib
+ Requires: glib-2.0
+ Version: @VERSION@
+-Libs: -L${libdir} @G_MODULE_LDFLAGS@ -lgmodule-2.0 @G_MODULE_LIBS@
++Libs: -L${libdir} @G_MODULE_LDFLAGS@ -lgmodule-2.0
++Libs.private: @G_MODULE_LIBS@
+ Cflags:
+--- gmodule-no-export-2.0.pc.in	2007-11-24 07:41:02.0 +0100
 gmodule-no-export-2.0.pc.in	2007-12-22 12:59:43.0 +0100
+@@ -9,5 +9,6 @@
+ Description: Dynamic module loader for GLib
+ Requires: glib-2.0
+ Version: @VERSION@
+-Libs: -L${libdir} -lgmodule-2.0 @G_MODULE_LIBS@
++Libs: -L${libdir} -lgmodule-2.0
++Libs.private: @G_MODULE_LIBS@
+ Cflags:
+--- gthread-2.0.pc.in	2007-11-24 07:41:02.0 +0100
 gthread-2.0.pc.in	2007-12-22 12:59:43.0 +0100
+@@ -7,5 +7,6 @@
+ Description: Thread support for GLib
+ Requires: glib-2.0
+ Version: @VERSION@
+-Libs: -L${libdir} -lgthread-2.0 @G_THREAD_LIBS@
++Libs: -L${libdir} -lgthread-2.0
++Libs.private: @G_THREAD_LIBS@
+ Cflags: @G_THREAD_CFLAGS@
--- audio/libid3tag/files/patch-id3tag.pc.in	2003-12-29 20:54:29.0 +0100
+++ audio/libid3tag/files/patch-id3tag.pc.in	2007-12-22 11:31:05.0 +0100
@@ -1,6 +1,6 @@
 --- id3tag.pc.in.orig	1970-01-01 09:00:00.0 +0900
 +++ id3tag.pc.in	2003-11-11 08:42:38.0 +0900
-@@ -0,0 +1,10 @@
+@@ -0,0 +1,11 @@
 [EMAIL PROTECTED]@
 [EMAIL PROTECTED]@
 [EMAIL PROTECTED]@
@@ -9,5 +9,6 @@
 +Name: ID3TAG
 +Description: libid3tag - ID3 tag manipulation library
 +Version: @VERSION@
-+Libs: -L${libdir} -lid3tag -lz
++Libs: -L${libdir} -lid3tag
++Libs.private: -lz
 +Cflags:
--- audio/libmad/files/mad.pc.in	2004-10-12 00:20:46.0 +0200
+++ audio/libmad/files/mad.pc.in	2007

Re: multimedia/mplayer doesn't build (default options)

2007-12-22 Thread Dominic Fandrey
I've got a solution now. After the build failed just go to your WRKDIR and run
gmake. The build will finish just fine. I've got no idea why it doesn't work
through the ports.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"