Re: how do i suggest a program for your ports collection?
Thomas, good day.
Sun, Jan 23, 2011 at 08:25:23AM +0100, Thomas Dettbarn wrote:
is there some formal way of suggesting a program for your ports
collection?
Yes, it is described in
http://www.freebsd.org/doc/en/books/porters-handbook/book.html#PORTING-SUBMITTING
The thing is, i wrote this hex editor:
http://www.freshmeat.net/projects/dhex which i am rather proud of.
and now i would like to spread it.
You should create the port by yourself and become the maintainer
or you should find some other person who will do it (and become the
maintainer of the FreeBSD port for your software).
however, i am an openbsd user. so i don't know how to exactly make a
port for freebsd.
There is a Porter's Handbook,
http://www.freebsd.org/doc/en/books/porters-handbook/book.html
but if you don't want to port the stuff (or have not enough time),
I should say that having used DHEX for a couple of minutes I should
say that it is a good tool for my ocassional hex-related work, so
I can port and maintain it or I can help you to port it.
And may I also suggest the attached patch to the DHEX Makefile:
it will allow people to set their own values of CC, CFLAGS, CPPFLAGS
and LDFLAGS. For example, FreeBSD has the stock settings for the
CFLAGS and currently we can choose the compilers to be at least
gcc or clang. The stuff is described in
http://www.freebsd.org/doc/en/books/porters-handbook/book.html#DADS-CC
and
http://www.freebsd.org/doc/en/books/porters-handbook/book.html#DADS-CFLAGS
Hope that sheds some light on the topic.
And the additional nit: compiling dhex on the FreeBSD 9.x shows some
signedness warnings:
{{{
output.c: In function 'printmainmenu':
output.c:410: warning: pointer targets in initialization differ in signedness
output.c:411: warning: pointer targets in initialization differ in signedness
output.c:412: warning: pointer targets in initialization differ in signedness
output.c:413: warning: pointer targets in initialization differ in signedness
output.c:414: warning: pointer targets in initialization differ in signedness
output.c:415: warning: pointer targets in initialization differ in signedness
output.c:416: warning: pointer targets in initialization differ in signedness
output.c:417: warning: pointer targets in initialization differ in signedness
output.c:418: warning: pointer targets in initialization differ in signedness
output.c:419: warning: pointer targets in initialization differ in signedness
output.c:422: warning: pointer targets in initialization differ in signedness
output.c:423: warning: pointer targets in initialization differ in signedness
output.c:424: warning: pointer targets in initialization differ in signedness
output.c:425: warning: pointer targets in initialization differ in signedness
output.c:426: warning: pointer targets in initialization differ in signedness
output.c:427: warning: pointer targets in initialization differ in signedness
output.c:428: warning: pointer targets in initialization differ in signedness
output.c:429: warning: pointer targets in initialization differ in signedness
output.c:430: warning: pointer targets in initialization differ in signedness
output.c:431: warning: pointer targets in initialization differ in signedness
main.c: In function 'main':
main.c:450: warning: pointer targets in passing argument 3 of 'gotomask' differ
in signedness
main.c:459: warning: pointer targets in passing argument 4 of 'searchmask'
differ in signedness
main.c:509: warning: pointer targets in passing argument 3 of 'searchfor'
differ in signedness
configfile.c: In function 'readconfigfile':
configfile.c:183: warning: pointer targets in passing argument 2 of 'getcolors'
differ in signedness
configfile.c:184: warning: pointer targets in passing argument 2 of
'configkeytab' differ in signedness
}}}
I am not sure if they are harmful or harmless, but I usually it worth
to consider compiler's warnings. Don't know if you had seen them
on the systems you were testing/using DHEX, so reproducing them there.
--
Eygene Ryabinkin,,,^..^,,,
[ Life's unfair - but root password helps! | codelabs.ru ]
[ 82FE 06BC D497 C0DE 49EC 4FF0 16AF 9EAE 8152 ECFB | freebsd.org ]
--- Makefile.orig 2011-01-23 11:09:21.676581518 +0300
+++ Makefile 2011-01-23 11:18:17.417579047 +0300
@@ -1,11 +1,12 @@
-CC= gcc
-LDFLAGS= -L/usr/lib -L/usr/local/lib -L/usr/lib/ncurses -L/usr/local/lib/ncurses
-CPPFLAGS= -I/usr/include -I/usr/local/include -I/usr/include/ncurses -I/usr/local/include/ncurses
-CFLAGS= -O3 -Wall -std=c99
+CC?= gcc
+LDFLAGS?= -L/usr/lib -L/usr/local/lib -L/usr/lib/ncurses -L/usr/local/lib/ncurses
+CPPFLAGS?= -I/usr/include -I/usr/local/include -I/usr/include/ncurses -I/usr/local/include/ncurses
+CFLAGS?= -O3
+CFLAGS+= -Wall -std=c99
#CFLAGS+= -ffunction-sections -fdata-sections
#LDFLAGS+= --gc-sections
LIBS= -lncurses
-DESTDIR= /usr/local/bin
+DESTDIR?= /usr/local/bin
OFILES=buffers.o input.o output.o
Re: how do i suggest a program for your ports collection?
I should say that having used DHEX for a couple of minutes I should say that it is a good tool for my ocassional hex-related work, so I can port and maintain it or I can help you to port it. like i said: i am mostly an openbsd user, so i'd REALLY appreciate it if you could become the ports maintainer. of course, i could always set up a virtual machine, install freebsd in there. however, since i wouldn't use it very often, i fear for the port's quality. And may I also suggest the attached patch to the DHEX Makefile: thank you very much, i'll have a look at it. And the additional nit: compiling dhex on the FreeBSD 9.x shows some signedness warnings: I am not sure if they are harmful or harmless, but I usually it worth yes, i saw them. whenever i added -pendantic. currently, those warnings are just a nuisance. but i'll tackle them in the next release. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: how do i suggest a program for your ports collection?
On 23 January 2011 09:04, Thomas Dettbarn det...@dettus.net wrote: however, i am an openbsd user. so i don't know how to exactly make a port for freebsd. I'll do it if you don't want to learn for one port? thank you very much. i really appreciate that. however, eygene ryabinkin was slightly faster than you. ;) No problem. Hope it goes well! Wow, I've just remembered where I recognised your name You're the author of the World's Nastiest Linux Distribution aren't you??? Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: how do i suggest a program for your ports collection?
Wow, I've just remembered where I recognised your name You're the author of the World's Nastiest Linux Distribution aren't you??? guilty as charged ;) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Xournal: Please, help me with my first port
On 22 January 2011 16:28, Chris Rees utis...@gmail.com wrote: On 22 January 2011 15:13, Jan Henrik Sylvester m...@janh.de wrote: The DATADIR whines are addressed in this patch, have a look: http://www.bayofrum.net/~chris/patches/xournal-pkg-plist.diff Thanks, but since the port does not honor DATADIR, it should not be there -- or the DATADIR case must be fixed first. Addressed below. That's all I had time to look at at the moment, perhaps others can help! Alright, came back and now the patch has the desktop-install target defined instead of using the post-install. This is reflected in the patch linked above ^^^ Thanks, I was looking for something like that, but it should be INSTALL_TARGET= install desktop-install, because desktop-install does not include install. Certainly. Looks as though we should define the do-install: target rather than rely on the provided ones; this means that we can make the port DATADIR safe. I'll look shortly. I've stuck it in my Tinderbox for testing, follow it here: http://tinderbox.bayofrum.net/index.php?action=describe_portid=196 Thanks! I do not know Tinderbox enough to understand, why your mkfontscale build tried to install an outdated version of freetype2. Take a look at the new patch so far; I'm still working on Busybox at the moment, so I'm afraid I can't step too much more through it, but it should give you a little more to work on. I've tidied the REINPLACE lines for you too. http://www.bayofrum.net/~chris/patches/xournal.diff DATADIR-safe appears unnecessary according to the conversation http://www.mailinglistarchive.com/freebsd-ports@freebsd.org/msg08234.html , so I think that this port should be fine as is right now. Try submitting it, it should be fine. Cheers! Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: how do i suggest a program for your ports collection?
Thomas Dettbarn det...@dettus.net wrote: hello. is there some formal way of suggesting a program for your ports collection? the thing is, i wrote this hex editor: http://www.freshmeat.net/projects/dhex which i am rather proud of. and now i would like to spread it. however, i am an openbsd user. so i don't know how to exactly make a port for freebsd. Nice program! I'll create a port for it if you like. Emanuel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: how do i suggest a program for your ports collection?
On 23 January 2011 12:18, Emanuel Haupt eha...@freebsd.org wrote: Thomas Dettbarn det...@dettus.net wrote: hello. is there some formal way of suggesting a program for your ports collection? the thing is, i wrote this hex editor: http://www.freshmeat.net/projects/dhex which i am rather proud of. and now i would like to spread it. however, i am an openbsd user. so i don't know how to exactly make a port for freebsd. Nice program! I'll create a port for it if you like. Emanuel As I was, a little too late: http://lists.freebsd.org/pipermail/freebsd-ports/2011-January/065507.html Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Xournal: Please, help me with my first port
On 01/23/2011 11:42, Chris Rees wrote:
Take a look at the new patch so far; I'm still working on Busybox at
the moment, so I'm afraid I can't step too much more through it, but
Just a question about what you did so far: Why the
CONFIGURE_ARGS+=--prefix=${PREFIX}? I have tested with a different
PREFIX before and it was successful -- that is what the second part of
the REINPLACE accomplished. What does your line improve?
Or is it a first step, if I wanted to make the port DATADIR-safe?
it should give you a little more to work on. I've tidied the REINPLACE
lines for you too.
Thanks, that is better to read.
http://www.bayofrum.net/~chris/patches/xournal.diff
DATADIR-safe appears unnecessary according to the conversation
http://www.mailinglistarchive.com/freebsd-ports@freebsd.org/msg08234.html
, so I think that this port should be fine as is right now. Try
submitting it, it should be fine.
That is what I thought and since I would have to patch the source (at
least main.c) and the Mafile(s), I did not consider it to be worse it,
since I do not believe anyone will ever use a different DATADIR for this
port.
That leads to my second question: Is your proposal to replace the
share/xournal in pkg-plist by %%DATADIR%% correct although the port
is not DATADIR-safe? Currently, if DATADIR is set the port ends up to be
installed with wrong +CONTENTS, since the installation ignores DATADIR
being set, but +CONTENTS uses it.
I believe that it is correct what portlint says: If and only if your
port is DATADIR-safe (that is, a user can override DATADIR when building
this port and the port will still work correctly) consider using DATADIR
macro; if you are unsure if this port is DATADIR-safe, then ignore this
warning. Thus, there should not be DATADIR in my pkg-plist as long as
the port is not DATADIR-safe.
Cheers,
Jan Henrik
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Xournal: Please, help me with my first port
On 23 January 2011 16:24, Jan Henrik Sylvester m...@janh.de wrote:
On 01/23/2011 11:42, Chris Rees wrote:
Take a look at the new patch so far; I'm still working on Busybox at
the moment, so I'm afraid I can't step too much more through it, but
Just a question about what you did so far: Why the
CONFIGURE_ARGS+=--prefix=${PREFIX}? I have tested with a different PREFIX
before and it was successful -- that is what the second part of the
REINPLACE accomplished. What does your line improve?
Or is it a first step, if I wanted to make the port DATADIR-safe?
it should give you a little more to work on. I've tidied the REINPLACE
lines for you too.
Thanks, that is better to read.
http://www.bayofrum.net/~chris/patches/xournal.diff
DATADIR-safe appears unnecessary according to the conversation
http://www.mailinglistarchive.com/freebsd-ports@freebsd.org/msg08234.html
, so I think that this port should be fine as is right now. Try
submitting it, it should be fine.
That is what I thought and since I would have to patch the source (at least
main.c) and the Mafile(s), I did not consider it to be worse it, since I do
not believe anyone will ever use a different DATADIR for this port.
That leads to my second question: Is your proposal to replace the
share/xournal in pkg-plist by %%DATADIR%% correct although the port is
not DATADIR-safe? Currently, if DATADIR is set the port ends up to be
installed with wrong +CONTENTS, since the installation ignores DATADIR being
set, but +CONTENTS uses it.
I believe that it is correct what portlint says: If and only if your port
is DATADIR-safe (that is, a user can override DATADIR when building this
port and the port will still work correctly) consider using DATADIR macro;
if you are unsure if this port is DATADIR-safe, then ignore this warning.
Thus, there should not be DATADIR in my pkg-plist as long as the port is not
DATADIR-safe.
Perhaps you should ignore the portlint warnings and leave it as
share/xournal then.
If you stick up a PR with it attached, it looked absolutely fine by me
either way!
Chris
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Xournal: Please, help me with my first port
On 01/23/2011 17:35, Chris Rees wrote:
On 23 January 2011 16:24, Jan Henrik Sylvesterm...@janh.de wrote:
On 01/23/2011 11:42, Chris Rees wrote:
Take a look at the new patch so far; I'm still working on Busybox at
the moment, so I'm afraid I can't step too much more through it, but
Just a question about what you did so far: Why the
CONFIGURE_ARGS+=--prefix=${PREFIX}? I have tested with a different PREFIX
before and it was successful -- that is what the second part of the
REINPLACE accomplished. What does your line improve?
Or is it a first step, if I wanted to make the port DATADIR-safe?
Should I include that line?
(I have just retested: The port installs to the correct PREFIX without
that line and seems to be working fine.)
I believe that it is correct what portlint says: If and only if your port
is DATADIR-safe (that is, a user can override DATADIR when building this
port and the port will still work correctly) consider using DATADIR macro;
if you are unsure if this port is DATADIR-safe, then ignore this warning.
Thus, there should not be DATADIR in my pkg-plist as long as the port is not
DATADIR-safe.
Perhaps you should ignore the portlint warnings and leave it as
share/xournal then.
Thanks.
BTW: I am going to ignore your capitalization of makefile in the first
line, too, since it is non-capitalized in the porters handbook and 20210
over 240 ports go for the non-capitalized variant.
Cheers,
Jan Henrik
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Busybox update, call for testers on amd64
Hi all, I've finished updating busybox to 1.18.1, but I need someone on amd64 to test it please! It's at: http://www.bayofrum.net/~chris/patches/busybox-1.13-1.18.diff or http://www.bayofrum.net/~chris/patches/busybox-1.18.shar Cheers! Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Busybox update, call for testers on amd64
Chris, good day.
Sun, Jan 23, 2011 at 04:38:36PM +, Chris Rees wrote:
I've finished updating busybox to 1.18.1, but I need someone on amd64
to test it please!
It doesn't build on the 9-CURRENT, because of new utmpx:
{{{
CC libbb/messages.o
In file included from libbb/messages.c:51:
/usr/include/utmp.h:2:2: error: #error utmp.h has been replaced by utmpx.h
libbb/messages.c:59:2: error: #error unknown path to wtmp file
libbb/messages.c:65: error: expected expression before 'char'
}}}
It was amd64 machine, but the error will show up for i386
and others: bb still uses utmp.h that was deprecated starting
from 9.x.
Seems like that the fair number of files should be adopted
to 9.x:
{{{
./libbb/messages.c:#include utmp.h
./libbb/utmp.c:#include utmp.h
./loginutils/login.c:# include utmp.h /* USER_PROCESS */
./loginutils/getty.c:# include utmp.h /* LOGIN_PROCESS */
./loginutils/getty.c:#ifdef LOGIN_PROCESS/* defined in
System V utmp.h */
./coreutils/who.c:#include utmp.h
./init/init.c:# include utmp.h /* DEAD_PROCESS */
./init/halt.c:#include utmp.h
./miscutils/last.c:#include utmp.h
./miscutils/runlevel.c:#include utmp.h
./miscutils/last_fancy.c:#include utmp.h
./miscutils/wall.c:#include utmp.h
./networking/telnetd.c:# include utmp.h /* LOGIN_PROCESS */
}}}
--
Eygene Ryabinkin,,,^..^,,,
[ Life's unfair - but root password helps! | codelabs.ru ]
[ 82FE 06BC D497 C0DE 49EC 4FF0 16AF 9EAE 8152 ECFB | freebsd.org ]
pgpIlSoTFLBE7.pgp
Description: PGP signature
Re: Xournal: Please, help me with my first port
If prefix works without the CONFIGURE_ARGS then take it out. I put that line
in when experimenting with making it datadir safe.
The capitalization is my one-person campaign, so I fully expected it to be
ignored!
Chris
Sorry for top-posting, Android won't let me quote, but K-9 can't yet do
threading.
On 23 Jan 2011 16:59, Jan Henrik Sylvester m...@janh.de wrote:
On 01/23/2011 17:35, Chris Rees wrote:
On 23 January 2011 16:24, Jan Henrik Sylvesterm...@janh.de wrote:
On 01/23/2011 11:42, Chris Rees wrote:
Take a look at the new patch so far; I'm still working on Busybox at
the moment, so I'm afraid I can't step too much more through it, but
Just a question about what you did so far: Why the
CONFIGURE_ARGS+=--prefix=${PREFIX}? I have tested with a different
PREFIX
before and it was successful -- that is what the second part of the
REINPLACE accomplished. What does your line improve?
Or is it a first step, if I wanted to make the port DATADIR-safe?
Should I include that line?
(I have just retested: The port installs to the correct PREFIX without
that line and seems to be working fine.)
I believe that it is correct what portlint says: If and only if your
port
is DATADIR-safe (that is, a user can override DATADIR when building this
port and the port will still work correctly) consider using DATADIR
macro;
if you are unsure if this port is DATADIR-safe, then ignore this
warning.
Thus, there should not be DATADIR in my pkg-plist as long as the port is
not
DATADIR-safe.
Perhaps you should ignore the portlint warnings and leave it as
share/xournal then.
Thanks.
BTW: I am going to ignore your capitalization of makefile in the first
line, too, since it is non-capitalized in the porters handbook and 20210
over 240 ports go for the non-capitalized variant.
Cheers,
Jan Henrik
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Xournal: Please, help me with my first port
Thanks for all your suggestions! Cheers, Jan Henrik ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: how do i suggest a program for your ports collection?
On Sun 23 Jan 2011 at 00:25:47 PST Eygene Ryabinkin wrote: Thomas, good day. Sun, Jan 23, 2011 at 08:25:23AM +0100, Thomas Dettbarn wrote: is there some formal way of suggesting a program for your ports collection? Thanks for porting this so quickly, Eygene. One small request, however, for you or Thomas. Can you add a manpage? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: how do i suggest a program for your ports collection?
Quoth Charlie Kester on Sunday, 23 January 2011: On Sun 23 Jan 2011 at 00:25:47 PST Eygene Ryabinkin wrote: Thomas, good day. Sun, Jan 23, 2011 at 08:25:23AM +0100, Thomas Dettbarn wrote: is there some formal way of suggesting a program for your ports collection? Thanks for porting this so quickly, Eygene. One small request, however, for you or Thomas. Can you add a manpage? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org Indeed. When I run it and pass a filename as an argument, I get just a blank screen. The only way I could get ouit was Ctrl-C. dhex -h didn't tell me much, either. -- Sterling (Chip) Camden | sterl...@camdensoftware.com | 2048D/3A978E4F http://chipsquips.com | http://camdensoftware.com | http://chipstips.com pgpuSG1R44GtO.pgp Description: PGP signature
New port math/sprng: Need some help, please
I created a port for SPRNG version 2, the Scalable Parallel Pseudo
Random Number Generators Library ( http://sprng.cs.fsu.edu/ ).
It builds and installs but it is not usable so far because of some
problems with the method of building shared libraries.
The sources seem to be incomplete in some way. They only build static
libraries and there is no install target in the code. I had to patch the
sources on several places to get it compiled.
Now there remain several problems with the installed libraries 'libsprng*':
(1) After installation with ${INSTALL_LIB} they do not have any symbols
any more.
nm /usr/ports/math/sprng/work/sprng2.0/lib/libsprng.so.2.0
shows symbols built in, the next does not
nm /usr/local/lib/libsprng.so.2.0
(2) The fortran stuff is not build in correctly. SPRNG has two scripts
to test the installed sprng code, 'checksprng' and 'timesprng'. Both
give correct results for the C interface and both fail for the fortran
interface.
Probably there a more issues with the port and patches :-(
I have only little experience in creating ports and almost no skills in
C/C++ programming, so I could really need some help.
Thanks in advance,
Rainer Hurling
# This is a shell archive. Save it in a file, remove anything before
# this line, and then unpack it by entering sh file. Note, it may
# create directories; files and directories will be owned by you and
# have default permissions.
#
# This archive contains:
#
# Makefile
# distinfo
# files
# files/patch-SRC_make.INTEL
# files/patch-SRC_sprng_Makefile
# files/patch-EXAMPLES_checkpoint-simple.c
# files/patch-EXAMPLES_pi-simple.c
# files/patch-EXAMPLES_spawn.c
# files/patch-TESTS_chisquare.c
# files/patch-TESTS_collisions.c
# files/patch-TESTS_coupon.c
# files/patch-TESTS_maxt.c
# files/patch-TESTS_poker.c
# files/patch-TESTS_random__walk.c
# files/patch-TESTS_sum.c
# files/patch-TESTS_init__tests.c
# files/patch-SRC_primes__32.c
# files/patch-SRC_primes__64.c
# files/patch-EXAMPLES_checkpoint.c
# files/patch-TESTS_stirling.c
# files/patch-TESTS_Makefile
# files/patch-TESTS_communicate.c
# files/patch-TESTS_metropolis.c
# files/patch-SRC_pmgcg_pmlcg.c
# pkg-descr
# pkg-plist
# pkg-message
#
echo x - Makefile
sed 's/^X//' Makefile 'b67911656ef5d18c4ae36cb6741b7965'
X# Ports collection makefile for: sprng
X# Date created:23 January 2011
X# Whom:Rainer Hurling rhur...@gwdg.de
X#
X# $FreeBSD$
X
XPORTNAME= sprng
XPORTVERSION= 2.0b
XCATEGORIES=math parallel
XMASTER_SITES= http://sprng.fsu.edu/Version2.0/
XDISTNAME= ${PORTNAME}${PORTVERSION}
X
XMAINTAINER=rhur...@gwdg.de
XCOMMENT= The Scalable Parallel Random Number Generators Library
X
XLIB_DEPENDS= pthread.20:${PORTSDIR}/devel/pth \
X gmp.10:${PORTSDIR}/math/gmp \
X mpich.2:${PORTSDIR}/net/mpich2
X
XWRKSRC=${WRKDIR}/${PORTNAME}2.0
X
XUSE_LDCONFIG= yes
XUSE_GCC= 4.4+
X
X.include bsd.port.pre.mk
X
Xpost-patch:
X# [Activate MPI usage]
X @${REINPLACE_CMD} -e 's|#MPIDEF = -DSPRNG_MPI|MPIDEF = -DSPRNG_MPI|' \
X ${WRKSRC}/make.CHOICES
X# [Activate GMP usage]
X @${REINPLACE_CMD} -e 's|GMPLIB = -lgmp|GMPLIB = -L/usr/local/lib
-lgmp|' \
X ${WRKSRC}/make.CHOICES
X @${REINPLACE_CMD} -e 's|mpi.h|mpi.h|' \
X ${WRKSRC}/EXAMPLES/pi-simple_mpi.c \
X ${WRKSRC}/TESTS/fft.c \
X ${WRKSRC}/TESTS/sum.c
X @${FIND} ${WRKSRC} -name *.c | ${XARGS} ${REINPLACE_CMD} -e \
X 's|void main|int main|g'
X# [Workaround] poker.c:19: error: 'index' redeclared as different kind
of symbol
X @${REINPLACE_CMD} -e 's|index|indexx|' \
X ${WRKSRC}/TESTS/poker.c
X
Xpost-build:
X @${REINPLACE_CMD} -e 's|./||' \
X ${WRKSRC}/checksprng \
X ${WRKSRC}/timesprng
X @${REINPLACE_CMD} -e 's| gen| ${DATADIR}/gen|' \
X ${WRKSRC}/checksprng \
X ${WRKSRC}/timesprng
X
Xdo-install:
X ${MKDIR} ${DATADIR}
X ${INSTALL_LIB} ${WRKSRC}/lib/libsprng.a ${PREFIX}/lib
X ${INSTALL_LIB} ${WRKSRC}/lib/libsprngtest.a ${PREFIX}/lib
X ${INSTALL_LIB} ${WRKSRC}/lib/libsprng.so.2.0 ${PREFIX}/lib
X ${INSTALL_LIB} ${WRKSRC}/lib/libsprngtest.so.2.0 ${PREFIX}/lib
X ${LN} -sf ${PREFIX}/lib/libsprng.so.2.0 ${PREFIX}/lib/libsprng.so.2
X ${LN} -sf ${PREFIX}/lib/libsprng.so.2 ${PREFIX}/lib/libsprng.so
X ${LN} -sf ${PREFIX}/lib/libsprngtest.so.2.0
${PREFIX}/lib/libsprngtest.so.2
X ${LN} -sf ${PREFIX}/lib/libsprngtest.so.2 ${PREFIX}/lib/libsprngtest.so
X (cd ${WRKSRC}/include ${INSTALL_DATA} sprng.h sprng_f.h interface.h
${PREFIX}/include)
X ${INSTALL} ${WRKSRC}/checksprng ${PREFIX}/bin
X ${INSTALL}
Re: ports/154125: [MAINTAINER] sysutils/lsof: update to 4.85A
Hi, Before I committed this update, I have tested lsof 4.85A on 8.1 and it does work fine. I don't think it is reasonable to remove the patch and prevent 8.1 users from using lsof. At least, tinderbox running 8.1 requires lsof to work. hih Regards, sunpoet On Sun, Jan 23, 2011 at 7:43 AM, Larry Rosenman l...@lerctr.org wrote: PLEASE revert the configure patch. It is NOT supported by the upstream author, intentionally as he's never run the test suite against 8.1. On Sat, January 22, 2011 2:46 pm, sunp...@freebsd.org wrote: Synopsis: [MAINTAINER] sysutils/lsof: update to 4.85A State-Changed-From-To: open-closed State-Changed-By: sunpoet State-Changed-When: Sat Jan 22 20:46:15 UTC 2011 State-Changed-Why: Committed, with minor changes. Thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=154125 -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 -- Sunpoet Po-Chuan Hsieh sunpoet at sunpoet.net sunpoet at FreeBSD.org 4096R/CC57E36B 8AD8 68F2 7D2B 0A10 7E9B 8CC0 DC44 247E CC57 E36B http://people.FreeBSD.org/~sunpoet/pgpkeys.txt ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: ports/154125: [MAINTAINER] sysutils/lsof: update to 4.85A
On 1/23/2011 10:32 PM, Sunpoet Po-Chuan Hsieh wrote: Hi, Before I committed this update, I have tested lsof 4.85A on 8.1 and it does work fine. I don't think it is reasonable to remove the patch and prevent 8.1 users from using lsof. At least, tinderbox running 8.1 requires lsof to work. hih fwiw, lsof is optional for tinderbox, the port just happens to list it unconditionally. -- 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354 VP Apache Infrastructure; Member, Apache Software Foundation Committer,FreeBSD Foundation Consultant, P6M7G8 Inc. Sr. System Admin, Ridecharge Inc. Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
