Re: continued graphics/opencv-core problems
On 09.11.2013 23:38, Chess Griffin wrote: tried overriding that and building anyway. Maybe I'll just go ahead and let it build with gcc for the time being. Thanks to all who replied! Just to follow-up and confirm - rebuilding opencv-core with gcc worked just fine. Thanks! -- Chess Griffin ___ 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
continued graphics/opencv-core problems
For about 2-3 weeks now, I have continued to run into problems with opencv-core not building on my 9.2-RELEASE poudriere box that uses clang. I reported it here: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/183238 This problem prevents me from building multimedia/ffmpeg which in turn causes a bunch of issues with other ports, including audacious-plugins. Has anyone else run into this or have a solution? Thanks in advance. -- Chess Griffin ___ 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: continued graphics/opencv-core problems
On 09.11.2013 17:44, Jason E. Hale wrote: On Saturday, November 09, 2013 15:00:51 Chess Griffin wrote: Has anyone else run into this or have a solution? Thanks in advance. @Thierry - thank you for your reply - yes, my ports tree is up to date. It updates via cron every night and then I also manually update before trying opencv-core again Sorry for my silence on the matter. I have been extremely busy lately. The problem seems to be that you don't have libc++ installed. At the moment, if you wish to build with clang, the port must link to libc++. Otherwise, I suggest building with gcc (still the default compiler on 9.2). I do plan to address this in the next update which should hopefully be soon. I just have a few more bugs to work out. @jhale - thanks also. I figured you were working on it but I just thought I'd check for an interim fix in the meantime. But to your point, you are correct in that I don't have libc++ installed. If that's the one from ports, I see it is marked IGNORE but I have not tried overriding that and building anyway. Maybe I'll just go ahead and let it build with gcc for the time being. Thanks to all who replied! -- Chess Griffin ___ 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: I need help with git
On Mon, Feb 4, 2013, at 11:21 AM, Paul Schmehl wrote: I'm the maintainer for security/barnyard2. The software recently changed so that all distros are pulled from github. The developers made new commits, and now the port is broken, and I cannot figure out how to fix it. I am no git expert so this is just a guess but can you pull from a specific tag? https://github.com/firnsy/barnyard2/commits/v2-1.11 Looks like they tag the master branch at release. -- Chess Griffin ___ 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: portmaster -w -r icu wants to install new ports
On Thu, Dec 27, 2012, at 09:32 PM, Kevin Oberman wrote: As I often do, I recommend using pkg_libchk -o | grep libicu | cut -f1 -d: | sort | uniq' to provide a list of the ports that actually link to the shareable libraries in icu. Those are the only ports you really need to re-install. Walking up the dependency tree will catch many ports that depend on comething that links to a shareable, but don't link to it, itself. Thanks, this did seem to help. After doing this and rerunning portmaster I think I got the list down to the installed ports. In any event, all is updated and working well. Cheers! -- Chess Griffin ___ 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
portmaster -w -r icu wants to install new ports
Hi - I just updated my ports tree with portsnap and, per UPDATING, ran portmaster -w -r icu to rebuild ports that depend on icu. However, portmaster also listed a long list of new ports it was going to build and install -- things like shells/bash and a lot from x11/. Is this intended behavior? I thought portmaster -w -r icu would only build and reinstall all installed ports that depend on icu. Can't say I've come across portmaster doing this before but maybe I'm just forgetful in my old age. :-) Thanks. -- Chess Griffin ___ 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
dropping maintainership
Hello, Unfortunately, job and family demands are resulting in a lack of time to properly maintain the following ports, and thus I will need to drop their maintainership: audio/streamripper graphics/mypaint irc/bip multimedia/gpodder If anyone is interested in picking them up, please feel free to do so. Thanks. -- Chess Griffin pgpTdHkNoPykV.pgp Description: PGP signature
Re: cvs commit: ports/sysutils/searchmonkey Makefile distinfo
q...@freebsd.org wrote: Hi, The build which triggered this email is done under tinderbox-2.4.3, on 7-STABLE on amd64, with tinderd_flags=-nullfs -plistcheck -onceonly and ccache support, with the official up-to-date Ports Tree, with the following vars set: NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. Excerpt from http://T64.TecNik93.com/logs/7-STABLE-FTP/searchmonkey-0.8.1.log : It looks like my new pkg-plist was not included in the commit. It is in my PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=130062 -- Chess Griffin signature.asc Description: OpenPGP digital signature
Re: sysutils/screen package
Boris Kochergin wrote: Hi, List. I noticed that there isn't a package for sysutils/screen for 7.0. Compiling it from ports works fine, and I looked around and wasn't able to find logs relevant to it on http://pointyhat.freebsd.org/errorlogs/, so I was wondering if anyone could shed some light on why it's not available. Thanks. -Boris NO_PACKAGE is set in the Makefile, which also states: Tends to loop using 100% CPU when used from package - perhaps it hard-codes information about the build host -- Chess Griffin GPG Key: 0x0C7558C3 http://www.chessgriffin.com signature.asc Description: OpenPGP digital signature
Re: sysutils/screen package
Chess Griffin wrote: Boris Kochergin wrote: Hi, List. I noticed that there isn't a package for sysutils/screen for 7.0. Compiling it from ports works fine, and I looked around and wasn't able to find logs relevant to it on http://pointyhat.freebsd.org/errorlogs/, so I was wondering if anyone could shed some light on why it's not available. Thanks. -Boris NO_PACKAGE is set in the Makefile, which also states: Tends to loop using 100% CPU when used from package - perhaps it hard-codes information about the build host By the way misc/tmux is a really nice GNU Screen replacement. It's smaller, lighter, and BSD licensed. According to the developer, there is some cool stuff now in CVS (scrolling status line, interactive command prompt). I've been using it for awhile now and really enjoy it. -- Chess Griffin GPG Key: 0x0C7558C3 http://www.chessgriffin.com signature.asc Description: OpenPGP digital signature
Re: sysutils/screen package
On Fri, Jun 20, 2008 at 4:20 PM, Kitche [EMAIL PROTECTED] wrote: the Freebsd cons25 term information actually makes tmux not work correctly you sort of have to use a workaround by using a different term. Since the termcap info is missing cs it seems I have not run into any issues running tmux. My TERM is set to xterm. -- Chess Griffin GPG Public Key: 0x0C7558C3 http://www.chessgriffin.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xfce4: quit does not work
On Mon, Jun 2, 2008 at 6:00 PM, Carlos A. M. dos Santos [EMAIL PROTECTED] wrote: Hello, I have a brand new machine with 7.0-STABLE-200805 AMD64 (GENERIC kernel). Today I installed all the required packages using pkg_add -r, including xfce-4.4.2. Now if I run startxfce I get the desktop environment running but neither the Quit option of the desktop menu nor the quit button of the panel work. I got the same error starting XFce by means of GDM and by means of XDM. Running xfce4-session-logout by hand does not work too. I have another machine with xfce-4.4.1_1 and it do not have this problem, so I suspect that this is the same bug that was already reported here: http://bugzilla.xfce.org/show_bug.cgi?id=1109 Is there any known fix/workaround? Any help will be welcome. I recently had the exact same problem on one of my FreeBSD machines and for the life of me, I could not figure out what was going on. I was also using packages built on another machine. I cleared out everything in ~/.config, ~/.cache, and nothing fixed it. I found that same bug report but it didn't really help. So, I rebuilt all my xfce4 ports on the problem machine and the issue magically disappeared. Go figure. :-) -- Chess Griffin GPG Public Key: 0x0C7558C3 http://www.chessgriffin.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mailer question #2
On Tue, 01 Jan 2008 15:59:30 -0500 Chuck Robey [EMAIL PROTECTED] wrote: Finally, I got enough of my other problems fixed so I could go back to making my mail the best it could be. I took a look at your suggestions, and decided to try claws-mail first, but trying to figure out what to build, from the pkg-descr's, well, it's confusing, to say the least. You see, the mail/claws-mail/pkg-descr tells me all about (what seems to be a) totally different port, a mail/sylpheed[2]. In fact, when I take a look at the pkg-descrs for either the claws-mail or sylpheed ports, they both seem to be describing the sylpheed port, although they aren't copies, they are very much alike. Could you clear this up? Whats the relationship here, does anyone know it? I'm just trying to figure out what to build, so I can try another mailer for myself. This may not be exactly right, but essentially the history is as follows: Sylpheed was the original GTK1 mail client. At some point, there was either a fork or a development version called Sylpheed-Claws. The original Sylpheed became a GTK2 mail client called Sylpheed2. Sylpheed-Claws then changed its name to Claws-mail to avoid confusion, with apparently debatable results. :-) So, today there is Sylpheed2 and Claws-Mail. I use Claws-Mail and Mutt. All the various claws-mail-* ports are extra plugins. It also appears the pkg-descr for Claws-Mail needs to be updated to reference the name change as well as the correct website, www.claws-mail.org. I have prepared a patch for the maintainer and will submit it via GNATS. HTH. -- Chess Griffin GPG Public Key: 0x0C7558C3 http://www.chessgriffin.com signature.asc Description: PGP signature
Re: x11/gtk-theme-switch vs x11/gtk-theme-switch2
* Pav Lucistnik [EMAIL PROTECTED] [2007-12-27 14:45:18]: On Thu, 27 Dec 2007 13:25:34 +0200, Andriy Gapon wrote What is the difference between x11/gtk-theme-switch and x11/gtk-theme-switch2 ? diff doesn't report any :-) I expected that '2' port would have 'Gtk theme switch 2.0 Beta for Gtk+ 2.0' from http://www.muhri.net/nav.php3?node=gts I was very puzzled to see the exact replica of the other port. It's repocopy in flight. It will be different rather soon. See ports/118805 for a sneak preview :) There is also x11/gtkchtheme which is based on gtk-theme-switch and is for changing your gtk2 theme. Chess -- Chess Griffin GPG Public Key: 0x0C7558C3 http://www.chessgriffin.com pgpAApn1PnTVU.pgp Description: PGP signature
Re: mailer question #2
* Chuck Robey [EMAIL PROTECTED] [2007-12-17 23:28:30]: Any mailers handling those 3 requirements? Some that come to mind are: mozilla-thunderbird, claws-mail, evolution, kmail. Hope this helps. -- Chess Griffin GPG Public Key: 0x0C7558C3 http://www.chessgriffin.com pgppmQ7A1AGpL.pgp Description: PGP signature
Re: Check my work: notification-daemon-xfce
Warren Block wrote: Here's a port for the XFce notification daemon, which shows little popups for various events like unmounting media and so on: I was just thinking yesterday this would be nice to have in ports. I will test tonight. Thanks- Chess -- Chess Griffin GPG Key: 0x0C7558C3 http://www.chessgriffin.com signature.asc Description: OpenPGP digital signature
Re: Check my work: notification-daemon-xfce
* Warren Block [EMAIL PROTECTED] [2007-10-26 18:03:41]: On Fri, 26 Oct 2007, Chess Griffin wrote: Warren Block wrote: Here's a port for the XFce notification daemon, which shows little popups for various events like unmounting media and so on: I was just thinking yesterday this would be nice to have in ports. I will test tonight. Mike Bowie helpfully pointed out that fetching was broken, so MASTER_SITES has been fixed in the Makefile. I just tested out this out and it works very well. I received several different notification popups when mounting and unmounting various devices (mostly CD's and my Cowon iAudio MP3 player) and I did not encounter any issues. Thanks for making this port! Chess -- Chess Griffin GPG Public Key: 0x0C7558C3 http://www.chessgriffin.com pgpX70EKvv5Sp.pgp Description: PGP signature
Testing new port
Hello- I am finished with a new port for gPodder, a GTK2 podcast/media aggregator written in Python and was looking for a few beta testers. Should I go ahead and file a PR with the shar or should I post here? The application works fine and passes the various checks I ran through from the Porter's Handbook. The main issue with this application is that if one wants to use the optional iPod synchronization support, then it depends on libgpod, which unfortunately has broken Python bindings, so I don't think it will work. I filed PR #116168 about this. In any event, I don't have an iPod to test it with, though. Thanks, Chess -- Chess Griffin GPG Public Key: 0x0C7558C3 http://www.chessgriffin.com pgp7DJhtRpAIZ.pgp Description: PGP signature
Re: Major changes since 6.2?
* Kris Kennaway [EMAIL PROTECTED] [2007-10-18 00:46:48]: What are some of the major changes to ports/ported applications since 6.2-RELEASE (01/2007)? I am in the process of putting together a talk and would like to mention some of the highlights. The main ones are xorg 7.3, KDE 3.5.7 and GNOME 2.18.3. Have there been any other major changes of interest to end users over the past year? I think the addition of compiz and compiz-fusion to be of interest to many desktop users. Chess -- Chess Griffin GPG Public Key: 0x0C7558C3 http://www.chessgriffin.com pgpDeDjIRMN6x.pgp Description: PGP signature
Re: NOPORTDOCS and man/info pages
* Andrew Pantyukhin [EMAIL PROTECTED] [2007-10-13 12:28:10]: So, my questions are: Is the above handling of the man and info pages correct? It seems the answer is no, but just thought I would check. Not really, but I guess there may be some special cases that warrant the handling (e.g. megabytes of manpages, etc.) How does one choose not to install man and info pages if NOPORTDOCS does not apply to them? I seem to recall that there is a NO_INSTALL_MANPAGES knob but am not sure if that's the answer or if there is a NO_INSTALL_INFOPAGES. Some people tried to respect some knobs, but in general we just always install manpages. As for infopages, we usually only install them when there are no manpages or if the manpages are insufficient. Is is correct procedure to never include man and info pages in the pkg-plist like Porter's Handbook states? Sometimes it's necessary to list manpages in plist. E.g. when there are different sets of manpages for different languages. MANLANG and MAN# can only handle one set across all languages. Thank you very much, Andrew. Cheers- -- Chess Griffin GPG Public Key: 0x0C7558C3 http://www.chessgriffin.com pgpGH7g6UK54t.pgp Description: PGP signature
my previous email
I just realized I sent my previous email to ports@ instead of to the ports mailing list. Argh. Sorry about that. I will resend to the list. My apologies. -- Chess Griffin GPG Public Key: 0x0C7558C3 http://www.chessgriffin.com pgp0ZnRS2QToc.pgp Description: PGP signature
NOPORTDOCS and man/info pages
Hello- I am working on some small cleanup patches to a couple port Makefiles and had a few questions on how to handle man/info pages. I have come across a couple Makefiles that have something like this in post-install: .if defined(NOPORTDOCS) ... .else MAN1= portname.1 INFO= portname .endif It's my understanding after reading 5.9, 5.10, and 5.14.4 of the Porter's Handbook that the man and info page variables should be listed in the first part of the Makefile, before the .include bsd.port.pre.mk or .include bsd.port.mk for example. It also states in 5.14.4 that Note: NOPORTDOCS only controls additional documentation installed in DOCSDIR. It does not apply to standard man page and info pages. This statement seems to indicate that the above snippet would still install the man/info pages even if NOPORTDOCS was set. I have also seen where the manpage and info page are then also listed in pkg-plist, which I gather should not be the case according to 5.9 of the Porter's Handbook. So, my questions are: Is the above handling of the man and info pages correct? It seems the answer is no, but just thought I would check. How does one choose not to install man and info pages if NOPORTDOCS does not apply to them? I seem to recall that there is a NO_INSTALL_MANPAGES knob but am not sure if that's the answer or if there is a NO_INSTALL_INFOPAGES. Is is correct procedure to never include man and info pages in the pkg-plist like Porter's Handbook states? Am I way out in left field here? :-) Many thanks- Chess -- Chess Griffin GPG Public Key: 0x0C7558C3 http://www.chessgriffin.com pgpINv6uHDtq1.pgp Description: PGP signature
Re: my previous email
* Doug Barton [EMAIL PROTECTED] [2007-10-12 12:21:35]: On Fri, 12 Oct 2007, Chess Griffin wrote: I just realized I sent my previous email to ports@ instead of to the ports mailing list. Argh. Sorry about that. I will resend to the list. In general, [EMAIL PROTECTED] is just an alias for [EMAIL PROTECTED] The two can be used interchangeably. Doug Thanks, Doug. Yeah, I realized that with horror after I saw all my noise scattered all over the list. :-) Oh well, it's been a long week. My apologies to the list for the multiple emails. Chess -- Chess Griffin GPG Public Key: 0x0C7558C3 http://www.chessgriffin.com pgpF5oDiEpqYC.pgp Description: PGP signature
NOPORTDOCS and man/info pages
Hello- I am working on some small cleanup patches to a couple port Makefiles and had a few questions on how to handle man/info pages. I have come across a couple Makefiles that have something like this in post-install: .if defined(NOPORTDOCS) ... .else MAN1= portname.1 INFO= portname .endif It's my understanding after reading 5.9, 5.10, and 5.14.4 of the Porter's Handbook that the man and info page variables should be listed in the first part of the Makefile, before the .include bsd.port.pre.mk or .include bsd.port.mk for example. It also states in 5.14.4 that Note: NOPORTDOCS only controls additional documentation installed in DOCSDIR. It does not apply to standard man page and info pages. This statement seems to indicate that the above snippet would still install the man/info pages even if NOPORTDOCS was set. I have also seen where the manpage and info page are then also listed in pkg-plist, which I gather should not be the case according to 5.9 of the Porter's Handbook. So, my questions are: Is the above handling of the man and info pages correct? It seems the answer is no, but just thought I would check. How does one choose not to install man and info pages if NOPORTDOCS does not apply to them? I seem to recall that there is a NO_INSTALL_MANPAGES knob but am not sure if that's the answer or if there is a NO_INSTALL_INFOPAGES. Is is correct procedure to never include man and info pages in the pkg-plist like Porter's Handbook states? Many thanks- Chess -- Chess Griffin GPG Public Key: 0x0C7558C3 http://www.chessgriffin.com pgpaL8Gq5RH0w.pgp Description: PGP signature
Creating a new port -- issue with man page install
Hello-
I am working a new port (for gPodder, a GTK2 python-based media
aggregator) and so far everything seems to be working pretty well
(after reading through the Porter's Handbook -- what a great piece of
documentation). Anyway, I cannot seem to figure out one thing.
The tarball has a man page located in /gpodder-0.9.5/doc/man/gpodder.1.
In my Makefile, I have this:
MANCOMPRESSED= no
MAN1= ${PORTNAME}.1
PORTNAME is gpodder, BTW. Anyway, when I create a package, it
complains that it cannot find or install the man page and I am not
sure how to fix this. Some of the snipped output is this:
=== Compressing manual pages for gpodder-0.9.5
gzip: can't stat: /usr/local/man/man1/gpodder.1: No such file or directory
=== Registering installation for gpodder-0.9.5
=== Building package for gpodder-0.9.5
Creating package /usr/ports/packages/All/gpodder-0.9.5.tbz
snip
Creating bzip'd tar ball in '/usr/ports/packages/All/gpodder-0.9.5.tbz'
tar: man/man1/gpodder.1.gz: Cannot stat: No such file or directory
tar: Error exit delayed from previous errors.
pkg_create: make_dist: tar command failed with code 256
*** Error code 1
Stop in /usr/ports/multimedia/gpodder.
Any assistance is greatly appreciated.
Thanks in advance.
Chess
--
Chess Griffin
GPG Public Key: 0x0C7558C3
http://www.chessgriffin.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Creating a new port -- issue with man page install
On 9/6/07, Brooks Davis [EMAIL PROTECTED] wrote:
The error messages seem to indicate that the problem the manpage isn't
being installed. All the MAN# variables do is tell the ports system you
will be installing them. You should do something like:
post-install:
${INSTALL_MAN} ${WRKSRC}/doc/man/gpodder.1 ${MANPREFIX}/man/man1
Thank you very much, Brooks. Your suggestion worked perfectly.
Regards,
Chess
--
Chess Griffin
GPG Public Key: 0x0C7558C3
http://www.chessgriffin.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: xorg 7.2 ready for testing - successful clean install
I did a new minimal FreeBSD 6.2 install on a Thinkpad x40 and then installed Xorg 7.2, basically following the upgrade instructions -- I built libXft first, then xorg using make install clean in both cases. Ran the mergebase.sh script without issue (didn't expect any since this had been a new clean install without Xorg 6.9). Installed fluxbox and everything appears to work fine. Thanks to all the developers for a great job! Chess -- Chess Griffin GPG Public Key: 0x0C7558C3 http://www.chessgriffin.com signature.asc Description: OpenPGP digital signature
