Re: Conflict between lang/tcl85 and x11-toolkits/open-motif?
This can be fixed by using either the mentioned or if you require the tcl man pages add: WITHOUT_OPENMOTIF_MANUALS=yes to make.conf and rebuild open-motif. Chris On Tue, Oct 23, 2012 at 4:33 AM, Pietro Cerutti wrote: > On 2012-Oct-23, 05:02, Thomas Mueller wrote: > > Is there a conflict between lang/tcl85 and x11-toolkits/open-motif, not > > documented in the Makefiles, like trying to install files to the same > place? > > > > Trying in many steps, stopped by so many snags, I am trying to rebuild > all ports depending on png, starting from "portmaster -r png-", and this is > stopping me. > > > > I show relevant portion of the log: > > > > Installing and cross-linking C API (.3) docs > > Installing and cross-linking command (.n) docs > > ** > > IMPORTANT: > > ** > > tclConfig.sh in /usr/local/lib/tcl8.5/tclConfig.sh > > tcl.hin /usr/local/include/tcl8.5/tcl.h > > tclDecls.h in /usr/local/include/tcl8.5/tclDecls.h > > There are NOT default place, but good place to avoid > > conflicting with another version of Tcl/Tks. > > ===> Compressing manual pages for tcl-8.5.12_2 > > ===> Running ldconfig > > /sbin/ldconfig -m /usr/local/lib > > ===> Registering installation for tcl-8.5.12_2 > > Installing tcl-8.5.12_2...pkg: tcl-8.5.12_2 conflicts with > open-motif-2.3.3 (ins > > talls files into the same place). Problematic file: > /usr/local/man/man3/Object. > > 3.gz > > *** [fake-pkg] Error code 70 > > > > Stop in /BETA1/usr/ports/lang/tcl85. > > *** [install] Error code 1 > > > > Stop in /BETA1/usr/ports/lang/tcl85. > > > > (end of quoted portion of log) > > > > Where do I go from here? I didn't find any conflicts between lang/tcl85 > and > > x11-toolkits/open-motif documented in the Makefiles. > > Yes the problem exists indeed. I suggest that you reconfigure (make > config) in lang/tcl85 and unselect the TCL85_MAN option, then reinstall > tcl85. > > -- > Pietro Cerutti > The FreeBSD Project > g...@freebsd.org > > PGP Public Key: > http://gahr.ch/pgp > ___ 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: pkgng: Installing open-motif-2.3.4...pkg: open-motif-2.3.4 conflicts with tcl-8.5.13 (installs files into the same place). Problematic file: /usr/local/man/man3/Object.3.gz, *** [fake-pkg] Error c
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 this is being worked on. in the mean time disable man pages for tcl or open-motif. On 12/6/2012 6:31 PM, O. Hartmann wrote: > On one machine (FreeBSD 10.0-CURRENT #0 r243946: Thu Dec 6 > 12:18:13 CET 2012) , I can not install anymore the port > x11-toolskits/open-motif. > > It ends up with the error below. Another machine, also the same OS > and revision, has both tcl-8.5.13 AND open-motif-2.3.4 installed > and I can compile them both and reinstall them. > > I think there is something corrupt in the DB of pkgng. How is this > to repair? > > Thanks, > > Oliver > > [...] install -o root -g wheel -m 444 > /usr/ports/x11-toolkits/open-motif/work/motif-2.3.4/BUGREPORT > /usr/local/share/doc/open-motif install -o root -g wheel -m 444 > /usr/ports/x11-toolkits/open-motif/work/motif-2.3.4/README > /usr/local/share/doc/open-motif install -o root -g wheel -m 444 > /usr/ports/x11-toolkits/open-motif/work/motif-2.3.4/RELNOTES > /usr/local/share/doc/open-motif ===> Compressing manual pages for > open-motif-2.3.4 ===> Running ldconfig /sbin/ldconfig -m > /usr/local/lib ===> Registering installation for > open-motif-2.3.4 Installing open-motif-2.3.4...pkg: > open-motif-2.3.4 conflicts with tcl-8.5.13 (installs files into the > same place). Problematic file: /usr/local/man/man3/Object.3.gz *** > [fake-pkg] Error code 70 > > Stop in /usr/ports/x11-toolkits/open-motif. > > ===>>> Installation of open-motif-2.3.4 (x11-toolkits/open-motif) > failed ===>>> Aborting update > > Terminated > > ===>>> You can restart from the point of failure with this command > line: portmaster x11-toolkits/open-motif > -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJQwToKAAoJEAGnn5Nn8qWU1iIH/RMtFRkrADShRaxSTaXLgDGn M4Q94rE2/QPgUripK5aMvQK8ax2PAwflk31ZIX9h43zHb9wWA7fqiaOLDlEyUoWH AefKoDKwiJAvu3Lso7IRaOafyLlSuZuNK7Q0EO6pt77nCKLCKoZWsBHWUeC7QUaW pznXEk4V4FfM2QqATFhAg6pjnx8NaPJnW/Ci8a7g5EGI8agb3eHqlIjHu9Y/k0R+ h+saZClelEr1g0KxNLgQbw/KsTeem4typ6tDpfj71hC8Mgq2G3k9/3gV08uR3xbB PZwmHjwFAPod9Ys/Q9AHSBFmQw1KKg0y6kCGN+MNEkCWs2bIy9KfmrzWDXbY8qk= =kdyU -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"
Gnustep group
Looking at the current state of gnustep and I am wondering if any commiters would be interested in creating a gnustep group/team? as a lot of ports have no maintainer and would be nice if there was a ML and other means for gnustep ? 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: Gnustep group
On 03/17/2013 03:06 PM, Waitman Gobble wrote: Waitman Gobble wrote .. Chris Petrik wrote .. Looking at the current state of gnustep and I am wondering if any commiters would be interested in creating a gnustep group/team? as a lot of ports have no maintainer and would be nice if there was a ML and other means for gnustep ? 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" Hi, Sounds great. I'm not a committer but was looking at gnustep earlier today, have a need for a JBOS system and this could be good for a wall. It's an interesting coincidence I suppose. I'll check out ports status. Yes, after review I notice the GNUstep ports are totally not working.. it doesn't work with base clang. However, clang in ports works, and all the GNUstep modules build from svn without issue.. so it really should be a piece of cake to build some new GNUstep ports.. if there's interest. Here are my notes so far. https://dx.burplex.com/bin/gnustep.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" I plan on updating gnustep and friends as well as take all gnustep related ports. However it will take a while. ___ 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: Gnustep group
On 03/17/2013 04:14 PM, John Marino wrote: On 3/17/2013 22:58, Chris Petrik wrote: Yes, after review I notice the GNUstep ports are totally not working.. it doesn't work with base clang. However, clang in ports works, and all the GNUstep modules build from svn without issue.. so it really should be a piece of cake to build some new GNUstep ports.. if there's interest. Here are my notes so far. FWIW - All the GNUstep ports build fine in DPorts (ports on DragonFly). However, the compiler uses is the base compiler, which is GCC 4.7 with ObjC built-in. That would imply setting USE_GCC=4.6+ would "fix" gnustep on ports, no? John ___ 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" Base gcc in freebsd is 4.2 so yes that would needed. ___ 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: Gnustep group
On 03/17/2013 04:23 PM, Waitman Gobble wrote: John Marino wrote .. On 3/17/2013 22:58, Chris Petrik wrote: Yes, after review I notice the GNUstep ports are totally not working.. it doesn't work with base clang. However, clang in ports works, and all the GNUstep modules build from svn without issue.. so it really should be a piece of cake to build some new GNUstep ports.. if there's interest. Here are my notes so far. FWIW - All the GNUstep ports build fine in DPorts (ports on DragonFly). However, the compiler uses is the base compiler, which is GCC 4.7 with ObjC built-in. That would imply setting USE_GCC=4.6+ would "fix" gnustep on ports, no? John ___ 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" Maybe it will work, I tried with gcc48. One of the gnustep ports is stuck on trying to build gcc4.2 for some reason.. I don't recall which one at the moment, i think it was base? I would try the next minimum build which is 4.4 if that works then add in 4.4+ etc.. but i havent messed with it yet. ___ 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: Gnustep group
On 03/17/2013 05:21 PM, Waitman Gobble wrote: Chris Petrik wrote .. On 03/17/2013 04:23 PM, Waitman Gobble wrote: John Marino wrote .. On 3/17/2013 22:58, Chris Petrik wrote: Yes, after review I notice the GNUstep ports are totally not working.. it doesn't work with base clang. However, clang in ports works, and all the GNUstep modules build from svn without issue.. so it really should be a piece of cake to build some new GNUstep ports.. if there's interest. Here are my notes so far. FWIW - All the GNUstep ports build fine in DPorts (ports on DragonFly). However, the compiler uses is the base compiler, which is GCC 4.7 with ObjC built-in. That would imply setting USE_GCC=4.6+ would "fix" gnustep on ports, no? John ___ 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" Maybe it will work, I tried with gcc48. One of the gnustep ports is stuck on trying to build gcc4.2 for some reason.. I don't recall which one at the moment, i think it was base? I would try the next minimum build which is 4.4 if that works then add in 4.4+ etc.. but i havent messed with it yet. Yes, this should work. BUT why the heck would one of the GNUstep ports stubbornly demand to try to install gcc 4.2 from ports? Something to check out. GNUstep src from svn builds without any troubles, so it should be very easy to set up some new ports IMHO. The GNUstep apps build OK too, it's just a matter of setting the variable GNUSTEP_MAKEFILES to point to the Makefiles. Here's a screen shot of GORM running on my FreeBSD 10.0-CURRENT machine w/ XFCE4 desktop. https://dx.burplex.com/ui/gorm-sreenshot.png ___ 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 would be using the latest released ver not svn. ___ 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: tcpdump port version bump to 4.6.2
On 12/03/2014 10:45, Matthew Closson wrote: > Index: net/tcpdump/Makefile > === > --- net/tcpdump/Makefile (revision 373799) > +++ net/tcpdump/Makefile (working copy) > @@ -2,7 +2,7 @@ > # $FreeBSD$ > > PORTNAME= tcpdump > -PORTVERSION= 4.5.1 > +PORTVERSION= 4.6.2 > CATEGORIES= net ipv6 > MASTER_SITES= http://www.tcpdump.org/release/ > > Index: net/tcpdump/distinfo > === > --- net/tcpdump/distinfo (revision 373799) > +++ net/tcpdump/distinfo (working copy) > @@ -1,2 +1,2 @@ > -SHA256 (tcpdump-4.5.1.tar.gz) = > 14ab39657128f3a650aed4cf455f76c7590601087b6101c253d698f6e73f0b96 > -SIZE (tcpdump-4.5.1.tar.gz) = 1024455 > +SHA256 (tcpdump-4.6.2.tar.gz) = > 524ee4d8e83a6c663f6879004216a9a5bcb1c68b11920d653eb87b79d008e0b8 > +SIZE (tcpdump-4.6.2.tar.gz) = 1105356 > > If I should put this into a file or some other format please let me know. > Thanks, > > -Matt- > ___ > 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" > open a pr with this attached. signature.asc Description: OpenPGP digital signature
