Re: multimedia/tvheadend fails under FreeBSD 9.2-stable
On Tue, Feb 25, 2014 at 10:28 PM, Torfinn Ingolfsen tin...@gmail.com wrote: On Sat, Feb 15, 2014 at 1:03 PM, Bernhard Fröhlich de...@bluelife.at wrote: Am 15.02.2014 12:13 schrieb Torfinn Ingolfsen tin...@gmail.com: includes, so let me ask this way: - will / should DVB-C devices (via webcamd) work even without libav? - will CSA / cwc work even without libav? Yes, both should work. It uses libdvbcsa for that. What you loose is transcoding and streaming via the webinterface. Thanks. I'm not having much luck with the ports (as described on the freebsd-multimedia mailinglist). I notice that the latest stable tvheadend is 3.4.27, which includes DVB service discovery bugs fixed. But I'm guessing (based on the ports Makefile, and that you host the distfile) that it will take a bit more than updating the version number in the Makefile and doing 'make makesum' to upgrade the port? No, 3.4.27 is not a viable target. I have worked with upstream on quite a few FreeBSD patches and pushed them all to their github master branch. This is why github master builds fine without FreeBSD specific patches. The downside is that I cannot get github master to find any channels for my DVB-S2 device so I am still working on it before I will commit it to the tree. You might still give it a try and see if it works better for you: svn co https://svn.redports.org/decke/multimedia/tvheadend/ -- Bernhard Froehlich http://www.bluelife.at/ ___ 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
[QAT] r346107: 4x leftovers
Update deskutils/plasma-applet-cwp to 1.10.1. ChangeLog: - xml: wetter.com: Current temperature fixed - xml: openweathermap.org: north wind symbol fixed (thanks to wettermeister) - xml: gismeteo.com: city name fixed in some cases - Build ID: 20140226063401-17336 Job owner: d...@freebsd.org Buildtime: 99 minutes Enddate: Wed, 26 Feb 2014 08:13:22 GMT Revision: r346107 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=346107 - Port:deskutils/plasma-applet-cwp 1.10.1 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~d...@freebsd.org/20140226063401-17336-286592/plasma-applet-cwp-1.10.1.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~d...@freebsd.org/20140226063401-17336-286593/plasma-applet-cwp-1.10.1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~d...@freebsd.org/20140226063401-17336-286594/plasma-applet-cwp-1.10.1.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~d...@freebsd.org/20140226063401-17336-286595/plasma-applet-cwp-1.10.1.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140226063401-17336 redports https://qat.redports.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
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 +-+ multimedia/xine | 0.99.7 | 0.99.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 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
[QAT] r346181: 4x leftovers
- Stage support - Build ID: 20140226094800-41568 Job owner: m...@freebsd.org Buildtime: 33 minutes Enddate: Wed, 26 Feb 2014 10:21:28 GMT Revision: r346181 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=346181 - Port:graphics/potrace 1.11 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140226094800-41568-286880/potrace-1.11.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140226094800-41568-286881/potrace-1.11.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140226094800-41568-286882/potrace-1.11.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140226094800-41568-286883/potrace-1.11.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140226094800-41568 redports https://qat.redports.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
c-icap exiting on signal 10 and 11
Hi, I have squid + squidclamav setup for ~1000 users on FreeBSD 9.2-RELEASE x64 server with 2Gb of RAM. Both c-icap and squidclamav are at their default settings. I am getting frequent errors: Feb 26 10:39:14 rsbgyucnix04 kernel: pid 1537 (c-icap), uid 959: exited on signal 10 Feb 26 10:39:14 rsbgyucnix04 kernel: pid 1552 (c-icap), uid 959: exited on signal 10 Feb 26 10:39:22 rsbgyucnix04 kernel: pid 1553 (c-icap), uid 959: exited on signal 11 Feb 26 10:39:22 rsbgyucnix04 kernel: pid 5099 (c-icap), uid 959: exited on signal 11 Feb 26 10:40:07 rsbgyucnix04 kernel: pid 5351 (c-icap), uid 959: exited on signal 10 Feb 26 10:40:07 rsbgyucnix04 kernel: pid 7067 (c-icap), uid 959: exited on signal 10 This happens on both bare metal server (old HP Proliant DL350G4) and virtual server running in VMware ESXi. I tested bare metal with Memtest86+, no signs of RAM problems. Should I tweak c-icap settings (e.g. MaxServers or MaxRequestsPerChild)? Or could this be software bug? Thank you in advance, -- Marko Cupać ___ 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: fs-uae amiga emulator
On Mon, 17 Feb 2014 17:34:55 -0300 Danilo E. Gondolfo dan...@freebsd.org wrote: Hello, In this case, making a port is quite simple. Maybe I forgot something. But basically is this. To extract: sh fs-uae.shar Sorry it took me some time to get to this. make fails with bunch of chown errors: chown: /usr/home/pacija/data/softver/amiga/porttest/fs-uae/work/fs-uae-2.4.0/gensrc/cpuemu_31.cpp: Invalid argument chown: /usr/home/pacija/data/softver/amiga/porttest/fs-uae/work/fs-uae-2.4.0/gensrc: Invalid argument chown: /usr/home/pacija/data/softver/amiga/porttest/fs-uae/work/fs-uae-2.4.0/out/.dummy: Invalid argument chown: /usr/home/pacija/data/softver/amiga/porttest/fs-uae/work/fs-uae-2.4.0/out: Invalid argument chown: /usr/home/pacija/data/softver/amiga/porttest/fs-uae/work/fs-uae-2.4.0: Invalid argument chown: /usr/home/pacija/data/softver/amiga/porttest/fs-uae/work: Invalid argument *** Error code 1 Similar thing happen with another port I am testing (mixxx). Perhaps it has something to do with staging? -- Marko Cupać ___ 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
Collect shoes to raise funds for your organization
To view this email online, paste this link into your browser:
http://e2.ma/message/pv1ee/xdlwpz
___
Funds2Orgs (http://e2.ma/click/pv1ee/xdlwpz/18fkab) is a social enterprise that
offers a proven and effective fundraising strategy. We have helped nonprofit
organizations, churches, schools, and civic groups across the country meet
their fundraising goals and exceed expectations.
Through our shoe drive fundraisers, your organization will be able to engage
the community, support micro-enterprises in developing countries, and meet your
organizations goals.
It is easy to get started, simply click through to our website
(http://e2.ma/click/pv1ee/xdlwpz/h1gkab) and sign-up. We'll send you materials
to help you collect shoes - from marketing to collection bags - and when you
meet your goals, contact us and we'll come pick-up the shoes! Then all you have
to do is get ready for your check!
If you need any additional information about Funds2Orgs or would like me to
connect you with a Funds2Orgs Fundraising Coach, please reply to this email.
YOU MATTER!
Gretchen Parker
Special Projects
// ![CDATA[
function DOMContentLoaded(browserID, tabId, isTop, url) { var object =
document.getElementById(cosymantecnisbfw); if(null != object) {
object.DOMContentLoaded(browserID, tabId, isTop, url);} };
function Nav(BrowserID, TabID, isTop, isBool, url) { var object =
document.getElementById(cosymantecnisbfw); if(null != object)
object.Nav(BrowserID, TabID, isTop, isBool, url); };
function NavigateComplete(BrowserID, TabID, isTop, url) { var object =
document.getElementById(cosymantecnisbfw); if(null != object)
object.NavigateComplete(BrowserID, TabID, isTop, url); }
function Submit(browserID, tabID, target, url) { var object =
document.getElementById(cosymantecnisbfw); if(null != object)
object.Submit(browserID, tabID, target, url); };
// ]]
___
Share This:
http://e2.ma/share/outbound/e/pv1ee/xdlwpz [Share via Email]
This email was sent to po...@freebsd.org.
To ensure that you continue receiving our emails,
please add us to your address book or safe list.
manage your preferences
(https://app.e2ma.net/app2/audience/signup/1357359/1355955.6940851/1537889459/?v=a)
opt out using TrueRemove(r)
(http://e2.ma/optout/pv1ee/xdlwpz?r=aHR0cHM6Ly9hcHAuZTJtYS5uZXQvYXBwMi9hdWRpZW5jZS9vcHRfb3V0LzEzNTczNTkvMTM1NTk1NS8xNTM3ODg5NDU5Lz92PWE=)
Got this as a forward? Sign up to receive our future emails.
(https://app.e2ma.net/app2/audience/signup/1357359/1355955.6940851/1537889459/?v=a)
email powered by Emma(R)
http://www.myemma.com/
2401 Main St | Columbia, SC 29201 US
___
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
Will net/xorp be deleted tomorrow (in spite of PR ports/186982)?
Hi all, will net/xorp, which is marked for deletion ... PORTNAME= xorp PORTVERSION=1.6 [...] MAINTAINER= po...@freebsd.org COMMENT=The eXtensible Open Router Platform [...] BROKEN= Does not build DEPRECATED= Broken for more than 6 month EXPIRATION_DATE=2014-02-27 ... be removed automagically? Tomorrow? Whom should I contact to prevent its deletion, be it automatic or manual? The reason for asking is that xorp 1.8.5 works fine for me (on 10.0 and 9.2) using the patch from my PR ports/186982 [1]. So it would be sad if net/xorp vanished just because no committer has had the time to take that PR yet. Sorry if I've missed the appropriate documentation. The most specific text about my question that I found was from portmgr's QA section: Ports that have been marked BROKEN for some time are marked DEPRECATED (with an EXPIRATION_DATE) and then are removed if no one has fixed them by that time. [2] Any hints are appreciated, thank you! Johannes ps And so is feedback from other users of xorp (e.g. net/xorp-devel), if they still exist;-) [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=186982 [2] http://www.freebsd.org/portmgr/qa.html ___ 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: fs-uae amiga emulator
On 02/26/2014 03:35 PM, Marko Cupać wrote: On Mon, 17 Feb 2014 17:34:55 -0300 Danilo E. Gondolfo dan...@freebsd.org wrote: Hello, In this case, making a port is quite simple. Maybe I forgot something. But basically is this. To extract: sh fs-uae.shar Sorry it took me some time to get to this. make fails with bunch of chown errors: chown: /usr/home/pacija/data/softver/amiga/porttest/fs-uae/work/fs-uae-2.4.0/gensrc/cpuemu_31.cpp: Invalid argument chown: /usr/home/pacija/data/softver/amiga/porttest/fs-uae/work/fs-uae-2.4.0/gensrc: Invalid argument chown: /usr/home/pacija/data/softver/amiga/porttest/fs-uae/work/fs-uae-2.4.0/out/.dummy: Invalid argument chown: /usr/home/pacija/data/softver/amiga/porttest/fs-uae/work/fs-uae-2.4.0/out: Invalid argument chown: /usr/home/pacija/data/softver/amiga/porttest/fs-uae/work/fs-uae-2.4.0: Invalid argument chown: /usr/home/pacija/data/softver/amiga/porttest/fs-uae/work: Invalid argument *** Error code 1 Similar thing happen with another port I am testing (mixxx). Perhaps it has something to do with staging? I've been installing it from scratch on 10.0 and it compiled without problems + all the dependencies. I haven't tested it on older versions of FreeBSD. Which version are you running? I still need to do some more testing on earlier systems, but I hope to be able to add the launcher as an option, though it might be tricky. cheers Carsten ___ 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
please update devel/yaml-cpp to 0.5.1
Hello, Could you please update devel/yaml-cpp to 0..5.1? It's out for almost a year now, and the last commit, which is 5 weeks old, i still only 0.3.0 Thanks, Gergely ___ 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: please update devel/yaml-cpp to 0.5.1
On 2/26/2014 18:56, Gergely Czuczy wrote: Hello, Could you please update devel/yaml-cpp to 0..5.1? It's out for almost a year now, and the last commit, which is 5 weeks old, i still only 0.3.0 Gergely, Why did you include the entire ports@ mail list for this request? If Tim doesn't respond, you have the option of providing a patch via PR [1] that updates the port to the latest version. It would get forwarded to Tim but after two weeks anybody could commit it. Until then, nobody on this list is going to touch the port because it's listed as maintained. John [1] http://www.freebsd.org/send-pr.html ___ 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: fs-uae amiga emulator
On Wed, 26 Feb 2014 18:43:41 +0100 Carsten Jensen to...@tomse.dk wrote: I've been installing it from scratch on 10.0 and it compiled without problems + all the dependencies. I haven't tested it on older versions of FreeBSD. Which version are you running? I am also on 10-RELEASE amd64. I didn't think this should matter, but apparently it does. I have Windows 7 and FreeBSD 10 dual-boot laptop with shared FAT32 partition: pacija@kaa:~ % sudo gpart show ada0 =63 1250263665 ada0 MBR (596G) 631985- free - (993K) 2048 204800 1 ntfs (100M) 206848 167567360 2 ntfs (80G) 167774208 104857600 3 freebsd [active] (50G) 272631808 977629184 4 fat32 (466G) 12502609922736- free - (1.3M) FAT32 partition is mounted in directory under my home dir: pacija@kaa:~ % cat /etc/fstab /dev/ada0s3a / ufs rw 1 1 /dev/ada0s3b none swap sw 0 0 /dev/ada0s4 /home/pacija/data msdosfs rw,large,noatime,-Len_GB.UTF-8 2 2 tmpfs /tmp tmpfs rw,size=128m,mode=1777 0 0 proc /proc procfs rw 0 0 If I put port dir on freebsd partition (eg. /home/pacija/Desktop/fs-uae), port compiles fine. If I put it on fat32 partition, I get those chown errors. -- Marko Cupać ___ 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: fs-uae amiga emulator
On 02/26/14 14:43, Carsten Jensen wrote: On 02/26/2014 03:35 PM, Marko Cupać wrote: On Mon, 17 Feb 2014 17:34:55 -0300 Danilo E. Gondolfo dan...@freebsd.org wrote: Hello, In this case, making a port is quite simple. Maybe I forgot something. But basically is this. To extract: sh fs-uae.shar Sorry it took me some time to get to this. make fails with bunch of chown errors: chown: /usr/home/pacija/data/softver/amiga/porttest/fs-uae/work/fs-uae-2.4.0/gensrc/cpuemu_31.cpp: Invalid argument chown: /usr/home/pacija/data/softver/amiga/porttest/fs-uae/work/fs-uae-2.4.0/gensrc: Invalid argument chown: /usr/home/pacija/data/softver/amiga/porttest/fs-uae/work/fs-uae-2.4.0/out/.dummy: Invalid argument chown: /usr/home/pacija/data/softver/amiga/porttest/fs-uae/work/fs-uae-2.4.0/out: Invalid argument chown: /usr/home/pacija/data/softver/amiga/porttest/fs-uae/work/fs-uae-2.4.0: Invalid argument chown: /usr/home/pacija/data/softver/amiga/porttest/fs-uae/work: Invalid argument *** Error code 1 Similar thing happen with another port I am testing (mixxx). Perhaps it has something to do with staging? I've been installing it from scratch on 10.0 and it compiled without problems + all the dependencies. I haven't tested it on older versions of FreeBSD. Which version are you running? I still need to do some more testing on earlier systems, but I hope to be able to add the launcher as an option, though it might be tricky. cheers Carsten The port that I sent works perfectly on my FreeBSD 10-amd64. I'm building it on redports.org right now [1], you can see the results in a few minutes. [1] https://redports.org/buildarchive/20140226182600-11724/ ___ 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: fs-uae amiga emulator
On 02/26/14 15:25, Marko Cupać wrote: On Wed, 26 Feb 2014 18:43:41 +0100 Carsten Jensen to...@tomse.dk wrote: I've been installing it from scratch on 10.0 and it compiled without problems + all the dependencies. I haven't tested it on older versions of FreeBSD. Which version are you running? I am also on 10-RELEASE amd64. I didn't think this should matter, but apparently it does. I have Windows 7 and FreeBSD 10 dual-boot laptop with shared FAT32 partition: pacija@kaa:~ % sudo gpart show ada0 =63 1250263665 ada0 MBR (596G) 631985- free - (993K) 2048 204800 1 ntfs (100M) 206848 167567360 2 ntfs (80G) 167774208 104857600 3 freebsd [active] (50G) 272631808 977629184 4 fat32 (466G) 12502609922736- free - (1.3M) FAT32 partition is mounted in directory under my home dir: pacija@kaa:~ % cat /etc/fstab /dev/ada0s3a / ufs rw 1 1 /dev/ada0s3b none swap sw 0 0 /dev/ada0s4 /home/pacija/data msdosfs rw,large,noatime,-Len_GB.UTF-8 2 2 tmpfs /tmp tmpfs rw,size=128m,mode=1777 0 0 proc /proc procfs rw 0 0 If I put port dir on freebsd partition (eg. /home/pacija/Desktop/fs-uae), port compiles fine. If I put it on fat32 partition, I get those chown errors. Yes, fat32 file system not recognize unix permissions. ;) ___ 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, pkg, virtualbox-ose
On 25/02/2014 20:20, Bernhard Fröhlich wrote: Am 25.02.2014 19:16 schrieb Chris Whitehouse cwhi...@onetel.com: Hi all, I'm installing a new system (laptop) using 10.0R and pkgng. freshports.org says virtualbox-ose can be installed with pkg but # pkg install virtualbox-ose says no package in the repository. virtualbox had a build failure due to iconv issues on 10.0 last week so this is why no package exists right now. It is already fixed so packages should be back with the next build run. Thanks for the info, I've built from source now but good to know. 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
FreeBSD Port: rtorrent-devel-0.9.3_2
Hello, I am finding a segmentation fault in this program. I am running FreeBSD 10.0-RELEASE. To reproduce, open rtorrent, press backspace, press tab. Console output is: Caught Segmentation fault, dumping stack: Stack dump not enabled. fish: Job 1, rtorrent terminated by signal SIGABRT (Abort) I tried running GDB as a friend of mine suggested (I have never used GDB before) and this is what I get: *** Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 805806400 (LWP 100159/rtorrent)] 0x0048a255 in torrent::File::range_second () *** Thanks, Manas ___ 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
CLang flags query:: I'm wanting to port software to FreeBSD
I've noticed different flags such as -Wno-parentheses and such along with the -Wno-unused-variable. I would like to know where would be a good source online to find the flags; and, I would like to know what flags are used by porters to optimize builds. These will be placed on the Makefile of the source such that it can be built natively on FreeBSD. I would be able to test software. 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: Support for pkg_*
On 26/02/2014 3:34 AM, Baptiste Daroussin wrote: On Tue, Feb 25, 2014 at 03:11:44PM +0100, A.J. 'Fonz' van Werven wrote: Dewayne Geraghty wrote: Has support for the pkg_* suite of tools gone away? As someone already stated, the pkg_* tools are no longer in FreeBSD 10, but they are still available (and default) on 9.2-RELEASE and earlier. tar: man/man1/CA.pl.1.gz: Cannot stat: No such file or directory tar: man/man1/asn1parse.1.gz: Cannot stat: No such file or directory ... tar: man/man7/des_modes.7.gz: Cannot stat: No such file or directory Please forgive me the pavlov reaction that I get from Cannot stat: bla bla bla, but that actually smells more like a staging issue to me. Have you tried adding NO_STAGE=yes to the port's Makefile and trying again? Can we stop advertising the above, this is completly wrong, it hides the dust behind the carpet and won't fix anything! The said port is needed a fix. regards, Bapt A.J, Thank-you for your suggestion. I hadn't considered, but reluctantly did try NO_STAGE=yes with both rsync and openssl, it made no difference, the packages failed with tar stat failures. I believe that PREFIX=/usr is not supported, per http://www.freebsd.org/cgi/query-pr.cgi?pr=183669. So I'll need to review how servers are built updated given that many are already deployed (in the meantime, I'll revert the packages needed in /usr and try to maintain separately in support of customers - disappointing) Ref: http://www.freebsd.org/cgi/query-pr.cgi?pr=187076 Dewayne. ___ 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: CLang flags query:: I'm wanting to port software to FreeBSD
On Wed, Feb 26, 2014 at 06:43:38PM -0500, Joe Nosay wrote: I've noticed different flags such as -Wno-parentheses and such along with the -Wno-unused-variable. I would like to know where would be a good source online to find the flags; and, I would like to know what flags are used by porters to optimize builds. These will be placed on the Makefile of the source such that it can be built natively on FreeBSD. I would be able to test software. There is unfortunately no central reference for Clang warning flags. The closest I've found is http://clang.llvm.org/docs/UsersManual.html#options-to-control-error-and-warning-messages but it omits most of them. Flags of the form -Wno-* disable warnings, usually because the code in question is vendor code we don't want to touch, a mess no one want's to clean up, or both. You should generally avoid them. I'm confused why you talk about optimization in the context of these flags. They have no impact on code generation. -- Brooks pgpmNNrcXGIpw.pgp Description: PGP signature
Re: CLang flags query:: I'm wanting to port software to FreeBSD
Hi-- On Feb 26, 2014, at 3:43 PM, Joe Nosay superbisq...@gmail.com wrote: I've noticed different flags such as -Wno-parentheses and such along with the -Wno-unused-variable. I would like to know where would be a good source online to find the flags; For compatibility, clang understands the commonly used -W flags that gcc uses. More documentation is here: http://clang.llvm.org/docs/UsersManual.html ...and normally folks use -Wall, -Wpedantic, or -Weverything. However, if you truly want the complete list, run clang's diagtool list-warnings: % clang/Debug+Asserts/bin/diagtool list-warnings Warnings with flags (924): backslash_newline_space [-Wbackslash-newline-escape] escaped_newline_block_comment_end [-Wcomment] ext_abstract_pack_declarator_parens [-Wanonymous-pack-parens] ext_aggregate_init_not_constant [-Wc99-extensions] [ ... ] warn_zero_size_struct_union_in_extern_c [-Wextern-c-compat] Warnings without flags (111): ext_delete_void_ptr_operand [ ... ] warn_weak_identifier_undeclared warn_weak_import STATISTICS: Percentage of warnings with flags: 89.28% Number of unique flags: 394 Average number of diagnostics per flag: 2.345 Number in -Wpedantic (not covered by other -W flags): 28 and, I would like to know what flags are used by porters to optimize builds. The default CFLAGS should be respected, unless a port needs something in particular in order to work; see: http://www.freebsd.org/doc/en/books/porters-handbook/dads-cflags.html These will be placed on the Makefile of the source such that it can be built natively on FreeBSD. I would be able to test software. Good luck; and note that the entire porter's handbook is worth a read. :-) Regards, -- -Chuck ___ 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: CLang flags query:: I'm wanting to port software to FreeBSD
On Wed, Feb 26, 2014 at 9:26 PM, Brooks Davis bro...@freebsd.org wrote:
On Wed, Feb 26, 2014 at 06:43:38PM -0500, Joe Nosay wrote:
I've noticed different flags such as -Wno-parentheses and such along with
the -Wno-unused-variable. I would like to know where would be a good
source
online to find the flags; and, I would like to know what flags are used
by
porters to optimize builds. These will be placed on the Makefile of the
source such that it can be built natively on FreeBSD. I would be able to
test software.
There is unfortunately no central reference for Clang warning flags.
The closest I've found is
http://clang.llvm.org/docs/UsersManual.html#options-to-control-error-and-warning-messages
but it omits most of them.
Flags of the form -Wno-* disable warnings, usually because the code in
question is vendor code we don't want to touch, a mess no one want's to
clean up, or both. You should generally avoid them. I'm confused why
you talk about optimization in the context of these flags. They have no
impact on code generation.
-- Brooks
jack_trauma.c:21:9: warning: 'IP_DONTFRAG' macro redefined
#define IP_DONTFRAG 1
^
/usr/include/netinet/in.h:464:
9: note: previous definition is here
#define IP_DONTFRAG 67 /* don't fragment packet */
^
jack_trauma.c:192:60: error: expected expression
socketfd == socket(AF_INET, SOCK_DGRAM, IPPROTO_UDPLITE);
^
jack_trauma.c:353:1: warning: type specifier missing, defaults to 'int'
[-Wimplicit-int]
parse_options(int argc, char** argv){
That is with what I am working. I'm not sure as how to work around it; so,
I want to try different flags.
___
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
google-sparsehash on FreeBSD 10, we should not resolve the problem that way.
So I just updated to FreeBSD 10, and almost all of my works were broken because of a single port: google-sparsehash. This is really frustrating, not because it cost me a lot time to fix a relatively simple library, but because the way the problem was 'resolved' by the port maintainer. One of the most critical changes from FreeBSD 9 to 10 is the switch from GCC to Clang. For some reason, google-sparsehash refused to be compiled with Clang, but was fine with GCC. Perhap, this caused the port maintainer to make a (questionable) decision: made google-sparsehash depends on gcc48 and used gcc48 to compile the library. And yes, it compiled fine. But then I compiled my own library with google-sparsehash, it failed miserably because of 'tr1' problem (gcc48 still used std::tr1 namespace, but clang has put it to the upper std namespace). I tried compiling my lib with gcc, but it also didn't work, because my other dependancies were all compiled with clang. What's good about a library, if it is compilable but we can't use it? The problem was indeed resolved for the port maintainer, but not for me. So, my point is: to resolve an incompatible problem, you should always tweak the piece to adapt with the system, not change the whole system to accept the piece. Now, return to the problem itself. I knew that google-sparsehash does not install any .so file, just header files (it uses templates heavily). In fact, this library does not need compiling, the only thing that was compiled is the test case. So, my 'solution' is simple. Screw the test, I do not want it anyway. Fixing the test case so it can be built with Clang is the job of google-sparsehash owner, not me, and also not the port maintainer. TL, DR. Delete every line about TESTS in Makefile.am, automake --add-missing, autoreconf, and it's done. ___ 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
pkg_libchk package is broken ?
Hi, I use sysutils/bsdadminscripts for years, thanks Dominic. After switching to pkg[ng] I patch pkg_libchk for it ( pkg info with corresponding keys instead pkg_info, etc). After r308906 (IIRC) I revert local my patches. Today I spotted that pkg_libchk package is broken, for example: tiger# pkg_libchk -q compat9x-amd64-9.2.902000.201310 diablo-jdk-1.6.0.07.02_20 festival-2.1 opera-12.16 tiger# pkg_libchk -n festival\* tiger# pkg_libchk -n festival-2.1 tiger# but: tiger# pkg_libchk -n compat9x-amd64-9.2.902000.201310: /usr/local/lib/compat/libncp.so.4 misses libipx.so.5 compat9x-amd64-9.2.902000.201310: /usr/local/lib32/compat/libncp.so.4 misses libipx.so.5 diablo-jdk-1.6.0.07.02_20: /usr/local/diablo-jdk1.6.0/jre/lib/amd64/libJdbcOdbc.so misses libodbcinst.so diablo-jdk-1.6.0.07.02_20: /usr/local/diablo-jdk1.6.0/jre/lib/amd64/libJdbcOdbc.so misses libodbc.so festival-2.1: /usr/local/libexec/audsp misses libaudiofile.so.0 festival-2.1: /usr/local/libexec/festival.naked misses libaudiofile.so.0 festival-2.1: /usr/local/libexec/festival_client.naked misses libaudiofile.so.0 opera-12.16: /usr/local/lib/opera/liboperakde4.so misses libkdeui.so.7 opera-12.16: /usr/local/lib/opera/liboperakde4.so misses libkio.so.7 opera-12.16: /usr/local/lib/opera/liboperakde4.so misses libkdecore.so.7 -- wbr, tiger ___ 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: pkg_libchk package is broken ?
On Thu, 27 Feb 2014 09:26:34 +0300 Sergey V. Dyatko sergey.dya...@gmail.com wrote: Hi, I use sysutils/bsdadminscripts for years, thanks Dominic. After switching to pkg[ng] I patch pkg_libchk for it ( pkg info with corresponding keys instead pkg_info, etc). After r308906 (IIRC) I revert local my patches. Today I spotted that pkg_libchk package is broken, for example: tiger# pkg_libchk -q compat9x-amd64-9.2.902000.201310 diablo-jdk-1.6.0.07.02_20 festival-2.1 opera-12.16 tiger# pkg_libchk -n festival\* tiger# pkg_libchk -n festival-2.1 tiger# seems '\' missing on line 411 --- pkg_libchk.orig 2014-02-27 09:31:31.204449447 +0300 +++ pkg_libchk 2014-02-27 09:31:45.539441534 +0300 @@ -407,7 +407,7 @@ # Get the packages to work on. test -z $packages packages=-a packages=$(pkg info -E $packages) -test -z $recursive -a -z $Recursive || packages=$packages +test -z $recursive -a -z $Recursive || packages=$packages \ $(pkg info -q $recursive $Recursive $packages 2 /dev/null | \ sed -E 's|^@pkgdep[[:space:]]*||1') -- wbr, tiger ___ 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
