duplicity new version
There is a new version of duplicity out 0.7.11. https://launchpad.net/duplicity It fixes a bug where the b2-backend will stop working this week when the company backblaze update their api. Thank you for your great work with the ports collection! I'm using FreeNAS, and it is by far the best NAS I ever used, thanks to FreeBSD and ZFS. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: duplicity new version
On Tue, Feb 14, 2017 at 10:46:05AM +0100, Mikael Moutakis wrote: > There is a new version of duplicity out 0.7.11. > https://launchpad.net/duplicity > > It fixes a bug where the b2-backend will stop working this week when the > company backblaze update their api. > > Thank you for your great work with the ports collection! I'm using FreeNAS, > and it is by far the best NAS I ever used, thanks to FreeBSD and ZFS. Hi. There is already a PR for this update. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216366 If you can, please test it. Regards. -- Danilo G. Baio (dbaio) signature.asc Description: PGP signature
Re: Problem with building libgcrypt
On Tue, 14 Feb 2017 15:11:30 +1100 (EST) Dave Horsfall wrote: >>> What is the output of "pkg which /usr/local/lib/libiconv.la"? >> >> Not found; I sense a generic approach to any more errors of this type :-) > > Removed as suggested (along with libxslt) as nothing claimed to be using > it, now it's complaining that they're missing when building graphics/peps > (I gave docbook a miss): > > libtool: error: cannot find the library '/usr/local/lib/libiconv.la' or > unhandled argument '/usr/local/lib/libiconv.la' > > Why is libiconv.la now suddenly required? > > At this rate it'll be a full install, but that is definitely a last > resort (and the 10.3 CD I burned had better be readable). Keep following the 20140909 entry in UPDATING. You should run this command now: find /usr/local/lib -name '*.la' | xargs grep -l 'libiconv\.la' | xargs pkg which ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
pecl-memcached (3)
Hi, pecl-memcached has been updated in the ports tree from 2.2.0.5 to 3.0.1 however 3+ version is for PHP7 only, An IGNORE notice is in the Makefile, we'll all be on php7 sometime, but as PHP56 is still in security release should v3 be a seperate port to avoid v2 generating update alerts via ports mgmt tools? Paul. -- ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pecl-memcached (3)
On Tue, Feb 14, 2017 at 9:11 PM, Paul Macdonald wrote: > Hi, > > pecl-memcached has been updated in the ports tree from 2.2.0.5 to 3.0.1 > > however 3+ version is for PHP7 only, > > An IGNORE notice is in the Makefile, > > we'll all be on php7 sometime, but as PHP56 is still in security release > should v3 be a seperate port to avoid v2 generating update alerts via ports > mgmt tools? > > Paul. > > -- > > Hello, pecl-memcached will follow the latest version (3.x) and pecl-memcached2 was added for php56 users. Regards, sunpoet ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pecl-memcached (3)
On Tue, 14 Feb 2017 13:11:09 -, Paul Macdonald wrote: pecl-memcached has been updated in the ports tree from 2.2.0.5 to 3.0.1 however 3+ version is for PHP7 only, An IGNORE notice is in the Makefile, we'll all be on php7 sometime, but as PHP56 is still in security release should v3 be a seperate port to avoid v2 generating update alerts via ports mgmt tools? v2 was moved to databases/pecl-memcached2 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
net-mgmt/prometheus update to 1.5.2, comitter requested
Hi All, Could I get a committer to apply my latest update patch for net-mgmt/ prometheus? Patch is available here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216973 Thanks so much, -Jev ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Expulsion of John Marino - reasons and impact?
Occasionally we’re called to account for our decisions, reflect upon their correctness and at times reverse the decision. John Marino (John) has conducted himself with a passion for making decisions in the interests of ports' users over many years with great professionalism and enthusiasm. At times, this passion exudes into bravado, even exuberance. This is not uncommon when sharing deep-seated beliefs of how things should be done. Sometimes, perhaps too rarely we see contrary opinions expressed in the various FreeBSD lists. As I’ve observed with my first and second level managers, the weak managers never hire people that challenge their views, or have talents superior to their own; they hire people with lesser abilities. To their detriment they deny themselves the opportunity to grow. Similarly with community-based projects, I’m currently a Director of one, in this context strongly divergent views distract from the singular imperative of helping others. Regardless such views cause, reflection – are we heading in the right direction; are our actions aligned with our mission; is our strategy meeting the goals of our customers (the needy in the community); are we properly communicating and advocating our purpose. Time consuming and sometimes unpleasant, the opportunity to review and challenge is worthwhile. John is significant contributor to the ports user-base, he has advocated views which represent the needs of the user-community and his expulsion, the reasons for them and the analysis of his expulsion upon the project should be communicated, for transparency and reassurance that such decisions are in the interests of everyone. This is simply inadequate: https://svnweb.freebsd.org/ports?view=revision&revision=433827 https://svnweb.freebsd.org/ports?view=revision&revision=433856 I value John’s forthright opinions, and his motivations and contribution to GNU, Ada, DragonflyBSD and FreeBSD are not unrecognised. He articulates his position clearly; his design and development efforts are sound, and the development of Synth is appreciated. This lack of transparency suggests that he is divergent, so lets examine this as a reason for expulsion. Was it due to providing a choice. Users of FreeBSD have a choice: a) build their own build/development system b) use poudererie - which to me is another layer of complexity and another source of frequent change c) use synth - where transparency and is relatively simple to use. The ports system has undergone significant change over the last 4 years, much of it needed and requiring significant time and active contribution by the meta-ports developers. Unfortunately the cost to those using the ports system during this time has been significant. I see John as a stabilising influence (as Doug Barton was) - is this the reason? Lets just examine FreeBSD for a moment. The project is fantastic and so many different ideas and approaches have collaborated and continue to progress; I was a saddened when Matt Dillon split from FreeBSD. Its a testament to all that there remain, that a high level of exchange and collaboration continues and John has acted as a conduit and has contributed in this area also. So how should we view “The FreeBSD Project"? Its really split along the logical boundaries of: the base system, the ports meta-system, and the ports system. The ports system is actively maintained by many ports “maintainers” and the frequency of change reflects the changes to applications (source) that is under greater scrutiny to be (more) secure. This is ok, and I’ll come back to this. I started with FreeBSD in 2003, when packages were available and this greatly contributed to my uptake of FreeBSD. Over time, I needed to customise my settings sometimes for performance reasons, usually for security reasons. I was very happy with the ports system, and I was able to work-around the changing library versioning issues; but it did need to be fixed. Roughly 4-5 years ago pkg and the meta-ports system underwent significant and needed change. The folks doing this work have done a great job; but. The implementation of the changes had a deleterious effect. The frequency of change became intolerable, at one point we had 0.25 of an FTE just maintaining our build systems. We rebuilt all packages overnight which enabled testing in the event of critical issues for our clients. Had we known of the meta-ports flux we would've changed our business model and commitments to our customer base. Now we see discussions over whether ports should be supported past the EOL of an OS. Seriously? I had a client that refused OS upgrades, so we maintained up-to-date ports for around 4 years after FreeBSD 6.1 was EOL. Ridiculous but a credit to the ports and meta-ports developers/maintainers, at the time. Our view of FreeBSD being rock-solid was reinforced. However, nothing like this should be expected to be supported, though packages should be able
Re: Expulsion of John Marino - reasons and impact?
Hi! Thank you for your post, and for asking this question: [About John Marino] > At the very least we should know why, and by what criteria he is judged? We all hope that this is explained in more detail, the sooner the better. And thank you for also asking all the other questions. -- p...@opsec.eu+49 171 3101372 3 years to go ! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Expulsion of John Marino - reasons and impact?
On 2/14/2017 12:50 PM, Dewayne Geraghty wrote: > https://svnweb.freebsd.org/ports?view=revision&revision=433827 I think that commit message combined with https://www.freebsd.org/internal/code-of-conduct.html is enough. > > https://svnweb.freebsd.org/ports?view=revision&revision=433856 This commit may have been an error and is being discussed. -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Re: Expulsion of John Marino - reasons and impact?
On Wed, 15 Feb 2017 07:50:46 +1100 Dewayne Geraghty wrote > Occasionally we’re called to account for our decisions, reflect upon their > correctness and at times reverse the decision. > > > > John Marino (John) has conducted himself with a passion for making > decisions in the interests of ports' users over many years with great > professionalism and enthusiasm. I'm usually very much disinclined to get even remotely involved in what may appear to be political / internal drama. But in this instance, I feel strongly compelled to respond. I met John through my initial interest in getting involved in the ports system -- maintaining ports. I immediately recognized that John was a man of strong convictions. He was always outspoken -- he spoke "straight", and I greatly appreciated it! We had many disagreements. I'm strong minded, and as a result, resistant to change. But I must humbly admit that I ultimately had to agree with John nearly every time. As a result I have a tremendous amount of respect for John -- he earned it! Some may find outspoken people abrasive, or undesirable, and reject them. If that's the case here; I can easily say they're missing the forest, for the trees. Sound reasonable advice, and knowledge is good; no matter *what* tone it's spoken. I can tell you this; John gave me a leg up, into becoming a ports maintainer. He must have done a fair job, in my opinion. As I currently maintain over 100 (one hundred) ports. I have but one outstanding pr(1). Which I was working on, when I read this message. I can also tell you; because of my strong mindedness, I was *not* an ideal candidate for a mentor. I can assure you, I challenged John's patience a number of times. But out of his guidance, and insistence TDTRT. I've managed to maintain the number of ports I do today. So I guess what I'm trying to say is this; John demands the best. Which produces high quality output from those whom work with him. If John Marino has been excommunicated from FreeBSD. The only looser will be FreeBSD itself. My writeup on this is due to the OP alluding to the reason for John's expulsion somehow being related to his "outspokenness". Something *I* found to be a *great* *attribute*. Thanks for all your time, and consideration. --Chris ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Expulsion of John Marino - reasons and impact?
> On 14 Feb 2017, at 22:16, Bryan Drewery wrote: > >> On 2/14/2017 12:50 PM, Dewayne Geraghty wrote: >> https://svnweb.freebsd.org/ports?view=revision&revision=433827 > > I think that commit message combined with > https://www.freebsd.org/internal/code-of-conduct.html is enough. The commit message basically says that he misbehaved once too often and the CoC defines what "misbehave" might mean. Not over the top transparent/detailed to be honest. > >> >> https://svnweb.freebsd.org/ports?view=revision&revision=433856 > > This commit may have been an error and is being discussed. That seems quite draconian and - if it isn't reversed - needs a good explanation. -m > > > -- > Regards, > Bryan Drewery > ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Expulsion of John Marino - reasons and impact?
On 2/14/2017 2:58 PM, Michael Gmelin wrote: >> On 14 Feb 2017, at 22:16, Bryan Drewery wrote: >>> On 2/14/2017 12:50 PM, Dewayne Geraghty wrote: >>> https://svnweb.freebsd.org/ports?view=revision&revision=433827 >> I think that commit message combined with >> https://www.freebsd.org/internal/code-of-conduct.html is enough. > The commit message basically says that he misbehaved once too often and the > CoC defines what "misbehave" might mean. Not over the top > transparent/detailed to be honest. Right, would you want an organization you volunteered for to drag your name through the mud for some reason? I don't think it's our place (the project) to say more than we already have publicly. Please drop this before it gets out of hand. Discussing people personally/negatively in a public forum is not appropriate. -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Re: Expulsion of John Marino - reasons and impact?
> On 15 Feb 2017, at 00:15, Bryan Drewery wrote: > > On 2/14/2017 2:58 PM, Michael Gmelin wrote: On 14 Feb 2017, at 22:16, Bryan Drewery wrote: On 2/14/2017 12:50 PM, Dewayne Geraghty wrote: https://svnweb.freebsd.org/ports?view=revision&revision=433827 >>> I think that commit message combined with >>> https://www.freebsd.org/internal/code-of-conduct.html is enough. >> The commit message basically says that he misbehaved once too often and the >> CoC defines what "misbehave" might mean. Not over the top >> transparent/detailed to be honest. > > Right, would you want an organization you volunteered for to drag your > name through the mud for some reason? I don't think it's our place (the > project) to say more than we already have publicly. Please drop this > before it gets out of hand. Discussing people personally/negatively in > a public forum is not appropriate. > Well, if it was something he said in public, pointing to it might be enlightening. On the other hand, I assume he could always do that himself if he feels like it. One way or the other, I'll miss his positive contributions and I'm saddened that this happened. -m ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Finally got ports rebuilt!
Well, almost; just a few rough edges to smooth over. Background: after upgrading to 10.3 from 9.3, I then attacked the long-neglected ports area. Now, I sort of inherited this installation, and having an engineering background i.e. "if it ain't broke, don't fix it". Just so you know where I come from, I also have 40+ years of Unix experience across a wide range of platforms; FreeBSD is my first, although I used SunOS and BSDi for many years, so I'm hardly new to BSD. I was scrupulous about installing various security fixes, however... So... There appears to be circular dependencies involving libiconv and libxslt, which I resolved by installing them by hand. All sorts of things want the Ruby bloatware (it won't build on my box) so I installed it as a package. Riding shotgun for most of the night (yawn...), some things kept wanting to build LLVM (!), so I merely blew them away one by one (there's no way that LLVM will build here); I doubt whether I'll miss them, but I can always install them as packages if they're needed. UUCP needed to be rebuilt? And Apache, although installed from ports, was not selected to be rebuilt for some reason. Anyway, that's pretty much it; many thanks to David Wolfskill and Tijl Coosemans for their kind assistance, and to the list members for their forbearance as I went through this learning exercise; I promise to keep ports up to date in the future. Thanks again. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
xorg-server 1.18.4 segfaults
Hi, After recent update of xorg-server, the new xorg-server segfaults. I'm using FreeBSD in VirtualBox so the video driver is vboxvideo. I've already rebuilt virtualbox-ose-additions. What can I do? I attach the xorg log. -- `whois vmeta.jp | nkf -w` meta [180360.851] X.Org X Server 1.18.4 Release Date: 2016-07-19 [180360.852] X Protocol Version 11, Revision 0 [180360.853] Build Operating System: FreeBSD 11.0-RELEASE-p2 amd64 [180360.854] Current Operating System: FreeBSD graphite.local.haw.jp 11.0-RELEASE-p2 FreeBSD 11.0-RELEASE-p2 #0: Mon Oct 24 06:55:27 UTC 2016 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 [180360.854] Build Date: 15 February 2017 05:31:30AM [180360.855] [180360.855] Current version of pixman: 0.34.0 [180360.856]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [180360.856] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [180360.867] (==) Log file: "/var/log/Xorg.20.log", Time: Wed Feb 15 11:36:51 2017 [180360.868] (==) Using config file: "/etc/X11/xorg.conf" [180360.868] (==) Using system config directory "/usr/local/share/X11/xorg.conf.d" [180360.869] (==) No Layout section. Using the first Screen section. [180360.869] (==) No screen section available. Using defaults. [180360.869] (**) |-->Screen "Default Screen Section" (0) [180360.869] (**) | |-->Monitor "" [180360.870] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [180360.871] (**) Option "AutoAddDevices" "true" [180360.871] (**) Option "AutoEnableDevices" "true" [180360.871] (**) Automatically adding devices [180360.871] (**) Automatically enabling devices [180360.871] (==) Not automatically adding GPU devices [180360.871] (==) Max clients allowed: 256, resource mask: 0x1f [180360.871] (==) FontPath set to: /usr/local/share/fonts/misc/, /usr/local/share/fonts/TTF/, /usr/local/share/fonts/OTF/, /usr/local/share/fonts/Type1/, /usr/local/share/fonts/100dpi/, /usr/local/share/fonts/75dpi/ [180360.871] (==) ModulePath set to "/usr/local/lib/xorg/modules" [180360.871] (II) The server relies on devd to provide the list of input devices. If no devices become available, reconfigure devd or disable AutoAddDevices. [180360.871] (II) Loader magic: 0x813b80 [180360.871] (II) Module ABI versions: [180360.871]X.Org ANSI C Emulation: 0.4 [180360.871]X.Org Video Driver: 20.0 [180360.872]X.Org XInput driver : 22.1 [180360.872]X.Org Server Extension : 9.0 [180360.872] (--) PCI:*(0:0:2:0) 80ee:beef:: rev 0, Mem @ 0xe000/33554432, BIOS @ 0x/65536 [180360.872] (II) "glx" will be loaded by default. [180360.872] (II) LoadModule: "kbd" [180360.874] (II) Loading /usr/local/lib/xorg/modules/input/kbd_drv.so [180360.874] (II) Module kbd: vendor="X.Org Foundation" [180360.874]compiled for 1.18.4, module version = 1.9.0 [180360.874]Module class: X.Org XInput Driver [180360.874]ABI class: X.Org XInput driver, version 22.1 [180360.874] (II) LoadModule: "synaptics" [180360.875] (II) Loading /usr/local/lib/xorg/modules/input/synaptics_drv.so [180360.875] (II) Module synaptics: vendor="X.Org Foundation" [180360.875]compiled for 1.18.4, module version = 1.9.0 [180360.876]Module class: X.Org XInput Driver [180360.876]ABI class: X.Org XInput driver, version 22.1 [180360.876] (II) LoadModule: "glx" [180360.876] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so [180360.880] (II) Module glx: vendor="X.Org Foundation" [180360.880]compiled for 1.18.4, module version = 1.0.0 [180360.880]ABI class: X.Org Server Extension, version 9.0 [180360.880] (==) AIGLX enabled [180360.880] (==) Matched vboxvideo as autoconfigured driver 0 [180360.880] (==) Matched modesetting as autoconfigured driver 1 [180360.880] (==) Matched scfb as autoconfigured driver 2 [180360.880] (==) Matched vesa as autoconfigured driver 3 [180360.880] (==) Assigned the driver to the xf86ConfigLayout [180360.880] (II) LoadModule: "vboxvideo" [180360.881] (II) Loading /usr/local/lib/xorg/modules/drivers/vboxvideo_drv.so [180360.882] (II) Module vboxvideo: vendor="Oracle Corporation" [180360.882]compiled for 1.18.0, module version = 1.0.1 [180360.882]Module class: X.Org Video Driver [180360.882]ABI class: X.Org Video Driver, version 20.0 [180360.882] (**) Load address of symbol "VBOXVIDEO" is 0x80710e600 [180360.882] (II) LoadModule: "modesetting" [180360.882] (II) Loading /usr/local/lib/xorg/modules/drivers/modesetting_drv.so [180360.883] (II) Module modesetting: vendor="X.Org Foundation" [180360.883]compiled for 1.18.4, module version = 1.18.4 [180360.883]Module class: X.Org Video Driver [180360.883]ABI class: X.Org Video Driver,
Re: xorg-server 1.18.4 segfaults
On Wed, Feb 15, 2017 at 02:54:50AM +, Koichiro IWAO wrote: > [180361.824] (EE) Backtrace: > [180361.836] (EE) 0: /usr/local/bin/Xorg (OsInit+0x38a) [0x5abfca] > [180361.846] (EE) 1: /lib/libthr.so.3 (_pthread_sigmask+0x50d) [0x802989bbd] > [180361.857] (EE) 2: /lib/libthr.so.3 (_pthread_getspecific+0xe9f) > [0x802989acf] > [180361.871] (EE) 3: ? (?+0xe9f) [0x8032] > [180361.882] (EE) 4: /usr/local/llvm39/lib/libLLVM-3.9.so > (_ZN4llvm13StringMapImpl15LookupBucketForENS_9StringRefE+0xf0) [0x80b0c0340] > [180361.898] (EE) 5: /usr/local/llvm39/lib/libLLVM-3.9.so > (LLVMParseCommandLineOptions+0x7cf) [0x80b08497f] > [180361.909] (EE) 6: /usr/local/llvm39/lib/libLLVM-3.9.so > (LLVMParseCommandLineOptions+0x92c) [0x80b084c1c] > [180361.923] (EE) 7: /usr/local/llvm39/lib/libLLVM-3.9.so > (_ZN4llvm2cl6Option11addArgumentEv+0x7c) [0x80b078dec] > [180361.934] (EE) 8: /usr/local/llvm37/lib/libLLVMSupport.so.3.7 > (_ZNSt3__127__insertion_sort_incompleteIRNS_6__lessINS_4pairIN4llvm10TimeRecordENS_12basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEESB_EEPSB_EEbT0_SF_T_+0x67d) > [0x8199ae31d] > [180361.944] (EE) 9: /usr/local/llvm37/lib/libLLVMSupport.so.3.7 > (_ZN4llvm3sys8WatchdogD1Ev+0x32) [0x8199e6264] > [180361.955] (EE) 10: /usr/local/llvm37/lib/libLLVMSupport.so.3.7 (_init+0xe) > [0x819944ebc] > [180361.964] (EE) 11: ? (_rtld_is_dlopened+0x1532) [0x80081a3e2] > [180361.978] (EE) 12: ? (dlopen+0x191) [0x800816311] > [180361.991] (EE) 13: /usr/local/lib/xorg/modules/extensions/libglx.so > (_init+0x1c544) [0x804a594f4] > [180362.005] (EE) 14: /usr/local/lib/xorg/modules/extensions/libglx.so > (_init+0x1b9d9) [0x804a57df9] > [180362.017] (EE) 15: /usr/local/lib/xorg/modules/extensions/libglx.so > (_init+0x1b056) [0x804a56a26] > [180362.029] (EE) 16: /usr/local/bin/Xorg (InitExtensions+0x61) [0x4ab931] > [180362.039] (EE) 17: /usr/local/bin/Xorg (remove_fs_handlers+0x3a2) > [0x43b4b2] > [180362.050] (EE) 18: /usr/local/bin/Xorg (_start+0x17f) [0x42507f] > [180362.064] (EE) 19: ? (?+0x17f) [0x80083917f] > [180362.065] (EE) > [180362.066] (EE) Segmentation fault at address 0x819a07000 Deinstall llvm 3.7. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: xorg-server 1.18.4 segfaults
Konstantin, Deinstalling llvm37 helped, thanks! -- `whois vmeta.jp | nkf -w` meta ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: xorg-server 1.18.4 segfaults
Konstantin, Deinstalling llvm37 helped, thanks! P.S. I actually deinstalled all older versions of llvm, llvm36, llvm37. -- `whois vmeta.jp | nkf -w` meta ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
