Fwd: Install ctorrent-3.2_1 error, Makefile error?

2007-09-07 Thread Sunry Chen
-- Forwarded message --
From: Sunry Chen [EMAIL PROTECTED]
Date: Sep 7, 2007 3:07 PM
Subject: Re: Install ctorrent-3.2_1 error, Makefile error?
To: Nikola Lecic [EMAIL PROTECTED]


On 9/7/07, Nikola Lecic [EMAIL PROTECTED] wrote:
   (1) The identically arranged .for loop for PORTDOCS works correctly
   in e.g. devel/p5-Proc-ProcessTable;

   (2) There is no global isspace(3) problem with something weird, e.g.
   with your locale or something else.

 The last two things you can try are:

   (a) download

 
 http://cvsweb.freebsd.org/ports/net-p2p/ctorrent/ctorrent.tar.gz?tarball=1

   Replace net-p2p/ctorrent dir with it and try again;

[EMAIL PROTECTED] /tmp]# tar xzvf /usr/ports/net-p2p/ctorrent.tar.gz\?tarball\=1
x ctorrent/
x ctorrent/Makefile
x ctorrent/distinfo
x ctorrent/pkg-descr
[EMAIL PROTECTED] /tmp]# cd -
/usr/ports/net-p2p/ctorrent
[EMAIL PROTECTED] /usr/ports/net-p2p/ctorrent]# diff Makefile 
/tmp/ctorrent/Makefile
5c5
 # $FreeBSD: ports/net-p2p/ctorrent/Makefile,v 1.16 2007/08/24
09:40:35 flz Exp $
---
 # $FreeBSD: ports/net-p2p/ctorrent/Makefile,v 1.17 2007/08/25 11:49:56 flz 
 Exp $
30c29,31
   ${INSTALL_DATA} ${WRKSRC}/${PORTDOCS} ${DOCSDIR}/
---
 .for i in ${PORTDOCS}
   ${INSTALL_DATA} ${WRKSRC}/$i ${DOCSDIR}/
 .endfor
[EMAIL PROTECTED] /usr/ports/net-p2p/ctorrent]#

I see, the Makefiles a little diff from mine. :-)


   (b) try to reproduce the error using the minimal BSDmakefile I
   attached, which literally repeats the problematic line. If your
   output differs from

 # make
 test 1...
 README-DNH.TXT
 UserGuide
 test 2...
 README-DNH.TXT
 UserGuide

   then you maybe can book a hunted bug somewhere in
   src/usr.bin/make/for.c or related to isspace(3), triggered by
   something strange in your environment, maybe by your locale. But
   that's material for a new thread, perhaps on [EMAIL PROTECTED]

[EMAIL PROTECTED] /tmp]# make
test 1...
README-DNH.TXT
UserGuide
test 2...
README-DNH.TXT
UserGuide
___
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 get a static binary from ports

2007-09-07 Thread Karol Kwiatkowski
Karol Kwiatkowski wrote:
 Hi all,
 
 to keep it short:
 
 is there any ports knob to statically link binaries?
 If not, what steps should I take to modify a port?
 
 longer version:
 
 I'm trying to get a static binary out of the port. I thought it should
 be straight and easy, but I'm lost right now.
 
 The port in question is databases/rrdtool, uses libtool:15, gnu
 configure, gmake, etc.
 
 Normally, this port builds rrdtool binary which is dynamically linked
 (full path removed for brevity):
 
 # ldd (...)/work/rrdtool-1.2.23/src/.libs/rrdtool
 (...)/work/rrdtool-1.2.23/src/.libs/rrdtool:
 librrd.so.2 = not found (0x0)
 libfreetype.so.9 = /usr/local/lib/libfreetype.so.9 (0x28085000)
 libpng.so.5 = /usr/local/lib/libpng.so.5 (0x280ef000)
 libz.so.4 = /lib/libz.so.4 (0x28115000)
 libart_lgpl_2.so.5 = /usr/local/lib/libart_lgpl_2.so.5 (0x28127000)
 libm.so.5 = /lib/libm.so.5 (0x2813c000)
 libc.so.7 = /lib/libc.so.7 (0x28151000)
 
 With 'make CFLAGS+=-static' I get:
 
 # ldd (...)/work/rrdtool-1.2.23/src/rrdtool
 (...)/work/rrdtool-1.2.23/src/rrdtool:
 libfreetype.so.9 = /usr/local/lib/libfreetype.so.9 (0x280cb000)
 libpng.so.5 = /usr/local/lib/libpng.so.5 (0x28135000)
 libz.so.4 = /lib/libz.so.4 (0x2815b000)
 libart_lgpl_2.so.5 = /usr/local/lib/libart_lgpl_2.so.5 (0x2816d000)
 libm.so.5 = /lib/libm.so.5 (0x28182000)
 libc.so.7 = /lib/libc.so.7 (0x28197000)
 
 librrd.so.2 is now included statically, but the rest is not. I tried
 various configure options like --enable-static, --disable-shared, also
 added '-static' to CFLAGS and/or LDFLAGS in Makefile plus various
 combinations of the above but that doesn't make a difference.
 
 How can I include the rest of the libraries in the binary?

OK, it seems it's a problem with rrdtool's build suite, and not only
I've got problems with it[1].

For the archives, in case of rrdtool's port, a simple workaround is to
patch src/Makefile (exists after 'configure' part, so those patches are
host's dependent):

# cat src_Makefile.patch
--- src/Makefile.orig   2007-09-06 14:01:07.0 +0200
+++ src/Makefile2007-09-06 15:13:15.0 +0200
@@ -183,7 +183,7 @@
 INSTALL_PROGRAM = install  -s -o root -g wheel -m 555
 INSTALL_SCRIPT = install  -o root -g wheel -m 555
 INSTALL_STRIP_PROGRAM = ${SHELL} $(install_sh) -c -s
-LDFLAGS = -L/usr/local/lib
+LDFLAGS = -all-static -L/usr/local/lib
 LIBOBJS =
 LIBS =
 LIBTOOL = $(SHELL) /usr/local/bin/libtool


And while we're here it might be worth changing path to default font so
the binary can work as a 'standalone' (here to 'current'):

@@ -301,7 +301,7 @@
 #
 #ACLOCAL_M4   = $(top_srcdir)/config/aclocal.m4
 #AUTOHEADER = ${SHELL}
/mnt/big/FreeBSD/work/usr/ports/databases/rrdtool/work/rrdtool-1.2.23/missing
--run autoheader --localdir=$(top_srcdir)/config
-fontsdir = $(datadir)/rrdtool/fonts
+fontsdir = .
 fonts_DATA = DejaVuSansMono-Roman.ttf
 AM_CPPFLAGS = -DRRD_DEFAULT_FONT=\$(RRD_DEFAULT_FONT)\ -DNUMVERS=1.2023
 UPD_C_FILES = \


Cheers and thanks for the pointers.

Karol

[1] http://ramblingfoo.blogspot.com/2007/08/softfloat-rrdtool-sequel.html

-- 
Karol Kwiatkowski   karol.kwiat at gmail dot com
OpenPGP 0x06E09309



signature.asc
Description: OpenPGP digital signature


Upgrading to squid-2.6.15 is not recommended.

2007-09-07 Thread RW

The squid site is recommending that people skip 2.6.15 and go straight
to 2.6.16

http://squidproxy.wordpress.com/2007/09/03/dont-upgrade-to-squid-26stable15-skip-straight-to-squid-26stable16/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: why an Hamachi port? yet another VPN?

2007-09-07 Thread Lapo Luchini
Lapo Luchini wrote:
 Moreover, this works has already been done, and yours truly also
 prepared a port to automate it.
 
 The only thing lacking is someone interested in it enough to give me
 feedback on the PR ports/112982.

Update: the port has been committed, thanks edwin ;-)

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


Re: gramps fails to run

2007-09-07 Thread David J Brooks
On Friday 07 September 2007 01:13:50 am Lars Eighner wrote:
 On Thu, 6 Sep 2007, David J Brooks wrote:
  After upgrading all my python stuff to 2.5, gramps will no longer start.
  I have tried rebuilding gramps, but its apparently still looking for
  python 2.4, at least some of the time.

 Two things I'd try if I were you:

 1) is there a link python-python2.5 in /usr/local/bin?  If not, I'd
 install one.

 2) I'd try adding PYTHON_DEFAULT_WERSION=python2.5 to /etc/make.conf and
 rebuilding gramps.

Thanks for the suggestions Lars. I tried both, (amending the spelling of 
WERSION to VERSION ;) but gramps still produces the same set of warnings and 
errors at runtime.

David
-- 
Hey, what do you expect from a culture that
*drives* on *parkways* and *parks* on *driveways*?
-- Gallagher
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]


FreeBSD Port: exim-4.67

2007-09-07 Thread Maxim Sirenko

Hi.

Why Exim is stil 4.67 in FreeBSD ports tree?
I use it and see that it already has to be 4.68.

With respect,
Maxim.
___
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: exim-4.67

2007-09-07 Thread Larry Rosenman
resync your ports tree.  4.68 is in there, and I'm running it from ports.



-- 
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 512-248-2683E-Mail: [EMAIL PROTECTED]
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Maxim Sirenko
Sent: Friday, September 07, 2007 2:17 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: FreeBSD Port: exim-4.67

Hi.

Why Exim is stil 4.67 in FreeBSD ports tree?
I use it and see that it already has to be 4.68.

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

___
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: exim-4.67

2007-09-07 Thread Kirill Ponomarew
On Fri, Sep 07, 2007 at 10:16:44PM +0300, Maxim Sirenko wrote:
 Hi.
 
 Why Exim is stil 4.67 in FreeBSD ports tree?
 I use it and see that it already has to be 4.68.

Please, update your ports.

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


[HEADSUP] bsd.perl.mk import coming soon

2007-09-07 Thread Mark Linimon
The refactoring that gabor has done to recreate bsd.perl.mk will be
imported soon, along with the many ports that it simplifies.  Due to
the size of the patch, I expect there to be collisions that I will have
to adjust as I go, so expect the tree to be broken briefly while I work
through the checkin.

The main feature of the change will be to allow USE_PERL5= 5.8.0+ (and
similarly for USE_PERL5_RUN, USE_PERL5_BUILD, PERL_CONFIGURE and
PERL_MODBUILD).  As a side-effect, the remaining few stragglers that
attempt to keep perl5.003 going will be dropped.  (Other committers
have also been removing that code).

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


Updating X.org FreeBSD ports to 7.3

2007-09-07 Thread Florent Thoumie
As some of you may know already, X.org released X11R7.3 yesterday. Since 
we already made the move to modular ports for 7.2, the work to update 
ports to 7.3 was much faster.


It's not likely to cause any major breakage but I'd like to get some 
feedback (from users and pointyhat) before I commit the update, so it 
probably won't reach the CVS repository before wednesday.


Here's a diff against current ports tree:

http://dump.xbsd.org/freebsd/xorg73.diff.gz

PS: I'll be away (and unreachable) getting some sunburns this week-end, 
so leave a message on x11@ and I'll answer when I'm back.


flz 4 x11@

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


Totem and Ghostscript-gpl build failure

2007-09-07 Thread Da Rock
Hi all.

I've done quite a bit of searching and head scratching for 2 days now, and I 
can't find an answer for this.
I'm trying to build rhythmbox and gnome2-lite and both fail to build in ports. 
I've tried building gnome instead and it stops in totem.

The error returned for totem is gnome-libtool: link: 
libtotem_player_la-totem-statusbar.lo is not a valid libtool object.

The error for ghostscript is undefined reference errors in function 
opvp_to_utf8 to libiconv_close, resulting in an error code 1 for gmake and an 
error code 2 for the port build.

Is there a fix or workaround for this? Or am I missing something?

Thanks guys.


_
Telstra’s Next GTM Network - now on Pre-Paid. Find out more. 
www.spreadthegoodstuff.com.au
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fclk%2Eatdmt%2Ecom%2FOAT%2Fgo%2Fnnmsnnxg008046oat%2Fdirect%2F01%2F_t=765565283_r=Telstra_FFF_Prepaid_Hotmail_Email_Taglines_JuySep07_Aug_m=EXT___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]