Possibly unbuildable ports reminder

2007-02-14 Thread Bill Fenner
Dear porters,

  This is just a reminder to please periodically check the list of
unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ .
A list by MAINTAINER is

http://people.freebsd.org/~fenner/errorlogs/

so you can easily check the status of ports that you maintain.  In
addition, the list of ports with no MAINTAINER with build problems is

http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED]

Since no one is responsible for these ports, the problem won't get
fixed unless someone on this list takes the initiative.

Thanks for your help!

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


Re: math/ATLAS upgrade fails Benchmarking xzllttst

2007-02-14 Thread Karsten Rothemund
On Tue, Feb 13, 2007 at 10:54:10AM -0800, John Bowman wrote:
> I am duplicating Karsten Rothemund's earlier post, as my error message 
> is identical except for timing numbers:
> 
> Unfortunately I only have the last few lines (because of the portupgrade):
> 

I had a private mail contact with Maho NAKATA (maintainer of the
port), who asked me if it possible to use math/atlas-devel.

The result is, atlas-devel compiles fine and actave-devel seems to
work. Maybe you try try this as well.

Hope this helps,

Karsten

-- 
   
Karsten Rothemund <[EMAIL PROTECTED]> /"\
PGP-Key: 0x7019CAA5   \ /
Fingerprint: E752 C759 B9B2 2057 E42F  \  ASCII Ribbon Campaign
 50EE 47AC A7CE 7019 CAA5 / \ Against HTML Mail and News


pgpsOcOQBL785.pgp
Description: PGP signature


Python 2.4.4 and devel/ncurses

2007-02-14 Thread Rong-En Fan
distinfo pkg-plist ports/lang/python24/files patch-CVE-2006-4980
patch-setup.py]
Reply-To: 
In-Reply-To: <[EMAIL PROTECTED]>

[I move to ports@ for discussion. Also CC'ing ncurses author]

On Wed, Feb 14, 2007 at 02:07:32PM +0100, Kirill Ponomarew wrote:
> On Wed, Feb 14, 2007 at 06:07:33AM +, Xin LI wrote:
> > delphij 2007-02-14 06:07:29 UTC
> > 
> >   FreeBSD ports repository
> > 
> >   Modified files:
> > Mk   bsd.python.mk 
> > lang/python  Makefile distinfo 
> > lang/python-doc-html distinfo 
> > lang/python24Makefile distinfo pkg-plist 
> > lang/python24/files  patch-setup.py 
> >   Removed files:
> > lang/python24/files  patch-CVE-2006-4980 
> >   Log:
> >   Update to Python 2.4.4.
> >   
> >   Approved by:maintainer timeout, alexbl (python@)
> >   Tested by:  pointyhat
> >   PR: ports/105901
> 
> Upgrading from python24-2.4.3_3 to python24-2.4.4 fails on AMD64 6.2 RELEASE.
> 
> cc -DNDEBUG -O2 -fno-strict-aliasing -pipe -D__wchar_t=wchar_t 
> -DTHREAD_STACK_SIZE=0x2 -fPIC -fno-strict-aliasing -I. 
> -I/usr/ports/lang/python24/work/Python-2.4.4/./Include -I/usr/local/include 
> -I/usr/ports/lang/python24/work/Python-2.4.4/Include 
> -I/usr/ports/lang/python24/work/Python-2.4.4 -c 
> /usr/ports/lang/python24/work/Python-2.4.4/Modules/_cursesmodule.c -o 
> build/temp.freebsd-6.2-PRERELEASE-amd64-2.4/_cursesmodule.o
> cc -shared -pthread -O2 -fno-strict-aliasing -pipe -D__wchar_t=wchar_t 
> -DTHREAD_STACK_SIZE=0x2 
> build/temp.freebsd-6.2-PRERELEASE-amd64-2.4/_cursesmodule.o -L/usr/local/lib 
> -lncurses -o build/lib.freebsd-6.2-PRERELEASE-amd64-2.4/_curses.so
> Segmentation fault (core dumped)
> *** Error code 139

I can reproduce this with both i386/amd64 6.2-RELEASE with devel/ncurses
installed. ldd ${WRKSRC}/build/.../_curses.so says it is linked against
local/lib/libncurses.so.6 (ktrace on python executable also confirms that).

gdb shows (I have devel/ncurses-devel installed instead of ncurses 5.6):

(gdb) run
Starting program:
/home/admin/usr/ports/lang/python24/work/Python-2.4.4/python
warning: Unable to get location for thread creation breakpoint: generic
error
[New LWP 100158]
Python 2.4.4 (#1, Feb 14 2007, 21:57:09)
[GCC 3.4.6 [FreeBSD] 20060305] on freebsd6
Type "help", "copyright", "credits" or "license" for more information.
[New Thread 0x604000 (LWP 100158)]
>>> import _curses

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x604000 (LWP 100437)]
0x0008011ad7d4 in keybound () from /lib/libncurses.so.6
(gdb) bt
#0  0x0008011ad7d4 in keybound () from /lib/libncurses.so.6
#1  0x0008012fe281 in keyname () from /usr/local/lib/libtinfo.so.5.6
#2  0x00080142c1be in init_curses ()
at 
/home/admin/usr/ports/lang/python24/work/Python-2.4.4/Modules/_cursesmodule.c:2605
#3  0x0047215f in _PyImport_LoadDynamicModule (
name=0x7fffdf70 "_curses",
pathname=0x7fffdac0 
"/home/admin/usr/ports/lang/python24/work/Python-2.4.4/build/lib.freebsd-6.2-PRERELEASE-amd64-2.4/_curses.so",
 fp=0x80142b3b9)
at ./Python/importdl.c:53
#4  0x00470255 in load_module (name=0x7fffdf70 "_curses",
fp=0x101, buf=0x1 , type=3,
loader=0x101)
at 
/home/admin/usr/ports/lang/python24/work/Python-2.4.4/Python/import.c:1689
#5  0x0047061d in import_submodule (mod=0x5b3ea0,
subname=0x7fffdf70 "_curses", fullname=0x7fffdf70 "_curses")
at 
/home/admin/usr/ports/lang/python24/work/Python-2.4.4/Python/import.c:2276
[...]

I can build python 2.4.4 without problems on 7.x i386, which has ncurses
5.6 in base. Moreover, python 2.5 builds fine on these machines, i.e., 
with devel/ncurses installed. 

So, my guess is that devel/ncurses + base ncurses confuses python 2.4.4
build in someway...

Regards,
Rong-En Fan

> 
> -Kirill


pgpYppd6NOZgS.pgp
Description: PGP signature


Re: Python 2.4.4 and devel/ncurses

2007-02-14 Thread LI Xin
Hi,

Rong-En Fan wrote:
> distinfo pkg-plist ports/lang/python24/files patch-CVE-2006-4980
> patch-setup.py]
> Reply-To: 
> In-Reply-To: <[EMAIL PROTECTED]>
> 
> [I move to ports@ for discussion. Also CC'ing ncurses author]
> 
> On Wed, Feb 14, 2007 at 02:07:32PM +0100, Kirill Ponomarew wrote:
[...]
>> Upgrading from python24-2.4.3_3 to python24-2.4.4 fails on AMD64 6.2 RELEASE.
>>
>> cc -DNDEBUG -O2 -fno-strict-aliasing -pipe -D__wchar_t=wchar_t 
>> -DTHREAD_STACK_SIZE=0x2 -fPIC -fno-strict-aliasing -I. 
>> -I/usr/ports/lang/python24/work/Python-2.4.4/./Include -I/usr/local/include 
>> -I/usr/ports/lang/python24/work/Python-2.4.4/Include 
>> -I/usr/ports/lang/python24/work/Python-2.4.4 -c 
>> /usr/ports/lang/python24/work/Python-2.4.4/Modules/_cursesmodule.c -o 
>> build/temp.freebsd-6.2-PRERELEASE-amd64-2.4/_cursesmodule.o
>> cc -shared -pthread -O2 -fno-strict-aliasing -pipe -D__wchar_t=wchar_t 
>> -DTHREAD_STACK_SIZE=0x2 
>> build/temp.freebsd-6.2-PRERELEASE-amd64-2.4/_cursesmodule.o -L/usr/local/lib 
>> -lncurses -o build/lib.freebsd-6.2-PRERELEASE-amd64-2.4/_curses.so
>> Segmentation fault (core dumped)
>> *** Error code 139
> 
> I can reproduce this with both i386/amd64 6.2-RELEASE with devel/ncurses
> installed. ldd ${WRKSRC}/build/.../_curses.so says it is linked against
> local/lib/libncurses.so.6 (ktrace on python executable also confirms that).
> 
> gdb shows (I have devel/ncurses-devel installed instead of ncurses 5.6):
> 
> (gdb) run
> Starting program:
> /home/admin/usr/ports/lang/python24/work/Python-2.4.4/python
> warning: Unable to get location for thread creation breakpoint: generic
> error
> [New LWP 100158]
> Python 2.4.4 (#1, Feb 14 2007, 21:57:09)
> [GCC 3.4.6 [FreeBSD] 20060305] on freebsd6
> Type "help", "copyright", "credits" or "license" for more information.
> [New Thread 0x604000 (LWP 100158)]
 import _curses
> 
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x604000 (LWP 100437)]
> 0x0008011ad7d4 in keybound () from /lib/libncurses.so.6
> (gdb) bt
> #0  0x0008011ad7d4 in keybound () from /lib/libncurses.so.6
> #1  0x0008012fe281 in keyname () from /usr/local/lib/libtinfo.so.5.6
> #2  0x00080142c1be in init_curses ()
> at 
> /home/admin/usr/ports/lang/python24/work/Python-2.4.4/Modules/_cursesmodule.c:2605
> #3  0x0047215f in _PyImport_LoadDynamicModule (
> name=0x7fffdf70 "_curses",
> pathname=0x7fffdac0 
> "/home/admin/usr/ports/lang/python24/work/Python-2.4.4/build/lib.freebsd-6.2-PRERELEASE-amd64-2.4/_curses.so",
>  fp=0x80142b3b9)
> at ./Python/importdl.c:53
> #4  0x00470255 in load_module (name=0x7fffdf70 "_curses",
> fp=0x101, buf=0x1 , type=3,
> loader=0x101)
> at 
> /home/admin/usr/ports/lang/python24/work/Python-2.4.4/Python/import.c:1689
> #5  0x0047061d in import_submodule (mod=0x5b3ea0,
> subname=0x7fffdf70 "_curses", fullname=0x7fffdf70 "_curses")
> at 
> /home/admin/usr/ports/lang/python24/work/Python-2.4.4/Python/import.c:2276
> [...]
> 
> I can build python 2.4.4 without problems on 7.x i386, which has ncurses
> 5.6 in base. Moreover, python 2.5 builds fine on these machines, i.e., 
> with devel/ncurses installed. 
> 
> So, my guess is that devel/ncurses + base ncurses confuses python 2.4.4
> build in someway...

Hmm...  So I guess this is machine independent?  I'll try to see if I
can produce this on my i386 crashbox, thanks for the clue.

Cheers,
-- 
Xin LI <[EMAIL PROTECTED]>  http://www.delphij.net/
FreeBSD - The Power to Serve!



signature.asc
Description: OpenPGP digital signature


Re: Python 2.4.4 and devel/ncurses

2007-02-14 Thread Rong-En Fan
On Wed, Feb 14, 2007 at 10:34:22PM +0800, LI Xin wrote:
> Hi,
> 
> Rong-En Fan wrote:
> > [I move to ports@ for discussion. Also CC'ing ncurses author]
> > 
> > On Wed, Feb 14, 2007 at 02:07:32PM +0100, Kirill Ponomarew wrote:
> [...]
> >> Upgrading from python24-2.4.3_3 to python24-2.4.4 fails on AMD64 6.2 
> >> RELEASE.
> >>
> >> cc -DNDEBUG -O2 -fno-strict-aliasing -pipe -D__wchar_t=wchar_t 
> >> -DTHREAD_STACK_SIZE=0x2 -fPIC -fno-strict-aliasing -I. 
> >> -I/usr/ports/lang/python24/work/Python-2.4.4/./Include 
> >> -I/usr/local/include -I/usr/ports/lang/python24/work/Python-2.4.4/Include 
> >> -I/usr/ports/lang/python24/work/Python-2.4.4 -c 
> >> /usr/ports/lang/python24/work/Python-2.4.4/Modules/_cursesmodule.c -o 
> >> build/temp.freebsd-6.2-PRERELEASE-amd64-2.4/_cursesmodule.o
> >> cc -shared -pthread -O2 -fno-strict-aliasing -pipe -D__wchar_t=wchar_t 
> >> -DTHREAD_STACK_SIZE=0x2 
> >> build/temp.freebsd-6.2-PRERELEASE-amd64-2.4/_cursesmodule.o 
> >> -L/usr/local/lib -lncurses -o 
> >> build/lib.freebsd-6.2-PRERELEASE-amd64-2.4/_curses.so
> >> Segmentation fault (core dumped)
> >> *** Error code 139
> > 
> > I can reproduce this with both i386/amd64 6.2-RELEASE with devel/ncurses
> > installed. ldd ${WRKSRC}/build/.../_curses.so says it is linked against
> > local/lib/libncurses.so.6 (ktrace on python executable also confirms that).
> > 
> > gdb shows (I have devel/ncurses-devel installed instead of ncurses 5.6):
> > 
> > (gdb) run
> > Starting program:
> > /home/admin/usr/ports/lang/python24/work/Python-2.4.4/python
> > warning: Unable to get location for thread creation breakpoint: generic
> > error
> > [New LWP 100158]
> > Python 2.4.4 (#1, Feb 14 2007, 21:57:09)
> > [GCC 3.4.6 [FreeBSD] 20060305] on freebsd6
> > Type "help", "copyright", "credits" or "license" for more information.
> > [New Thread 0x604000 (LWP 100158)]
>  import _curses
> > 
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread 0x604000 (LWP 100437)]
> > 0x0008011ad7d4 in keybound () from /lib/libncurses.so.6
> > (gdb) bt
> > #0  0x0008011ad7d4 in keybound () from /lib/libncurses.so.6
> > #1  0x0008012fe281 in keyname () from /usr/local/lib/libtinfo.so.5.6
> > #2  0x00080142c1be in init_curses ()
> > at 
> > /home/admin/usr/ports/lang/python24/work/Python-2.4.4/Modules/_cursesmodule.c:2605
> > #3  0x0047215f in _PyImport_LoadDynamicModule (
> > name=0x7fffdf70 "_curses",
> > pathname=0x7fffdac0 
> > "/home/admin/usr/ports/lang/python24/work/Python-2.4.4/build/lib.freebsd-6.2-PRERELEASE-amd64-2.4/_curses.so",
> >  fp=0x80142b3b9)
> > at ./Python/importdl.c:53
> > #4  0x00470255 in load_module (name=0x7fffdf70 "_curses",
> > fp=0x101, buf=0x1 , type=3,
> > loader=0x101)
> > at 
> > /home/admin/usr/ports/lang/python24/work/Python-2.4.4/Python/import.c:1689
> > #5  0x0047061d in import_submodule (mod=0x5b3ea0,
> > subname=0x7fffdf70 "_curses", fullname=0x7fffdf70 "_curses")
> > at 
> > /home/admin/usr/ports/lang/python24/work/Python-2.4.4/Python/import.c:2276
> > [...]
> > 
> > I can build python 2.4.4 without problems on 7.x i386, which has ncurses
> > 5.6 in base. Moreover, python 2.5 builds fine on these machines, i.e., 
> > with devel/ncurses installed. 
> > 
> > So, my guess is that devel/ncurses + base ncurses confuses python 2.4.4
> > build in someway...
> 
> Hmm...  So I guess this is machine independent?  I'll try to see if I

Yes. And, python 2.4.3 fails, too.


Regards,
Rong-En Fan

> can produce this on my i386 crashbox, thanks for the clue.
> 
> Cheers,
> -- 
> Xin LI <[EMAIL PROTECTED]>http://www.delphij.net/
> FreeBSD - The Power to Serve!
> 




pgpqitVgN70M5.pgp
Description: PGP signature


Re: FreeBSD Port: amanda-client-2.5.1p3,1

2007-02-14 Thread Craig Boston
On Sun, Feb 11, 2007 at 08:17:21AM -0600, Karl Friesen wrote:
> Amanda-client-2.5.1p3,1 is broken
> 
> In particular the arguments that sendsize hands to dump are bad.
> Using 2.5.1p3,1 the command line used was:
> 
>   "/sbin/dump 0SSsf 0 1048576 - /dev/da0s1a"
> 
> where with (a locally patched) 2.5.1p2 the command line was:
>   "/sbin/dump 0ShLsf 0 1048576 - /dev/da0s1a"

I'm seeing the same problem here.  Fortunately I only upgraded one
machine so far.

> My local patch was to add the L option (to quell warning messages).
> 
> The first question is why there is an extra "S" in the command line, but 
> the real problem is caused by the elimination of the "h" which changes 
> the argument list.  The "h" was the argument that required the "0" in 
> the argument list.

It looks like the code in sendsize.c that generates the dump arguments
was completely rewritten between p2 and p3, and a mistake was made
(PARAM_DUMP_ESTIMATE used twice instead of PARAM_HONOR_NODUMP).  A patch
is attached that should fix it.

We can add the patch to ports if necessary, but as the problem exists in
upstream sources it should really be fixed there.

> I cannot say if the same problem exists in sendbackup.  My dumps didn't 
> make it that far :(

Glancing through sendbackup-dump.c it looks like everything should be
fine there (though I'm actually a little surprised that the -L patch
still applies cleanly).  I haven't run a backup with the fixed sendsize
yet, however, so I guess we'll see.

Craig
--- client-src/sendsize.c.orig	Wed Feb 14 08:47:15 2007
+++ client-src/sendsize.c	Wed Feb 14 08:45:10 2007
@@ -1190,7 +1190,7 @@
 #  endif
 	dumpkeys = vstralloc(level_str,
 			 PARAM_DUMP_ESTIMATE,
-			 PARAM_DUMP_ESTIMATE,
+			 PARAM_HONOR_NODUMP,
 			 "s", "f", NULL);
 
 #  ifdef HAVE_DUMP_ESTIMATE
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Python 2.4.4 and devel/ncurses

2007-02-14 Thread Thomas Dickey
On Wed, Feb 14, 2007 at 10:30:11PM +0800, Rong-En Fan wrote:
> distinfo pkg-plist ports/lang/python24/files patch-CVE-2006-4980
> patch-setup.py]
> Reply-To: 
> In-Reply-To: <[EMAIL PROTECTED]>
...
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x604000 (LWP 100437)]
> 0x0008011ad7d4 in keybound () from /lib/libncurses.so.6
> (gdb) bt
> #0  0x0008011ad7d4 in keybound () from /lib/libncurses.so.6
> #1  0x0008012fe281 in keyname () from /usr/local/lib/libtinfo.so.5.6

Is /usr/local/lib/libtinfo.so.5.6 built using the rpath option?
If it's not (or not working properly), that could be the problem.
Also, if /lib/libncurses.so.6 happened to be loaded first, that
could be the issue.

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net


pgpNCsbsYNmLx.pgp
Description: PGP signature


Re: Python 2.4.4 and devel/ncurses

2007-02-14 Thread Rong-En Fan
On Wed, Feb 14, 2007 at 10:09:12AM -0500, Thomas Dickey wrote:
> On Wed, Feb 14, 2007 at 10:30:11PM +0800, Rong-En Fan wrote:
> > distinfo pkg-plist ports/lang/python24/files patch-CVE-2006-4980
> > patch-setup.py]
> > Reply-To: 
> > In-Reply-To: <[EMAIL PROTECTED]>
> ...
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread 0x604000 (LWP 100437)]
> > 0x0008011ad7d4 in keybound () from /lib/libncurses.so.6
> > (gdb) bt
> > #0  0x0008011ad7d4 in keybound () from /lib/libncurses.so.6
> > #1  0x0008012fe281 in keyname () from /usr/local/lib/libtinfo.so.5.6
> 
> Is /usr/local/lib/libtinfo.so.5.6 built using the rpath option?
> If it's not (or not working properly), that could be the problem.

Yes, --enable-rpath is passed to configure.

> Also, if /lib/libncurses.so.6 happened to be loaded first, that
> could be the issue.

$ kdump -T | grep  curses\.so
 45383 python   1171466835.725865 NAMI  "/lib/libncurses.so.5.6"
 45383 python   1171466835.725888 NAMI  "/usr/lib/libncurses.so.5.6"
 45383 python   1171466835.725914 NAMI  "/usr/lib/compat/libncurses.so.5.6"
 45383 python   1171466835.725940 NAMI  "/usr/X11R6/lib/libncurses.so.5.6"
 45383 python   1171466835.725967 NAMI  "/usr/local/lib/libncurses.so.5.6"
 45383 python   1171466835.725995 NAMI  "/usr/local/lib/libncurses.so.5.6"
 45383 python   1171466835.726209 NAMI  "/lib/libncurses.so.6"
 45383 python   1171466835.726234 NAMI  "/lib/libncurses.so.6"
[I typed 'import _curses' at python prompt then 5+ seconds later, I hit enter]
 45383 python   1171466842.011160 NAMI  "_curses.so"
 45383 python   1171466842.011279 NAMI  "/usr/local/lib/python24.zip/_curses.so"
 45383 python   1171466842.011451 NAMI  
"/home/rafan/work/FreeBSD/ports/lang/python24/work/Python-2.4.4/Lib/_curses.so"
 45383 python   1171466842.011640 NAMI  
"/home/rafan/work/FreeBSD/ports/lang/python24/work/Python-2.4.4/Lib/plat-freebsd6/_curses.so"
 45383 python   1171466842.011859 NAMI  
"/home/rafan/work/FreeBSD/ports/lang/python24/work/Python-2.4.4/Lib/lib-tk/_curses.so"
 45383 python   1171466842.012050 NAMI  
"/home/rafan/work/FreeBSD/ports/lang/python24/work/Python-2.4.4/Modules/_curses.so"
 45383 python   1171466842.012236 NAMI  
"/home/rafan/work/FreeBSD/ports/lang/python24/work/Python-2.4.4/build/lib.freebsd-6.2-PRERELEASE-amd64-2.4/_curses.so"
 45383 python   1171466842.012313 NAMI  
"/home/rafan/work/FreeBSD/ports/lang/python24/work/Python-2.4.4/build/lib.freebsd-6.2-PRERELEASE-amd64-2.4/_curses.so"
 45383 python   1171466842.012551 NAMI  "/lib/libncurses.so.5.6"
 45383 python   1171466842.012575 NAMI  "/usr/lib/libncurses.so.5.6"
 45383 python   1171466842.012603 NAMI  "/usr/lib/compat/libncurses.so.5.6"
 45383 python   1171466842.012630 NAMI  "/usr/X11R6/lib/libncurses.so.5.6"
 45383 python   1171466842.012658 NAMI  "/usr/local/lib/libncurses.so.5.6"

It seems to me that rpath works as expected but /lib/libncurses.so.6 is
loaded first...

> 
> -- 
> Thomas E. Dickey
> http://invisible-island.net
> ftp://invisible-island.net




pgpLgKUZFV7yV.pgp
Description: PGP signature


Re: Python 2.4.4 and devel/ncurses

2007-02-14 Thread Thomas Dickey
On Wed, Feb 14, 2007 at 10:09:12AM -0500, Thomas Dickey wrote:
> On Wed, Feb 14, 2007 at 10:30:11PM +0800, Rong-En Fan wrote:
> > distinfo pkg-plist ports/lang/python24/files patch-CVE-2006-4980
> > patch-setup.py]
> > Reply-To: 
> > In-Reply-To: <[EMAIL PROTECTED]>
> ...
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread 0x604000 (LWP 100437)]
> > 0x0008011ad7d4 in keybound () from /lib/libncurses.so.6
> > (gdb) bt
> > #0  0x0008011ad7d4 in keybound () from /lib/libncurses.so.6
> > #1  0x0008012fe281 in keyname () from /usr/local/lib/libtinfo.so.5.6

btw, there shouldn't be any calls from libtinfo to libncurses even
if things are working properly (I check different configurations using
a script to list externals for the shared libraries to guard against
this, but of course even that may overlook some configuration...).

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net


pgp1EwfG8BdVF.pgp
Description: PGP signature


Re: Python 2.4.4 and devel/ncurses

2007-02-14 Thread Thomas Dickey
On Wed, Feb 14, 2007 at 11:30:11PM +0800, Rong-En Fan wrote:
> On Wed, Feb 14, 2007 at 10:09:12AM -0500, Thomas Dickey wrote:
> > On Wed, Feb 14, 2007 at 10:30:11PM +0800, Rong-En Fan wrote:
> > > distinfo pkg-plist ports/lang/python24/files patch-CVE-2006-4980
> > > patch-setup.py]
> > > Reply-To: 
> > > In-Reply-To: <[EMAIL PROTECTED]>
> > ...
> > > Program received signal SIGSEGV, Segmentation fault.
> > > [Switching to Thread 0x604000 (LWP 100437)]
> > > 0x0008011ad7d4 in keybound () from /lib/libncurses.so.6
> > > (gdb) bt
> > > #0  0x0008011ad7d4 in keybound () from /lib/libncurses.so.6
> > > #1  0x0008012fe281 in keyname () from /usr/local/lib/libtinfo.so.5.6
> > 
> > Is /usr/local/lib/libtinfo.so.5.6 built using the rpath option?
> > If it's not (or not working properly), that could be the problem.
> 
> Yes, --enable-rpath is passed to configure.

good (that reduces the possibilities a little).
 
> > Also, if /lib/libncurses.so.6 happened to be loaded first, that
> > could be the issue.
> 
> $ kdump -T | grep  curses\.so

hmm - then what's doing the first load?

>  45383 python   1171466835.725865 NAMI  "/lib/libncurses.so.5.6"
>  45383 python   1171466835.725888 NAMI  "/usr/lib/libncurses.so.5.6"
>  45383 python   1171466835.725914 NAMI  "/usr/lib/compat/libncurses.so.5.6"
>  45383 python   1171466835.725940 NAMI  "/usr/X11R6/lib/libncurses.so.5.6"
>  45383 python   1171466835.725967 NAMI  "/usr/local/lib/libncurses.so.5.6"
>  45383 python   1171466835.725995 NAMI  "/usr/local/lib/libncurses.so.5.6"
>  45383 python   1171466835.726209 NAMI  "/lib/libncurses.so.6"
>  45383 python   1171466835.726234 NAMI  "/lib/libncurses.so.6"
> [I typed 'import _curses' at python prompt then 5+ seconds later, I hit enter]
>  45383 python   1171466842.011160 NAMI  "_curses.so"
>  45383 python   1171466842.011279 NAMI  
> "/usr/local/lib/python24.zip/_curses.so"
>  45383 python   1171466842.011451 NAMI  
> "/home/rafan/work/FreeBSD/ports/lang/python24/work/Python-2.4.4/Lib/_curses.so"
>  45383 python   1171466842.011640 NAMI  
> "/home/rafan/work/FreeBSD/ports/lang/python24/work/Python-2.4.4/Lib/plat-freebsd6/_curses.so"
>  45383 python   1171466842.011859 NAMI  
> "/home/rafan/work/FreeBSD/ports/lang/python24/work/Python-2.4.4/Lib/lib-tk/_curses.so"
>  45383 python   1171466842.012050 NAMI  
> "/home/rafan/work/FreeBSD/ports/lang/python24/work/Python-2.4.4/Modules/_curses.so"
>  45383 python   1171466842.012236 NAMI  
> "/home/rafan/work/FreeBSD/ports/lang/python24/work/Python-2.4.4/build/lib.freebsd-6.2-PRERELEASE-amd64-2.4/_curses.so"
>  45383 python   1171466842.012313 NAMI  
> "/home/rafan/work/FreeBSD/ports/lang/python24/work/Python-2.4.4/build/lib.freebsd-6.2-PRERELEASE-amd64-2.4/_curses.so"
>  45383 python   1171466842.012551 NAMI  "/lib/libncurses.so.5.6"
>  45383 python   1171466842.012575 NAMI  "/usr/lib/libncurses.so.5.6"
>  45383 python   1171466842.012603 NAMI  "/usr/lib/compat/libncurses.so.5.6"
>  45383 python   1171466842.012630 NAMI  "/usr/X11R6/lib/libncurses.so.5.6"
>  45383 python   1171466842.012658 NAMI  "/usr/local/lib/libncurses.so.5.6"
> 
> It seems to me that rpath works as expected but /lib/libncurses.so.6 is
> loaded first...

There was some discussion about a year ago, which pointed out a problem.
The readline package loads termcap, which could be provided by ncurses.
You might be hitting that problem (readline, or another package).
The fix would be to ensure that "termcap" loads the same library as
"curses".

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net


pgp6MO5dSr1DD.pgp
Description: PGP signature


Re: Backing up old installed files?

2007-02-14 Thread Alejandro Pulver
On Sat, 10 Feb 2007 13:27:42 -0800
Darren Pilgrim <[EMAIL PROTECTED]> wrote:

> I'm writing a port for a script that stores the configuration data in 
> the same file as the program code itself.  The long-term solution is to 
> move the configuration data to another file, of course; however, that's 
> proving to be a far slower process than originally expected.
> 
> Other than delaying the submission until the configuration data is split 
> from the script, what can/should I do?

Hello.

You can install the original script in ${PREFIX}/libexec and a wrapper
script in ${PREFIX}/bin, that would copy it to the user's home
directory if not exists and run it from there.

For example, the wrapper script could be (considering it is listed in
SUB_FILES):

#!/bin/sh

test -f ~/.script.sh || cp %%PREFIX%%/libexec/script.sh ~/.script.sh && \
chmod u+w ~/.script.sh
exec ~/.script.sh "$@"

See games/cube (the wrapper script files/cube_client.in) for an
example, but it considers the program needs to run from its data
directory.

Best Regards,
Ale


signature.asc
Description: PGP signature


A bit of a silly question - but I am desperate

2007-02-14 Thread Thomas Sparrevohn
Hi 

My old trusty FreeBSD server just died and naturally that happened days
before the new machine arrived - fortunately I did not lose too much data -
however I did lose my settings and that my problem

Using a ADSL router with NAT and firewall settings (Open on http/https and
outgoings) there was some setting I used to get "fetch http://{whatever}"; to
work and I cannot remember what it was - The firewall settings has not
changed - but every time I trying to get anything using "fetch
http://{bla,bla}"; nothing come over - connection is fine 

Can anybody help?

Thanks in advance (PS. I am sure its trivial) - I just cannot remember what
it was 

Regards
Thomas 

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


Re: multimedia/kbtv: broken saa kmod?

2007-02-14 Thread Danny Pansters
I don't see this happening but I did get other (casting) errors that gcc calls 
warnings. Start with a fresh make extract then put the attached diffs in 
kbtv_wrksrc_dir/saa/patches/

This makes it build for me on both amd64 and i386 (on STABLE). I haven't 
crawled under my desk yet and switched the TV card to my AMD box so I can 
only say that it compiles on amd (amd64 native, not in 32 bits mode I don't 
use that at all).

It doesn't contain any secam support yet either (I'll probably do that in my 
own saa.c module).

HTH,

Dan

> On Tue, 13 Feb 2007 06:09:13 +0300 Yuri Pankov wrote:
> > I've attached a patch allowing saa kmod to compile cleanly on amd64 with
> > WERROR defined.
>
> Thanks, Yuri, pathces applied cleanly. But while compiling I get:
> -
> ===> kmod (all)
> Warning: Object directory not changed from original
> /usr/ports/multimedia/kbtv/work/kbtv-1.2.3/saa/saa/kmod @ -> /usr/src/sys
> machine -> /usr/src/sys/amd64/include
> awk -f @/tools/makeobjops.awk @/dev/iicbus/iicbus_if.m -h
> awk -f @/tools/makeobjops.awk @/kern/device_if.m -h
> awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h
> awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h
> cc -O2 -fno-strict-aliasing -pipe  -Werror -D_KERNEL -DKLD_MODULE -nostdinc
> -I-   -I. -I@ -I@/contrib/altq -I@/../include -I/usr/include
> -finline-limit=8000 -fno-common  -fno-omit-frame-pointer -mcmodel=kernel
> -mno-red-zone  -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow 
> -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Wall
> -Wredundant-decls -Wnested-externs -Wstrict-prototypes 
> -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual 
> -fformat-extensions -std=c99 -c saa713x.c cc -O2 -fno-strict-aliasing -pipe
>  -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I-   -I. -I@ -I@/contrib/altq
> -I@/../include -I/usr/include -finline-limit=8000 -fno-common 
> -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone  -mfpmath=387
> -mno-sse -mno-sse2 -mno-mmx -mno-3dnow  -msoft-float
> -fno-asynchronous-unwind-tables -ffreestanding -Wall -Wredundant-decls
> -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith
> -Winline -Wcast-qual  -fformat-extensions -std=c99 -c saa713x_i2c.c
> saa713x_i2c.c:157: error: conflicting types for 'saa_i2c_write'
> ./saa713x_i2c.h:32: error: previous declaration of 'saa_i2c_write' was here
> saa713x_i2c.c:157: error: conflicting types for 'saa_i2c_write'
> ./saa713x_i2c.h:32: error: previous declaration of 'saa_i2c_write' was here
> *** Error code 1
>
> Stop in /usr/ports/multimedia/kbtv/work/kbtv-1.2.3/saa/saa/kmod.
> *** Error code 1
>
> Stop in /usr/ports/multimedia/kbtv/work/kbtv-1.2.3/saa/saa.
> -
>
> Help me! ;-)
>
>
> WBR
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Backing up old installed files?

2007-02-14 Thread Darren Pilgrim

Alejandro Pulver wrote:

On Sat, 10 Feb 2007 13:27:42 -0800
Darren Pilgrim <[EMAIL PROTECTED]> wrote:

I'm writing a port for a script that stores the configuration data in 
the same file as the program code itself.  The long-term solution is to 
move the configuration data to another file, of course; however, that's 
proving to be a far slower process than originally expected.


Other than delaying the submission until the configuration data is split 
from the script, what can/should I do?


Hello.

You can install the original script in ${PREFIX}/libexec and a wrapper
script in ${PREFIX}/bin, that would copy it to the user's home
directory if not exists and run it from there.


That wouldn't work in this case.  The script is a daemon (postfix policy 
service), not a user program.


The best I've come up with so far is to install the script to 
${PREFIX}/share/${PORTNAME}, then add a note to pkg-message to have the 
user copy the script to runnable location (i.e., the postfix config 
directory), edit the internal config and set the path in /etc/rc.conf. 
This means a manual step to install/upgrade and an orphan when the port 
is deinstalled, but it's the least-evil solution I've come up with.

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


Looking for kernel constants / documentation - RTC, wordsize

2007-02-14 Thread Garrett Cooper

Hello again,
	In my effort to continue porting tvtime to freebsd I've come across 
several issues in compiling the app.


	One sets of issues are compiling files with Linux specific, mostly 
dealing with RTC. I did a bit of searching, discovered that the mplayer 
dealt with a similar issue and the port author submitted the following 
patch, but I can't seem to find the rtc.h header file:


 #ifdef HAVE_RTC
+#ifdef HAVE_BSDRTC
+#include 
+#define RTC_IRQP_SET RTCIO_IRQP_SET
+#define RTC_PIE_ON RTCIO_PIE_ON
+#else
 #include 
 #endif
+#endif

HAVE_BSDRTC is defined by the configure file. Would anyone know where 
rtc.h is right off-hand?


Another question is function-wise, will I have to worry about the 
details with FreeBSD's RTC vs Linux's RTC (apparently Linux's RTC is 
more defined than FreeBSD's as of 2 years ago, or so some mailing list 
guy said) or can I just ignore them?


Finally, where can I find the constant defined in bits/wordsize.h called 
"__WORDSIZE" (or "WORDSIZE", perhaps)?


Thanks,

-Garrett
___
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: amanda-client-2.5.1p3,1

2007-02-14 Thread Jun Kuriyama
At Wed, 14 Feb 2007 08:54:47 -0600,
Craig Boston wrote:
> It looks like the code in sendsize.c that generates the dump arguments
> was completely rewritten between p2 and p3, and a mistake was made
> (PARAM_DUMP_ESTIMATE used twice instead of PARAM_HONOR_NODUMP).  A patch
> is attached that should fix it.
> 
> We can add the patch to ports if necessary, but as the problem exists in
> upstream sources it should really be fixed there.
> 
> > I cannot say if the same problem exists in sendbackup.  My dumps didn't 
> > make it that far :(
> 
> Glancing through sendbackup-dump.c it looks like everything should be
> fine there (though I'm actually a little surprised that the -L patch
> still applies cleanly).  I haven't run a backup with the fixed sendsize
> yet, however, so I guess we'll see.
> 
> Craig
> [2 sendsize.patch ]
> --- client-src/sendsize.c.origWed Feb 14 08:47:15 2007
> +++ client-src/sendsize.c Wed Feb 14 08:45:10 2007
> @@ -1190,7 +1190,7 @@
>  #  endif
>   dumpkeys = vstralloc(level_str,
>PARAM_DUMP_ESTIMATE,
> -  PARAM_DUMP_ESTIMATE,
> +  PARAM_HONOR_NODUMP,
>"s", "f", NULL);
>  
>  #  ifdef HAVE_DUMP_ESTIMATE

Thank you for your investigation.  I've committed your patch into our
repository.


-- 
Jun Kuriyama <[EMAIL PROTECTED]> // IMG SRC, Inc.
 <[EMAIL PROTECTED]> // FreeBSD Project
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


[Fwd: Re: A bit of a silly question - but I am desperate]

2007-02-14 Thread Garrett Cooper

Wrong list--oops.
-Garrett
--- Begin Message ---

Thomas Sparrevohn wrote:
Hi 


My old trusty FreeBSD server just died and naturally that happened days
before the new machine arrived - fortunately I did not lose too much data -
however I did lose my settings and that my problem

Using a ADSL router with NAT and firewall settings (Open on http/https and
outgoings) there was some setting I used to get "fetch http://{whatever}"; to
work and I cannot remember what it was - The firewall settings has not
changed - but every time I trying to get anything using "fetch
http://{bla,bla}"; nothing come over - connection is fine 


Can anybody help?

Thanks in advance (PS. I am sure its trivial) - I just cannot remember what
it was 


Regards
	Thomas 


This question is probably better suited for the questions@ list.
-Garrett
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
--- End Message ---
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

symon creating dates in year 31900

2007-02-14 Thread Dan Langille

Anyone using syutils/symon?

I noticed this problem today after installing symon on a 6.2 box

# mkdir ~/tmp
# cd ~/tmp
# /usr/local/share/symon/c_smrrds.sh cpu0
cpu0.rrd created
# rrdtool info  cpu0.rrd | head
filename = "cpu0.rrd"
rrd_version = "0003"
step = 5
last_update = 944503401600


Notice the date, that's a bit odd:

# date -r 944503401600
Wed Feb 14 00:00:00 PST 31900


This was with rrdtool-1.2.19_1 on FreeBSD 6.2-STABLE #6: Fri Feb  9 
15:54:22 PST 2007




On another system, with a slightly different rrdtoo, I get better results:

# /usr/local/share/symon/c_smrrds.sh cpu0
cpu0.rrd created
# rrdtool info cpu0.rrd | head
filename = "cpu0.rrd"
rrd_version = "0003"
step = 5
last_update = 1171429200
# date -r 1171429200
Wed Feb 14 00:00:00 EST 2007

Now that's something a little more reasonable.

Does anyone get similar results?

Failing a solution, does anyone know how to reset the last_update field in 
an rrd file?


--
Dan Langille - http://www.langille.org/
BSDCan - The Technical BSD Conference: http://www.bsdcan.org/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: where to install kld ports

2007-02-14 Thread Yoshihiro Ota
Thanks to Jurgen, first.  I wasn't sure where was the best place to bring it to 
a discussion so that I sent the patch.

I somehow though that .ko was installed into /book/kernel and being removed 
with installkernel.  So, when I saw that fusefs installed its ko installed into 
/usr/local/modules, I thought it was a good idea.  That was unnecessary, then.

Perhaps, shouldn't KMODDIR defined somewhere in ports/Mk/*mk and no individual 
ports need to define it themselves?

Thanks,
Hiro

On Wed, 14 Feb 2007 07:45:05 +0100
Alex Dupre <[EMAIL PROTECTED]> wrote:

> Juergen Lock ha scritto:
> > The upside would be that the kld wouldn't be deleted
> > by installkernel
> 
> I don't think they are deleted, the modules directory is not replaced on
> installkernel. If the kld is needed at boot time by loader it cannot
> stay in /usr/local, but probably kqemu can be loaded later.
> 
> --
> Alex Dupre
> ___
> 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]"


Library minor versions conflicting with PLIST with no minor versions

2007-02-14 Thread Conrad J. Sabatier
I know I've seen a few other reports of this problem in the lists
recently, and am just wondering if anyone has anything further to
report.

I've been seeing the odd port here and there building libraries with
minor version numbers included in the filenames, whereas the PLIST
specifies only the major version numbers, or vice versa.  This is
causing other ports to fail to link properly, in some cases where the
dependent port is expecting the library with the minor number included,
and others where the dependent port is expecting the library without
the minor number.

Very odd behavior, and it's only cropped up within the last week or
two.  I can't figure out what the heck's going on here.

This is under 7.0-CURRENT on the amd64 arch, by the way.

Anyone?

-- 
Conrad J. Sabatier <[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: Library minor versions conflicting with PLIST with no minor versions

2007-02-14 Thread Kris Kennaway
On Wed, Feb 14, 2007 at 11:32:51PM -0600, Conrad J. Sabatier wrote:
> I know I've seen a few other reports of this problem in the lists
> recently, and am just wondering if anyone has anything further to
> report.
> 
> I've been seeing the odd port here and there building libraries with
> minor version numbers included in the filenames, whereas the PLIST
> specifies only the major version numbers, or vice versa.  This is
> causing other ports to fail to link properly, in some cases where the
> dependent port is expecting the library with the minor number included,
> and others where the dependent port is expecting the library without
> the minor number.
> 
> Very odd behavior, and it's only cropped up within the last week or
> two.  I can't figure out what the heck's going on here.
> 
> This is under 7.0-CURRENT on the amd64 arch, by the way.
> 
> Anyone?

See the heads up I sent the other week.

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


[PATCH] snort-2.6.1.2 libnet dependency pointing to wrong binary

2007-02-14 Thread Garrett Cooper

Cheng-Lung Sung wrote:

Can you apply this patch and try again?
On Wed, Feb 14, 2007 at 06:34:33PM -0800, Garrett Cooper wrote:

Cheng-Lung Sung wrote:

Hi,
   Can you try reinstall ports/net/libnet10 and try again?
On Fri, Feb 09, 2007 at 07:11:03PM -0800, Garrett Cooper wrote:
I looked briefly at the config log and it appears that gcc under 
7-CURRENT doesn't support all the tests available in confdefs.h (C++ 
checks).


I've attached the error logfile as asked by the port message.

-Garrett
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by configure, which was
generated by GNU Autoconf 2.59.  Invocation command line was

 $ ./configure --enable-dynamicplugin --enable-flexresp 
 --with-libnet-includes= --with-libnet-libraries= --with-mysql=no 
 --with-odbc=no --with-postgresql=no --disable-prelude 
 --prefix=/usr/local --build=i386-portbld-freebsd7.0
I did that actually. Multiple times. Or do I need to uninstall both 
libnet10 and it's dependencies, then reinstall snort?


-Garrett





Index: Makefile
===
RCS file: /home/pcvs/ports/security/snort/Makefile,v
retrieving revision 1.81
diff -u -r1.81 Makefile
--- Makefile7 Feb 2007 01:57:04 -   1.81
+++ Makefile15 Feb 2007 03:38:48 -
@@ -77,8 +77,8 @@
 .endif
 BUILD_DEPENDS+=${LIBNET_CONFIG}:${PORTSDIR}/net/libnet10
 CONFIGURE_ARGS+=   --enable-flexresp \
-   --with-libnet-includes=${LIBNET_INCDIR} \
-   --with-libnet-libraries=${LIBNET_LIBDIR}
+   --with-libnet-includes=${LOCALBASE}/includes/libnet10 \
+   --with-libnet-libraries=${LOCALBASE}/lib/libnet10
 .endif
 
 .if defined(WITH_FLEXRESP2)


Unfortunately the patch you provided above doesn't work..

Here's a patch that will work though. Thanks for getting me on the right 
direction with a fix :).


I'm CC'ing the ports@ list just for documentation purposes.

-Garrett
--- MakefileWed Feb 14 22:45:23 2007
+++ /home/gcooper/Makefile  Wed Feb 14 22:46:03 2007
@@ -50,9 +50,9 @@
 .endif
 
 .if defined(WITH_FLEXRESP)
-LIBNET_CONFIG?=/usr/local/bin/libnet-config
+LIBNET_CONFIG?=${LOCALBASE}/bin/libnet10-config
 .elif defined(WITH_FLEXRESP2)
-LIBNET_CONFIG?=/usr/local/bin/libnet11-config
+LIBNET_CONFIG?=${LOCALBASE}/bin/libnet11-config
 .endif
 
 .if exists(${LIBNET_CONFIG})
@@ -77,8 +77,8 @@
 .endif
 BUILD_DEPENDS+=${LIBNET_CONFIG}:${PORTSDIR}/net/libnet10
 CONFIGURE_ARGS+=   --enable-flexresp \
-   --with-libnet-includes=${LOCALBASE}/include \
-   --with-libnet-libraries=${LOCALBASE}/lib/
+   --with-libnet-includes=${LIBNET_INCDIR} \
+   --with-libnet-libraries=${LIBNET_LIBDIR}
 .endif
 
 .if defined(WITH_FLEXRESP2)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Looking for kernel constants / documentation - RTC, wordsize

2007-02-14 Thread Garrett Cooper

Garrett Cooper wrote:

Hello again,
In my effort to continue porting tvtime to freebsd I've come across 
several issues in compiling the app.


One sets of issues are compiling files with Linux specific, mostly 
dealing with RTC. I did a bit of searching, discovered that the mplayer 
dealt with a similar issue and the port author submitted the following 
patch, but I can't seem to find the rtc.h header file:


 #ifdef HAVE_RTC
+#ifdef HAVE_BSDRTC
+#include 
+#define RTC_IRQP_SET RTCIO_IRQP_SET
+#define RTC_PIE_ON RTCIO_PIE_ON
+#else
 #include 
 #endif
+#endif

HAVE_BSDRTC is defined by the configure file. Would anyone know where 
rtc.h is right off-hand?


Another question is function-wise, will I have to worry about the 
details with FreeBSD's RTC vs Linux's RTC (apparently Linux's RTC is 
more defined than FreeBSD's as of 2 years ago, or so some mailing list 
guy said) or can I just ignore them?


Finally, where can I find the constant defined in bits/wordsize.h called 
"__WORDSIZE" (or "WORDSIZE", perhaps)?


Thanks,

-Garrett


I found out about the rtc stuff. It appears that there's a port in 
emulators/rtc that takes care of a majority of the compatibility issues. 
Going to talk to the @hacker guys about the last constant reference.


About wordsize though--does anyone know if and where that might be?

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


Re: Looking for kernel constants / documentation - RTC, wordsize

2007-02-14 Thread Peter Jeremy
On 2007-Feb-14 18:33:04 -0800, Garrett Cooper <[EMAIL PROTECTED]> wrote:
>Finally, where can I find the constant defined in bits/wordsize.h called 
>"__WORDSIZE" (or "WORDSIZE", perhaps)?

I can't find any "__WORDSIZE" (or "WORDSIZE") in FreeBSD sources.
Maybe __LONG_BIT, LONG_BIT, __WORD_BIT or WORD_BIT from 
would work.

-- 
Peter Jeremy


pgp0Hsg0xjrb9.pgp
Description: PGP signature


Re: Looking for kernel constants / documentation - RTC, wordsize

2007-02-14 Thread Garrett Cooper

Peter Jeremy wrote:

On 2007-Feb-14 18:33:04 -0800, Garrett Cooper <[EMAIL PROTECTED]> wrote:
Finally, where can I find the constant defined in bits/wordsize.h called 
"__WORDSIZE" (or "WORDSIZE", perhaps)?


I can't find any "__WORDSIZE" (or "WORDSIZE") in FreeBSD sources.
Maybe __LONG_BIT, LONG_BIT, __WORD_BIT or WORD_BIT from 
would work.


Hmmm... thanks for the heads up--I'll give it a shot :).
-Garrett

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