[9.0 RC1] Unable to build Image Magik and glib-20
hi mates, I get build-failures while i try to update the following ports, with the help of portmaster: * devel/glib20 config.status: executing glib/glibconfig.h commands config.status: executing chmod-scripts commands === Building for glib-2.28.8_2 make all-recursive make: illegal option -- - usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable] [-d flags] [-E variable] [-f makefile] [-I directory] [-j max_jobs] [-m directory] [-V variable] [variable=value] [target ...] gmake: *** [all] Erreur 2 *** Error code 1 Stop in /usr/ports/devel/glib20. *** Error code 1 Stop in /usr/ports/devel/glib20. === make failed for devel/glib20 === Aborting update --- *graphics/ImageMagik === Building for ImageMagick-6.7.3.4 /bin/sh ./config/mkinstalldirs . ltdl/ cp ./ltdl/argz_.h ltdl/argz.h-t mv ltdl/argz.h-t ltdl/argz.h make all-am make: illegal option -- - usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable] [-d flags] [-E variable] [-f makefile] [-I directory] [-j max_jobs] [-m directory] [-V variable] [variable=value] [target ...] gmake: *** [all] Erreur 2 *** Error code 1 Stop in /usr/ports/graphics/ImageMagick. *** Error code 1 Stop in /usr/ports/graphics/ImageMagick. === make failed for graphics/ImageMagick === Aborting update === Update for graphics/ImageMagick failed === Aborting update 'Sounds like there is something missing or outdated in ports/Mk ? Thanks in advance. -- David Marec, mailto:david.ma...@davenulle.org http://user.lamaiziere.net/david/Site http://www.diablotins.org/ ___ 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: Recent ports removal
* Martin Wilke (m...@freebsd.org) wrote: They have been deprecated for a while and noone said anything about those, that is the purpose of the DEPRECATED status. The not used anymore mean not used in Why should we go through it again and again? If it's not broken, it's useable, you may not remove it, period. the portstree (ie no more depended on). Most of the portstree is leaf ports, now what? If someone really needs it, he can: What we need is to not have to do extra work and to not have extra noise on the maillist because someone does unneeded things. I really don't want to call that vandalism. You can't only put in u have also to put out. Why don't we take out Gnome and KDE then? I don't use it. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru ___ 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
mysql-gui-tools
Hi, I've noticed that the mysql-gui-tools port has been removed. A few months ago I had found a way to fix the build (in fact, change one line in an include file somewhere) but was unsure if it would work with other mysql versions than the one I'm using. Is it possible to bring back the port so I can submit that change so that at least some people can use it again? Kind regards, Benny Goemans __ Benny Goemans Software Architect Senior Analyst/Developer Tel: +32 496 624513 Wacadu BVBA, BE0830.680.977 ___ 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: Recent ports removal
Le 11.11.2011 11:07, Dmitry Marakasov a écrit : Why don't we take out Gnome and KDE then? I don't use it. Cause, there is still guys that are ready to maintain them, and, futhermore, some stuff in the ports tree that depend on them ? -- David Marec, mailto:david.ma...@davenulle.org http://user.lamaiziere.net/david/Site http://www.diablotins.org/ ___ 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: mysql-gui-tools
Hi, On Fri, Nov 11, 2011 at 1:04 PM, Benny Goemans benny.goem...@belgacom.net wrote: Hi, I've noticed that the mysql-gui-tools port has been removed. A few months ago I had found a way to fix the build (in fact, change one line in an include file somewhere) but was unsure if it would work with other mysql versions than the one I'm using. Is it possible to bring back the port so I can submit that change so that at least some people can use it again? It doesn't look like the Porter's Handbook has a section on re-animating dead ports. But you could always submit it as a new port (with your fix included): http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-submitting.html I guess that would also make you the new port maintainer. HTH -- Regards, Torfinn Ingolfsen ___ 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: Recent ports removal
On Fri, 11 Nov 2011 14:07:08 +0400 Dmitry Marakasov articulated: * Martin Wilke (m...@freebsd.org) wrote: They have been deprecated for a while and noone said anything about those, that is the purpose of the DEPRECATED status. The not used anymore mean not used in Why should we go through it again and again? If it's not broken, it's useable, you may not remove it, period. the portstree (ie no more depended on). Most of the portstree is leaf ports, now what? If someone really needs it, he can: What we need is to not have to do extra work and to not have extra noise on the maillist because someone does unneeded things. I really don't want to call that vandalism. You can't only put in u have also to put out. Why don't we take out Gnome and KDE then? I don't use it. That reality might come sooner than you think but for an entirely different reason. http://www.technograte.com/2011/05/18/gnome-to-drop-support-for-bsd-solaris-unix/ http://www.omgubuntu.co.uk/2011/05/gnome-to-drop-support-for-bsd-solaris-unix/ -- Jerry ♔ ___ 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: Recent ports removal
On 11 November 2011 13:09, Jerry je...@seibercom.net wrote: On Fri, 11 Nov 2011 14:07:08 +0400 Dmitry Marakasov articulated: * Martin Wilke (m...@freebsd.org) wrote: They have been deprecated for a while and noone said anything about those, that is the purpose of the DEPRECATED status. The not used anymore mean not used in Why should we go through it again and again? If it's not broken, it's useable, you may not remove it, period. the portstree (ie no more depended on). Most of the portstree is leaf ports, now what? If someone really needs it, he can: What we need is to not have to do extra work and to not have extra noise on the maillist because someone does unneeded things. I really don't want to call that vandalism. You can't only put in u have also to put out. Why don't we take out Gnome and KDE then? I don't use it. That reality might come sooner than you think but for an entirely different reason. http://www.technograte.com/2011/05/18/gnome-to-drop-support-for-bsd-solaris-unix/ http://www.omgubuntu.co.uk/2011/05/gnome-to-drop-support-for-bsd-solaris-unix/ Hm. The real problem of course is that although addport is written in Perl, rmport is written in sh; thus making it much more convenient to use on a machine without Perl. Possible solutions: - Reimport Perl to base - Rewrite addport to sh (though that would undo a lot of recent work :/) - Rewrite rmport in perl? This way we could make a better equilibrium -- a committer looking to fiddle a category Makefile would no longer be forced to choose between installing Perl and removing a port, which would remove the incentive to remove rather than add. Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Recent ports removal
On Fri, 11 Nov 2011 14:07:08 +0400 Dmitry Marakasov amd...@amdmi3.ru mentioned: * Martin Wilke (m...@freebsd.org) wrote: They have been deprecated for a while and noone said anything about those, that is the purpose of the DEPRECATED status. The not used anymore mean not used in Why should we go through it again and again? If it's not broken, it's useable, you may not remove it, period. the portstree (ie no more depended on). Most of the portstree is leaf ports, now what? If someone really needs it, he can: What we need is to not have to do extra work and to not have extra noise on the maillist because someone does unneeded things. I really don't want to call that vandalism. You can't only put in u have also to put out. Why don't we take out Gnome and KDE then? I don't use it. Because portmgr@ is using it? There're numerous cases when unmaintained, buggy, vulnerable and plainly dangerous stuff stays in tree because someone in portmgr gang likes it when other applications not used by them being removed without prior discussion notice. Because your opinion doesn't matter. Neither is mine. Like in old good USSR times... -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ 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: Recent ports removal
Why don't we take out Gnome and KDE then? I don't use it. It's this kind of comment that is souring me on the FreeBSD community. Can't we just disagree politely anymore? mcl ___ 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: Recent ports removal
On Fri, Nov 11, 2011 at 12:40:12PM -0800, Stanislav Sedov wrote: Because portmgr@ is using it? There're numerous cases when unmaintained, buggy, vulnerable and plainly dangerous stuff stays in tree because someone in portmgr gang likes it when other applications not used by them being removed without prior discussion notice. There are always periodic emails, both to individual maintainers and ports@, that summarize which ports are deprecated, expiring, and forbidden. That's served as the best springboard for discussion I know how to do in an automated fashion, for several years. In many rounds of those emails I get responses which result in ports being kept from the scrapheap. I'm not aware of vulnerable things that stay in (other than gnats3, which is still part of our infrastructure), and php52, which apparently is so widely used that we must continue to support it despite our best effrots to clean up the tree. Which other ones are there? From your email I'm sure you don't believe me, but we are attempting to be objective about removing stale, broken, and dangerous code. It's an imperfect art and relies on judgement calls. Surely we can come up with a better alternative than just leave ports in forever. I don't think this serves our users well. mcl ___ 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: Recent ports removal
On 11/10/2011 03:06, Dmitry Marakasov wrote: * Baptiste Daroussin (b...@freebsd.org) wrote: They have been deprecated for a while and noone said anything about those, that is the purpose of the DEPRECATED status. The not used anymore mean not used in Why should we go through it again and again? If it's not broken, it's useable, you may not remove it, period. Yes, we realize that you, and a small minority of other interested parties, have this belief in spite of endless repetition of the reasoning, by the people who do the actual work to keep the ports tree functional, as to why your desire to keep every port is not a workable solution. I personally have handled the removal of hundreds of broken and vulnerable ports over the last several months. A very small percentage (2% perhaps?) were ports that people cared enough to fix, and the fact that someone fixed them is a great outcome. OTOH, in several cases after contacting the port's maintainer I was told that yes indeed, they would like the port removed, but were unsure of how to go about it. The removed ports are in the CVS attic where any interested party can retrieve and fix them. However the fact that no one has made a peep about them is a pretty strong indication that they were simply dead weight that we were carrying for no good reason. Doug -- We could put the whole Internet into a book. Too practical. Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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: Recent ports removal
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 (I just picked one message to do a reply-all, not specific to any one single message but all of them). Technically speaking the current approach's problem is that the user might have no chance of seeing it before the port is removed. By its nature, deprecated ports tends not to be updated for long time, port tools like portmaster, portupgrade will not even see it because no PORTREVISION bump happen. For users who install from packages, there is no deprecation message at all, and it's pretty likely that these user when updating to a new version suddenly find the software missing. I think if we want to deprecate ports in a constant manner, we need to do a better job of letting the user (or let's say potential contributor) know it. My own server in China have went offline for a few months before my friend rebuild and install one for me, and I suddenly noticed that some of previous ports maintained by someone else have been marked as DEPRECATED because upstream gone. Think about this: FreeBSD is not just a product, it's also a project and a community. It's never an overkill to do more things to keep developers, contributors and potential contributors happy and continue to contribute. Making them happy is not do whatever they want us to do but to think more about what they would think, and how we can improve. Cheers, - -- Xin LI delp...@delphij.nethttps://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (FreeBSD) iQEcBAEBCAAGBQJOvZ5uAAoJEATO+BI/yjfBkxYIAKwfR3KRGr4l0AY1fV8Os0MR +0GTUlOnTtaIybk81NcmLhyonSr1GsKAbqyAz5D9hsVFWdNOIeP6G/AnYRIak9Gs ffrFCIN6WjiFmYORQVSTOl3noQmAC4E066vl2PceOUL8sHyHI6O85SuraY0noaVQ p3AV58sQqIuUTpV4f3gPG1nFiDrJT1ZxtLANWjveSNNKDrdcalgjPtPbv1DUYPgp 10me7cVkqp5rrCs2fVUP92037x7XljAZjDi8AaEPf/LtV7Rb+IgC9bE1erk8u8w5 RHoWp2er6szTi70v3CUH7YI7WV31wpphBCY75w/kcvJ4FW1OmUOMjXksVfvLZo8= =xhBR -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: Recent ports removal
On 11/11/2011 14:15, Xin LI wrote: (I just picked one message to do a reply-all, not specific to any one single message but all of them). Technically speaking the current approach's problem is that the user might have no chance of seeing it before the port is removed. That's going to be true no matter what approach we use, or what time period we choose. There are plenty of boxes that just sit there happily doing their work without being updated. If that's the case, then the fact that a port is deprecated or removed isn't really a problem for them. Vulnerable ports are a different issue, but we have portaudit for that. By its nature, deprecated ports tends not to be updated for long time, port tools like portmaster, portupgrade will not even see it because no PORTREVISION bump happen. portmaster -L will warn you about ports marked DEPRECATED/FORBIDDEN/IGNORE/BROKEN if you run it against an updated ports tree. One area where we actually can improve here is to also put this information in the INDEX. I have an idea for that, just haven't been able to put the time into making it happen. For users who install from packages, there is no deprecation message at all, and it's pretty likely that these user when updating to a new version suddenly find the software missing. I would think that the lack of a package would be a pretty clear message that there is an issue that needs attention, wouldn't you? :) Perhaps we need to rethink the policy on whether packages should be created for deprecated ports. I think if we want to deprecate ports in a constant manner, we need to do a better job of letting the user (or let's say potential contributor) know it. I think you're right that we can do more, so what is your proposal? Doug -- We could put the whole Internet into a book. Too practical. Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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: mysql-gui-tools
On Fri, Nov 11, 2011 at 8:01 AM, Torfinn Ingolfsen tin...@gmail.com wrote: It doesn't look like the Porter's Handbook has a section on re-animating dead ports. Not yet. But you could always submit it as a new port (with your fix included): This is the important part. You need to fix the reason it was removed (perhaps by becoming the upstream maintainer as well) FWIW I'd prefer a patch against the old version instead of a shar like a new port. I don't know how other committers feel about this. http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-submitting.html If you need help just ask on this list. I guess that would also make you the new port maintainer. Yep -- Eitan Adler ___ 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-adding a port [was: Re: mysql-gui-tools]
On Fri, Nov 11, 2011 at 01:04:41PM +0100, Benny Goemans wrote: Is it possible to bring back the port so I can submit that change so that at least some people can use it again? I've just added a section to our Committer's Guide, since it seems something that many people don't understand how to do: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/ports.html#AEN1347 I'd be glad to get reactions/corrections. mcl ___ 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: Re-adding a port [was: Re: mysql-gui-tools]
On Fri, 11 Nov 2011, Mark Linimon wrote: On Fri, Nov 11, 2011 at 01:04:41PM +0100, Benny Goemans wrote: Is it possible to bring back the port so I can submit that change so that at least some people can use it again? I've just added a section to our Committer's Guide, since it seems something that many people don't understand how to do: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/ports.html#AEN1347 I'd be glad to get reactions/corrections. Re-adding kind of makes my teeth hurt. Suggested patch attached.Index: article.sgml === RCS file: /home/dcvs/doc/en_US.ISO8859-1/articles/committers-guide/article.sgml,v retrieving revision 1.305 diff -u -r1.305 article.sgml --- article.sgml11 Nov 2011 23:51:12 - 1.305 +++ article.sgml12 Nov 2011 04:26:09 - @@ -2608,11 +2608,11 @@ /qandadiv qandadiv - titleRe-adding a Deleted Port/title + titleRecovering a Deleted Port/title qandaentry question - paraHow do I re-add a deleted port?/para + paraHow do I bring back a deleted port?/para /question answer @@ -2624,7 +2624,7 @@ and then navigate to replaceablecategory/replaceable/replaceableportname/replaceable/filenameAttic/filename/ . Pick a date that is before the removal but after the last true - commit./para + commit./para /step step @@ -2633,7 +2633,7 @@ /step step - paraMake whatever changes needed to make the port + paraMake whatever changes are needed to make the port work again. (If it was deleted due to no more distfiles being available, you will need to volunteer to become the upstream maintainer yourself and host the distfiles, or @@ -2641,11 +2641,11 @@ /step step - paraRe-add the port via commandcvs commit/command./para + paraAdd the port via commandcvs commit/command./para /step step - paraRe-add the makevarSUBDIR/makevar listing of the port + paraAdd the makevarSUBDIR/makevar listing of the port in the parent directory filenameMakefile/filename./para /step @@ -2656,7 +2656,7 @@ step paraIf the port had an entry in - filenameports/LEGAL/filename, re-add that./para + filenameports/LEGAL/filename, add that./para /step /procedure /answer ___ 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: Re-adding a port [was: Re: mysql-gui-tools]
On 11/11/2011 20:28, Warren Block wrote: On Fri, 11 Nov 2011, Mark Linimon wrote: On Fri, Nov 11, 2011 at 01:04:41PM +0100, Benny Goemans wrote: Is it possible to bring back the port so I can submit that change so that at least some people can use it again? I've just added a section to our Committer's Guide, since it seems something that many people don't understand how to do: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/ports.html#AEN1347 I'd be glad to get reactions/corrections. Re-adding kind of makes my teeth hurt. Suggested patch attached. Given the context, I think re-adding fits. -- We could put the whole Internet into a book. Too practical. Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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
emulators/virtualbox-ose-kmod fails on HEAD
I'm running r227447 and get the following: cc -O2 -pipe -DRT_OS_FREEBSD -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -w -DVBOX_WITH_HARDENING -DVBOX_WITH_64_BITS_GUESTS -DRT_ARCH_AMD64 -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -Iinclude -I. -Ir0drv -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -fno-omit-frame-pointer -mno-sse -mcmodel=kernel -mno-red-zone -mno-mmx -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -c /usr/local/tmp/frontier/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/debug/bin/src/vboxdrv/freebsd/SUPDrv-freebsd.c /usr/local/tmp/frontier/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/debug/bin/src/vboxdrv/freebsd/SUPDrv-freebsd.c:104: error: 'D_PSEUDO' undeclared here (not in a function) *** Error code 1 Stop in /usr/local/tmp/frontier/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/debug/bin/src/vboxdrv. *** Error code 1 -- We could put the whole Internet into a book. Too practical. Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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
