Re: More libgmp leftovers due to indirect dependencies
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Jan Henrik Sylvester wrote:
| math/libqalculate and print/lilypond both link libgmp.so.X, but have not
| been bumped with the libgmp.so.7->libgmp.so.8 update as they do not list
| the dependency.
|
| math/libqalculate pulls in libgmp via libcln and print/lilypond via
| libguile, thus the default package will always depend on libgmp.
|
| Both should have their PORTREVISION bumped and
| gmp.8:${PORTSDIR}/math/libgmp4 added to LIB_DEPENDS not to be missed
| next time.
print/lilypond fixed, thanks!
|
| Cheers,
| Jan Henrik
|
- --
Pietro Cerutti
g...@freebsd.org
PGP Public Key:
http://gahr.ch/pgp
+-+
| How do you get |
|that backwards b?|
+-+
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.11 (FreeBSD)
iEYEAREKAAYFAkoRpe0ACgkQwMJqmJVx9451UQCdGcS06fjU6HpV3YBZSAzhqBpr
AucAniymFT5gbwmJcogLyqTYXe2o8jvp
=eQEX
-END PGP SIGNATURE-
___
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: My ports.
On 2010-Feb-22, 08:48, Marcelo Araujo wrote: > Hi guys, > > There are some ports that I haven't interested and neither used anymore, > so I'm here to check if there is anyone that would be interested to push > them and maintain those updated before set up those to po...@. > > Please, send me a list of ports that you want and I'm gonna release to you > or fell free to take it by yourself. > I'll take these. x11-toolkits/fox12 x11-toolkits/fox14 x11-toolkits/fox16 -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpkUTqc9JvKH.pgp Description: PGP signature
Re: My ports.
On 2010-Mar-11, 15:00, Marcelo wrote: > Hi dear Pietro, Hi Marcelo, > Which one do you intend to catch it up in your hands? > > I'll take these. > > > > x11-toolkits/fox12 > > x11-toolkits/fox14 > > x11-toolkits/fox16 Uhm, eh? -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpQxGWFoHgdu.pgp Description: PGP signature
Re: My ports.
On 2010-Mar-11, 15:59, Marcelo wrote: > Please, go ahead, they need an update urgently. > Thanks to care on they. Actually, I'm thinking about dropping support for fox12 :) I'll DEPRECATE it and remove it in a few weeks. In the process, I'll drop x11-toolkits/fxscintilla-fox12, x11-toolkits/ruby-fox12, and I'll update editors/mondrian to use fox16. That should happen seemingly painlessly :) > > > 2010/3/11 Pietro Cerutti > > > On 2010-Mar-11, 15:00, Marcelo wrote: > > > Hi dear Pietro, > > > > Hi Marcelo, > > > > > Which one do you intend to catch it up in your hands? > > > > > > I'll take these. > > > > > > > > x11-toolkits/fox12 > > > > x11-toolkits/fox14 > > > > x11-toolkits/fox16 > > > > Uhm, eh? > > > > -- > > Pietro Cerutti > > The FreeBSD Project > > g...@freebsd.org > > > > PGP Public Key: > > http://gahr.ch/pgp > > > > > > -- > Marcelo Araujo > ara...@freebsd.org -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpHsd4tSp3k8.pgp Description: PGP signature
Re: [RFC] Reduce namespace pollution on zlib.h
On 2010-Mar-27, 02:51, Dag-Erling Smørgrav wrote: > Xin LI writes: > > So... May I consider my import just exposed some existing bugs in other > > applications and we don't want to workaround these issues? > > Correct. Just to make it clear so that everyone knows how we're going to handle this: are you (src people) going to commit a fix to unexpose LFS crap or are we (ports people) supposed to fix each and every single port that supposes to be on Linux? The attentive reader will note a bias towards the former :) -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpBDuTIcSGH3.pgp Description: PGP signature
Re: [RFC] Reduce namespace pollution on zlib.h
On 2010-Mar-31, 03:41, Xin LI wrote: > I will merge an upstream change from zlib, which basically unexpose LFS > stuff on FreeBSD, and I plan to keep the off_t bits == 64. However, I would > highly recommend ports maintainers to push upstream fix for LFS64 definition > removal since they are wrong on FreeBSD Sounds great, thanks! > > On Mar 31, 2010 3:30 AM, "Pietro Cerutti" wrote: > > On 2010-Mar-27, 02:51, Dag-Erling Smørgrav wrote: > > Xin LI writes: > > > So... ... > Just to make it clear so that everyone knows how we're going to handle > this: are you (src people) going to commit a fix to unexpose LFS crap > or are we (ports people) supposed to fix each and every single port > that supposes to be on Linux? > > The attentive reader will note a bias towards the former :) > > -- > Pietro Cerutti > The FreeBSD Project > g...@freebsd.org > > PGP Public Key: > http://gahr.ch/pgp > ___ > 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" -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpbtgmgIxofi.pgp Description: PGP signature
Re: Aqsis has incorrect dependency fltk-threads
On 2010-Mar-31, 20:48, Jared Barneck wrote: > Hey all, > > I searched the forum and didn't see any mention of Aqsis in recent posts. I > downloaded ports just now (which I also see is not recommended to a lot of > big changes) though I am not sure this is related to those big changes or not. > > Anyway, I was building Aqsis and it failed to build due to the dependency on > fltk-threads. Fixed, thanks! -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpu3M9YEFiau.pgp Description: PGP signature
Re: databases/php5-odbc vs. libiodbc
On 2010-Jun-15, 19:21, Kyryll A Mirnenko aka Mirya wrote: > Currently the databases/php5-odbc PHP extension is hardcoded to be compiled > with unixODBC backend, so the users that have libiodbc installed (as a > dependency of kde4 ports, for ex.) can't installed the first 'cause those two > ODBC ports conflict with each other. > The php-odbc configure script however says (./configure --help) it can be > compiled with iODBC support (--with-iodbc=/usr/local), but for some reason > simply replacing the configure script arguments for the port (with libiodbc > installed from ports) result in nothing being done: the configure script > creates the Makefile with empty target, so nothing is built actually. > Did anyone have success before with building php5-odbc lniked to iodbc > backend? I've been able have the php5-odbc extension link against libiodbc by applying this patch [1] to lang/php5. I haven't conducted any run-tests, though. Please feel free to report success / failure :) [1] http://people.freebsd.org/~gahr/Makefile.ext.diff -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpIcen8SpxEk.pgp Description: PGP signature
Re: FreeBSD Port: mysql-gui-tools-5.0r14_3
On 2010-Aug-01, 18:33, Tadeusz Raczkowski wrote: > mysql-gui-tools seems to have a dependency on mysql version 5.0. Just > wondering if it is possible to build mysql-gui-tools for mysql version > 5.1! Hi Tadeusz, sorry for the delay getting back to you! I've just committed a patch to allow the use of a mysql version other than 5.0. I have tested with 5.1; it builds & runs just fine! Thanks for your suggestion! -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgptPiojfB5M8.pgp Description: PGP signature
FOX ToolKit changes
Hi all, as you have probably noticed (I broke the INDEX twice in the last 24h [tnx pav@ for promptly fixing it!]), I have committed a set of changes to the ports related to the FOX ToolKit. Here's a brief summary. = Added ports = - x11-toolkits/fox17 . introduction to the new development branch, version 1.7.21 - editors/fxite . a cross platform editor, built on top of FXScintilla and FOX 16 = Modified ports = - x11-toolkits/fxscintilla . updated to latest version (2.11.0) . dropped support for FOX 12 (removed) and FOX 14 (unsupported) - x11-toolkits/fox14 . updated CONFLICTS to reflect the removal of FOX 12 and addition of FOX 17 - x11-toolkits/ruby-fox16 . updated CONFLICTS to reflect the removal of FOX 12 and addition of FOX 17 . PORTREVISION bump to chase FXScintilla's shlib bump - x11-fm/xfe . updated to the latest version (1.32.1) . now maintained by me = Removed ports = - x11-toolkits/fox12 - x11-toolkits/fxscintilla-fox12 - x11-toolkits/fxscintilla-fox14 - x11-toolkits/ruby-fox12 - editors/mondrian - devel/freeride - devel/freebase Enjoy the Fox Toolkit at http://www.fox-toolkit.org/ :) -- Pietro Cerutti g...@gahr.ch PGP Public Key: http://gahr.ch/pgp pgpP1VnGtbwoG.pgp Description: PGP signature
Re: cvs commit: ports/mail/procmail Makefile
On 2011-Aug-30, 13:45, Beech Rintoul wrote: > On Tuesday 30 August 2011 11:01:18 Ted Hatfield wrote: > > On Tue, 30 Aug 2011, Matthias Andree wrote: > > > Am 30.08.2011 19:57, schrieb Mark Linimon: > > >> On Tue, Aug 30, 2011 at 07:44:12PM +0200, Matthias Andree wrote: > > >>> It only warns, it does not prevent fresh installs on systems that don't > > >>> have the same port/package already installed. > > >> > > >> "code, not policy" ... ? > > > > > > Well... is _is_ policy and meant as such. We make decisions for ports > > > users all the time, and this is no exception. > > > > If procmail has no ongoing security issues and it compiles and installs > > with no problems what's the reasoning behind removing it from the ports > > tree? > > > > As far as I can see the reasoning advocated at this time is that > > procmail hasn't been in active development since 2001. Shouldn't that > > be seen as a sign of stability. > > > > I'm not a software developer so maybe I'm missing something obvious > > about this situation. Feel free to educate/convice me that I should > > make the effort to switch from procmail to maildrop. > > > > I've been using procmail now for 16 years and I'm very happy with it's > > performance. Moving to maildrop would be a significant amount of effort > > for both me and my users. > > > > Ted Hatfield > > I second that, I also have it installed in several places and haven't had any > problems. I don't want to have to move to another app just because someone > feels like deprecating a mature port. I think the old addage "if it ain't > broke" applies here. +1 here! Please stop this deprecation madness and stop thinking that our users are a bunch of stupids. I use procmail daily and I don't have any problems with it. If we want to deprecate ports basing on the potential damage caused by their misuse, I'd start with everything prefixed with lang/ or devel/. -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpRn9efsT6lj.pgp Description: PGP signature
HEADS UP --- Update to x11-toolkits/fltk coming
Hi, you're receiving this email because one of your ports depends on x11-toolkits/fltk, according to $ grep fltk /usr/ports/INDEX-9 | cut -d '|' -f 6 | sort | uniq I'm preparing an update to fltk-1.3.0 and I would like to give you the chance to test your port against this new version. If no serious issues should raise in the next 15 days, I will commit the update (plus relative PORTREVISION bump on all dependent ports) on September 21st. It's going to be something in this direction: http://lists.freebsd.org/pipermail/cvs-ports/2010-March/191191.html Thank you for testing the patch available here: http://people.freebsd.org/~gahr/fltk-1.3.0.diff Kind Regards, -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpljO6anW6rM.pgp Description: PGP signature
Re: HEADS UP --- Update to x11-toolkits/fltk coming
On 2011-Sep-06, 06:26, Stephen Montgomery-Smith wrote: > On 09/06/2011 04:18 AM, Pietro Cerutti wrote: > > Hi, > > > > you're receiving this email because one of your ports depends on > > x11-toolkits/fltk, according to > > > > $ grep fltk /usr/ports/INDEX-9 | cut -d '|' -f 6 | sort | uniq > > > > I'm preparing an update to fltk-1.3.0 and I would like to give you the > > chance to test your port against this new version. > > > > If no serious issues should raise in the next 15 days, I will commit the > > update (plus relative PORTREVISION bump on all dependent ports) on > > September 21st. It's going to be something in this direction: > > http://lists.freebsd.org/pipermail/cvs-ports/2010-March/191191.html > > > > Thank you for testing the patch available here: > > http://people.freebsd.org/~gahr/fltk-1.3.0.diff > > > > Kind Regards, > > > > The port graphics/qslim isn't building correctly with this new fltk. > This is needed science/vis5d+. graphics/qslim has no maintainer. I have a patch for that, which you can find here: http://people.freebsd.org/~gahr/qslim-fltk.diff Thanks! > > c++ -c -O2 -pipe -DMIX_ANSI_IOSTREAMS -fpermissive -fPIC > -I/usr/local/include -DHAVE_BOOL -fno-strict-aliasing MxStdGUI.cxx > MxStdGUI.cxx:18:32: error: FL/fl_file_chooser.H: No such file or directory > In file included from MxAsp.h:17, > from MxStdGUI.h:20, > from MxStdGUI.cxx:14: > MxDynBlock.h: In member function 'void MxDynBlock::room_for(int)': > MxDynBlock.h:38: warning: there are no arguments to 'resize' that depend > on a template parameter, so a declaration of 'resize' must be available > MxDynBlock.h: In member function 'typename MxBlock::iterator > MxDynBlock::end()': > MxDynBlock.h:65: warning: there are no arguments to 'begin' that depend > on a template parameter, so a declaration of 'begin' must be available > MxDynBlock.h: In member function 'typename MxBlock::const_iterator > MxDynBlock::end() const': > MxDynBlock.h:66: warning: there are no arguments to 'begin' that depend > on a template parameter, so a declaration of 'begin' must be available > In file included from MxSMF.h:22, > from MxStdGUI.cxx:16: > MxStack.h: In member function 'T& MxStack::top()': > MxStack.h:29: warning: there are no arguments to 'last' that depend on a > template parameter, so a declaration of 'last' must be available > MxStack.h: In member function 'const T& MxStack::top() const': > MxStack.h:30: warning: there are no arguments to 'last' that depend on a > template parameter, so a declaration of 'last' must be available > MxStack.h: In member function 'bool MxStack::is_empty()': > MxStack.h:32: warning: there are no arguments to 'length' that depend on > a template parameter, so a declaration of 'length' must be available > MxStack.h: In member function 'T& MxStack::pop()': > MxStack.h:34: warning: there are no arguments to 'drop' that depend on a > template parameter, so a declaration of 'drop' must be available > MxStack.h: In member function 'void MxStack::push()': > MxStack.h:44: warning: there are no arguments to 'add' that depend on a > template parameter, so a declaration of 'add' must be available > MxStack.h:44: warning: there are no arguments to 'length' that depend on > a template parameter, so a declaration of 'length' must be available > MxStdGUI.cxx: In member function 'virtual void > MxStdGUI::cmdline_file(const char*)': > MxStdGUI.cxx:89: error: 'fl_file_chooser' was not declared in this scope > gmake: *** [MxStdGUI.o] Error 1 > *** Error code 1 > > Stop in /usr/ports/graphics/qslim. > wilberforce# -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpQt9P748gQK.pgp Description: PGP signature
Re: HEADS UP --- Update to x11-toolkits/fltk coming
On 2011-Sep-06, 07:28, Stephen Montgomery-Smith wrote: > On 09/06/2011 06:26 AM, Stephen Montgomery-Smith wrote: > > On 09/06/2011 04:18 AM, Pietro Cerutti wrote: > >> Hi, > >> > >> you're receiving this email because one of your ports depends on > >> x11-toolkits/fltk, according to > >> > >> $ grep fltk /usr/ports/INDEX-9 | cut -d '|' -f 6 | sort | uniq > >> > >> I'm preparing an update to fltk-1.3.0 and I would like to give you the > >> chance to test your port against this new version. > >> > >> If no serious issues should raise in the next 15 days, I will commit the > >> update (plus relative PORTREVISION bump on all dependent ports) on > >> September 21st. It's going to be something in this direction: > >> http://lists.freebsd.org/pipermail/cvs-ports/2010-March/191191.html > >> > >> Thank you for testing the patch available here: > >> http://people.freebsd.org/~gahr/fltk-1.3.0.diff > >> > >> Kind Regards, > >> > > > > The port graphics/qslim isn't building correctly with this new fltk. > > This patch seems to fix it. Even if it is garbled by the text > processor/mail user, it should be obvious what it does - change the case > of some letters in two occurrences of FL/Fl_File_Chooser.H Yes, that is correct. > > diff -urN files-orig/patch-mixkit_src_MxStdGUI.cxx > files/patch-mixkit_src_MxStdGUI.cxx > --- files-orig/patch-mixkit_src_MxStdGUI.cxx1970-01-01 > 00:00:00.0 + > +++ files/patch-mixkit_src_MxStdGUI.cxx 2011-09-06 12:20:44.0 + > @@ -0,0 +1,11 @@ > +--- mixkit/src/MxStdGUI.cxx-orig 2011-09-06 12:19:02.0 + > mixkit/src/MxStdGUI.cxx2011-09-06 12:19:38.0 + > +@@ -15,7 +15,7 @@ > + #include "MxGLUtils.h" > + #include "MxSMF.h" > + #include > +-#include > ++#include > + #include > + > + > diff -urN files-orig/patch-tools_qslim_qvis.cxx > files/patch-tools_qslim_qvis.cxx > --- files-orig/patch-tools_qslim_qvis.cxx 1970-01-01 > 00:00:00.0 + > +++ files/patch-tools_qslim_qvis.cxx2011-09-06 12:21:26.0 + > @@ -0,0 +1,11 @@ > +--- tools/qslim/qvis.cxx-orig 2011-09-06 12:19:12.0 + > tools/qslim/qvis.cxx 2011-09-06 12:20:06.0 + > +@@ -14,7 +14,7 @@ > + #include > + #include > + > +-#include > ++#include > + #include > + #include > + #include > > diff -urN files-orig/patch-mixkit_src_MxStdGUI.cxx > files/patch-mixkit_src_MxStdGUI.cxx > --- files-orig/patch-mixkit_src_MxStdGUI.cxx1970-01-01 00:00:00.0 > + > +++ files/patch-mixkit_src_MxStdGUI.cxx 2011-09-06 12:20:44.0 + > @@ -0,0 +1,11 @@ > +--- mixkit/src/MxStdGUI.cxx-orig 2011-09-06 12:19:02.0 + > mixkit/src/MxStdGUI.cxx2011-09-06 12:19:38.0 + > +@@ -15,7 +15,7 @@ > + #include "MxGLUtils.h" > + #include "MxSMF.h" > + #include > +-#include > ++#include > + #include > + > + > diff -urN files-orig/patch-tools_qslim_qvis.cxx > files/patch-tools_qslim_qvis.cxx > --- files-orig/patch-tools_qslim_qvis.cxx 1970-01-01 00:00:00.0 > + > +++ files/patch-tools_qslim_qvis.cxx2011-09-06 12:21:26.0 + > @@ -0,0 +1,11 @@ > +--- tools/qslim/qvis.cxx-orig 2011-09-06 12:19:12.0 + > tools/qslim/qvis.cxx 2011-09-06 12:20:06.0 + > +@@ -14,7 +14,7 @@ > + #include > + #include > + > +-#include > ++#include > + #include > + #include > + #include > -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgp3hUSAckEt7.pgp Description: PGP signature
Re: HEADS UP --- Update to x11-toolkits/fltk coming
On 2011-Sep-06, 08:28, Stephen Montgomery-Smith wrote: > On 09/06/2011 07:32 AM, Pietro Cerutti wrote: > > On 2011-Sep-06, 07:28, Stephen Montgomery-Smith wrote: > >> On 09/06/2011 06:26 AM, Stephen Montgomery-Smith wrote: > >>> On 09/06/2011 04:18 AM, Pietro Cerutti wrote: > >>>> Hi, > >>>> > >>>> you're receiving this email because one of your ports depends on > >>>> x11-toolkits/fltk, according to > >>>> > >>>> $ grep fltk /usr/ports/INDEX-9 | cut -d '|' -f 6 | sort | uniq > >>>> > >>>> I'm preparing an update to fltk-1.3.0 and I would like to give you the > >>>> chance to test your port against this new version. > >>>> > >>>> If no serious issues should raise in the next 15 days, I will commit the > >>>> update (plus relative PORTREVISION bump on all dependent ports) on > >>>> September 21st. It's going to be something in this direction: > >>>> http://lists.freebsd.org/pipermail/cvs-ports/2010-March/191191.html > >>>> > >>>> Thank you for testing the patch available here: > >>>> http://people.freebsd.org/~gahr/fltk-1.3.0.diff > >>>> > >>>> Kind Regards, > >>>> > >>> > >>> The port graphics/qslim isn't building correctly with this new fltk. > >> > >> This patch seems to fix it. Even if it is garbled by the text > >> processor/mail user, it should be obvious what it does - change the case > >> of some letters in two occurrences of FL/Fl_File_Chooser.H > > > > Yes, that is correct. > > Can you commit this change at the same time as you commit the fltk > update? It will be easier for you to get the timing correct than it > will for me. Sure, I will keep that patch and commit it when I update fltk. > Also, gmsh and vis5d+ (other ports that I maintain) seemed to build just > fine. octave also built just fine, but that's maho's port, so I will > let him have the final word. Thank you very much for looking at that! -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpC6lcVGYdcS.pgp Description: PGP signature
Re: HEADS UP --- Update to x11-toolkits/fltk coming
On 2011-Sep-22, 16:30, Maho NAKATA wrote: > Hi *, now I'm testing x11-toolkits/fltk for math/octave port. > sorry for delay. I'm a bit behind schedule too, I'll probably get to it only next week! Happy testing ;) > thanks > > From: Pietro Cerutti > Subject: Re: HEADS UP --- Update to x11-toolkits/fltk coming > Date: Tue, 06 Sep 2011 15:53:31 +0200 > > > On 2011-Sep-06, 08:28, Stephen Montgomery-Smith wrote: > >> On 09/06/2011 07:32 AM, Pietro Cerutti wrote: > >> > On 2011-Sep-06, 07:28, Stephen Montgomery-Smith wrote: > >> >> On 09/06/2011 06:26 AM, Stephen Montgomery-Smith wrote: > >> >>> On 09/06/2011 04:18 AM, Pietro Cerutti wrote: > >> >>>> Hi, > >> >>>> > >> >>>> you're receiving this email because one of your ports depends on > >> >>>> x11-toolkits/fltk, according to > >> >>>> > >> >>>> $ grep fltk /usr/ports/INDEX-9 | cut -d '|' -f 6 | sort | uniq > >> >>>> > >> >>>> I'm preparing an update to fltk-1.3.0 and I would like to give you the > >> >>>> chance to test your port against this new version. > >> >>>> > >> >>>> If no serious issues should raise in the next 15 days, I will commit > >> >>>> the > >> >>>> update (plus relative PORTREVISION bump on all dependent ports) on > >> >>>> September 21st. It's going to be something in this direction: > >> >>>> http://lists.freebsd.org/pipermail/cvs-ports/2010-March/191191.html > >> >>>> > >> >>>> Thank you for testing the patch available here: > >> >>>> http://people.freebsd.org/~gahr/fltk-1.3.0.diff > >> >>>> > >> >>>> Kind Regards, > >> >>>> > >> >>> > >> >>> The port graphics/qslim isn't building correctly with this new fltk. > >> >> > >> >> This patch seems to fix it. Even if it is garbled by the text > >> >> processor/mail user, it should be obvious what it does - change the case > >> >> of some letters in two occurrences of FL/Fl_File_Chooser.H > >> > > >> > Yes, that is correct. > >> > >> Can you commit this change at the same time as you commit the fltk > >> update? It will be easier for you to get the timing correct than it > >> will for me. > > > > Sure, I will keep that patch and commit it when I update fltk. > > > >> Also, gmsh and vis5d+ (other ports that I maintain) seemed to build just > >> fine. octave also built just fine, but that's maho's port, so I will > >> let him have the final word. > > > > Thank you very much for looking at that! > > > > -- > > Pietro Cerutti > > The FreeBSD Project > > g...@freebsd.org > > > > PGP Public Key: > > http://gahr.ch/pgp -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgp8KszWJwYXq.pgp Description: PGP signature
Re: Problem with ldconfig detecting libraries installed by devel/gdcm
Hi Stephen,
I have fixed this issue in the new version of the gdcm port (2.2.0),
which I have committed a few minutes ago.
Thanks for pointing this out!
Kind Regards,
On 2011-Dec-26, 12:51, Stephen Montgomery-Smith wrote:
> I want to create a port that uses devel/gdcm as a dependency. But writing:
> LIB_DEPENDS+= gdcmCommon:${PORTSDIR}/devel/gdcm
> doesn't work. It does build the port, but it fails to detect that the
> port is installed.
>
> I notice that when I type:
> ldconfig -r | grep gdcm
> that it doesn't find the installed libraries. But this can be fixed by
> doing
> ln -s libgdcmCommon.so.2.0.18 libgdcmCommon.so.2
> Note that the devel/gdmc port only installs
> libgdcmCommon.so.2.0.18 libgdcmCommon.so.2.0libgdcmCommon.so
>
> I contacted the port maintainer a few days ago, and this email is copied
> to him. But I would also like to submit a PR that includes a fix so
> that his job is easier.
>
> But I am unsure what is the "officially correct" way to fix this? Is it
> a bug in ldconfig? Or should the port create these links? Or were the
> original writers of gdcm incorrect when the specify a major version
> number that includes a period?
>
> Thanks, Stephen
> ___
> 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"
--
Pietro Cerutti
The FreeBSD Project
g...@freebsd.org
PGP Public Key:
http://gahr.ch/pgp
pgpOgZsHB2yHX.pgp
Description: PGP signature
Re: xfe build fails on 8-i386
On 2012-Feb-19, 14:32, Doug Barton wrote: > Howdy, > > I'm having problems building xfe on recent 8-stable i386: > > cc -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I.. -I. > -I.. -I../intl -I/usr/local/include -I/usr/local/include/freetype2 > -I/usr/local/include -I/usr/local/include -D_THREAD_SAFE > -I/usr/local/include -I/usr/local/include/freetype2 -I/usr/local/include > -I/usr/local/include -D_THREAD_SAFE -O2 -O2 -pipe -fno-strict-aliasing > -MT ttyinit.o -MD -MP -MF .deps/ttyinit.Tpo -c -o ttyinit.o `test -f > '../xvt/ttyinit.c' || echo './'`../xvt/ttyinit.c > ../xvt/ttyinit.c:144:17: error: pty.h: No such file or directory > ../xvt/ttyinit.c: In function 'write_utmp': > ../xvt/ttyinit.c:217: error: 'struct utmp' has no member named 'ut_type' > ../xvt/ttyinit.c:217: error: 'USER_PROCESS' undeclared (first use in > this function) > ../xvt/ttyinit.c:217: error: (Each undeclared identifier is reported > only once > ../xvt/ttyinit.c:217: error: for each function it appears in.) > ../xvt/ttyinit.c:218: error: 'struct utmp' has no member named 'ut_id' > ../xvt/ttyinit.c:218: error: 'struct utmp' has no member named 'ut_id' > ../xvt/ttyinit.c: In function 'tidy_utmp': > ../xvt/ttyinit.c:319: warning: comparison between pointer and integer > ../xvt/ttyinit.c:321: error: 'struct utmp' has no member named 'ut_type' > ../xvt/ttyinit.c:321: error: 'DEAD_PROCESS' undeclared (first use in > this function) > gmake[2]: *** [ttyinit.o] Error 1 > > Full build log available at http://people.freebsd.org/~dougb/xfe-build.log Fixed, thanks. -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpNTKbS11zSt.pgp Description: PGP signature
Re: No working IDE in FreeBSD!
On 2012-Feb-26, 11:48, O. Hartmann wrote: > On 02/23/12 14:38, Eduardo Morras wrote: > > At 12:22 23/02/2012, O. Hartmann wrote: > > Codelite, i use it and works fine (Freebsd 8.2) with Clang. Version on > > ports is 3.0 not 3.5. On the webpage you have information about how to > > configure for use with clang/llvm. > > Codelite looks nice. But why is codelite setup in editors/codelite and > not in devel/codelite as other IDEs? > > By the way, do all IDEs supported by FreeBSD suffer from being outdated > and aged eons? CodeLite 3.5 is at this very moment the most recent > version and claims to provide a much better LLVM/CLANG support. > > Hope I can convince the maintainer by sending a PR ;-) I am working on an update to codelite to 3.5.5375. However, it contains a lot of Linux specific things that I'll need to track down before I can commit the update. In particular, clang/llvm support and the database designer components are causing me problems. Anyway, the updated version will hit the ports tree within several days. -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgptrrwo44isy.pgp Description: PGP signature
Re: No working IDE in FreeBSD!
On 2012-Feb-28, 15:44, Pietro Cerutti wrote: > On 2012-Feb-26, 11:48, O. Hartmann wrote: > > On 02/23/12 14:38, Eduardo Morras wrote: > > > At 12:22 23/02/2012, O. Hartmann wrote: > > > Codelite, i use it and works fine (Freebsd 8.2) with Clang. Version on > > > ports is 3.0 not 3.5. On the webpage you have information about how to > > > configure for use with clang/llvm. > > > > Codelite looks nice. But why is codelite setup in editors/codelite and > > not in devel/codelite as other IDEs? > > > > By the way, do all IDEs supported by FreeBSD suffer from being outdated > > and aged eons? CodeLite 3.5 is at this very moment the most recent > > version and claims to provide a much better LLVM/CLANG support. > > > > Hope I can convince the maintainer by sending a PR ;-) > > I am working on an update to codelite to 3.5.5375. However, it contains > a lot of Linux specific things that I'll need to track down before I can > commit the update. In particular, clang/llvm support and the database > designer components are causing me problems. > > Anyway, the updated version will hit the ports tree within several days. I have just updated codelite to 3.5.5375. This update includes optional support for MySQL and PostgreSQL in Database Explorer, and clang-based code completion. Enjoy, -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpKokBLQ6dIw.pgp Description: PGP signature
Re: graphics/libosmesa updated from
On 2012-Mar-06, 12:02, Anton Shterenlikht wrote: > On ia64 r225618, updating from libosmesa-7.11.2 > to 8.0.1 I get this error: > > mklib: Making FreeBSD static library: libmesa.a > cc -c -o state_tracker/st_atom.o state_tracker/st_atom.c -DFEATURE_GL=1 > -DHAVE_POSIX_MEMALIGN -DCHAN_BITS=32 -DDEFAULT_SOFTWARE_DEPTH_BITS=31 > -I../../include -I../../src/glsl -I../../src/mesa -I../../src/mapi > -I../../src/gallium/include -I../../src/gallium/auxiliary -O2 -pipe > -I/usr/local/include -fPIC -fno-strict-aliasing -O2 -pipe > -I/usr/local/include -fPIC -fno-strict-aliasing -Wall -Wmissing-prototypes > -std=c99 -fno-strict-aliasing -fno-builtin-memcmp -O2 -pipe > -I/usr/local/include -fPIC -fno-strict-aliasing -fPIC -fvisibility=hidden > In file included from ../../src/gallium/include/pipe/p_compiler.h:32, > from ../../src/gallium/include/pipe/p_defines.h:31, > from state_tracker/st_atom.c:32: > ../../src/gallium/include/pipe/p_config.h:152:2: error: #error Unknown > Endianness > gmake[2]: *** [state_tracker/st_atom.o] Error 1 > gmake[2]: Leaving directory > `/usr/ports/graphics/libosmesa/work/Mesa-8.0.1/src/mesa' > gmake[1]: *** [subdirs] Error 1 Hi Anton, would you please try to build the attached port? Thanks, -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpFX2lnbS5LP.pgp Description: PGP signature
Re: graphics/libosmesa updated from
On 2012-Mar-06, 13:46, Pietro Cerutti wrote: > On 2012-Mar-06, 12:02, Anton Shterenlikht wrote: > > On ia64 r225618, updating from libosmesa-7.11.2 > > to 8.0.1 I get this error: > > > > mklib: Making FreeBSD static library: libmesa.a > > cc -c -o state_tracker/st_atom.o state_tracker/st_atom.c -DFEATURE_GL=1 > > -DHAVE_POSIX_MEMALIGN -DCHAN_BITS=32 -DDEFAULT_SOFTWARE_DEPTH_BITS=31 > > -I../../include -I../../src/glsl -I../../src/mesa -I../../src/mapi > > -I../../src/gallium/include -I../../src/gallium/auxiliary -O2 -pipe > > -I/usr/local/include -fPIC -fno-strict-aliasing -O2 -pipe > > -I/usr/local/include -fPIC -fno-strict-aliasing -Wall -Wmissing-prototypes > > -std=c99 -fno-strict-aliasing -fno-builtin-memcmp -O2 -pipe > > -I/usr/local/include -fPIC -fno-strict-aliasing -fPIC -fvisibility=hidden > > In file included from ../../src/gallium/include/pipe/p_compiler.h:32, > > from ../../src/gallium/include/pipe/p_defines.h:31, > > from state_tracker/st_atom.c:32: > > ../../src/gallium/include/pipe/p_config.h:152:2: error: #error Unknown > > Endianness > > gmake[2]: *** [state_tracker/st_atom.o] Error 1 > > gmake[2]: Leaving directory > > `/usr/ports/graphics/libosmesa/work/Mesa-8.0.1/src/mesa' > > gmake[1]: *** [subdirs] Error 1 > > Hi Anton, > > would you please try to build the attached port? .. which has been eaten by the mailing list. Here it is: http://people.freebsd.org/~gahr/libosmesa-8.0.1-ia64.shar -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpCoYI3sdSlR.pgp Description: PGP signature
Re: cvs commit: ports/games/8kingdoms Makefile ports/misc/airoflash Makefile ports/graphics/autopano-sift Makefile ports/x11/avant-window-navigator-xfce4 Makefile ports/lang/boo Makefile ports/x11/cl-
; 1.32 +3 -0 ports/games/flightgear-atlas/Makefile > 1.31 +3 -0 ports/games/freeorion/Makefile > 1.16 +3 -0 ports/games/rigsofrods/Makefile > 1.25 +3 -0 ports/games/secretmaryochronicles/Makefile > 1.15 +3 -0 ports/games/sfbol/Makefile > 1.101 +3 -0 ports/games/wesnoth-devel/Makefile > 1.20 +3 -0 ports/games/xchadance/Makefile > 1.14 +3 -0 ports/graphics/autopano-sift/Makefile > 1.30 +3 -0 ports/graphics/linux-ac3d/Makefile > 1.9 +3 -0 ports/graphics/long-exposure-tools/Makefile > 1.18 +3 -0 ports/graphics/solang/Makefile > 1.7 +3 -0 ports/lang/boo/Makefile > 1.35 +3 -0 ports/mail/lmtpd/Makefile > 1.107 +3 -0 ports/math/octave-devel/Makefile > 1.5 +3 -0 ports/math/petsc-mpich/Makefile > 1.38 +3 -0 ports/math/petsc/Makefile > 1.13 +3 -0 ports/math/scilab-toolbox-sivp/Makefile > 1.13 +3 -0 ports/misc/airoflash/Makefile > 1.29 +3 -0 ports/misc/kde3-i18n-hsb/Makefile > 1.60 +3 -0 ports/misc/kde3-i18n-mt/Makefile > 1.38 +3 -0 ports/misc/kde3-i18n-nso/Makefile > 1.27 +3 -0 ports/multimedia/moonlight/Makefile > 1.11 +3 -0 ports/multimedia/p5-Video-Info/Makefile > 1.16 +3 -0 ports/multimedia/xfmedia-remote-plugin/Makefile > 1.11 +3 -0 ports/net-im/pino/Makefile > 1.91 +3 -0 ports/net-p2p/gnunet/Makefile > 1.6 +3 -0 ports/net-p2p/py-bittorrent-core/Makefile > 1.66 +3 -0 ports/net-p2p/py-bittorrent/Makefile > 1.19 +3 -0 ports/net/perldap/Makefile > 1.5 +3 -0 ports/net/spnetkit/Makefile > 1.44 +3 -0 ports/palm/coldsync/Makefile > 1.20 +3 -0 ports/print/cups-magicolor/Makefile > 1.50 +3 -0 ports/science/hdf/Makefile > 1.7 +3 -0 ports/security/pantera/Makefile > 1.6 +3 -0 ports/sysutils/linux-megamgr/Makefile > 1.22 +3 -0 ports/sysutils/thunar-volman-plugin/Makefile > 1.84 +3 -0 ports/www/kazehakase/Makefile > 1.7 +3 -0 ports/x11-drivers/xf86-video-rdc/Makefile > 1.38 +3 -0 ports/x11-themes/gtk-qt-engine/Makefile > 1.5 +3 -0 ports/x11-themes/kde-icons-amaranth-althaea/Makefile > 1.3 +3 -0 ports/x11-themes/kde-icons-amaranth/Makefile > 1.7 +3 -0 ports/x11-themes/kde-icons-krystaline/Makefile > 1.3 +3 -0 ports/x11-themes/kde-icons-realistic/Makefile > 1.3 +3 -0 ports/x11-toolkits/xforms-i18n/Makefile > 1.3 +3 -0 ports/x11/avant-window-navigator-xfce4/Makefile > 1.6 +3 -0 ports/x11/cl-clx-sbcl/Makefile > 1.40 +3 -0 ports/x11/x3270/Makefile -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgp9iAoicPucA.pgp Description: PGP signature
Re: cvs commit: ports/games/8kingdoms Makefile ports/misc/airoflash Makefile ports/graphics/autopano-sift Makefile ports/x11/avant-window-navigator-xfce4 Makefile ports/lang/boo Makefile ports/x11/cl-
On 2012-Apr-10, 06:56, Mark Linimon wrote: > On Tue, Apr 10, 2012 at 01:45:38PM +0200, Frederic Culot wrote: > > To conciliate such a necessary action without hurting the feelings of those > > maintainers who despite their work could not update the state of their port > > in a > > timely manner, maybe it would be good to be more verbose in the log of such > > commits. Inspired by linimon's emails, something like the following could be > > added: > > I do get some responses from maintainers to those emails, and (except > in the cases where the email gets stuck in my mbox) I honor their requests > for an extension. OTOH in general I get personal replies and not replies > to the list, so people aren't seeing that interaction in public. > > From my standpoint, by the time something has been broken for 6 months, > the maintainer will have already gotten multiple emails from portsmon. > So, I'm going to have to say I'm a little frustrated if I need to send > another round of mail even on top of that. That's exactly my point: maintainers are very likely to know the situation by the time these deprecation campaigns set off, and committing to their ports without prior approval is in contrast with our policy. I still do not see the necessity to deprecate maintained ports, even though a port might be maintained as broken for a long period of time. The maintainer might be waiting for something to happen either upstream or in our infrastructure, which could release the port from brokenness. -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpWY2RVMXgYc.pgp Description: PGP signature
Re: cvs commit: ports/games/8kingdoms Makefile ports/misc/airoflash Makefile ports/graphics/autopano-sift Makefile ports/x11/avant-window-navigator-xfce4 Makefile ports/lang/boo Makefile ports/x11/cl-
On 2012-Apr-10, 09:32, Marcelo Araujo wrote: > 2012/4/10 Mark Linimon > > > On Tue, Apr 10, 2012 at 01:45:38PM +0200, Frederic Culot wrote: > > > To conciliate such a necessary action without hurting the feelings of > > those > > > maintainers who despite their work could not update the state of their > > port in a > > > timely manner, maybe it would be good to be more verbose in the log of > > such > > > commits. Inspired by linimon's emails, something like the following > > could be > > > added: > > > > I do get some responses from maintainers to those emails, and (except > > in the cases where the email gets stuck in my mbox) I honor their requests > > for an extension. OTOH in general I get personal replies and not replies > > to the list, so people aren't seeing that interaction in public. > > > > From my standpoint, by the time something has been broken for 6 months, > > the maintainer will have already gotten multiple emails from portsmon. > > So, I'm going to have to say I'm a little frustrated if I need to send > > another round of mail even on top of that. > > > > > I strongly agree with the bapt's action to set some ports that are often > broken to deprecated or even some of them that are broken for a long time > to deprecated. > > There is nothing more frustrating than try to install a port an it doesn't > fetch or doesn't build. I might agree on that. But how is a DEPRECATED port better than a BROKEN one in this regard? -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpbmPvdVo2NB.pgp Description: PGP signature
Re: cvs commit: ports/games/8kingdoms Makefile ports/misc/airoflash Makefile ports/graphics/autopano-sift Makefile ports/x11/avant-window-navigator-xfce4 Makefile ports/lang/boo Makefile ports/x11/cl-
On 2012-Apr-10, 11:20, Marcelo Araujo wrote: > 2012/4/10 Pietro Cerutti > > > > > > I might agree on that. But how is a DEPRECATED port better than a BROKEN > > one in this regard? > > > > > In my point of view, no make sense have a bunch of ports that actually > doesn't works or because there is a fetch problem or even it is set as > BROKEN. Who never was upset when need and find a port but it is BROKEN for > some reason, In my view, have a port BROKEN or haven't it, is the same. Of > course, I mean when a port is BROKEN for all plataforms as well as for all > FreeBSD version. I agree on that. > > I believe set it as DEPRECATED is a good way to make the maintainer take > attention to fix it soon as possible, due he has put effort to insert this > software on the ports tree in the past. What about submitting a PR, as we usually do for anything else? If it's ok to wait 15 days (maintainer timeout) to commit an update to a port that brings in important features, it is even more so to wait to deprecate one. > In case that has any issue related with the ports framework that make the > ports be broken, he can ping any developer to give him more time to fix or > even rollback the DEPRECATED commit with a proper message on the commit's > log. This is awkward. We're not supposed to spend our time rolling back unwanted commits. We're supposed to make sure that a commit made to someone else's port is wanted in the first place. > It also will let us know, what's happen with that port and maybe someone > else could give a hand to help the maintainer to fix it. Well, as I see it, marking a port as DEPRECATED is kind of a final decision. I.e., I'll start to look at alternatives and forget about it. If you mark a port as DEPRECATED and 12 hours later I back off your chance with a comment "I'm working on it", a really unconsistent and confused message will pass. -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpW8cZ2RQyFm.pgp Description: PGP signature
Re: cvs commit: ports/games/8kingdoms Makefile ports/misc/airoflash Makefile ports/graphics/autopano-sift Makefile ports/x11/avant-window-navigator-xfce4 Makefile ports/lang/boo Makefile ports/x11/cl-
On 2012-Apr-10, 09:04, Jerry wrote: > On Tue, 10 Apr 2012 07:40:09 -0500 > Mark Linimon articulated: > > > Finally, I agree that FreeBSD can't "guarantee" any given ports will > > work, but I think we owe the users the effort to make sure if a port > > is included, it's at least not completely useless. > > To "guarantee" that the port will work is certainly beyond the scope > of the ports system; however, to guarantee that it is fetch-able > and build-able is an implied action by the simple fact that it is > included in the ports structure. If, after a reasonable amount of time, > a solution for a port's inability to properly build or if the port is > just plain not able to be fetched, then it should be removed from the > port system. There is no upside to keeping ports that will not build, > or cannot be fetched. For the record, the port in question was fetchable / buildable / runnable. For some reason, some python class sometimes doesn't get byte-compiled, resulting in packaging (PLIST) errors. -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgppnRkZc7urK.pgp Description: PGP signature
Re: cvs commit: ports/games/8kingdoms Makefile ports/misc/airoflash Makefile ports/graphics/autopano-sift Makefile ports/x11/avant-window-navigator-xfce4 Makefile ports/lang/boo Makefile ports/x11/cl-
On 2012-Apr-10, 17:17, Mel Flynn wrote:
> On 4/10/2012 16:47, Pietro Cerutti wrote:
> > On 2012-Apr-10, 11:20, Marcelo Araujo wrote:
> >> 2012/4/10 Pietro Cerutti
> >>>
> >>>
> >>> I might agree on that. But how is a DEPRECATED port better than a BROKEN
> >>> one in this regard?
> >>>
> >>>
> >> In my point of view, no make sense have a bunch of ports that actually
> >> doesn't works or because there is a fetch problem or even it is set as
> >> BROKEN. Who never was upset when need and find a port but it is BROKEN for
> >> some reason, In my view, have a port BROKEN or haven't it, is the same. Of
> >> course, I mean when a port is BROKEN for all plataforms as well as for all
> >> FreeBSD version.
> >
> > I agree on that.
> >
> >>
> >> I believe set it as DEPRECATED is a good way to make the maintainer take
> >> attention to fix it soon as possible, due he has put effort to insert this
> >> software on the ports tree in the past.
> >
> > What about submitting a PR, as we usually do for anything else? If it's
> > ok to wait 15 days (maintainer timeout) to commit an update to a port
> > that brings in important features, it is even more so to wait to
> > deprecate one.
>
> Not to discredit your work in any way, but 6 months of being BROKEN can
> be classified as maintainer timeout in the general case.
That's your opinion, and while I agree on the general idea that six
months is a lot, I would like actions / behavior to be based on policies
previously agreed upon and documented.
"15 days --> implicit approval (maintainer timeout)" is documented
"6 months --> implicit deprecation of broken ports" is not
> On a more constructive note - why don't you mention the specific port?
> Maybe some of us on the list can help you figure out why some files
> sometimes don't get byte compiled or provide you with a work-around
> solution (dynamically generated plist comes to mind).
The port is editors/komodo-edit. sbz@ gave me a hint about forcing
byte-compilation of all the python classes using
post-install:
@${PYTHON_CMD} -O -m compileall -q ${DATADIR} || true
@${PYTHON_CMD} -m compileall -q ${DATADIR} || true
but I never got to commit that. I'm testing it right now and unbreak the
port very soon. Thank you!
--
Pietro Cerutti
The FreeBSD Project
g...@freebsd.org
PGP Public Key:
http://gahr.ch/pgp
pgp8vdcN6uHEQ.pgp
Description: PGP signature
Re: pkg audit -F segfault on sparc64 and ia64 [WAS: Re: pkg audit segfault]
On 2012-Apr-18, 13:44, Anton Shterenlikht wrote: > On Mon, Apr 16, 2012 at 04:13:06PM +0100, Anton Shterenlikht wrote: > > On Mon, Apr 16, 2012 at 04:58:27PM +0200, Julien Laffaye wrote: > > > On 04/16/2012 04:21 PM, Anton Shterenlikht wrote: > > > >pkg audit -F > > > On my 9.0-RELEASE amd64, it works fine. > > segfault also on sparc64 r230787M I have a couple of sparc64 machines on which I can test, but that won't be before next week.. I'll follow-up. > > # pkg -vvv > version: 1.0-beta11 > abi: freebsd:10:sparc64:64 > db dir: /var/db/pkg > cache dir: /var/cache/pkg > ports dir: /usr/ports > Log into syslog: yes > Assume always yes: no > Handle rc scripts: no > Track shlibs: no > Automatic depdency tracking: no > Custom keywords directory: none > Repository: none > # > > # pkg audit -F > http://portaudit.FreeBSD.org/auditfile.tbz 100% 76KB 75.7KB/s > 75.7KB/s 00:00 > 0 problem(s) in your installed packages found. > Segmentation fault (core dumped) > > # gdb /usr/local/sbin/pkg pkg.core > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "sparc64-marcel-freebsd"... > Core was generated by `pkg'. > Program terminated with signal 11, Segmentation fault. > Reading symbols from /usr/local/lib/libpkg.so.0...done. > Loaded symbols for /usr/local/lib/libpkg.so.0 > Reading symbols from /lib/libutil.so.9...done. > Loaded symbols for /lib/libutil.so.9 > Reading symbols from /lib/libjail.so.1...done. > Loaded symbols for /lib/libjail.so.1 > Reading symbols from /lib/libc.so.7...done. > Loaded symbols for /lib/libc.so.7 > Reading symbols from /usr/lib/libarchive.so.5...done. > Loaded symbols for /usr/lib/libarchive.so.5 > Reading symbols from /lib/libsbuf.so.6...done. > Loaded symbols for /lib/libsbuf.so.6 > Reading symbols from /usr/lib/libfetch.so.6...done. > Loaded symbols for /usr/lib/libfetch.so.6 > Reading symbols from /usr/lib/libelf.so.1...done. > Loaded symbols for /usr/lib/libelf.so.1 > Reading symbols from /lib/libthr.so.3...done. > Loaded symbols for /lib/libthr.so.3 > Reading symbols from /lib/libedit.so.7...done. > Loaded symbols for /lib/libedit.so.7 > Reading symbols from /lib/libz.so.6...done. > Loaded symbols for /lib/libz.so.6 > Reading symbols from /usr/lib/libbz2.so.4...done. > Loaded symbols for /usr/lib/libbz2.so.4 > Reading symbols from /usr/lib/liblzma.so.5...done. > Loaded symbols for /usr/lib/liblzma.so.5 > Reading symbols from /lib/libbsdxml.so.4...done. > Loaded symbols for /lib/libbsdxml.so.4 > Reading symbols from /lib/libcrypto.so.6...done. > Loaded symbols for /lib/libcrypto.so.6 > Reading symbols from /usr/lib/libssl.so.6...done. > Loaded symbols for /usr/lib/libssl.so.6 > Reading symbols from /lib/libmd.so.5...done. > Loaded symbols for /lib/libmd.so.5 > Reading symbols from /lib/libncurses.so.8...done. > Loaded symbols for /lib/libncurses.so.8 > Reading symbols from /libexec/ld-elf.so.1...done. > Loaded symbols for /libexec/ld-elf.so.1 > #0 0x407f31a8 in __sparc_utrap_install () from /lib/libc.so.7 > [New Thread 41c04400 (LWP 100130/pkg)] > (gdb) bt > #0 0x407f31a8 in __sparc_utrap_install () from /lib/libc.so.7 > #1 0x407f32cc in __sparc_utrap_install () from /lib/libc.so.7 > #2 0x407f3570 in __sparc_utrap_install () from /lib/libc.so.7 > #3 0x407f2dac in __sparc_utrap_install () from /lib/libc.so.7 > #4 0x40225b74 in dlsym () from /libexec/ld-elf.so.1 > #5 0x40225b74 in dlsym () from /libexec/ld-elf.so.1 > Previous frame identical to this frame (corrupt stack?) > (gdb) > > -- > Anton Shterenlikht > Room 2.6, Queen's Building > Mech Eng Dept > Bristol University > University Walk, Bristol BS8 1TR, UK > Tel: +44 (0)117 331 5944 > Fax: +44 (0)117 929 4423 > ___ > 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" -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpwgGkTHRaQp.pgp Description: PGP signature
Re: gegl
On 2011-Mar-02, 16:48, Michal Varga wrote: > On Wed, 2011-03-02 at 16:26 +0100, Pietro Cerutti wrote: > > On 2011-Mar-02, 15:57, Michal Varga wrote: > > > Out of curiosity - how is it even possible that this update made it as > > > far as into ports tree, when it - at least as I understand from the PR - > > > clearly doesn't work on *both* *STABLE* *supported* branches and only > > > goes well with the very latest CURRENT? > > > > The original update doesn't cause any problems on CURRENT, > > 7.4-RELEASE, or 8.2-RELEASE. It does cause problems on STABLE branches. > > > > Is this guaranteed? > > As here with... > > > uname -a > FreeBSD 7.4-STABLE FreeBSD 7.4-STABLE #0: Sun Feb 27 22:30:14 CET 2011 > > ...gegl (unpatched) still fails: > > > exp_combine.cpp: In function 'gfloat expcombine_get_file_ev(const gchar*)': > exp_combine.cpp:99: error: 'log2f' was not declared in this scope > gmake[2]: *** [exp_combine-exp_combine.o] Error 1 > > > Note that 7.4-RELEASE was back in Feb 21. Or was there a change specific > to 7.4-RELEASE that for some reason didn't make it into STABLE? OK, I have nailed down the source of the problem. GEGL has an optional dependency on graphics/exiv2 which is not tracked by the port, i.e. exiv2 is not built as a dependency of the port, and GEGL doesn't rely on it if it doesn't find it. It turns out that the failing C module (exp_combine.c) is only compiled when EXIV is found. Thus, on a fresh system (i.e., tinderbox) the error won't appear. It will, however, on a system where EXIV is installed. Please check whether you have graphics/exiv2 installed in your system to confirm this hypothesis. I have still not decided whether to include exiv2 as a mandatory or optional dependency, cause configure doesn't handle --without-exiv2 correctly when exiv2 is installed (i.e., GEGL will be built with EXIV support in that case). Thanks for the hints, and sorry for the noise. -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpM3bdFMOqAB.pgp Description: PGP signature
Re: gegl
On 2011-Mar-02, 15:57, Michal Varga wrote: > On Wed, 2011-03-02 at 17:39 +0300, Ruslan Mahmatkhanov wrote: > > 02.03.2011 13:06, Christoph Moench-Tegeder пишет: > > > ## Christoph Moench-Tegeder (c...@burggraben.net): > > > > > >> Looks as if we (at least on 8.2) are missing log2(), log2f(), log2l(), > > >> even though they are in C99 (partially C89) and POSIX since at least > > >> 2008. (I can't find them in math.h, log2l() is commented out). > > >> If nobody else does, I might get around to workaround-patching this later > > >> today. > > > > > > There it is: ports/155183 > > > Please check the patch there, in case I broke the math (logarithms are > > > easy enough, but anyway...). > > > > > > > > > Regards, > > > Christoph > > > > Still doesn't builds for me. > > smeshariki2# sysctl kern.osreldate > > kern.osreldate: 802500 > > > > If i change the check on something like: > > if __FreeBSD_version < 704000 || (__FreeBSD_version > 80 && > > __FreeBSD_version < 803000) > > > > then it build fine. > > > > Out of curiosity - how is it even possible that this update made it as > far as into ports tree, when it - at least as I understand from the PR - > clearly doesn't work on *both* *STABLE* *supported* branches and only > goes well with the very latest CURRENT? The original update doesn't cause any problems on CURRENT, 7.4-RELEASE, or 8.2-RELEASE. It does cause problems on STABLE branches. > Wouldn't a single test run on either 7.x or 8.x before committing the > port reveal this issue? Just my thoughts. Yes, it would have. I just don't have the infrastructure nor the time to test on all supported release + stable branches. -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpd0RK6kL2F4.pgp Description: PGP signature
CFT: net-im/openfire 3.7.0
Hi all, I have a patch ready to upgrade net-im/openfire to 3.7.0, here: http://people.freebsd.org/~gahr/openfire-3.7.0.diff I plan to commit this patch later this week and mark as IGNORE the development port at net-im/openfire-devel, if nobody comes with a very good reason not to do so. Thanks for testing! -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpVvslW92tgO.pgp Description: PGP signature
Re: Deprecation campaign
On 2011-Mar-17, 10:26, Matthias Andree wrote: > Am 17.03.2011 05:33, schrieb Ruslan Mahmatkhanov: > > 17.03.2011 02:33, Michel Talon пишет: > >> Hello, > >> > >> i noted that ucpp is deprecated because it cannot be fetched > >> from original site. This is an alternate c preprocessor > >> supposed to be better than the gnu one, written by Thomas > >> Pornin. I happen to know the guy (*), so i searched if > >> the soft had been moved, and indeed it can be found here: > >> http://code.google.com/p/ucpp/ > >> I hope you may reconsider your decision. > >> > >> With my best regards > >> > >> (*) i think he now runs a crypto firm in the Boston area. > > > > I've tried to adopt the port to new distfile.. > > It builds but doesn't produce ucpp binary. > > Maybe you or anybody can look what's wrong. > > Guys, > > all these efforts to rescue the ports are all good, but: do we actually > _need_ the ports? Just having one more port isn't a value in itself. It's a potential value. Having one port less is a potential loss. > And if yes, can someone step up to become maintainer of the port, > meaning, upgrade it to new versions, sort FreeBSD bug reports and > forward/file them with the upstream authors, and all that? Well, this is not how it works. There are a lot of old ports which are not being developped upstreams anymore. Probably nobody is interested in maintaining those, because there's nothing to do to those ports other than fixing potential build problems. However, this doesn't imply that the port is useless or that nobody's interested in using it. Not all consumers of FreeBSD ports follow ports@. I'd be very carful on killing ports. I agree on killing BROKEN ports where the distfiles are not fetchable anymore. In this case, nobody can benefit from having the (non working) port. But I wouldn't go further. And I'd welcome ANY effort to resurrect a port or make it workable again, even if it does not imply setting a real MAINTAINER. -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpfNBzlZEw61.pgp Description: PGP signature
Re: CFT: net-im/openfire 3.7.0
Hi all, openfire-3.7.0 is in ports. Best Regards, On 2011-Mar-14, 12:25, Pietro Cerutti wrote: > Hi all, > > I have a patch ready to upgrade net-im/openfire to 3.7.0, here: > http://people.freebsd.org/~gahr/openfire-3.7.0.diff > > I plan to commit this patch later this week and mark as IGNORE > the development port at net-im/openfire-devel, if nobody comes > with a very good reason not to do so. > > Thanks for testing! > > -- > Pietro Cerutti > The FreeBSD Project > g...@freebsd.org > > PGP Public Key: > http://gahr.ch/pgp -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpGEOWjlEb3z.pgp Description: PGP signature
Re: [ECFT] pkgng 0.1-alpha1: a replacement for pkg_install
On 2011-Mar-25, 15:03, Julien Laffaye wrote: > >>> What about DB corruption/loss? Do you keep the /var/db/pkg//xxx > >>> files even with pkgng and only use the DB as a way to speed up some work > >>> (so > >>> the DB corruption just requires to run pkg2ng), or are you lost of the DB > >>> is > >>> lost? > >>> > >> > >> Nothing is done about DB corruption/loss, I am not sure we need to do > >> something. > >> Maybe. > > > > I would say "for sure". Info: In Solaris 10 sqlite is used for the service > > managenemt framework (SMF). It is possible that the DB is corrupt in some > > bad situations. In this case you have to rebuild the DB (script provided, > > been there, had to use it). > > If sqlite is properly used with transactions, it is very hard to > corrupt the database. But if hardware lies to us and say that the data > is on disk whereas it isnt... what can we do? > Another potential problem is fsync(), but if it is broken on FreeBSD > we want to fix it! > > BTW, the goal is to only have the database and not the flat files. > If you are paranoid about power outage, use something like zfs snapshots... No need to look for strange scenarios, I'm surely going to sudo rm -f the file more sooner than later, so... maybe just save a copy? -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgp4AYvylMp4W.pgp Description: PGP signature
Fix build w/ gcc 4.2 - any priority?
Hi list, in these days I'm doing my best as fixing ports marked as broken with gcc 4.2 (http://www.freebsd.org/cgi/query-pr-summary.cgi?originator=pietro+cerutti). I would like to know if there is any way to somehow prioritize my work, e.g. by the number of users who are using a broken port. Is there anything like bsdstats that I can use to see that? Thanks, -- Pietro Cerutti PGP Public Key: http://gahr.ch/pgp signature.asc Description: OpenPGP digital signature
Re: Fix build w/ gcc 4.2 - any priority?
Mark Linimon wrote: > On Sun, Nov 04, 2007 at 03:08:45PM +0100, Pietro Cerutti wrote: >> Is there anything like bsdstats that I can use to see that? > > FreshPorts has http://www.freshports.org/graphs.php?id=7, but > it's only the top 20, so not really. > yep... and none of them has problems ;-) thanks > mcl -- Pietro Cerutti PGP Public Key: http://gahr.ch/pgp signature.asc Description: OpenPGP digital signature
[CFT] audio/holyshout revisited
Hi all, the following modifications have been applied to audio/holyshout: - fixed building with GCC 4.2; - ported to use audio/lame instead of internal [outdated] library; - upgraded to use audio/libshout2 instead of audio/libshout Unfortunately, not knowing Icecast at all, it's difficult to me to do thorough tests to find bugs or misbehaviors. I've run the program a few times locally and everything seems to work correctly, but more feedback would be very useful! Please test audio/holyshout with the patch below: http://www.gahr.ch/FreeBSD/patches/117778_holyshout.diff Thank you very much! -- Pietro Cerutti PGP Public Key: http://gahr.ch/pgp ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports/117266: New port: www/linux-netscape-navigator The All-New Netscape Navigator 9.0
Randy Pratt wrote: > Still no joy: > > # pkg_create -b linux-netscape-navigator-9.0.0.3 > tar: lib/linux-netscape-navigator/defaults/pref/browser-prefs.js: > Cannot stat: No such file or directory tar: Error exit delayed from > previous errors. pkg_create: make_dist: tar command failed with code 256 > > ===> Deinstalling linux-netscape-navigator-9.0.0.3 > pkg_delete: file > '/usr/local/lib/linux-netscape-navigator/defaults/pref/browser-prefs.js' > doesn't exist pkg_delete: couldn't entirely delete package (perhaps the > packing list is incorrectly specified?) > > # ls work/navigator/defaults/pref/ > total 34 > -rw-r--r-- 1 root wheel118 Nov 2 07:39 channel-prefs.js > -rw-r--r-- 1 root wheel805 Nov 2 07:39 firefox-branding.js > -rw-r--r-- 1 root wheel207 Nov 2 07:39 firefox-l10n.js > -rw-r--r-- 1 root wheel 26833 Nov 2 07:39 firefox.js > > It seems the browser-prefs.js is missing in the tarball and never > gets installed. The browser-prefs.js file indeed isn't part of the tarball, but gets anyway installed on my system: > pkg_info -W /usr/local/lib/linux-netscape-navigator/defaults/pref/browser-prefs.js /usr/local/lib/linux-netscape-navigator/defaults/pref/browser-prefs.js was installed by package linux-netscape-navigator-9.0.0.3 The port uses the infrastructure provided by /usr/ports/www/linux-seamonkey/Makefile.common, as all other "linux-gecko" ports do. I think the cause is to be searched inside that file. I'll investigate. Follow-up to ports@ set. Maybe someone there has a good hint ;-) > > Randy -- Pietro Cerutti PGP Public Key: http://gahr.ch/pgp signature.asc Description: OpenPGP digital signature
Re: ports/117266: New port: www/linux-netscape-navigator The All-New Netscape Navigator 9.0
Andrew Pantyukhin wrote: > On Fri, Nov 16, 2007 at 03:32:44PM +0100, Pietro Cerutti wrote: >> The browser-prefs.js file indeed isn't part of the tarball, but gets >> anyway installed on my system: >> >>> pkg_info -W >> /usr/local/lib/linux-netscape-navigator/defaults/pref/browser-prefs.js >> /usr/local/lib/linux-netscape-navigator/defaults/pref/browser-prefs.js >> was installed by package linux-netscape-navigator-9.0.0.3 >> >> The port uses the infrastructure provided by >> /usr/ports/www/linux-seamonkey/Makefile.common, as all other >> "linux-gecko" ports do. I think the cause is to be searched inside that >> file. > > Yep, look at the post-patch target. I can't say if that should be > disabled for netscape until I examine the browser a bit deeper, > but I will. > > In the meantime, could you please provide a complete shar or > tarball of the latest version in any form. Here's the tarball for 9.0.0.3: http://www.gahr.ch/FreeBSD/patches/117266_linux-netscape-navigator-9.0.0.3.tar.bz2 > > Thanks! -- Pietro Cerutti PGP Public Key: http://gahr.ch/pgp signature.asc Description: OpenPGP digital signature
Re: Optional patching
Paul Schmehl wrote:
> Is there a way to include a patch as an option to a port? I maintain
> the security/barnyard port. There's a patch that is necessary for
> barnyard to work correctly on a 64bit system. I'm wondering if I can
> use OPTIONS to make this patch optional if the system is 64 bit, but I'm
> not sure what the syntax would be inside the if statement.
>
> .if defined(WITH_64BIT)
> do-patch: patchname
> .endif
I would do something like (please check the list of 64 bits platforms)
.if ${ARCH} == "amd64" || ${ARCH} == "ia64" || ${ARCH} == "sparc64"
# apply the patch here
.endif
>
> I assume the patch would have to be in the filesdir but could not be
> named "patch-foo" or it would always be applied, correct?
>
Please check the reply from pav@ for this ;-)
--
Pietro Cerutti
PGP Public Key:
http://gahr.ch/pgp
signature.asc
Description: OpenPGP digital signature
Re: request about misc/chmlib
Jockey Kyd wrote: > Hi. > > It seems that misc/chmlib doesn't include any executable to install, say, > enum_chmLib, extract_chmLib, chm_http, etc. There's also no option left for us > to control this installation. But these utilities are so useful that can > replace any other chm readers from my point of view, especially chm_http. Indeed, a good idea.. > So here I request that these tools be included. I've send a PR with the change request: PR: ports/118861 Please keep an eye on it to see when it gets committed: http://www.freebsd.org/cgi/query-pr.cgi?pr=118861 > > Thanks a lot. Thank you for the advice! > > Jockey -- Pietro Cerutti PGP Public Key: http://gahr.ch/pgp signature.asc Description: OpenPGP digital signature
Re: Optional patching
Wesley Shields wrote:
> On Wed, Dec 19, 2007 at 01:03:23PM -0600, Paul Schmehl wrote:
>> --On Wednesday, December 19, 2007 16:59:37 +0100 Pietro Cerutti
>> <[EMAIL PROTECTED]> wrote:
>>
>>> Paul Schmehl wrote:
>>>> Is there a way to include a patch as an option to a port? I maintain
>>>> the security/barnyard port. There's a patch that is necessary for
>>>> barnyard to work correctly on a 64bit system. I'm wondering if I can
>>>> use OPTIONS to make this patch optional if the system is 64 bit, but I'm
>>>> not sure what the syntax would be inside the if statement.
>>>>
>>>> .if defined(WITH_64BIT)
>>>> do-patch: patchname
>>>> .endif
>>>
>>> I would do something like (please check the list of 64 bits platforms)
>>>
>>> .if ${ARCH} == "amd64" || ${ARCH} == "ia64" || ${ARCH} == "sparc64"
>>> # apply the patch here
>>> .endif
>>>
>>>> I assume the patch would have to be in the filesdir but could not be
>>>> named "patch-foo" or it would always be applied, correct?
>>>>
>>> Please check the reply from pav@ for this ;-)
>> That brings up an interesting question. Which would be the preferred
>> method? To use an OPTION knob? Or simply apply the patch if the arch
>> matches? I'm thinking the latter. I've tested the former method, and it
>> works fine. Does it matter which method I use?
>
> I don't think it matters really, but is probably a matter of personal
> preference. The only problem with using an option that I see is that if
> the user has no idea if (s)he is on a 64bit platform and turns the
> option off. It's for this reason I'd suggest using the .if ${ARCH}
> approach.
This would be my argument too.
>
> -- WXS
--
Pietro Cerutti
PGP Public Key:
http://gahr.ch/pgp
signature.asc
Description: OpenPGP digital signature
Re: freebsd-games: hack needs -fwritable-strings
James Cook wrote: > $ uname -a > FreeBSD glider 6.3-PRERELEASE FreeBSD 6.3-PRERELEASE #0: Tue Dec 11 13:40:40 > PST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GLIDER i386 > > The problem: > - Install games/freebsd-games > - run hack > - Say "y" when it asks if you're experienced. > - Type "T" for tourist. > There will be a bus error. > > This seems to be caused by line 170 of hack.u_init.c, which attempts to > modify a string constant. > > SOLUTION: > Add -fwritable-strings to CFLAGS in hack's Makefile. (There's already > a patch that changes that line of the Makefile, so this is easy to > change.) the -fwritable-strings option has been deprecated on GCC 3.x and has removed on GCC 4.x. A code modernization is likely to be needed. -- Pietro Cerutti PGP Public Key: http://gahr.ch/pgp signature.asc Description: OpenPGP digital signature
Re: mod_webapp port broken
main.h:150: >> error: syntax error before "apr_pool_t" >> /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include/wa_main.h:232: >> error: syntax error before '*' token >> /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include/wa_main.h:232: >> warning: data definition has no type or storage class >> In file included from >> /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include/wa.h:117, >> from >> /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/lib/wa_main.c:59: >> /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include/wa_request.h:114: >> error: syntax error before "apr_pool_t" >> /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include/wa_request.h:146: >> error: syntax error before "apr_table_t" >> /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/lib/wa_main.c:62: >> error: syntax error before '*' token >> /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/lib/wa_main.c:62: >> warning: data definition has no type or storage class >> /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/lib/wa_main.c: >> In function `wa_init': >> /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/lib/wa_main.c:82: >> error: `APR_SUCCESS' undeclared (first use in this function) >> /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/lib/wa_main.c:82: >> error: (Each undeclared identifier is reported only once >> /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/lib/wa_main.c:82: >> error: for each function it appears in.) >> gmake[2]: *** [wa_main.lo] Error 1 >> gmake[2]: Leaving directory >> `/usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/lib' >> gmake[1]: *** [subdir] Error 2 >> gmake[1]: Leaving directory >> `/usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp' >> gmake: *** [lib-build] Error 2 >> *** Error code 2 >> >> Stop in /usr/ports/www/mod_webapp. >> >> Now, I've run this several times with various changes all with the same >> result. I've checked my $LOCALBASE and $PORTSDIR variables which point to >> /usr/local and /usr/ports respectively. I've run make using >> -Dwith-apr-include=/usr/local/include/apr-1 - all no good. >> >> Am I missing something? And if you want to mark it as broken thats ok, but >> I'd like to know how to get around it myself... > > > It installs fine over here. just a ditto.. > > First check the simple things: run make clean, update your ports tree, > run portupgrade, and try again. > > Best > > James -- Pietro Cerutti PGP Public Key: http://gahr.ch/pgp ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: New version while port is on the waiting list
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Igor Serikov wrote: >Hello porters, Hello, > > I have submitted a new port. While it was sitting in the PR database - > and it is still there - I produced a new version. > What can/should I do? Submit a followup with the new diff/shar Have a look at the bottom of the page where your PR is. There's a "Submit Followup" e-mail link. > > Regards, Thanks, >Igor. - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (FreeBSD) iEYEAREKAAYFAke++usACgkQwMJqmJVx947PRwCfeVu4A+BzTsujYVNk5RoPB4R3 kf4An3sAg6roBk7RCEcfaSo/KwUMVVJy =UvZI -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
CUPS 1.3.6
Hello, is anybody working on updating CUPS to 1.3.6 or is there any planning? If I would, is there any chance to get it committed during the slush? Thanks, -- Pietro Cerutti PGP Public Key: http://gahr.ch/pgp ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
CUPS 1.3.6
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, is anybody working on updating CUPS to 1.3.6 or is there any planning? If I would, is there any chance to get it committed during the slush? Thanks, - -- Pietro Cerutti PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHwsCjwMJqmJVx944RAsvlAKCb110n9zDkUGaxSdjl1zY6FQJOTgCfQGQw CAMNMDLY2LWCL55f0dsd0lA= =Jfvq -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Port: xfce4-systemload-plugin-0.4.2_3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Stefan Huerter wrote: | Guckux Thorsten Hi, | I am using the systemload and the memory shows incorrect stats: Memory: | 533MB of 18014398509481758MB used... | My system is: | FreeBSD whisky.guckux.de 7.0-STABLE FreeBSD 7.0-STABLE #0: Sat Mar 1 | 12:22:13 UTC 2008 amd64 | 4GB real mem are installed... | | any hints? Would you like to try the following patch and see if it fixes the problem? http://people.freebsd.org/~gahr/xfce4-systemload-plugin.diff | thx in advance I hope this helps, | Stefan - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (FreeBSD) iEYEAREKAAYFAkfgY44ACgkQwMJqmJVx947WSACgp8wpRLKp5aT9N5YSkyTFBeig EvkAoLgX2ceuzVYo8L2HV9MtiJdhfiQ3 =Z/zi -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: updating devel/directfb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Anatoly Borodin wrote: | Hi! Hello Anatoly, | I want to maintain devel/directfb port, the first thing is to update | it to 1.1.0 or 1.1.1 from the 0.9.16 version. I was working on that together with [EMAIL PROTECTED] The problem is that neither of the two is really familiar with directfb. Would you like to test the following patch, not only for build problems, but also - and in particular - for run-time problems/errors. http://people.freebsd.org/~gahr/directfb.diff If everything is ok, I will commit it and pass maintainship to you. | Thanks in advance. Thank you! - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (FreeBSD) iEYEAREKAAYFAkfhMFIACgkQwMJqmJVx944DaACffVn3Mx+IbbLRNYytyNFRDID8 7BUAn0mNXUokKlUVwApuXqwPUwvINuRI =GTcW -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Port: x11/xautolock
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Stefan Thurner wrote: | Hi! | | xlockmore ist not a real run dependency. It's just an option as a | possible locker program. nope, it's the default locker. Removing the dependency on it would mean provide a list of option allowing to choose among the whole set of available lockers. And since a locker is just a program being executed upon timeout, anything could be a locker. | regards | -Stefan - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (FreeBSD) iEYEAREKAAYFAkfhlvkACgkQwMJqmJVx945QjwCcDAwP5tIgPBq9wk5WWJ+UFUhe POMAn1yGpwosQ5bNxX/AqNzEu7aQJYLY =SwW1 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Port: x11/xautolock
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Stefan Thurner wrote: | On Wed, Mar 19, 2008 at 11:43:06PM +0100, Pietro Cerutti wrote: |> -BEGIN PGP SIGNED MESSAGE- |> Hash: SHA512 |> |> Stefan Thurner wrote: |> | Hi! |> | |> | xlockmore ist not a real run dependency. It's just an option as a |> | possible locker program. |> |> nope, it's the default locker. Removing the dependency on it would mean |> provide a list of option allowing to choose among the whole set of |> available lockers. |> And since a locker is just a program being executed upon timeout, |> anything could be a locker. |> | Ok. But an option to just disable xlockmore would be nice. xlock comes with xlockmore on FreeBSD. It would mean disable a default. | | Another question. It seems resources specified in ~/:Xdefaults | are ignored by xautolock. I have: It's ~/.Xdefaults not ~/:Xdefaults | | Xautolock*locker: slock | Xautolock*time: 10 | | and it doesn't work. If I set the options at command line it | works as it should. | | Any hints? I'm not an X expert, sorry. P.S. please keep the mailing list CC'd, you're likely to get more useful answers that way ;-) | | -Stefan - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (FreeBSD) iEYEAREKAAYFAkfhpOgACgkQwMJqmJVx945BPwCg0Zh8Wxa0HRD3+t0fpvIqm3wb VtsAoOIDgsIERLK1uj9xOT+MctqNBjH7 =R0LJ -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: updating devel/directfb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Anatoly Borodin wrote: | Thank you for this patch, but I need 1.1.1 version (I use some | features released here), so I merged you patch with mine. The result | is http://fractalizator.googlepages.com/directfb-0.9.16-1.1.1.patch.txt Hi back, the patch is ok. It only has a plist problem when neither WITH_X11= nor WITH_SDL= is set: pkg_delete: file '/usr/local/lib/directfb-1.1-0/inputdrivers' doesn't exist pkg_delete: unable to completely remove directory '/usr/local/lib/directfb-1.1-0/inputdrivers' Could you quickly look at it? - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (FreeBSD) iEYEAREKAAYFAkfiQQAACgkQwMJqmJVx9454oQCfa0bVQPRlCu321mqEp3lJmNNZ nggAoJocgvaonlHAtzLi2DS2K2USrqRy =cXp9 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: libnjb pkg-plist incorrect?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Jan Henrik Sylvester wrote: | %%PORTDOCS%%share/doc/libnjb-%%PORTVERSION%%/html/dir_d03f56ed3ef2c0e11ac283c787a57d7a.html | | is in pkg-plist of libnjb, but I got this file: | dir_517a6f2c7427bc36231829858e370602.html | | Therefore package creation fails. :-) it's my fault... stay tuned for a correction within minutes! Thanks for pointing it out! ~ > Jan Henrik - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (FreeBSD) iEYEAREKAAYFAkfmU00ACgkQwMJqmJVx945irACfb1NJLt51bVMMSKIkEeJI9LCE +dwAoLR5Q5nkLt992cyDa698y3VmxLXt =yOp9 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
unbreak emulators/doscmd
Hi Des, I have a patch to unbreak emulators/doscmd on >= 80, would you mind to have a look at it? http://people.freebsd.org/~gahr/doscmd.diff Thanks, Best Regards -- Pietro Cerutti PGP Public Key: http://gahr.ch/pgp signature.asc Description: OpenPGP digital signature
sudo pkg_add -r gives "Syntax error..."
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi list, since a few days I cannot add packages with "sudo pkg_add -r " anymore.. Example: | sudo pkg_add -r screen Error: FTP Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7.0-release/Latest/screen.tbz: Syntax error, command unrecognized pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7.0-release/Latest/screen.tbz' by URL This happens only with "sudo" (pkg_add -r as root works fine). The behavior has been seen on different machines, even on a freshly installed one. Any clue? Tnx! - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (FreeBSD) iEYEAREKAAYFAkfyrzwACgkQwMJqmJVx946HKACffIyLVO6N7vUEN8dRldMGTNf9 uOcAnj0kwsmFFQKgCNzjUSna/msFEvTo =TdDH -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sudo pkg_add -r gives "Syntax error..."
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Pietro Cerutti wrote: | | sudo pkg_add -r screen | Error: FTP Unable to get | ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7.0-release/Latest/screen.tbz: | Syntax error, command unrecognized | pkg_add: unable to fetch | 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7.0-release/Latest/screen.tbz' | by URL | Problem is local.. My gateway didn't like FTP ;) Thanks guys on #bsdports.. - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (FreeBSD) iEYEAREKAAYFAkfzfuYACgkQwMJqmJVx946sUwCcCrE57fx6E3TRBByx8f9sbAi2 R98AoIfC4AW1qtQjzR4gGv+XezKjsrib =kdTA -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Port: sysutils/wmmemload
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Jeremy Chadwick wrote: | Please open a PR on this issue and someone will take care of it. :-) Please don't. I've already done that ;) http://www.freebsd.org/cgi/query-pr.cgi?pr=122384 Best, - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (FreeBSD) iEYEAREKAAYFAkfz8sAACgkQwMJqmJVx946EVgCeMC6VsSUn9PHHqpR628tmWow4 nSYAoJaVXwsTJLcO4yRzxP69UhK7Glm3 =V6vP -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Port: cflowd-2.1.b1_10,1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Eddie Parra wrote: | Ports team, | | According to the URL below, cflowd is "broken" on FreeBSD 7.0 | http://www.freebsd.org/cgi/cvsweb.cgi/ports/net-mgmt/cflowd/ | | I haven't experienced a broken port before. Are ports as old as cflowd | usually fixed? I have been able to patch the port in order to build it, but I don't have any knowledge of the software itself, so would you be so kind to test it using the patch below? http://gahr.ch/FreeBSD/patches/_pending/cflowd.diff If you report success, I will commit the patch. | Thanks, Thank you | -Eddie - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (FreeBSD) iEYEAREKAAYFAkf7yNMACgkQwMJqmJVx947PowCeOzvLq2Od5ftSC5/95KW5cONS MxMAoJDV0UQiFt6lpGEpqTTQRj+Aucra =MuaN -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Port: cflowd-2.1.b1_10,1
Eddie Parra wrote: diff Makefile < cflowd.diff This should have been: patch < cflowd.diff It complied... I will have to test it later tonight / tomorrow. Ok, let me know! Thanks, Thank you -Eddie Pietro Cerutti ___ 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: cflowd-2.1.b1_10,1
Eddie Parra wrote: Pietro, Eddie, Your patch works! Thanks again! Great. Miwi has just committed my patch! Have fun! Tnx miwi! Bye Eddie! -Eddie Pietro Cerutti ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
samba-libsmbclient fails on 8.0-CURRENT
Hi Timur, could you have a look at this? http://gahr.ch:8080/errors/8.0-FreeBSD/samba-libsmbclient-3.0.28.log Tnx, Best! Pietro Cerutti ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: www/links port fails to build with DirectFB library
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Adam Martin wrote: | To whom it might concern, | | I've started a rebuild of all ports, on my home system, and links | port failed, with the libdirectfb. I have fixed it -- the dependancy | line with the "libdirectfb" entry should be changed to "directfb". An update to directfb and thus to links is underway.. please be patient, it will be fixed soon! | Regards, Best, | ADAM David Alan Martin - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (FreeBSD) iEYEAREKAAYFAkgE32cACgkQwMJqmJVx947XKQCgk0P+VSdUAIjC/54Wd6YFYZH1 4OgAn1UxP0W0KKvcN4KWjnIF42B6BJDC =q85c -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
CFT: devel/directfb update to 1.1.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi guys, A patch to update devel/directfb to 1.1.1 is ready to be committed, but I would like to have some feedback first: The following patch updates devel/directfb, games/freesci (dependent) and www/links (dependent): http://www.gahr.ch/FreeBSD/patches/_pending/directfb_complete.diff Please apply the patch as follows: # cd /usr/ports # patch < directfb_complete.diff rebuild devel/directfb, games/freesci and www/links Any feedback is welcome! - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (FreeBSD) iEYEAREKAAYFAkgFP1UACgkQwMJqmJVx947UwwCdEh4SHcvAR+uoBVyEtbISTRC3 uzsAn10tnHNe+p4ljkucY9ohZ0Q5j0i+ =UJoo -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CFT: devel/directfb update to 1.1.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Ganael LAPLANCHE wrote: | On Wed, 16 Apr 2008 01:50:46 +0200, Pietro Cerutti wrote |> Hi guys, | | Hi Pietro, | |> A patch to update devel/directfb to 1.1.1 is ready to be committed, but |> I would like to have some feedback first: | | Unfortunately, it does not compile on my machine (FreeBSD 6.3-STABLE, amd64) : Sorry, I made an error rolling the patch. Please try again, the patch is always at: http://gahr.ch/FreeBSD/patches/_pending/directfb_complete.diff Thanks! | | Best regards, | | Ganaël LAPLANCHE | [EMAIL PROTECTED] | http://www.martymac.com - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (FreeBSD) iEYEAREKAAYFAkgFuxIACgkQwMJqmJVx946OGwCgkpPwPe9uamCjMylIlETUOQmg oI8AmwfEV2JvNCA9D9J/m3GisukylOxS =r8pY -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CFT: devel/directfb update to 1.1.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Ganael LAPLANCHE wrote:
| On Wed, 16 Apr 2008 16:01:43 +0300, Anatoly Borodin wrote
| It produces the same error as previously reported : "No system
found!". Very
| strange, but applying those two patches allows the libs to be found
and mplayer
| to (nearly) start :
|
| --- lib/direct/interface.c.orig 2008-04-12 13:25:57.542006795 +0200
| +++ lib/direct/interface.c 2008-04-12 13:26:27.732927708 +0200
| @@ -164,7 +164,7 @@
| /*
|* Iterate directory.
|*/
| - while (readdir_r( dir, &tmp, &entry ) == 0 && entry) {
| + while (entry = readdir( dir )) {
|void *handle = NULL;
|char buf[4096];
|
| --- lib/direct/modules.c.orig 2008-04-12 13:25:45.166038341 +0200
| +++ lib/direct/modules.c2008-04-12 13:27:56.054698492 +0200
| @@ -158,7 +158,7 @@
|return 0;
| }
|
| - while (readdir_r( dir, &tmp, &entry ) == 0 && entry) {
| + while (entry = readdir( dir )) {
|void *handle;
|DirectModuleEntry *module;
|intentry_len = strlen(entry->d_name);
Actually, there is a bug in those two functions. What about this one?
- --- lib/direct/modules.c.orig 2008-04-16 16:51:42.0 +0200
+++ lib/direct/modules.c2008-04-16 16:51:53.0 +0200
@@ -158,7 +158,7 @@
~ return 0;
~ }
- - while (readdir_r( dir, &tmp, &entry ) == 0 && entry) {
+ while (!readdir_r( dir, &tmp, &entry ) == 0 && entry) {
~ void *handle;
~ DirectModuleEntry *module;
~ intentry_len = strlen(entry->d_name);
- --- lib/direct/interface.c.orig 2008-04-16 16:49:47.0 +0200
+++ lib/direct/interface.c 2008-04-16 16:50:52.0 +0200
@@ -164,7 +164,7 @@
~ /*
~ * Iterate directory.
~ */
- - while (readdir_r( dir, &tmp, &entry ) == 0 && entry) {
+ while (!readdir_r( dir, &tmp, &entry ) && entry) {
~ void *handle = NULL;
~ char buf[4096];
| Best regards,
Best,
| Ganaël LAPLANCHE
- --
Pietro Cerutti
[EMAIL PROTECTED]
PGP Public Key:
http://gahr.ch/pgp
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (FreeBSD)
iEYEAREKAAYFAkgGEwIACgkQwMJqmJVx947LvACgyUDzENJvTKcS+ExOtmrRLF90
l1YAoINBx7I/Qo8rcvELwRa1bi4d/aiO
=KGAo
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CFT: devel/directfb update to 1.1.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Pietro Cerutti wrote:
| Ganael LAPLANCHE wrote:
| | On Wed, 16 Apr 2008 16:01:43 +0300, Anatoly Borodin wrote
|
| | It produces the same error as previously reported : "No system
| found!". Very
| | strange, but applying those two patches allows the libs to be found
| and mplayer
| | to (nearly) start :
| |
| | --- lib/direct/interface.c.orig 2008-04-12 13:25:57.542006795 +0200
| | +++ lib/direct/interface.c 2008-04-12 13:26:27.732927708 +0200
| | @@ -164,7 +164,7 @@
| | /*
| |* Iterate directory.
| |*/
| | - while (readdir_r( dir, &tmp, &entry ) == 0 && entry) {
| | + while (entry = readdir( dir )) {
| |void *handle = NULL;
| |char buf[4096];
| |
| | --- lib/direct/modules.c.orig 2008-04-12 13:25:45.166038341 +0200
| | +++ lib/direct/modules.c2008-04-12 13:27:56.054698492 +0200
| | @@ -158,7 +158,7 @@
| |return 0;
| | }
| |
| | - while (readdir_r( dir, &tmp, &entry ) == 0 && entry) {
| | + while (entry = readdir( dir )) {
| |void *handle;
| |DirectModuleEntry *module;
| |intentry_len = strlen(entry->d_name);
|
| Actually, there is a bug in those two functions. What about this one?
|
| --- lib/direct/modules.c.orig2008-04-16 16:51:42.0 +0200
| +++ lib/direct/modules.c2008-04-16 16:51:53.0 +0200
| @@ -158,7 +158,7 @@
| ~ return 0;
| ~ }
|
| - while (readdir_r( dir, &tmp, &entry ) == 0 && entry) {
| + while (!readdir_r( dir, &tmp, &entry ) == 0 && entry) {
| ~ void *handle;
| ~ DirectModuleEntry *module;
| ~ intentry_len = strlen(entry->d_name);
|
| --- lib/direct/interface.c.orig2008-04-16 16:49:47.0 +0200
| +++ lib/direct/interface.c2008-04-16 16:50:52.0 +0200
| @@ -164,7 +164,7 @@
| ~ /*
| ~ * Iterate directory.
| ~ */
| - while (readdir_r( dir, &tmp, &entry ) == 0 && entry) {
| + while (!readdir_r( dir, &tmp, &entry ) && entry) {
| ~ void *handle = NULL;
| ~ char buf[4096];
|
|
| | Best regards,
| Best,
|
| | Ganaël LAPLANCHE
Sorry, I'm hallucinating... forget it..
- --
Pietro Cerutti
[EMAIL PROTECTED]
PGP Public Key:
http://gahr.ch/pgp
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (FreeBSD)
iEUEAREKAAYFAkgGFDYACgkQwMJqmJVx946ffgCXfxfnwMaD1nmE5Gu19dthTM2n
3QCeLTBhjhyP3ePpYgbkKnGrtRheEAM=
=0+5s
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CFT: devel/directfb update to 1.1.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Ganael LAPLANCHE wrote:
| On Wed, 16 Apr 2008 16:53:55 +0200, Pietro Cerutti wrote
|
| Hi again :)
|
|> Actually, there is a bug in those two functions. What about this one?
|
|> - - while (readdir_r( dir, &tmp, &entry ) == 0 && entry) {
|> + while (!readdir_r( dir, &tmp, &entry ) && entry) {
|
| Hmmm, isn't that similar ? Anyway, it does not seem to work better :/
Indeed, it's identical. It was an error from my part, please forget it. :-/
|
| Ganaël LAPLANCHE
| [EMAIL PROTECTED]
| http://www.martymac.com
|
- --
Pietro Cerutti
[EMAIL PROTECTED]
PGP Public Key:
http://gahr.ch/pgp
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (FreeBSD)
iEYEAREKAAYFAkgGIU4ACgkQwMJqmJVx947dZwCgxwhjto5+J1XJRNB0EFej+HQv
PzUAoMNPADQMBWsEnSoR/IjSN5YlA5bt
=fZaK
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: samba-libsmbclient fails on 8.0-CURRENT
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Pav Lucistnik wrote: | Pietro Cerutti pÃÅ¡e v so 12. 04. 2008 v 13:38 +0200: | |> could you have a look at this? |> |> http://gahr.ch:8080/errors/8.0-FreeBSD/samba-libsmbclient-3.0.28.log | | Is both your host and your jail same OSVERSION? This is the fallout from | lockf changes in current... | Nope, the box is running 7.0-RELEASE and the tindie's jail is on CURRENT. Is there any other solution than upgrading the box to CURRENT? Tnx, - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (FreeBSD) iEYEAREKAAYFAkgHxvsACgkQwMJqmJVx947RFwCfQhKji8GgWdRBKBx3OMdLABz3 OOUAnRwi2p04LBv/+UuKzhn3s1M0rroC =6S2m -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: INDEX build optimizations - please review
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Kris Kennaway wrote: | Another important optimization is to use /rescue/sh instead of /bin/sh | for index builds. The former is statically linked and this is much | faster to execute. True, but the for is not even guaranteed to exist (WITHOUT_RESCUE in src.conf or similar). I would opt for checking, and use it only if it exists | Kris - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREKAAYFAkhOsRUACgkQwMJqmJVx945PpgCeO6ylFV7Lnsizo1p0v9h1jJX1 1RYAn2jwtKuwiy4aXAAsST2CidupEKmO =hsgo -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: INDEX build optimizations - please review
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Pietro Cerutti wrote: | Kris Kennaway wrote: | | | Another important optimization is to use /rescue/sh instead of /bin/sh | | for index builds. The former is statically linked and this is much | | faster to execute. | | True, but the for is not even guaranteed to exist (WITHOUT_RESCUE in | src.conf or similar). "the for"??? err... "the file" I meant.. | | I would opt for checking, and use it only if it exists | | | Kris | - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREKAAYFAkhOsgMACgkQwMJqmJVx946UagCgoLs7no6NgcLPLSn0lzOHyB0M 4HcAn359kBKeDCevr4IM5cOFfEHh6p6q =81w7 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: New Ports: OWAMP
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Guilherme Eliseu Rhoden wrote: | Hi all, | | I've ported owamp (OneWay PING - OneWay active measurement protocol) to | FreeBSD ports. | | I can upload the code to ports CVS. How can I create an CSV accounting | to do this? You can't. CVS isn't open for commits. You better fill-in a PR [1] with your port attached and let someone with CVS write access commit it. [1] http://www.freebsd.org/support/bugreports.html | Thanks, Thanks, | Guilherme - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREKAAYFAkhWvX4ACgkQwMJqmJVx945TugCeMlwKN84OvGr2FKG4mlx0FyRv lDAAoLq6T/6GJHBBeBQxhLFoTkFxId84 =9Vgk -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Question about ports adding cronjobs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 David Hawthorne wrote: | I have a piece of software I've been working on that gathers stats about | the local host and shoves them into rrd files, with an accompanying web | front-end page that generates pretty graphs from the RRDs on demand. I | have a package done up for it, and I'd like to add it to the ports tree | eventually, but I'm stuck on how to get it to automagically add the | cronjob to have the stats gathering script run every five minutes, and I | don't know of any ports that add cronjobs off the top of my head to go | look at. | | Is there an approved standard for doing this? It doesn't have to be as | root, either, it can run under a different user. Any advice on how to | get the port to add the user (and remove it properly when the port is | deinstalled) properly and securely would be appreciated as well. The only port which comes to my mind which goes near to what you want to achieve is sysutils/bsdstats, which installs a script in periodic/monthly. If running daily is enough you may want to look at that. Another option would be to create a support script/daemon and place it in rc.d. The script/daemon would then sit idle and wake up once every and gather your statistics. Third option: instruct the user (via a message at post-install stage) on how to setup the cron job. | | Bonus points for providing the lines that would need to go into a | CONTENTS file for the package, because that's what I'm working with | right now for testing it on multiple machines. | | Thanks! - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREKAAYFAkhYQokACgkQwMJqmJVx945RwgCgqXsRvtIs4zUqp3zxo2Z7g25n R3EAn2ZqcCxPsYwHnrNNq363bPQIK//o =I8a4 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Question about ports adding cronjobs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Robert Huff wrote: | Pietro Cerutti writes: | |> | I |> | have a package done up for it, and I'd like to add it to the ports tree |> | eventually, but I'm stuck on how to get it to automagically add the |> | cronjob to have the stats gathering script run every five minutes, and I |> | don't know of any ports that add cronjobs off the top of my head to go |> | look at. |> | |> | Is there an approved standard for doing this? |> |> Another option would be to create a support script/daemon and |> place it in rc.d. The script/daemon would then sit idle and wake |> up once every and gather your |> statistics. |> |> Third option: instruct the user (via a message at post-install |> stage) on how to setup the cron job. | | I would _much_ prefer either of these. The idea of adding a | cron job - even if there's a message displayed at the end of | installation - makes me nervous. I didn't meant "you add the cronjob and inform the user", but instead "you inform the user how he can setup the cronjob, if he wants so". Anyway, I agree with you. | | | Robert Huff | - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREKAAYFAkhYScUACgkQwMJqmJVx947oOgCfSSezN97mpCgvAxhFyKCsRbBj j64AoLYgmZvSz+SNtOmpB4dZPOusmvxY =kT9k -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Question about ports adding cronjobs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Pietro Cerutti wrote: | Robert Huff wrote: | | Pietro Cerutti writes: | | | |> | I | |> | have a package done up for it, and I'd like to add it to the ports | tree | |> | eventually, but I'm stuck on how to get it to automagically add the | |> | cronjob to have the stats gathering script run every five minutes, | and I | |> | don't know of any ports that add cronjobs off the top of my head | to go | |> | look at. | |> | | |> | Is there an approved standard for doing this? | |> | |> Another option would be to create a support script/daemon and | |> place it in rc.d. The script/daemon would then sit idle and wake | |> up once every and gather your | |> statistics. | |> | |> Third option: instruct the user (via a message at post-install | |> stage) on how to setup the cron job. | | | | I would _much_ prefer either of these. The idea of adding a | | cron job - even if there's a message displayed at the end of | | installation - makes me nervous. | | I didn't meant "you add the cronjob and inform the user", but instead | "you inform the user how he can setup the cronjob, if he wants so". Ups.. I think I've misunderstood your comment. Sorry for the noise. | | Anyway, I agree with you. | | | | | | | Robert Huff | | | | ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]" - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREKAAYFAkhYSjIACgkQwMJqmJVx946kvgCgvvScJErrsY5U9DEAnlRkfO3+ +3AAoMaeOhsFoNL/eavCbvVrEtNbjsdh =a+OV -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Question about ports adding cronjobs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Jeremy Chadwick wrote: | On Wed, Jun 18, 2008 at 01:02:34AM +0200, Pietro Cerutti wrote: |> -BEGIN PGP SIGNED MESSAGE- |> Hash: SHA512 |> |> David Hawthorne wrote: |> | I have a piece of software I've been working on that gathers stats about |> | the local host and shoves them into rrd files, with an accompanying web |> | front-end page that generates pretty graphs from the RRDs on demand. I |> | have a package done up for it, and I'd like to add it to the ports tree |> | eventually, but I'm stuck on how to get it to automagically add the |> | cronjob to have the stats gathering script run every five minutes, and I |> | don't know of any ports that add cronjobs off the top of my head to go |> | look at. |> | |> | Is there an approved standard for doing this? It doesn't have to be as |> | root, either, it can run under a different user. Any advice on how to |> | get the port to add the user (and remove it properly when the port is |> | deinstalled) properly and securely would be appreciated as well. |> |> The only port which comes to my mind which goes near to what you want to |> achieve is sysutils/bsdstats, which installs a script in periodic/monthly. |> If running daily is enough you may want to look at that. |> |> Another option would be to create a support script/daemon and place it |> in rc.d. The script/daemon would then sit idle and wake up once every |> and gather your statistics. |> |> Third option: instruct the user (via a message at post-install stage) on |> how to setup the cron job. | | Or a fourth option: do what mail/postfix does, and prompt you | interactively during the install phase whether or not you want | done to your system. In the case of mail/postfix, it prompts you to | permit modification of /etc/mail/mailer.conf. Thought that as well, but it complicates package building and doesn't bring much. I mean, to echo "add xx yy to your crontab" is not a big deal.. | | Automatic modification of cronjobs, system files, etc. == generally | shunned. I don't mind if the port asks me for permission to do such, | but I do mind if it blindly starts modifying things on my system without | my approval. | - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREKAAYFAkhYT9gACgkQwMJqmJVx947y6gCgw8EPXi4iyaQuKHB4E0nAMCDX 4YYAoJ6LHH3zgki6D4LFb3oa2fUv3g3q =SByC -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: INDEX build optimizations - please review
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Kris Kennaway wrote:
| Pietro Cerutti wrote:
|> -BEGIN PGP SIGNED MESSAGE-
|> Hash: SHA512
|>
|> Kris Kennaway wrote:
|>
|> | **
|> | * NOTE TO PORT DEVELOPERS
|> | **
|> |
|> | Variable assignments with != are bad! Try as hard as you can to avoid
|> | using them -- especially in Mk/*! Every time something processes your
|> | makefile it will spawn a command, even if it is not relevant for the
|> | operation being performed. If you need to run shell commands, try to
|> | isolate them within a makefile target. You can avoid code duplication
|> | by assigning the *shell commands* (not their output) to a variable and
|> | inserting it into your code block.
|> |
|> | e.g. instead of
|> |
|> | --
|> | VARIABLE!=do some shell stuff; do some other stuff
|> |
|> | target:
|> | echo ${VARIABLE}
|> | --
|> |
|> | do this (or similar):
|> |
|> | --
|> | VARIABLE_CMDS=do some shell stuff; do some other stuff
|> |
|> | target:
|> | echo $(${VARIABLE_CMDS})
|> | --
|> |
|> | This defers the command execution to the point where the target
|> runs, so
|> | in the case when the target is *not* run, then you avoid wasting one or
|> | more process executions.
|>
|> Yes, in theory.
|>
|> Any clue why this doesn't work?
|>
|> SCHED_NAME= sysctl -n kern.sched.name
|>
|> all:
|> ~ echo $(${SCHED_NAME})
|
| Try $$(${SCHED_NAME}) (escape the $ you don't want make to process)
mh yep... :) tnx!
|
| Kris
- --
Pietro Cerutti
[EMAIL PROTECTED]
PGP Public Key:
http://gahr.ch/pgp
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (FreeBSD)
iEYEAREKAAYFAkhaNa4ACgkQwMJqmJVx944OVgCggOX/Pa/LkLltaQM/Orl+NESL
SXAAn0tIPuesfM1DNU8Fnf89wHufU3+F
=/McK
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: INDEX build optimizations - please review
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Kris Kennaway wrote:
| **
| * NOTE TO PORT DEVELOPERS
| **
|
| Variable assignments with != are bad! Try as hard as you can to avoid
| using them -- especially in Mk/*! Every time something processes your
| makefile it will spawn a command, even if it is not relevant for the
| operation being performed. If you need to run shell commands, try to
| isolate them within a makefile target. You can avoid code duplication
| by assigning the *shell commands* (not their output) to a variable and
| inserting it into your code block.
|
| e.g. instead of
|
| --
| VARIABLE!=do some shell stuff; do some other stuff
|
| target:
| echo ${VARIABLE}
| --
|
| do this (or similar):
|
| --
| VARIABLE_CMDS=do some shell stuff; do some other stuff
|
| target:
| echo $(${VARIABLE_CMDS})
| --
|
| This defers the command execution to the point where the target runs, so
| in the case when the target is *not* run, then you avoid wasting one or
| more process executions.
Yes, in theory.
Any clue why this doesn't work?
SCHED_NAME= sysctl -n kern.sched.name
all:
~echo $(${SCHED_NAME})
|
| Kris
|
- --
Pietro Cerutti
[EMAIL PROTECTED]
PGP Public Key:
http://gahr.ch/pgp
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (FreeBSD)
iEYEAREKAAYFAkhaMxIACgkQwMJqmJVx945CEgCePoNe6vevue/Hfww4DpM0vJrM
r/gAn0aAJ+Y68FqLSi7axSdOHuo5EiY4
=6LX2
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
CFT: audio/lilypond update to 2.11.47
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear all, I have a patch to update audio/lilypond to 2.11.47. Lilypond builds fine according to my tests, but since I have little familiarity with the software itself I thing I'll go for a CFT and wait for feedback before committing the patch. Please test & report failure / success: http://gahr.ch/FreeBSD/patches/_pending/lilypond.diff Thanks! - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREKAAYFAkhbrz0ACgkQwMJqmJVx945aIQCfeFc5f+i7Z2nnU8O8AF2Q4Ic9 p9wAn0jIK8jMEuYopXLg3Ri1BGvX6491 =TTnt -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Creating New Port - Question about Installation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Schiz0 wrote:
| Hey,
|
| I'm attempting to create a new port for btsh:
| http://btsh.sourceforge.net/
| The website isn't finished yet, but it's a command-line interface for
| torrent websites.
|
| Anyway, the original .tar.bz2 that the author wrote has no configure
| script or makefile. All it has is an "INSTALL" script. The INSTALL
| script prompts for a directory to install to, then copies the proper
| files over and sets some permissions.
|
| I'm wondering how I can create a port out of this. I read the porters
| handbook and developed a Makefile so far:
|
|
| # Ports Makefile for: btsh
| # Date created:June 26 2008
| # Whom:Schiz0
| #
| # $FreeBSD$
| #
| PORTNAME=btsh
| PORTVERSION=0.1.1
| CATEGORIES=net-p2p shells
| # Eventually the project is moving over to sourceforge
| MASTER_SITES=http://labgecko.com/btsh/
| [EMAIL PROTECTED]
| COMMENT=BitTorrent SHell
| BUILD_DEPENDS=bash:${PORTSDIR}/shells/bash
| BUILD_DEPENDS=wget:${PORTSDIR}/ftp/wget
The second BUILD_DEPENDS definition will overwrite the first one. Use:
BUILD_DEPENDS= bash:${PORTSDIR}/shells/bash \
wget:${PORTSDIR}}/ftp/wget
Moreover, sure they're not RUN_DEPENDS as well?
| USE_BZIP2=yes
| NO_INSTALL_MANPAGES=yes
| .include
|
|
| Basically, I'm wondering how I can do this. Should I set NO_BUILD and
| HAS_CONFIGURE to prevent FreeBSD from trying to build and configure it
| itself?
|
| Also, is this port in the correct cateorgies? This is not a BitTorrent
| client, it's just a cli interface to the torrent websites. It lets
| users read the forums, search for torrents, reply to inbox PMs, etc.
|
| This is my first attempt at building a port, so any
| pointers/suggestions/etc will be extremely helpful.
|
| Thank you!
| ___
| freebsd-ports@freebsd.org mailing list
| http://lists.freebsd.org/mailman/listinfo/freebsd-ports
| To unsubscribe, send any mail to "[EMAIL PROTECTED]"
- --
Pietro Cerutti
[EMAIL PROTECTED]
PGP Public Key:
http://gahr.ch/pgp
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (FreeBSD)
iEYEAREKAAYFAkhkKAgACgkQwMJqmJVx944hLQCeOBx5OTW1axIuMyKBVS+HpKbw
CucAni42lJp9SPlffVaZAue43qx/agZq
=A5nu
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports/124985: [patch] devel/dmucs unbreak on 64bits archs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 [EMAIL PROTECTED] wrote: | Synopsis: [patch] devel/dmucs unbreak on 64bits archs | | State-Changed-From-To: open->closed | State-Changed-By: fjoe | State-Changed-When: Mon Jul 7 16:18:07 UTC 2008 | State-Changed-Why: | Proper integer type for holding pointers is "long", not "size_t". I definitely do not agree. Please note that a pointer is not required to fit into a long, while it is required to fit into a size_t. Your solution may work as soon as we are concerned only with LP64 machines. As soon as a LLP64 arch steps in, you break things. | Also, std:map<> containers where sockets are stored should be modified. | | Corrected version of the patch committed, thanks! | | http://www.freebsd.org/cgi/query-pr.cgi?pr=124985 - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREKAAYFAkhyRa0ACgkQwMJqmJVx9442QgCg2AjK428zBbh/KxEtrCVPee1q P80An0H65+EJ79ctx4YpycrwuOkwOttV =4zPQ -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Port: nut-2.2.2
gt; dstate-hal.c: At top level: |> dstate-hal.c:642: error: syntax error before '*' token |> dstate-hal.c: In function `hal_set_bool': |> dstate-hal.c:647: error: `key' undeclared (first use in this function) |> dstate-hal.c:647: error: `value' undeclared (first use in this function) |> dstate-hal.c:659: warning: implicit declaration of function |> `libhal_changeset_set_property_bool' |> dstate-hal.c:659: error: `cs' undeclared (first use in this function) |> dstate-hal.c: At top level: |> dstate-hal.c:125: warning: 'nut2hal_cmd' defined but not used |> gmake[1]: *** [dstate-hal.o] Error 1 |> gmake[1]: Leaving directory `/usr/ports/sysutils/nut/work/nut-2.2.2 |> /drivers' |> gmake: *** [all-recursive] Error 1 |> *** Error code 2 | |> Stop in /usr/ports/sysutils/nut. |> *** Error code 1 | |> Stop in /usr/ports/sysutils/nut. | | |> computer: FreeBSD pbsd 6.3-RELEASE FreeBSD 6.3-RELEASE #1: Fri Feb 15 |> 09:53:17 EST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PATRIOTEBSD i386 | | Hi Yves, | | what OPTIONS did you select? Can you please 'cd' to the ports directory | and run 'make config' and write me what is selected or not. Or just paste the output of make showconfig :) | As it seems to be related to "hal", what version of the "hal port" is | installed on your system, make sure that hal is up to date. | | Regards | Joerg | | -- The beginning is the most important part of the work. | -Plato ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]" - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREKAAYFAkhyRg0ACgkQwMJqmJVx947kKQCgzLGxC+YolvFsYxpEB9xDA+Cm VvIAoIMLwjxzshKCr7qSe484aKvfLNLD =Ub+N -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports/124985: [patch] devel/dmucs unbreak on 64bits archs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Kostik Belousov wrote: | On Mon, Jul 07, 2008 at 06:34:54PM +0200, Pietro Cerutti wrote: |> I definitely do not agree. Please note that a pointer is not required to |> fit into a long, while it is required to fit into a size_t. | I do not think that C99 requires the size_t to be capable of holding | the pointer. size_t is only required to hold result of sizeof. size_t is required to be of rank equal to or greater than any other object you can create from within the C language. This implies that it can (i.e., it is required to be able to) hold a pointer type. | | It is intptr_t type that shall do it. Unfortunately intptr_t is not defined prior to C99, and I still haven't got used to use it. Yes, that would be the preferred solution. - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREKAAYFAkhyUFAACgkQwMJqmJVx947UnACcDktT+bwe6LLs3/YPBief8PO3 Ku8AoN6AUlCVXmnbbyBEIdVLDORUdWpr =IGu+ -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports/124985: [patch] devel/dmucs unbreak on 64bits archs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Max Khon wrote: | Hello! | | Pietro Cerutti wrote: | |> | On Mon, Jul 07, 2008 at 06:34:54PM +0200, Pietro Cerutti wrote: |> |> I definitely do not agree. Please note that a pointer is not |> required to |> |> fit into a long, while it is required to fit into a size_t. |> | I do not think that C99 requires the size_t to be capable of holding |> | the pointer. size_t is only required to hold result of sizeof. |> |> size_t is required to be of rank equal to or greater than any other |> object you can create from within the C language. This implies that it |> can (i.e., it is required to be able to) hold a pointer type. | | Does it? http://bytes.com/forum/thread735346.html It doesn't. My error. Seems that the only way to go is intptr_t ... | | /fjoe | ___ | freebsd-ports@freebsd.org mailing list | http://lists.freebsd.org/mailman/listinfo/freebsd-ports | To unsubscribe, send any mail to "[EMAIL PROTECTED]" - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREKAAYFAkhyWDMACgkQwMJqmJVx9465fwCgoq5XXPQUivHMiOH6SvrUyoIS 1LwAoK8BCVCZ9UvK/mH9h/kVACLvyQ3F =0LyT -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Clang as default compiler November 4th
On 2012-Sep-11, 23:29, Doug Barton wrote: > What we need to do is what I and others have been asking to do for > years. We need to designate a modern version of gcc (no less than 4.6) > as the official default ports compiler, and rework whatever is needed to > support this. Fortunately, that goal is much more easily achieved than > fixing ports to build and run with clang. (It's harder than it sounds > because there are certain key libs that define some paths depending on > what compiler they were built with, but still easier than dealing with > clang in the short term.) I like the idea very much. My only concern is that gcc is heavy to build. I can't imagine booting into a freshly installed production machine and having to install gcc just to build the couple of ports that I need there. Unless we provide a fast shortcut way to have make depends install gcc via pkg when needed, or some similar mechanism.. -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpjvBufkSprf.pgp Description: PGP signature
Re: [BRAINSTORMIG] name of the variable for passing command line options via make
On 2012-Sep-25, 00:15, Baptiste Daroussin wrote: > Hi, > > One of the missing thing since we switch to OptionNG is a reliable ability to > pass options via command line that would override make.conf and config file > options. > > Here is an implementation that do work: > http://people.freebsd.org/~bapt/OVERRIDE_BLA.diff > > Now OVERRIDE_SET/UNSET doesn't seems to be the best name :) > > http://www.freebsd.org/cgi/query-pr.cgi?pr=170180 > > Here are other proposition from me: > LATE_SET/UNSET > CMD_SET/UNSET WITH / WITHOUT -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgp324gvT9ZY5.pgp Description: PGP signature
Re: Conflict between lang/tcl85 and x11-toolkits/open-motif?
On 2012-Oct-23, 05:02, Thomas Mueller wrote: > Is there a conflict between lang/tcl85 and x11-toolkits/open-motif, not > documented in the Makefiles, like trying to install files to the same place? > > Trying in many steps, stopped by so many snags, I am trying to rebuild all > ports depending on png, starting from "portmaster -r png-", and this is > stopping me. > > I show relevant portion of the log: > > Installing and cross-linking C API (.3) docs > Installing and cross-linking command (.n) docs > ** > IMPORTANT: > ** > tclConfig.sh in /usr/local/lib/tcl8.5/tclConfig.sh > tcl.hin /usr/local/include/tcl8.5/tcl.h > tclDecls.h in /usr/local/include/tcl8.5/tclDecls.h > There are NOT default place, but good place to avoid > conflicting with another version of Tcl/Tks. > ===> Compressing manual pages for tcl-8.5.12_2 > ===> Running ldconfig > /sbin/ldconfig -m /usr/local/lib > ===> Registering installation for tcl-8.5.12_2 > Installing tcl-8.5.12_2...pkg: tcl-8.5.12_2 conflicts with open-motif-2.3.3 > (ins > talls files into the same place). Problematic file: > /usr/local/man/man3/Object. > 3.gz > *** [fake-pkg] Error code 70 > > Stop in /BETA1/usr/ports/lang/tcl85. > *** [install] Error code 1 > > Stop in /BETA1/usr/ports/lang/tcl85. > > (end of quoted portion of log) > > Where do I go from here? I didn't find any conflicts between lang/tcl85 and > x11-toolkits/open-motif documented in the Makefiles. Yes the problem exists indeed. I suggest that you reconfigure (make config) in lang/tcl85 and unselect the TCL85_MAN option, then reinstall tcl85. -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpzQfBbgc0LL.pgp Description: PGP signature
Re: tk85 Port Maintenance
On 2012-Oct-31, 08:36, Joseph a Nagy Jr wrote: > On 10/31/12 08:24, Chris Rees wrote: > > On 31 October 2012 13:03, Joseph a Nagy Jr wrote: > >> Hi All, > >> > >> I'd like to volunteer to maintain the tk85 port. I've already begun > >> making updates to the Makefile[0] in a workbench directory and have a > >> working update to it. All changes were due to feedback from portlint. > >> Any and all feedback would be appreciated. > > > > I've set you as maintainer. > > > >> [0]: http://pastebin.com/6DuzdAzv > > > > Did you check with Martin Matuska that he's OK with removing the > > attribution lines? > > I was being helped with this by a gentleman on FreeNode in ##copyfree > (s/he's also in ##freebsd (trout)). If that's not acceptable practice I > can undo it. > > I've emailed Martin about another port (tk-wrapper) and have yet to > receive a response. I was wanting to not send another email if the first > was unwelcome. I'll check with him asap. > > > Why are you using LIB_DEPENDS instead of USE_TCL? > > It was in the original Makefile and saw no reason to change it. I can > make that change though. > > > Check it's not a master port before you remove the ? from COMMENT too. > > > 10-4. Please be informed that I have in the pipeline some work on Tcl/Tk ports, including removal of the -thread slaves. Having said that, I don't have any major concerns about you taking maintainership of tk85, apart from the technical details pointed out by Chris, and I have not looked at the patch very carefully, but if you're going to touch the Tcl ports as well, I'd like the two of us to collaborate and sync work. Are you also interested in taking lang/tcl85? Thanks! -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpTGHEgsyQBk.pgp Description: PGP signature
Re: tk85 Port Maintenance
On 2012-Oct-31, 08:03, Joseph a Nagy Jr wrote: > Hi All, > > I'd like to volunteer to maintain the tk85 port. I've already begun > making updates to the Makefile[0] in a workbench directory and have a > working update to it. All changes were due to feedback from portlint. > Any and all feedback would be appreciated. > > [0]: http://pastebin.com/6DuzdAzv Ehm, your diff fails to apply here.. -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpZdRNPZ2Wvp.pgp Description: PGP signature
Re: tk85 Port Maintenance
On 2012-Oct-31, 09:14, Joseph a Nagy Jr wrote: > On 10/31/12 08:57, Pietro Cerutti wrote: > > On 2012-Oct-31, 08:03, Joseph a Nagy Jr wrote: > >> Hi All, > >> > >> I'd like to volunteer to maintain the tk85 port. I've already begun > >> making updates to the Makefile[0] in a workbench directory and have a > >> working update to it. All changes were due to feedback from portlint. > >> Any and all feedback would be appreciated. > >> > >> [0]: http://pastebin.com/6DuzdAzv > > > > Ehm, your diff fails to apply here.. > > > > What's the issue? > patch < tk85.diff Hmm... Looks like a unified diff to me... The text leading up to this was: -- |--- Makefile.orig 2012-10-26 19:47:37.0 -0500 |+++ Makefile 2012-10-29 20:16:13.0 -0500 -- Patching file Makefile using Plan A... Reversed (or previously applied) patch detected! Assume -R? [y] Hunk #1 succeeded at 1 with fuzz 2. Hunk #2 failed at 12. Hunk #3 failed at 42. Hunk #4 failed at 61. Hunk #5 failed at 423. 4 out of 5 hunks failed--saving rejects to Makefile.rej done -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpkzJn4B7S6M.pgp Description: PGP signature
Re: tk85 Port Maintenance
On 2012-Oct-31, 15:25, Chris Rees wrote: > On 31 Oct 2012 15:21, "Pietro Cerutti" wrote: > > > > On 2012-Oct-31, 09:14, Joseph a Nagy Jr wrote: > > > On 10/31/12 08:57, Pietro Cerutti wrote: > > > > On 2012-Oct-31, 08:03, Joseph a Nagy Jr wrote: > > > >> Hi All, > > > >> > > > >> I'd like to volunteer to maintain the tk85 port. I've already begun > > > >> making updates to the Makefile[0] in a workbench directory and have a > > > >> working update to it. All changes were due to feedback from portlint. > > > >> Any and all feedback would be appreciated. > > > >> > > > >> [0]: http://pastebin.com/6DuzdAzv > > > > > > > > Ehm, your diff fails to apply here.. > > > > > > > > > > What's the issue? > > > > > patch < tk85.diff > > Hmm... Looks like a unified diff to me... > > The text leading up to this was: > > -- > > |--- Makefile.orig 2012-10-26 19:47:37.0 -0500 > > |+++ Makefile 2012-10-29 20:16:13.0 -0500 > > -- > > Patching file Makefile using Plan A... > > Reversed (or previously applied) patch detected! Assume -R? [y] > > Hunk #1 succeeded at 1 with fuzz 2. > > Hunk #2 failed at 12. > > Hunk #3 failed at 42. > > Hunk #4 failed at 61. > > Hunk #5 failed at 423. > > 4 out of 5 hunks failed--saving rejects to Makefile.rej > > done > > > > Say no to -r detected; it's noticed the maintainer change. > patch < tk85.diff Hmm... Looks like a unified diff to me... The text leading up to this was: -- |--- Makefile.orig 2012-10-26 19:47:37.0 -0500 |+++ Makefile 2012-10-29 20:16:13.0 -0500 -- Patching file Makefile using Plan A... Reversed (or previously applied) patch detected! Assume -R? [y] n Apply anyway? [n] y Hunk #1 failed at 1. Hunk #2 failed at 7. Hunk #3 failed at 40. Hunk #4 failed at 58. Hunk #5 failed at 420. 5 out of 5 hunks failed--saving rejects to Makefile.rej done -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgp80x5kbhkEQ.pgp Description: PGP signature
Re: tk85 Port Maintenance
On 2012-Oct-31, 11:28, Joseph a Nagy Jr wrote:
> On 10/31/12 10:39, Pietro Cerutti wrote:
>
> >> patch < tk85.diff
> > Hmm... Looks like a unified diff to me...
> > The text leading up to this was:
> > --
> > |--- Makefile.orig 2012-10-26 19:47:37.0 -0500
> > |+++ Makefile 2012-10-29 20:16:13.0 -0500
> > --
> > Patching file Makefile using Plan A...
> > Reversed (or previously applied) patch detected! Assume -R? [y] n
> > Apply anyway? [n] y
> > Hunk #1 failed at 1.
> > Hunk #2 failed at 7.
> > Hunk #3 failed at 40.
> > Hunk #4 failed at 58.
> > Hunk #5 failed at 420.
> > 5 out of 5 hunks failed--saving rejects to Makefile.rej
> > done
> >
>
> New diff[0], undoing some of the earlier changes even though portlint
> complains:
>
> portlint ~/port-maintenance/tk85/
> WARN: Makefile: unless this is a master port, COMMENT has to be set by
> "=", not by "?=".
This *is* a master port, so it's ok to have COMMENT?=
> WARN: Makefile: "LIB_DEPENDS" has to appear earlier.
This should be fixed as portlint suggests.
> WARN: Makefile: no port directory
> /usr/ports/lang/tcl${SHORT_TK_VER}-thread found, even though it is
> listed in LIB_DEPENDS.
I would try and use USE_TCL instead of LIB_DEPENDS here
> WARN: Makefile: LIB_DEPENDS don't specify the ABI version number .2 in
> Xft.2 unless it is really necessary.
This should be fixed as portlint suggests.
> 0 fatal errors and 4 warnings found.
>
> [0]: http://pastebin.com/apf1Y9H0
I'll have a look at it on Friday, thanks!
--
Pietro Cerutti
The FreeBSD Project
g...@freebsd.org
PGP Public Key:
http://gahr.ch/pgp
pgp7yUKsu0zLC.pgp
Description: PGP signature
Re: tk85 Port Maintenance
On 2012-Oct-31, 12:41, Joseph a Nagy Jr wrote:
> On 10/31/12 11:55, Pietro Cerutti wrote:
> > On 2012-Oct-31, 11:28, Joseph a Nagy Jr wrote:
>
> >> New diff[0], undoing some of the earlier changes even though portlint
> >> complains:
> >>
> >> portlint ~/port-maintenance/tk85/
> >> WARN: Makefile: unless this is a master port, COMMENT has to be set by
> >> "=", not by "?=".
> >
> > This *is* a master port, so it's ok to have COMMENT?=
> >
> >> WARN: Makefile: "LIB_DEPENDS" has to appear earlier.
> >
> > This should be fixed as portlint suggests.
> >
> >> WARN: Makefile: no port directory
> >> /usr/ports/lang/tcl${SHORT_TK_VER}-thread found, even though it is
> >> listed in LIB_DEPENDS.
> >
> > I would try and use USE_TCL instead of LIB_DEPENDS here
> >
> >> WARN: Makefile: LIB_DEPENDS don't specify the ABI version number .2 in
> >> Xft.2 unless it is really necessary.
> >
> > This should be fixed as portlint suggests.
> >
> >> 0 fatal errors and 4 warnings found.
> >>
> >> [0]: http://pastebin.com/apf1Y9H0
> >
> > I'll have a look at it on Friday, thanks!
> >
> >
>
> Going ahead to make those changes, old pastebin link is defunct.
>
> New diff with all changes:
> http://pastebin.com/iwhpXfcp
This won't apply, either. Could you provide a diff as dumped by svn diff
in tk85's directory?
--
Pietro Cerutti
The FreeBSD Project
g...@freebsd.org
PGP Public Key:
http://gahr.ch/pgp
pgphqntzhLdqz.pgp
Description: PGP signature
Re: tk85 Port Maintenance
On 2012-Nov-04, 08:48, Joseph a Nagy Jr wrote:
> On 11/02/12 06:21, Pietro Cerutti wrote:
> > On 2012-Oct-31, 12:41, Joseph a Nagy Jr wrote:
> >> On 10/31/12 11:55, Pietro Cerutti wrote:
> >>> On 2012-Oct-31, 11:28, Joseph a Nagy Jr wrote:
> >>
> >>>> New diff[0], undoing some of the earlier changes even though portlint
> >>>> complains:
> >>>>
> >>>> portlint ~/port-maintenance/tk85/
> >>>> WARN: Makefile: unless this is a master port, COMMENT has to be set by
> >>>> "=", not by "?=".
> >>>
> >>> This *is* a master port, so it's ok to have COMMENT?=
> >>>
> >>>> WARN: Makefile: "LIB_DEPENDS" has to appear earlier.
> >>>
> >>> This should be fixed as portlint suggests.
> >>>
> >>>> WARN: Makefile: no port directory
> >>>> /usr/ports/lang/tcl${SHORT_TK_VER}-thread found, even though it is
> >>>> listed in LIB_DEPENDS.
> >>>
> >>> I would try and use USE_TCL instead of LIB_DEPENDS here
> >>>
> >>>> WARN: Makefile: LIB_DEPENDS don't specify the ABI version number .2 in
> >>>> Xft.2 unless it is really necessary.
> >>>
> >>> This should be fixed as portlint suggests.
> >>>
> >>>> 0 fatal errors and 4 warnings found.
> >>>>
> >>>> [0]: http://pastebin.com/apf1Y9H0
> >>>
> >>> I'll have a look at it on Friday, thanks!
> >>>
> >>>
> >>
> >> Going ahead to make those changes, old pastebin link is defunct.
> >>
> >> New diff with all changes:
> >> http://pastebin.com/iwhpXfcp
> >
> > This won't apply, either. Could you provide a diff as dumped by svn diff
> > in tk85's directory?
> >
>
> Try this diff:
> http://pastebin.com/9YacWnss
* I won't comment on the LICENSE stuff, I don't know enough about it
* XFT_DESC
This is already defined in bsd.options.desc.mk. I'd say that
"Xft font library" is ok as a description.
* LIB_DEPENDS+= Xft:${PORTSDIR}/x11-fonts/libXft
This should really be
USE_XORG+= xft
* LIB_DEPENDS= tcl${SHORT_TK_VER}${THREADS_SUFFIX}:
If you're ok to wait until I get rid of the -thread slave ports,
you don't need to bother about this part of the Makefile
--
Pietro Cerutti
The FreeBSD Project
g...@freebsd.org
PGP Public Key:
http://gahr.ch/pgp
pgprpYlO1sP79.pgp
Description: PGP signature
Re: tk85 Port Maintenance
On 2012-Nov-07, 17:12, Joseph a Nagy Jr wrote:
> On 11/06/12 02:20, Pietro Cerutti wrote:
>
> > * I won't comment on the LICENSE stuff, I don't know enough about it
> >
> > * XFT_DESC
> > This is already defined in bsd.options.desc.mk. I'd say that
> > "Xft font library" is ok as a description.
> >
> > * LIB_DEPENDS+= Xft:${PORTSDIR}/x11-fonts/libXft
> > This should really be
> > USE_XORG+= xft
> >
> > * LIB_DEPENDS= tcl${SHORT_TK_VER}${THREADS_SUFFIX}:
> > If you're ok to wait until I get rid of the -thread slave ports,
> > you don't need to bother about this part of the Makefile
> >
>
> svn checked out, svn diff
>
> http://pastebin.com/kLdUFp9H
-XFT_DESC= Use Xft fonts
+XFT_DESC= Xft font library
This is not needed. As I said, XFT_DESC is already defined in
bsd.options.desc.mk
The tr -> ${TR} conversion is also wrong, you're changing what the sed
liner is looking for. If you do so, it won't find it anymore.
By the way, Tcl/Tk 8.5.13 is bound to be released in the next few days
(the first RC is out now, actually). You might want to include the
update in your diff :)
--
Pietro Cerutti
The FreeBSD Project
g...@freebsd.org
PGP Public Key:
http://gahr.ch/pgp
pgpmPUtle5SX3.pgp
Description: PGP signature
Need help with net-im/openfire
Hi porters, can anybody pick up net-im/openfire? I've been maintaining the port for years, but I can't keep up with it anymore. I am not using the port myself so I can't anticipate issues, plus the build system has changed from Ant to Maven, which I fear means additional time put into updating the port. I simply don't have the resources. If you are using the port, please consider maintaining it (send me an email and I'll assign you if you're not a committer). I will not update it and release maintainership soon. I have a few contacts of people using OpenFire, so I can still be a point of contact and commit patches and updates, given someone cooks them up for me. Thanks for your help! -- Pietro Cerutti ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: baikal-0.6.1
On Jun 15 2020, 21:47 UTC, Jim - OPP wrote: Are there any plans to update the port to version 0.7.0 in the bear future? The current port is requiring PHP 7.2 which ended active support in Nov 2019 and ends security only fixes in just over 5 months. The newest version has added support for PHP 7.4 per GitHub. Hi, I just pushed an update to 0.7.1 in r539335. I haven't tested it with 7.4 yet, but I plan to upgrade my server to it asap. Thanks for the heads up. -- Pietro Cerutti ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: tk85 Port Maintenance
On 2012-Nov-08, 09:12, Joseph a Nagy Jr wrote: > On 11/08/12 03:13, Pietro Cerutti wrote: > > > By the way, Tcl/Tk 8.5.13 is bound to be released in the next few days > > (the first RC is out now, actually). You might want to include the > > update in your diff :) > > > > http://pastebin.com/UmasjFfz I fear this won't be enough. There are implications of the update that you're not considering, e.g., PORTREVISION, distinfo, modifications to the patch files, ... I suggest that you take a step back and read the FreeBSD's Porters Handbook [1]. It is very well written and contains a lot of information you cannot do without if you plan to maintain a port. I'll be submitting a patch for the update to 8.5.13 (was released earlier today) shortly. Thanks, [1] http://www.freebsd.org/doc/en/books/porters-handbook/book.html -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpwebEROClmp.pgp Description: PGP signature
Re: tk85 Port Maintenance
On 2012-Nov-14, 14:52, Joseph a Nagy Jr wrote: > Off-list > > On 11/13/12 01:59, Pietro Cerutti wrote: > > On 2012-Nov-08, 09:12, Joseph a Nagy Jr wrote: > >> On 11/08/12 03:13, Pietro Cerutti wrote: > >> > >>> By the way, Tcl/Tk 8.5.13 is bound to be released in the next few days > >>> (the first RC is out now, actually). You might want to include the > >>> update in your diff :) > >>> > >> > >> http://pastebin.com/UmasjFfz > > > > I fear this won't be enough. There are implications of the update that > > you're not considering, e.g., PORTREVISION, distinfo, modifications to > > the patch files, ... > > > > I suggest that you take a step back and read the FreeBSD's Porters > > Handbook [1]. It is very well written and contains a lot of information > > you cannot do without if you plan to maintain a port. > > I'm sorry, I'm not seeing what I'm missing. As I said, PORTREVISION, distinfo, and the patch files. Look them up in the handbook. -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpkkW10QTA4p.pgp Description: PGP signature
[HEADS UP] Tcl/Tk on FreeBSD
Hello, it is a honour to me to announce that we finally have an official ML dedicated to the maintainance of Tcl/Tk -related ports on FreeBSD. It's tc...@freebsd.org. It's open, and you're welcome to join [1]. We have set up a Wiki page at http://wiki.freebsd.org/TclTk and an IRC channel on EFNet/#freebsd-tcltk. We're really at the beginning and starting to organize work. It's gonna be fun! Among other things, we're planning to slowly move Tcl/Tk -related ports under the maintenance of tc...@freebsd.org. If this rings a bell for a port that you're currently maintaining, please get in touch with us! We are not going to take anything by force, though. [1] http://lists.freebsd.org/mailman/listinfo/freebsd-tcltk Hope to see you soon on TclTk@ and EFNet/#freebsd-tcltk! Pietro (subscriber #2 of tcltk@) -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpGd4qFQ5NVS.pgp Description: PGP signature
