Re: [patch] new port games/chocolate-doom, need a bit of help
On Wed, Jan 16, 2013 at 09:55:10PM -0800, Jason Helfman thus spake: On Wed, Jan 16, 2013 at 03:33:00PM -0800, Jakub Lach thus spake: Hello, I took up where http://www.freebsd.org/cgi/query-pr.cgi?pr=161701 left, as I'm user of chocolate-doom for quite time, and was eyeing it for a while. Current WIP is (docs, optionng, timidity++ etc): https://www.dropbox.com/s/jq9j16sxvrsej9w/c-doom.txt (shar archive) Problem is, as you can see that chocolate-doom is bend on installing under games (see pkg-plist) if USE_AUTOTOOLS= is hashed. As I understand, I need auto* to actually process patched *in, to prevent installing bins under games/. But aclocal, autoconf etc all fail in various places. Anybody has an idea or should I just bug upstream to update files for fresher auto*? I already hate auto* with passion... I believe I have "fixed" the autotools portion of this, by not using it and by altering the respective Makefile.in files in a post-patch-script target. I added HACKING to post-install for documentation, as the rest of them listed are already done as part of the installation. I made some minor updates to your Makefile for the port, as well. http://people.freebsd.org/~jgh/files/chocolate-doom.shar It seems to work fine, and everything goes to the right place. Let me know what you think. -jgh I did have an opportunity to run this through a build cycle, and found that timidity++ has an issue, as timidity is already brought in by another dependency in the build cycle and the port won't build as this is a conflict. Here is a link to the log: http://meatwad.mouf.net/rubick/tb/errors/9.0-RELEASE-amd64-FreeBSD/chocolate-doom-1.7.0.log -jgh -- Jason Helfman FreeBSD Committer | http://people.freebsd.org/~jgh | The Power To Serve ___ 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: [patch] new port games/chocolate-doom, need a bit of help
On Wed, Jan 16, 2013 at 03:33:00PM -0800, Jakub Lach thus spake: Hello, I took up where http://www.freebsd.org/cgi/query-pr.cgi?pr=161701 left, as I'm user of chocolate-doom for quite time, and was eyeing it for a while. Current WIP is (docs, optionng, timidity++ etc): https://www.dropbox.com/s/jq9j16sxvrsej9w/c-doom.txt (shar archive) Problem is, as you can see that chocolate-doom is bend on installing under games (see pkg-plist) if USE_AUTOTOOLS= is hashed. As I understand, I need auto* to actually process patched *in, to prevent installing bins under games/. But aclocal, autoconf etc all fail in various places. Anybody has an idea or should I just bug upstream to update files for fresher auto*? I already hate auto* with passion... I believe I have "fixed" the autotools portion of this, by not using it and by altering the respective Makefile.in files in a post-patch-script target. I added HACKING to post-install for documentation, as the rest of them listed are already done as part of the installation. I made some minor updates to your Makefile for the port, as well. http://people.freebsd.org/~jgh/files/chocolate-doom.shar It seems to work fine, and everything goes to the right place. Let me know what you think. -jgh -- Jason Helfman FreeBSD Committer | http://people.freebsd.org/~jgh | The Power To Serve ___ 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: avr-binutils conflicts with binutils
On Tue, Jan 15, 2013 at 2:05 AM, Pierre DAVID wrote: > avr-binutils conflicts with binutils: > > > -- > ===> Registering installation for avr-binutils-2.20.1_1 as automatic > Installing avr-binutils-2.20.1_1...pkg: avr-binutils-2.20.1_1 conflicts > with binutils-2.23.1 (installs files into the same place). Problematic > file: /usr/local/share/locale/da/LC_MESSAGES/bfd.mo > *** [fake-pkg] Error code 70 > > Stop in /usr/ports/devel/avr-binutils. > > ===>>> Installation of avr-binutils-2.20.1_1 (devel/avr-binutils) failed > ===>>> Aborting update > > -- > > Pierre > Maybe adding the CONFLICT to if NLS is selected, would be best? Any thoughts on this? -jgh -- Jason Helfman | FreeBSD Committer j...@freebsd.org | http://people.freebsd.org/~jgh | The Power to Serve ___ 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"
[patch] new port games/chocolate-doom, need a bit of help
Hello, I took up where http://www.freebsd.org/cgi/query-pr.cgi?pr=161701 left, as I'm user of chocolate-doom for quite time, and was eyeing it for a while. Current WIP is (docs, optionng, timidity++ etc): https://www.dropbox.com/s/jq9j16sxvrsej9w/c-doom.txt (shar archive) Problem is, as you can see that chocolate-doom is bend on installing under games (see pkg-plist) if USE_AUTOTOOLS= is hashed. As I understand, I need auto* to actually process patched *in, to prevent installing bins under games/. But aclocal, autoconf etc all fail in various places. Anybody has an idea or should I just bug upstream to update files for fresher auto*? I already hate auto* with passion... -- View this message in context: http://freebsd.1045724.n5.nabble.com/patch-new-port-games-chocolate-doom-need-a-bit-of-help-tp5778363.html Sent from the freebsd-ports mailing list archive at Nabble.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: Plans for making MAKE_JOBS_SAFE the default?
On 16 January 2013 20:48, Eitan Adler wrote: > On 11 September 2012 12:13, Olivier Smedts wrote: >> 2012/9/4 Bryan Drewery : My proposal: - start an exp-run with FORCE_MAKE_JOBS set - mark all new failures with MAKE_JOBS_UNSAFE - flip the default right after the 9.1 release. > ... > > It has been months since I sent this mail without any official reply > whatsoever. At this point the exp-run machines are down and not > likely to return in the *near* future. > > Can I propose that this flag be flipped without an exp-run and fix the > fallout? It has been widely tested and has had exp-runs in the past. I think this would be extremely hard to justify, given that the ports tree is a live entity. We would effectively be asking our end users to debug MAKE_JOBS. This is not acceptable; we can't plan to have fallout. 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: Plans for making MAKE_JOBS_SAFE the default?
On 11 September 2012 12:13, Olivier Smedts wrote: > 2012/9/4 Bryan Drewery : >>> My proposal: >>> - start an exp-run with FORCE_MAKE_JOBS set >>> - mark all new failures with MAKE_JOBS_UNSAFE >>> - flip the default right after the 9.1 release. ... It has been months since I sent this mail without any official reply whatsoever. At this point the exp-run machines are down and not likely to return in the *near* future. Can I propose that this flag be flipped without an exp-run and fix the fallout? It has been widely tested and has had exp-runs in the past. -- 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"
converters/recode ISSUE error: width of 'ignore' exceeds its type
With GCC 4.6.3: ... libtool: compile: gcc46 -DLIBDIR=\"/usr/local/lib\" -DHAVE_CONFIG_H -I.. -I. -I../lib -I../libiconv -O2 -pipe -march=pentium4 -mtune=pentium4 -Wno-error -w -I/usr/local/include -O2 -pipe -march=pentium4 -mtune=pentium4 -fPIC -Wl,-rpath=/usr/local/lib/gcc46 -fno-strict-aliasing -c charname.c -fPIC -DPIC -o .libs/charname.o In file included from common.h:140:0, from charname.c:20: recodext.h:221:5: error: width of 'ignore' exceeds its type *** Error code 1 Stop in /usr/ports/converters/recode/work/recode-3.6/src. *** Error code 1 With GCC 4.2 - fine. ___ 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: graphics/opencv ISSUE with gcc 4.6.3
On, Wed Jan 16, 2013, awarecons wrote: [...] Can you please use send-pr(1) or the web interface[1] instead of those mails or at least provide enough information about your system environment to allow one to actually investigate on the issues, you mention? send-pr or [1] also have the advantage that your reports do not get lost. [1] http://www.freebsd.org/send-pr.html Thanks Marcus pgpfQJcsLQIRL.pgp Description: PGP signature
Re: FreeBSD Port: codeblocks-10.05_1
Le Wed, 16 Jan 2013 14:48:07 +0100, Ewout Boks a écrit : > Hi Port mantainer, > > Codeblocks has been updated to a new major release 12.x . The port > still builds the 3 year old 10.x version. When will the port be > updated? > > Best regards, > > Ewout Boks > > ___ > 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" I'm trying to port the new version but for now, my "fetch" is ugly (get a file from berlios via sourceforge ...) ; you can see it into the Makefile... Regards. Makefile Description: Binary data ___ 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"
graphics/opencv ISSUE with gcc 4.6.3
===> Building for opencv-2.3.1_5 [ 1%] Generating opencv_calib3d_pch_dephelp.cxx Scanning dependencies of target opencv_calib3d_pch_dephelp [ 1%] Building CXX object modules/calib3d/CMakeFiles/opencv_calib3d_pch_dephelp.dir/opencv_calib3d_pch_dephelp.o Linking CXX static library ../../lib/libopencv_calib3d_pch_dephelp.a [ 1%] Built target opencv_calib3d_pch_dephelp Scanning dependencies of target pch_Generate_opencv_calib3d [ 1%] Generating precomp.hpp [ 2%] Generating precomp.hpp.gch/opencv_calib3d_Release.gch /usr/lib/crt1.o: In function `_start1': crt1_c.c:(.text+0x9d): undefined reference to `main' collect2: ld returned 1 exit status *** Error code 1 Stop in /usr/ports/graphics/opencv/work/OpenCV-2.3.1. *** Error code 1 But gcc 4.2+ works fine. Wonder, if there's need of libmap or so? ___ 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"
audio/gstreamer-plugins-soundtouch ISSUE when integer_sample_format chosen in config of audio/soundtouch
audio/gstreamer-plugins-soundtouch ISSUE when integer_sample_format
chosen in config of audio/soundtouch
INTEGER_SAMPLES Use integer sample format
...
===> Building for gstreamer-plugins-soundtouch-0.10.23,3
CC libgstsoundtouch_la-plugin.lo
CXXlibgstsoundtouch_la-gstpitch.lo
gstpitch.cc: In function 'GstBuffer* gst_pitch_prepare_buffer(GstPitch*)':
gstpitch.cc:384:77: error: no matching function for call to
'soundtouch::SoundTouch::receiveSamples(gfloat*, guint&)'
gstpitch.cc:384:77: note: candidates are:
/usr/local/include/soundtouch/FIFOSamplePipe.h:190:18: note: virtual
uint soundtouch::FIFOProcessor::receiveSamples(soundtouch::SAMPLETYPE*,
uint)
/usr/local/include/soundtouch/FIFOSamplePipe.h:190:18: note: no
known conversion for argument 1 from 'gfloat* {aka float*}' to
'soundtouch::SAMPLETYPE* {aka short int*}'
/usr/local/include/soundtouch/FIFOSamplePipe.h:203:18: note: virtual
uint soundtouch::FIFOProcessor::receiveSamples(uint)
/usr/local/include/soundtouch/FIFOSamplePipe.h:203:18: note:
candidate expects 1 argument, 2 provided
gstpitch.cc: In function 'GstFlowReturn gst_pitch_chain(GstPad*, GstBuffer*)':
gstpitch.cc:902:52: error: no matching function for call to
'soundtouch::SoundTouch::putSamples(gfloat*, guint)'
gstpitch.cc:902:52: note: candidate is:
/usr/local/include/soundtouch/SoundTouch.h:236:18: note: virtual void
soundtouch::SoundTouch::putSamples(const SAMPLETYPE*, uint)
/usr/local/include/soundtouch/SoundTouch.h:236:18: note: no known
conversion for argument 1 from 'gfloat* {aka float*}' to 'const
SAMPLETYPE* {aka const short int*}'
gmake: *** [libgstsoundtouch_la-gstpitch.lo] Error 1
*** Error code 2
Stop in /usr/ports/audio/gstreamer-plugins-soundtouch.
___
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"
audio/ladspa ISSUE sed error
===> Applying FreeBSD patches for ladspa-1.13 /usr/bin/sed -i.bak -e 's,-ldl,,; s,-O3,-O2 -pipe -march=pentium4 -mtune=pentium4 -Wl,-rpath=/usr/local/lib/gcc46 -fno-strict-aliasing,; s,^CC,#CC,;s,^CPP,#CPP,;s,CPP,CXX,; s,^CXXFLAGS.*=,CXXFLAGS+=,' /usr/ports/audio/ladspa/work/ladspa_sdk/src/makefile sed: 1: "s,-ldl,,; s,-O3,-O2 -pi ...": bad flag in substitute command: '-' *** Error code 1 Stop in /usr/ports/audio/ladspa. ___ 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: Removal of Portmanager
>On Wed, Jan 16, 2013 at 08:48:37AM +, b.f. wrote: >> Mark wrote: >> >On Wed, Jan 16, 2013 at 01:51:39AM +, RW wrote: >> >> > Reports are sent to ports@ every 2 weeks. >> >> And I wonder how many people read carefully through all 478 entries. >> >And your suggestion is ... ? >> Try ports/ports-mgmt/portupdate-scan. > >portupdate-scan displays pertinent entries from /usr/ports/UPDATING. >How does that help you digest long lists posted on a mailing list? > Obviously, it can't: I misunderstood the original complaint. If portupdate-scan is parsing MOVED and UPDATING, it can help notify users of port removals before they update their packages, but not before the ports are removed. If users have an up-to-date ports tree in PORTSDIR, they can use something simple like: pkg_info -qoa | xargs -I @ grep -le EXPIRATION_DATE $PORTSDIR/@/Makefile to find which of their installed packages are likely to be removed, with obvious variations to list all DEPRECATED ports, etc. If they don't have a ports tree, they can use: http://portsmon.freebsd.org/portsconcordanceforexpiring.py b. ___ 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"
FreeBSD Port: codeblocks-10.05_1
Hi Port mantainer, Codeblocks has been updated to a new major release 12.x . The port still builds the 3 year old 10.x version. When will the port be updated? Best regards, Ewout Boks ___ 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"
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ graphics/wxsvg | 1.1.8 | 1.1.10 +-+ net/gatekeeper | 2.2.8 | 3.2-netbsd5.1-x86 +-+ net/liveMedia | 2012.12.18 | 2013.01.15 +-+ www/xist| 3.25| 4.8 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt If wish to stop receiving portscout reminders, please contact portsc...@portscout.freebsd.org Thanks. ___ 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: Removal of Portmanager
On Wed, Jan 16, 2013 at 08:48:37AM +, b.f. wrote: > Mark wrote: > >On Wed, Jan 16, 2013 at 01:51:39AM +, RW wrote: > >> > Reports are sent to ports@ every 2 weeks. > >> And I wonder how many people read carefully through all 478 entries. > >And your suggestion is ... ? > Try ports/ports-mgmt/portupdate-scan. portupdate-scan displays pertinent entries from /usr/ports/UPDATING. How does that help you digest long lists posted on a mailing list? Alex ___ 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: Removal of Portmanager
On Wed, Jan 16, 2013 at 10:38:50AM +0100, Stefan Esser wrote: > Am 16.01.2013 09:48, schrieb b.f.: > > Mark wrote: > > Try ports/ports-mgmt/portupdate-scan. > I just wanted to give it a try, but it does not seem to support PKGNG. > (I'll have a look to check whether that's easy to fix ...) I was under the impression that pkgng has similar functionality built-in (pkg updating), and so portupdate-scan would become obsolete once pkgng becomes standard. Do you think there's still a need for portupdate-scan even with pkgng? I'd be happy to look at fixing this, if I thought there was a point to it. Alex ___ 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"
UPDATING: "net/remmina"
Presently "net/remmina" is at version "0.9.3" in the ports system. According to the projects web site, Remmina 1.0 was released February 11, 2012. Is there any possibility of having the ports version updated to this release? The present version is nearly a year old. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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: Removal of Portmanager
Am 16.01.2013 09:48, schrieb b.f.: > Mark wrote: >> On Wed, Jan 16, 2013 at 01:51:39AM +, RW wrote: Reports are sent to ports@ every 2 weeks. >>> >>> And I wonder how many people read carefully through all 478 entries. >> >> And your suggestion is ... ? >> > > Try ports/ports-mgmt/portupdate-scan. I just wanted to give it a try, but it does not seem to support PKGNG. (I'll have a look to check whether that's easy to fix ...) Regards, STefan ___ 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: Removal of Portmanager
Mark wrote: >On Wed, Jan 16, 2013 at 01:51:39AM +, RW wrote: >> > Reports are sent to ports@ every 2 weeks. >> >> And I wonder how many people read carefully through all 478 entries. > >And your suggestion is ... ? > Try ports/ports-mgmt/portupdate-scan. b. ___ 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"
