Re: Newbie: problem using SUB_LIST in Makefile - SOLVED

2007-11-23 Thread Rainer Schwarze 
Dmitry Marakasov wrote:
> * Rainer Schwarze ([EMAIL PROTECTED]) wrote:
>> 1) What could be the reason that even XWRAPPER is not handled when the
>> replacement is performed?
> On my system similar stuff works without problems. First check all
[...]

I found the problem: The Makefile which I am working on uses SUB_LIST
either not at all or incorrectly. There is a target pre-configure which
contains an operation for manual replacement of the variables in
pkg-install.in :

pre-configure:
[...]
@${SED} -e 's,%%SPOOLDIR%%,${SPOOLDIR},g; s,%%QS_USER%%,${QS_USER},g; \
s,%%QS_ID%%,${QS_ID},g' ${FILESDIR}/pkg-install.in > ${PKGINSTALL}

So I know how to proceed...

>> 2) Is my approach of adding entries to SUB_LIST based on
>> WITH_.../WITHOUT_... correct? (Or is that impossible after including
>> bsd.port.pre.mk? As far as I understand, the WITH_.../WITHOUT_... are
>> available only after bsd.port.[*.]mk is included...?)
> Pretty correct. Actually, in generic case it _should_ be done after
> pre.mk, becausee options are often used (btw, you should think of
> using OPTIONS too):
> 
> ...
> OPTIONS=  CWRAPPER"Use C wrapper" on

You have the powers of a seer :-)
This is what I was appending to OPTIONS:
CWRAPPER "use C wrapper (no suid perl script needed)" on

> .include 
>  
> .if !defined(WITHOUT_CWRAPPER)

Just a newbie question: Is there a reason to use !defined(WITHOUT_...)
instead of defined(WITH_...) ?

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

php4-4.4.7_2: "/usr/ports/www/apachecommon22" non-existent -- dependency list incomplete

2007-11-23 Thread Boris Samorodov 
Hello,


seems to be a bug somewhere (imo php4 or bsd.apache.mk, thus cc'ing
apropriate maintainers):
-
localhost# uname -a
FreeBSD localhost 7.0-BETA3 FreeBSD 7.0-BETA3 #2: Thu Nov 22 01:14:27 MSK 2007  
   [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MOOS  i386

localhost# pwd
/usr/ports/lang/php4

localhost# make WITH_APACHE="YES" USE_APACHE="2.2" all-depends-list
/usr/ports/www/apache22
/usr/ports/devel/autoconf261
/usr/ports/lang/perl5.8
php4-4.4.7_2: "/usr/ports/www/apachecommon22" non-existent -- dependency list 
incomplete
/usr/ports/devel/libtool15
/usr/ports/textproc/expat2
/usr/ports/converters/libiconv
/usr/ports/devel/m4
/usr/ports/misc/help2man
/usr/ports/devel/gmake
/usr/ports/devel/autoconf-wrapper
/usr/ports/devel/p5-Locale-gettext
/usr/ports/devel/gettext
-

Thanks for your attention.


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

Re: FreeBSD Port: cyrus-imapd-2.3.9_1

2007-11-23 Thread Hajimu UMEMOTO 
Hi,

> On Wed, 21 Nov 2007 09:19:20 -0800
> Rich Wales <[EMAIL PROTECTED]> said:

richw> Hi.  Does a port of Cyrus 2.3.10 exist yet?  Or are you aware of any
richw> issues with 2.3.10 under FreeBSD for which patches might exist?

richw> I'm running Cyrus on a FreeBSD 6.2-RELEASE system.  I need to upgrade
richw> from 2.3.9 to 2.3.10 because I want to use replication but am running
richw> into stability problems with the replication code in 2.3.9.

richw> I tried building 2.3.10 from sources, using the same configuration
richw> options as in my 2.3.9 build from the port.  I added one patch from
richw> the Info-Cyrus list, relating to getgrouplist() calls, but otherwise
richw> used the 2.3.10 source "as is".

richw> The resulting 2.3.10 build suffered from problems with "ctl_cyrusdb -c"
richw> hanging, and other mail delivery attempts hanging (or timing out) and
richw> piling up in my Postfix queue.  I had to restart Cyrus frequently in
richw> order to clear these logjams.  Eventually, I gave up and went back to
richw> 2.3.9, but I can't stay there indefinitely because I need replication
richw> to work more solidly than it does in 2.3.9.

richw> Are you aware of any issues which might cause this sort of instability
richw> with 2.3.10?  If I can't find out (or figure out) what is going on, I'll
richw> probably have to move Cyrus off my FreeBSD box and put it on something
richw> like Ubuntu, where 2.3.10 appears to run without problems.

I've updated cyrus-imapd23 port to 2.3.10 with the patch for
getgrouplist issue, locally.  But, since the ports tree is in freeze
state now, I'm waiting the freeze is over.  2.3.10 is running well
here for about 20 days.  But, I'm not using replication at all.

Are you aware that GUID for replication has been changed to use SHA1?
I'm not sure but you might need to change GUID.  Please refer
install-upgrade.html.

You might want to try my cyrus-imapd23 port.  So, I've put it to:

http://www.imasy.or.jp/~ume/FreeBSD/cyrus-imapd23-port-20071124.tar.gz

Sincerely,

--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
[EMAIL PROTECTED]  [EMAIL PROTECTED],jp.}FreeBSD.org
http://www.imasy.org/~ume/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeNX Package

2007-11-23 Thread Wesley Shields 
On Fri, Nov 23, 2007 at 06:52:37PM -0500, User Ota wrote:
> I was browsing around looking for alternatives to vnc, and tried to 
> experiment with FreeNX.  I got this working with Debian, but I notice 
> that the port is marked as broken, reason being it fails to build wit 
> X.org 7.2.
> 
> I have package X.Org 7.3 installed.
> 
> This will probably sound a little idiotic, but does the port fail to 
> build against any version of X.org 7.2 and higher, or is it just marked 
> broken for general purposes (regardless of the fact it says it doesn't 
> build properly with v7.2)?

Assuming your talking about net/nxserver it would be better to ask the
maintainer.  I've CC'ed him on this, but it won't hurt to remove the
BROKEN line and try it for yourself?

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

Re: FreeNX Package

2007-11-23 Thread User Ota 
On Fri, Nov 23, 2007 at 08:07:52PM -0500, Wesley Shields wrote:
> On Fri, Nov 23, 2007 at 07:43:53PM -0500, User Ota wrote:
> > On Fri, Nov 23, 2007 at 07:36:49PM -0500, Wesley Shields wrote:
> > > On Fri, Nov 23, 2007 at 06:52:37PM -0500, User Ota wrote:
> > > > I was browsing around looking for alternatives to vnc, and tried to 
> > > > experiment with FreeNX.  I got this working with Debian, but I notice 
> > > > that the port is marked as broken, reason being it fails to build wit 
> > > > X.org 7.2.
> > > > 
> > > > I have package X.Org 7.3 installed.
> > > > 
> > > > This will probably sound a little idiotic, but does the port fail to 
> > > > build against any version of X.org 7.2 and higher, or is it just marked 
> > > > broken for general purposes (regardless of the fact it says it doesn't 
> > > > build properly with v7.2)?
> > > 
> > > Assuming your talking about net/nxserver it would be better to ask the
> > > maintainer.  I've CC'ed him on this, but it won't hurt to remove the
> > > BROKEN line and try it for yourself?
> > > 
> > > -- WXS
> > > ___
> > > freebsd-ports@freebsd.org mailing list
> > > http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> > > To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> > 
> > Sounds like a great idea, I'll try it and see how it goes.
> > 
> > By the way, should I post any error messages to this mailing list, or 
> > should I just post to freebsd-ports-bugs instead?
> 
> Discussing with the maintainer first is always a good idea.  When the
> maintainer is [EMAIL PROTECTED] (this mailing list) it is an
> unmaintained port and any questions regarding the port should be
> directed to the list.
> 
> -- WXS

Yeah, i'm running make on nxserver now, and it's giving tons of errors, 
such as:

cc1plus: warning: command line option "-Wmissing-declarations" is valid 
for C/ObjC but not for C++
cc1plus: warning: command line option "-Wnested-externs" is valid for 
C/ObjC but not for C++
g++ -c -O3 -I../nx-X11/exports/include -Wno-deprecated 
-Wmissing-declarations -Wnested-externs -I/usr/local/include 
-DIN_ADDR_T=in_addr_t -DVERSION=\"1.4.0\"  -I/usr/local/include 
-DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" 
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\"  -fpermissive -fPIC 
-I/usr/local/include  PolySegment.cpp
cc1plus: warning: command line option "-Wmissing-declarations" is valid 
for C/ObjC but not for C++
cc1plus: warning: command line option "-Wnested-externs" is valid for 
C/ObjC but not for C++

Also a lot of imake warnings from before, so I guess it's broken :P, 
anyways I'll discuss this with the maintainer.  Many thanks.


Russell Doucette

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

Re: FreeNX Package

2007-11-23 Thread dewey hylton 
Quoting Wesley Shields <[EMAIL PROTECTED]>:

> On Fri, Nov 23, 2007 at 06:52:37PM -0500, User Ota wrote:
> > I was browsing around looking for alternatives to vnc, and tried to 
> > experiment with FreeNX.  I got this working with Debian, but I notice 
> > that the port is marked as broken, reason being it fails to build wit 
> > X.org 7.2.
> > 
> > I have package X.Org 7.3 installed.
> > 
> > This will probably sound a little idiotic, but does the port fail to 
> > build against any version of X.org 7.2 and higher, or is it just marked 
> > broken for general purposes (regardless of the fact it says it doesn't 
> > build properly with v7.2)?
> 
> Assuming your talking about net/nxserver it would be better to ask the
> maintainer.  I've CC'ed him on this, but it won't hurt to remove the
> BROKEN line and try it for yourself?

good plan. and if it builds, _test it_ ... i've been able to get past enough 
errors that it builds, but it still doesn't operate correctly. if you get it to 
build and the pieces all work properly, let us know.



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

Idea about the ports tree included in the release

2007-11-23 Thread Doug Barton 
In thinking about the guy who posted to -stable about using the tar'ed
up version of the ports tree, I had an idea that would make that more
useful. How hard would it be to include the c[v]sup checkouts file
with the tarball, and install it into some standard location? I think
that would greatly increase the utility of the tarball, since you
could start from there and immediately update to the latest version
without having to pull down the whole tree again.

Doug

-- 

This .signature sanitized for your protection

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

Re: FreeNX Package

2007-11-23 Thread User Ota 
On Fri, Nov 23, 2007 at 09:27:56PM -0500, dewey hylton wrote:
> Quoting Wesley Shields <[EMAIL PROTECTED]>:
> 
> > On Fri, Nov 23, 2007 at 06:52:37PM -0500, User Ota wrote:
> > > I was browsing around looking for alternatives to vnc, and tried to 
> > > experiment with FreeNX.  I got this working with Debian, but I notice 
> > > that the port is marked as broken, reason being it fails to build wit 
> > > X.org 7.2.
> > > 
> > > I have package X.Org 7.3 installed.
> > > 
> > > This will probably sound a little idiotic, but does the port fail to 
> > > build against any version of X.org 7.2 and higher, or is it just marked 
> > > broken for general purposes (regardless of the fact it says it doesn't 
> > > build properly with v7.2)?
> > 
> > Assuming your talking about net/nxserver it would be better to ask the
> > maintainer.  I've CC'ed him on this, but it won't hurt to remove the
> > BROKEN line and try it for yourself?
> 
> good plan. and if it builds, _test it_ ... i've been able to get past enough 
> errors that it builds, but it still doesn't operate correctly. if you get it 
> to 
> build and the pieces all work properly, let us know.
> 
> 
> 

It went through a bunch of warnings and nonetheless built, until:

===>  Installing for nxserver-1.4.0_1
===>   nxserver-1.4.0_1 depends on executable: nc - found
===>   nxserver-1.4.0_1 depends on file: 
/usr/local/libdata/xorg/libraries - found
===>   Generating temporary packing list
===>  Checking if net/nxserver already installed
/bin/mkdir -p /usr/local/NX/lib /usr/local/NX/bin
install  -o root -g wheel -m 444 
/usr/ports/net/nxserver/work/nx-X11/lib/X11/libX11.so* /usr/local/NX/lib
install  -o root -g wheel -m 444 
/usr/ports/net/nxserver/work/nx-X11/lib/Xext/libXext.so* 
/usr/local/NX/lib
install  -o root -g wheel -m 444 
/usr/ports/net/nxserver/work/nx-X11/lib/Xrender/libXrender.so* 
/usr/local/NX/lib
install  -o root -g wheel -m 444 
/usr/ports/net/nxserver/work/nxcomp/libXcomp.so* /usr/local/NX/lib
install  -o root -g wheel -m 444 
/usr/ports/net/nxserver/work/nxcompext/libXcompext.so* /usr/local/NX/lib
install  -s -o root -g wheel -m 555 
/usr/ports/net/nxserver/work/nx-X11/programs/Xserver/nxagent 
/usr/local/NX/bin
install: /usr/ports/net/nxserver/work/nx-X11/programs/Xserver/nxagent: 
No such file or directory
*** Error code 71

Stop in /usr/ports/net/nxserver.
*** Error code 1

Stop in /usr/ports/net/nxserver.
*** Error code 1

Stop in /usr/ports/net/freenx.
*** Error code 1

Stop in /usr/ports/net/freenx.
** Command failed [exit code 1]: /usr/bin/script -qa 
/tmp/portinstall.35776.0 env make reinstall
** Fix the installation problem and try again.
** Listing the failed packages (*:skipped / !:failed)
! net/freenx(install error)
--->  Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed


So, unfortunately, it's a no go.  It seems it can't find one particular 
file, and I have a feeling this is related to all those warning messages 
beforehand, about imake and the Objective C flags.


Russell Doucette

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

FreeBSD Port: stvef-server-1.20_3

2007-11-23 Thread Stefan Konijnenberg 
Is this also for star trek Elite force 2??

 

 

Greetzz Stefan Konijnenberg

 

Mail.   [EMAIL PROTECTED]

Tel. 0614942804

 

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

FreeNX Package

2007-11-23 Thread User Ota 
I was browsing around looking for alternatives to vnc, and tried to 
experiment with FreeNX.  I got this working with Debian, but I notice 
that the port is marked as broken, reason being it fails to build wit 
X.org 7.2.

I have package X.Org 7.3 installed.

This will probably sound a little idiotic, but does the port fail to 
build against any version of X.org 7.2 and higher, or is it just marked 
broken for general purposes (regardless of the fact it says it doesn't 
build properly with v7.2)?


Russell Doucette

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

Re: how to distinguish direct/indirect requirements?

2007-11-23 Thread Alex Dupre 
Andrew Pantyukhin wrote:
> You can cd some/port/&&make depends

One way only. It would be more useful to know which installed ports
directly depend on a specific port.

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

Re: how to distinguish direct/indirect requirements?

2007-11-23 Thread Andrew Pantyukhin 
On Fri, Nov 23, 2007 at 10:49:35AM +0100, Lapo Luchini wrote:
> Is there a way to discriminate direct dependencies fro indirect
> ones, except from reading every single Makefile? (and knowing
> to full extent what USE_GNOME and similar lines really do take
> in as deps)

You can cd some/port/&&make depends, but personally, I've also
always thought that the difference between direct and indirect
dependencies should be embedded in the package system.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Newbie: problem using SUB_LIST in Makefile - SOLVED

2007-11-23 Thread Dmitry Marakasov 
* Rainer Schwarze ([EMAIL PROTECTED]) wrote:

> You have the powers of a seer :-)
> This is what I was appending to OPTIONS:
> CWRAPPER "use C wrapper (no suid perl script needed)" on

:))

> > .include 
> >  
> > .if !defined(WITHOUT_CWRAPPER)
> 
> Just a newbie question: Is there a reason to use !defined(WITHOUT_...)
> instead of defined(WITH_...) ?

There was once a rule that you should check for non-default values.

I.e. if you have
OPTIONS=CWRAPPER "C wrapper" on
you should check for WITHOUT_CWRAPPER

and if you have
OPTIONS=CWRAPPER "C wrapper" off
you should check for WITH_CWRAPPER

The cause of this is that WITH(OUT)_CWRAPPER may be defined in
/etc/make.conf, make environment or make commandline, and that
should have higher priority than value set with OPTIONS.

For example, you have:
OPTIONS=CWRAPPER "C wrapper" on

and in /etc/make.conf:
WITHOUT_CWRAPPER=   yes # I don't want any *** C wrappers!!!

Thus, both WITHOUT_CWRAPPER and WITH_CWRAPPER will be defined, but the
port will behave correctly if you check for WITHOUT_CWRAPPER.

Actually, this was fixed, so you can check for either WITH_ or WITHOUT_
as you like 
(http://lists.freebsd.org/pipermail/freebsd-ports/2007-April/039831.html),
but I prefer to stick with scheme described above.

-- 
Dmitry A. Marakasov| jabber: [EMAIL PROTECTED]
[EMAIL PROTECTED]   | http://www.amdmi3.ru
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

libgtkmozembed.so for Adobe Reader 8

2007-11-23 Thread Marcin Cieslak 


Hello,

New Adobe Reader 8 requires some HTML rendering capabilities mainly for 
his new advertising splash-screen.


Therefore it needs that libgtkmozembed.so is present and set in the 
preferences (without this you get annoying popup at startup but PDF 
functionality works fine).


libgtkmozembed.so is in every linux-* browser port, I use one from 
www/linux-seamonkey. However I think we should not add any of the 
linux-* ports as a dependency.


How this should be solved? A separate port (but still pulling large 
distfile)? A wrapper? Any other ideas?


--Marcin

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

Re: how to distinguish direct/indirect requirements?

2007-11-23 Thread Stephen Montgomery-Smith 
On Fri, Nov 23, 2007 at 11:25:25PM +0300, Andrew Pantyukhin wrote:
> On Fri, Nov 23, 2007 at 10:49:35AM +0100, Lapo Luchini wrote:
> > Is there a way to discriminate direct dependencies fro indirect
> > ones, except from reading every single Makefile? (and knowing
> > to full extent what USE_GNOME and similar lines really do take
> > in as deps)
> 
> You can cd some/port/&&make depends, but personally, I've also
> always thought that the difference between direct and indirect
> dependencies should be embedded in the package system.

Haven't been following this thread, so apologies if I misunderstand or repeat.

If you want only the direct depends, you can do this (under sh or bash)

cd the-port
for a in `make -V _LIB_RUN_DEPENDS`
do (cd `echo $a | sed -E 's/.*://'` && make -V PKGNAME); done
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

how to distinguish direct/indirect requirements?

2007-11-23 Thread Lapo Luchini 
It happened many times to me to ask myself: why I do have port XYZ
installed? surely "something needs it", but what?
"pkg_info -r/-R" are of little help, because every dependency of every
dependency (and other ranks of indirect dependencies too) are simply
registered as direct dependencies, so that pretty much every single
small gnome application depends on EVERY gnome and xorg port.

OK, in a sense it *really* depends on all of them, because one of them
missing would break it, but OTOH I'd like to know which ones are direct
dependencies and which ones are indirect, especially because in that
case my life would be easier wading through the correct Makefiles and
searching for "WITHOUT_*" knobs or other ways to "cut" some dependencies
I really don't want.

True, there are "package tree" ports such as pkg_tree, but for the very
reason that indirect dependencies are registered in exactly the same way
that direct ones are, they provide an output that's not very useful at
all (a very flattened tree).

Is there a way to discriminate direct dependencies fro indirect ones,
except from reading every single Makefile? (and knowing to full extent
what USE_GNOME and similar lines really do take in as deps)

Lapo

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

Re: Newbie: problem using SUB_LIST in Makefile - SOLVED

2007-11-23 Thread Rainer Schwarze 
Dmitry Marakasov wrote:
[...]
> For example, you have:
> OPTIONS=  CWRAPPER "C wrapper" on
> 
> and in /etc/make.conf:
> WITHOUT_CWRAPPER= yes # I don't want any *** C wrappers!!!
> 
> Thus, both WITHOUT_CWRAPPER and WITH_CWRAPPER will be defined, but the
> port will behave correctly if you check for WITHOUT_CWRAPPER.

> Actually, this was fixed, so you can check for either WITH_ or WITHOUT_
> as you like 
> (http://lists.freebsd.org/pipermail/freebsd-ports/2007-April/039831.html),
> but I prefer to stick with scheme described above.

Ah! Good to know :-)
Thanks for the information.

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