Re: Deprecating ISA sound cards

Anyone objecting to this, be careful, I might ship a pile of such things to you from the depths of the closets :-) mcl

Re: 13 stable build fail

Is this the same as: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256947 ? mcl

Re: Files in /etc containing empty VCSId header

On Mon, Jun 07, 2021 at 01:58:01PM -0600, Ian Lepore wrote: > Sometimes it's a real interesting exercise to figure out where a > file on your runtime system comes from in the source world. A tangential problem I trip over is "what is on this SD card?" It generally takes me 5-10 minutes to

Re: Help wanted: volunteer yourselves in .github/CODEOWNERS

On Mon, May 31, 2021 at 05:25:03AM +, Poul-Henning Kamp wrote: > They are enthusiastic FreeBSD users and potential future committers, > and should be treated as such! The same goes for non-committers and phabricator, IMHO. mcl

Re: i915kms and chip resets on rsc0?

On Thu, Jan 28, 2021 at 02:20:40PM -0800, Steve Kargl wrote: > This is all likely academic as I just saw John Baldwin's email > that stated i386 support is being dropped in FreeBSD-current. s/dropped/downgraded/ The only difference seems to be that security upgrades that _only_ affect i386 will

Re: pkg for 14-current

On Sun, Jan 24, 2021 at 07:45:08PM +0900, Yasuhiro Kimura wrote: > By the way, when -CURRENT was bumped from 12 to 13, there were some > ports that failed to be built on 13-CURRENT simply because they don't > expect there is version 13.x of FreeBSD. And probably such ports fails > to be built on

Re: CURRENT, usr/src on git, howto "mergemaster"?

On Wed, Jan 06, 2021 at 11:24:22AM +, tech-lists wrote: > >Moreover mergemaster is still officially documented and recommend as > >only right method in FreeBSD handbook. See > >https://www.freebsd.org/doc/handbook/makeworld.html. > >World is moving, we may have new tools but each deprecation

Re: HEADS UP: FreeBSD src repo transitioning to git this weekend

Folks, please change the Subject: line here. This has now become a thread of only tangiental interest to a typical FreeBSD developer (in this case, typified by me :-) ) mcl ___ freebsd-current@freebsd.org mailing list

Re: git tools for building in base?

On Tue, Nov 24, 2020 at 09:59:15PM -0700, Warner Losh wrote: > We hope to have it finished in time for 13.0. I also feel that it should be more a "requirement". I don't see the rush in getting 13.0 out the door. There is a lot to get working (especially in ports-land). mcl

Re: Is pkg site forbidden by brower?

On Sun, Sep 06, 2020 at 03:05:49PM -0400, Yoshihiro Ota wrote: > Do you own pkg sites? Only portmgr@ does that. So this matter can only be resolved by a discussion between portmgr@ and clusteradm@. mcl ___ freebsd-current@freebsd.org mailing list

Re: Plans for git (was: Please check the current beta git conversions)

On Thu, Sep 03, 2020 at 11:40:17AM -0700, Rodney W. Grimes wrote: > To the contrary 5 years ago the project on @developers basically > ran off one of the committers over the very idea of using git > for the project. It was shortly after I returned, so I find it > very ironic that now its all

Re: Plans for git (was: Please check the current beta git conversions)

On Wed, Sep 02, 2020 at 08:01:17AM +0200, Kurt Jaeger wrote: > A short intro on git for svn users: > https://hackmd.io/ML5TSl8mQ5-27B5eqDf7YA?view For people like me that will not click on random URLs ... ... just feed "svn to git cheat-sheet" to your favorite search engine. Disclaimer: my

Re: Please check the current beta git conversions

On Wed, Sep 02, 2020 at 08:30:28AM +, Thomas Mueller wrote: > NetBSD plans to switch from cvs to Mercurial. So ... from square wheels, to triangular ones??? mcl ___ freebsd-current@freebsd.org mailing list

Re: the state of amd64 ports on -CURRENT as of 20200827

I forgot to include the following statistic: repojail% grep duplicate_symbol regresslogs.out.wanted | wc -l 613 mcl ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any

the state of amd64 ports on -CURRENT as of 20200827

The latest build of amd64-CURRENT ports has just completed: http://beefy18.nyi.freebsd.org/build.html?mastername=head-amd64-default=p546132_s364744 The number of build failures is now 740. This is an slight drop from the initial post-clang11 commit of 830. This is due to diligent work by a

Re: Current panics on connecting disks to a LSI-3108 controller

On Wed, Jul 15, 2020 at 11:56:43AM +0200, Willem Jan Withagen wrote: > A bit of a pain, since pkg does not do it because ... > you need to manually fetch the tar from Broadcom first. Finally: > [pkg] also does not tell you why Just ask it: portsjail% cd sysutils/storcli portsjail% make

Re: lock order reversal and poudriere

On Sun, May 03, 2020 at 10:04:04AM -0600, Ian Lepore wrote: > That LOR site hasn't been updated in years. Many many years. If someone wants to help me set up a page on the wiki, let me know. (I have too much on my plate to do it myself.) mcl ___

Re: After update to r357104 build of poudriere jail fails with 'out of swap space'

On Sat, Jan 25, 2020 at 03:59:06PM -0800, Cy Schubert wrote: > A rule of thumb would probably be, have ~ 2 GB RAM for every core or > thread when doing large parallel builds. This is a rule of thumb that I have used for quite some time. Perhaps less is necessary for certain tasks, but if you

Re: AMD Secure Encrypted Virtualization - FreeBSD Status?

On Sat, Oct 05, 2019 at 01:09:50PM +0300, Greg V wrote: > please keep in mind that the wiki is, as usual, very outdated. I'd be happy to give assistance/advice to get the page updated. mcl ___ freebsd-current@freebsd.org mailing list

Re: sys/modules/sdio broken in .svn_revision 348842 'opt_cam.h' not found

On Mon, Jun 17, 2019 at 11:41:03AM +0200, Julian H. Stacey wrote: > svn_revision 348842 [ ...] > /usr/src/sys/modules/sdio/../../dev/sdio/sdiob.c:68:10: fatal error: > 'opt_cam.h' file not found > #include "opt_cam.h" > ^~~ > 1 error generated. This is extremely unlikely

Re: What is evdev and autoloading?

On Tue, Feb 19, 2019 at 06:25:32AM -0800, Rodney W. Grimes wrote: > We are certainly driving users away by our operation model If you want to help take up more support duties -- especially for aging hardware -- I doubt anyone would stop you. There is plenty of work to take up; just check

Re: What is evdev and autoloading?

On Mon, Feb 18, 2019 at 08:50:27AM -0800, Rodney W. Grimes wrote: > I think one serious problem here is the summary dismissal of things > simply on the "5 year old" basis. IIUC the graphics changes are being forced upon FreeBSD by external projects (mainly Linux-based) that are making huge

Re: r343843 /usr/ports/ make install error: unable to create target: 'No available targets are compatible with this triple.'

On Fri, Feb 08, 2019 at 12:18:33PM +, Graham Perrin wrote: > I still wonder whether these problems arose, somehow, from: > > 235215 – Bump LLVM_DEFAULT to 80 > AFAIK that's still being tested (not committed yet). mcl

Re: drm / drm2 removal in 12

On Sat, Aug 25, 2018 at 07:22:06PM -0700, Randy Bush wrote: > plonk Indeed. I encourage everyone else to do the same. I'm far too old for proof-by-repetition. mcl ___ freebsd-current@freebsd.org mailing list

Re: drm / drm2 removal in 12

On Sat, Aug 25, 2018 at 07:07:24AM +0800, blubee blubeeme wrote: > Are these guys insane and please avoid the nonsense about you're doing this > in your spare time. Let us know how whatever OS you wind up using instead works for you. I suggest you look for one that will put up with your constant

Re: how to make ports not install xorg or dependencies

On Tue, Jul 31, 2018 at 01:13:31PM +0200, Miroslav Lachman wrote: > As Guido Falsi already said it is not guaranteed that you will not > have ports with some X libs, because some ports does not have option > to disable X11 dependencies. IMHO those ports have bugs. mcl

Re: [PATCH] Recent libm additions

On Sun, Jul 15, 2018 at 01:09:41PM -0600, Warner Losh wrote: > I'm not saying that he has a lock. I'm saying he's are domain expert > and many mistakes can be avoided by talking to him. fwiw, substantially all the work done since at least 2013 is from kargl. (I am eliding the licensing, Makefile,

Re: swapping is completely broken in -CURRENT r334649?

On Fri, Jun 15, 2018 at 11:14:40AM +0200, Mikaël Urankar wrote: > Last time I tried (2 weeks ago) qemu-ppc64-static was broken, not sure the > situation has evolved since that. I've been told by more than one person that it works, but the 2? 3? times I've tried it it just hung. I have real

Re: PR backlog (was: [RFC] Deprecation and removal of the drm2 driver)

On Thu, May 31, 2018 at 09:04:25PM -0700, K. Macy wrote: > This is where culling older bug reports comes in. Well, even with doing that, the sheer number really doesn't help the S/N that much. It may make someone a bit neurotic like me feel a bit better, but that's all. > However, when I've

Re: PR backlog (was: [RFC] Deprecation and removal of the drm2 driver)

On Thu, May 31, 2018 at 10:25:10PM -0500, Matthew D. Fuller wrote: > because the incentives are rigged. A bad outside contribution brought > into ports more often yields "hey, you should have noticed" to the > committer and more opprobrium back to the submitter. I believe you're missing two

Re: PR backlog (was: [RFC] Deprecation and removal of the drm2 driver)

Straying off-topic from the Subject line ... On Thu, May 31, 2018 at 11:34:18AM -0400, Joe Maloney wrote: > Technically since I was using PC-BSD, and was a committer for that > project I had no real dire need to reach out to FreeBSD about the > [wireless driver issue]. I was simply trying to

Re: hwpmc - wither ppro and p4

On Thu, May 31, 2018 at 12:58:23PM -0700, Steve Kargl wrote: > On Thu, May 31, 2018 at 11:08:18AM -0700, Matthew Macy wrote: > > > > Based on the i386 discussion I recognize that there's a great deal of > > sentimental attachment to older hardware. However, there's very few > >

Re: [RFC] Deprecation and removal of the drm2 driver

On Fri, May 18, 2018 at 04:19:21PM -0400, Daniel Eischen wrote: > I can easily imagine an embedded x86 kiosk type appliance. We need to evaluate the tradeoff of "what we can imagine someone will do with FreeBSD" vs. "what are people using with FreeBSD right now." mcl

Re: Clang-6 and GNUisms.

The problem is even worse on armv6/armv7/aarch64, and much worse on powerpc64/sparc64, which still have gcc in base. I have not been saving up the emails where ports committers have been fixing various failure modes. I hesitate to start making harmless- seeming patches myself for fear of my

Re: valloric YCM [header definitions]

On Wed, Dec 06, 2017 at 02:18:29AM +0800, blubee blubeeme wrote: > I'm looking for where the u_int, u_long headers are defined? Although it seems to be out-of-date, for something fundamental like this you should be able to use the FXR instance: http://fxr.watson.org/fxr/search mcl

Re: orangepi [was: what happened to src/sys/boot?]

On Sun, Dec 03, 2017 at 09:33:09PM +0100, Milan Obuch wrote: > Please see thread on freebsd-arm mailing list starting with my message > titled 'Allwinner H3/H2+ dts question - regression?' Ah, ok. My brain did not associate "H3/H2+" with "Orange Pi" so I simply skipped it. In any case I can now

orangepi [was: what happened to src/sys/boot?]

On Sun, Dec 03, 2017 at 08:55:20PM +0200, Daniel Braniss wrote: > ok, the image created now boots on both orangepi-one and nanopi-neo, > but without ethernet! So w/rt orangepi-one testing I think I'm now at parity with your build -- with whatever bits I had a week ago. e.g. I also do not detect

ports recently marked broken on -current

So during my pass over recent powerpc64 package errorlogs, I found a few ports that were actually broken across all archs on -current, and made those commits. I may not have enough cycles to investigate all these down by myself, so I'm asking for help. Does anyone recognize any of these failure

Re: lang/gcc6-aux for head beyond __nonnull related issues: vm_ooffset_t and vm_pindex_t related changes (and more)

On Fri, Apr 14, 2017 at 08:27:29PM -0700, Mark Millard wrote: > I've seen material quoted from a exp-run that reported > that about 54(?) ports were then blocked by lang/gcc6-aux > not building. Although the first is an older run (the last complete run IIUC), there were 50 and 51 respectively as

Re: How many versions of clang/llvm are currently required to maintain a system

On Mon, Mar 06, 2017 at 03:00:23PM +, r...@gid.co.uk wrote: > Let me rephrase that: the link http://purelang.bitbucket.org/ > quoted on https://wiki.freebsd.org/ObsoleteLLVMVersions doesn’t work, That's the URL in lang/pure/Makefile. > should be https://bitbucket.org/purelang/ Hmm. I

Re: How many versions of clang/llvm are currently required to maintain a system

Please see https://wiki.freebsd.org/ObsoleteLLVMVersions . mcl ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HEADSUP: after r313194 on freebsd-current, lang/gcc ports require a rebuild

On Tue, Feb 28, 2017 at 11:24:27PM +0100, Ed Schouten wrote: > 2017-02-28 21:00 GMT+01:00 Konstantin Belousov : > > Ideally, ports should stop shipping mangled system includes, or even better, > > gcc stop doing fixincludes. > > Amen. Please let me know the magic wand you

Re: xpt related hang on sparc64

On Fri, Jan 13, 2017 at 11:23:13PM -0700, Alan Somers wrote: > That error message can mean many different things. You need to boot > in verbose mode to get a better idea. As a test I created a netbootable image from -current the other day. All I had available to test was an X1 which booted fine.

Re: [RFC] remove GNU rcs from FreeBSD 12

On Sun, Nov 06, 2016 at 12:09:30PM +0100, Eivind Nicolay Evensen wrote: > I also thought that perl was a good example of another piece of software > that once was provided and no longer is. Yes, that's true, but somewhat different. perl was removed because keeping it became incompatible with the

Re: [RFC] remove GNU rcs from FreeBSD 12

On Thu, Nov 03, 2016 at 10:17:23AM +0800, Julian Elischer wrote: > why should we remove it? IIUC the plan for several years has been to remove all GPLed software from base. But in any case the conversation is moot. It was removed from head on 20161015 by bapt:

Re: FreeBSD-11.0-BETA1-amd64-disc1.iso is too big for my 700MB CD-r

On Tue, Jul 12, 2016 at 04:09:10PM +0930, Shane Ambler wrote: > +1 on dropping CD images. I have 24U of things that don't have DVD players, including some tier-2 machines for which no upgrade is available. mcl ___ freebsd-current@freebsd.org mailing

Re: [CFT] packaging the base system with pkg(8)

On Wed, Apr 20, 2016 at 05:37:00AM +0300, dan_partelly wrote: > Year after year you hear about new GsoC projects, then nothing. I find > it hard to believe that none of those actually produced any useful code. The goal of GSoC is to introduce new people to FreeBSD more than it is to produce

Re: Time to be real

Thank you for your troll. For your convenience, we will do our best not to reply to you any further, to waste either your time, or valuable electrons. mcl ___ freebsd-current@freebsd.org mailing list

Re: HP 2B19WM PCI-E SD Reader

On Wed, Feb 04, 2015 at 08:21:44AM -0800, Adrian Chadd wrote: ... god, people go through a lot of work to not have to write a wifi driver. :) we're just concerned about you... ...r sanity. mcl ___ freebsd-current@freebsd.org mailing list

Re: Build failed in Jenkins: Build-UFS-image #599

On Sat, Dec 20, 2014 at 01:43:50PM -0800, Garrett Cooper wrote: One way to deal with this issue is to svn up a source tree, then rsync rsync? ITYM zfs clone :-) mcl ___ freebsd-current@freebsd.org mailing list

Re: OpenSSL vs. LibreSSL (OpenBSD)

On Thu, Apr 24, 2014 at 03:05:40PM -0700, Justin Hibbits wrote: We need to discuss the use of comic sans font across our web properties first. -Alfred You, sir, win 2 internets. - Justin seconded. ___ freebsd-current@freebsd.org mailing

Re: login.conf -- UTF-8

On Wed, Apr 02, 2014 at 03:56:35PM -0700, Sean Bruno wrote: I have been informed by folks that this change I suggest would help in the case of ports having to declare UTF-8 support explicitly or something. Clearly ports that need to do this are broken -- but this very much an edge-case of

Re: vt text cursor invisible in reverse video

On Wed, Apr 02, 2014 at 01:01:11PM +0200, Claude Buisson wrote: After 19 years of FreeBSD use and not being part of any chapel/coterie/mafia I don't keep much illusion about the outcome.. I'm sorry that you feel that way. Rest assured that a large number of those of us that work on FreeBSD do

Re: PR for pf in kernel

On Sun, Mar 02, 2014 at 12:39:07AM +0200, Michael Pounov wrote: Hi, I wrote this mail because on web page Submit Bug-report missing severity for PR and priority options. Those two fields have become meaningless due to everyone overusing them. Changing them will not have much effect. mcl

Re: Import of DragonFly Mail Agent

On Mon, Feb 24, 2014 at 09:40:26AM -0600, Bryan Drewery wrote: IMHO base should be the very minimalistic needs to get a server online, and should be secure and simple by default. ... Anything not meeting the bare-bones criteria can be installed with 'pkg install' or ports. +1 (OTOH I am not

Re: GCC withdraw

On Fri, Aug 30, 2013 at 10:41:18AM -0400, John Baldwin wrote: So my take away from this is that you have no plans to support any platform that doesn't support clang as you just expect ia64 and sparc64 to die and not be present in 11.0. That may be the best path, but I've certainly not seen

Re: [HEADSUP] No more pkg_install on HEAD by default

fwiw, nanobsd also is still on pkg_*, but I intend to come up with patches for that if someone else has not already done so. mcl ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send

Re: gccmakedep fix - 20130619

On Wed, Jun 19, 2013 at 01:51:42AM +0200, Oliver Pinter wrote: 3) Is not it better to submit via PR (GNATS) rather than a mailing list? That's what PRs are for... Mail are faster than PR-s. If we all go down that route, it means less and less people will try to read all the traffic on

Re: CLANG and -fstack-protector

On Thu, Feb 07, 2013 at 11:52:42PM +0100, Jeremie Le Hen wrote: You can do this, it will work for most of the ports but some ports do not honor CFLAGS. Ports that don't honor CFLAGS are broken ports. Having said that, the last time I ran a script that looked for them (and other things like

Re: Cross-architecture package installs

On Tue, Feb 05, 2013 at 10:34:18PM -0800, Tim Kientzle wrote: I'm working on tools to build ARM system images. Usually, these tools run on x86, which creates a problem for packages. fwiw, before the intrusion 3 months ago, I had been able to build native ARM packages with a loaned system.

Re: svn commit: r244865 - in head: . lib lib/libdisk share/mk

On Sun, Dec 30, 2012 at 06:57:45PM -0800, Garrett Cooper wrote: This is what exp- runs are for (portmgr can help with this). OTOH -exp runs are currently off the air. mcl ___ freebsd-current@freebsd.org mailing list

Re: -Current built with clang as default + ports

This is all good advice. Note, however: On Wed, Nov 14, 2012 at 10:59:49AM +0100, Dimitry Andric wrote: Of special interest are the results from the build cluster, where you can get a quick overview of which ports don't build, and how many other ports depend on them. Unfortunately those web

Re: November 5th is Clang-Day

On Thu, Nov 01, 2012 at 10:31:26PM -0700, Garrett Cooper wrote: On Thu, Nov 1, 2012 at 10:24 PM, Jan Beich jbe...@tormail.org wrote: emulators/wine doesn't work with lib32 built by clang, probably due to wine bugs. All of these items should be catalogued in a common place, like the wiki.

Re: [HEADSUP] FYI: patch to ports that do not build with clang has been committed

On Wed, Oct 10, 2012 at 05:11:07PM +0200, Roman Divacky wrote: Can we arrange exp builds with FORCE_BASE_CC_FOR_TESTING=clang that will report all ports with USE_GCC=* but build with clang? Sure. That was kind of the intention. mcl ___

[HEADSUP] FYI: patch to ports that do not build with clang has been committed

The commit mail hasn't gone through yet, so I guess I need to post this first and reference the commit mail later. Sometime in the near future, the default CC on -current will be switched to clang. The patch I have committed is a workaround -- an interim measure -- to get ready for this

Re: Clang as default compiler November 4th

On Thu, Sep 13, 2012 at 08:21:31AM +0200, Pietro Cerutti wrote: On 2012-Sep-11, 23:29, Doug Barton wrote: What we need to do is what I and others have been asking to do for years. We need to designate a modern version of gcc (no less than 4.6) as the official default ports compiler, and

Re: Clang as default compiler November 4th

On Tue, Sep 11, 2012 at 11:27:50AM +0200, Lars Engels wrote: At the moment the ports maintainers don't give much about if their ports build with CLANG or not because they're not forced to. I think this is a mis-representation. Adding the requirement your ports must work on clang is adding an

Re: Clang as default compiler November 4th

On Wed, Sep 12, 2012 at 03:03:43PM +0200, Lars Engels wrote: two of the ports I maintain don't build with CLANG, yet. I just checked that on the wiki page [1]. To repeat myself, the ports I've listed on that page are the big problems. People need to look at the errorlogs URLs up at the top to

Re: Clang as default compiler November 4th

On Tue, Sep 11, 2012 at 10:07:04AM +0100, David Chisnall wrote: There is some logic in the clang driver already for knowing when it is invoked as gcc. I'd be quite tempted to make gcc a symlink to clang and make clang default to gnu89 when invoked in that way. And how then does a port say I

Re: make: don't know how to make add-plist-buildinfo. Stop

It was a temporary disruption that I caused. It should be fixed now. mcl ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Why Are You NOT Using FreeBSD?

On Tue, Jun 05, 2012 at 12:18:33PM +0700, Erich wrote: I did not know this. Do you have a link for this? I never read about it. The EOL announcements have them. I don't think the release announcements do, however. mcl ___ freebsd-current@freebsd.org

Re: Why Are You NOT Using FreeBSD?

On Tue, Jun 05, 2012 at 01:00:45PM +0700, Erich wrote: All of these, with the exception of HEAD (which is always a valid tag), only apply to the src/ tree. The ports/, doc/, and www/ trees are not branched. If you create a branch, you must create a tag for that branch. However, you can create

Re: Why Are You NOT Using FreeBSD?

On Tue, Jun 05, 2012 at 03:23:01PM +0700, Erich wrote: But is this true for apache only or for the whole ports tree? Entire tree. mcl ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To

Re: Why Are You NOT Using FreeBSD?

One doesn't have to live at the bleeding edge with ports if one doesn't want to even when compiling. One can live a day, a week, a month behind the bleeding edge and allow other to hit problems and report them. To be pedantic, there's a lot of difference between reporting problems, and

Re: Use of C99 extra long double math functions after r236148

Perhaps a more general name might be appropriate so as to include fixed-point problems? math-libs@? numerics@? I'm sure someone will come up with a better name. mcl ___ freebsd-current@freebsd.org mailing list

Re: UFS+J panics on HEAD

On Wed, May 23, 2012 at 10:58:48PM +0100, Steven Hartland wrote: While it might be a shame to see FFS go by the wayside are there any big reasons why you would rather stick with FFS instead of moving to ZFS with all the benefits that brings? - ZFS eats bytes for breakfast. It is completely

Re: FYI clang fails to build ports argp-standalone

a) the best place is freebsd-ports@ b) we do periodic builds of ports with clang as default but in general clang is not ready to be the default compiler yet. Please see http://wiki.freebsd.org/PortsAndClang . mcl ___ freebsd-current@freebsd.org

Re: HEADSUP: /etc/malloc.conf format change

On Wed, Apr 25, 2012 at 09:37:36PM -0700, Tim Kientzle wrote: The Ports maintainers will run experimental ports builds on the port build clusters to help verify potentially disruptive changes like this before they are committed. Well, actually, portmgr@. Send a PR with [exp-run] in the

Re: /sys/conf/kmod.mk, line 111: Malformed conditional (${MK_CLANG_IS_CC}

On Tue, Apr 17, 2012 at 11:49:44AM +0200, Dimitry Andric wrote: It would hopefully error out. If you look in /usr/share/mk/bsd.kmod.mk, you will see this at the bottom: .if !defined(SYSDIR) || !exists(${SYSDIR}/kern/) || \ !exists(${SYSDIR}/conf/kmod.mk) .error Unable to locate

Re: Packages for Current ( 10.0 )

On Fri, Feb 17, 2012 at 12:04:45AM -0500, Mehmet Erol Sanliturk wrote: I would be very happy I can contribute anything to development of FreeBSD . We are always happy to have help :-) If there appears an agenda of testing problems and explicit instructions how to apply tests , me and other

Re: Packages for Current ( 10.0 )

The portmgr team has not yet started regular package builds for -current. We are working on re-allocating some resources to be able to do so. Note, however, that with -current being an early branch of a new major version, that the src that we are building against is changing rapidly. My personal

Re: stable/9 still looking for packages at 9-current

On 9. Jan 2012, at 01:04 , Arnaud Lacombe wrote: So you are saying that FreeBSD is currently providing on ftp://ftp.freebsd.org/pub images tagged as being 9.0 RELEASE (with checksum provided), in a `releases' directory, which are not actually release images per-se ? Excellent! You've shown

Re: stable/9 still looking for packages at 9-current

On 9 January 2012 18:16, Arnaud Lacombe lacom...@gmail.com wrote: Excellent!  You've shown the ability to understand flat, declarative, sentences that have no qualifying phrases. FWIW, this was more a sarcastic sentence I am being sarcastic because I am frustrated. I am frustrated because I

Re: stable/9 still looking for packages at 9-current

On Sun, Jan 08, 2012 at 07:26:47PM -0500, Eitan Adler wrote: On Sun, Jan 8, 2012 at 7:22 PM, Arnaud Lacombe lacom...@gmail.com wrote: Hi, On Thu, Jan 5, 2012 at 5:12 PM, Peter fb...@peterk.org wrote: Hello,  Installed 9-RELEASE amd64, [...] Has 9.0 been released ? 9.0 will, and only

Re: Benchmark (Phoronix): FreeBSD 9.0-RC2 vs. Oracle Linux 6.1 Server

On Sat, Dec 24, 2011 at 04:04:31PM +0100, O. Hartmann wrote: There maybe serious reasons having the Linuxulator, i do not know. But if not, why spending rare developer resources on that? This is a classical misunderstanding of the FreeBSD development model. There is no staff standing around

Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool

On Thu, Dec 29, 2011 at 10:23:58AM -0800, Pedro Giffuni wrote: How am I supposed to install prebuilt packages (and the myriad of dependencies) from now on? I strongly recommend using portmaster. The manpage is very dense but to start with, use something like the following (I'm just picking one

FreeBSD funding [was: Re: Benchmark (Phoronix): FreeBSD 9.0-RC2 vs. Oracle Linux 6.1] Server

I have slightly reordered your email in my reply, in order to put the most important item last. On Fri, Dec 23, 2011 at 12:01:33PM +0100, O. Hartmann wrote: I'm still with the system, although I desperately need scientific grade compilers or GPGPU support. Your use-case, while valid, is

status of ports and clang

I have recently been able to get the new build cluster on pointyhat-west set up to run full builds of ports with clang on amd64-9. I have documented the latest results on the wiki: http://wiki.freebsd.org/PortsAndClang If you are interested in working on ports being built via clang, this is

Re: amd64 packages

On Mon, Dec 12, 2011 at 10:46:08PM +0400, siur wrote: why there is still no packages for 10-current? Did I miss something? We're trying to debug multiple package building problems, and currently using i386-10 for that. Until we get farther along with that process, we aren't doing amd64-10 yet.

Re: Problem with pkg_add

On Fri, Dec 09, 2011 at 09:16:13AM -0500, Derek Tattersall wrote: After installing 9.0-RC2 or RC3, pkg_add -r fails in trying to access ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/package-9-current as the terminal directory is acually packages-9-stable. It is a one line change in the source

Re: 9.0 beta2 the new bsdinstaller

Wiki, gnats, scrap of paper on someones desk, etc? I've put a link to the few existing PRs in GNATS onto the wiki page. mcl ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any

Re: cvsup broken on amd64?

Usually rather quite later than sooner. A perfect opportunity for src committers to dive in and make a difference :-) mcl ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any

Re: http://www.freebsd.org/marketing/os-comparison.html

On Tue, Aug 30, 2011 at 09:45:09PM +0800, Paul Ambrose wrote: 3 There is a missing feature list about DTrace, but no schedule list about when to fix it. We just need someone who wants to spend a lot of time working on it. Without that, there is no point in putting up a schedule. mcl

Re: New installation script

On Sat, Aug 06, 2011 at 01:18:02PM -0400, Garrett Wollman wrote: I initially chose traditional Unix workstation, which was unusable. (Never did find the control or escape key, which made vi particularly difficult to use.) It should probably be labeled old-fart Unix user which would have

Re: [head tinderbox] failure on powerpc/powerpc

On Mon, Aug 08, 2011 at 06:53:40PM -0400, Super Bisquit wrote: Why does Tinderbox need cross tools? Is the build not native? If so, then the rationale would be to build on the architecture and not use cross compilation. - There are no powerpc machines currently online at *.FreeBSD.org. -

Re: gcc-4.5 and 4.6 needs to be recompiled due to /usr/src/UPDATE: 20110608:

Things that change the way the base system behaves w/rt ports need version bumps. mcl ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to

Re: Building FreeBSD 9.0-CUR/amd64 with CLANG fails

On Wed, May 04, 2011 at 09:17:23AM +0200, O. Hartmann wrote: I guess the ports-tree isn't mature for clang. That's correct. mcl ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send

Re: Request to mailing list freebsd-security rejected

On Mon, Mar 21, 2011 at 08:17:23AM -0400, Etienne Robillard wrote: Google cognitive dissonance for more info... Google plonk for more info. mcl ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To

Re: utmpx

On Fri, Nov 05, 2010 at 01:09:06PM +0100, Ed Schouten wrote: It should be noted that that list is a bit pessimistic, since various ports have been fixed in the mean time. Updates welcomed :-) mcl ___ freebsd-current@freebsd.org mailing list

Re: ZFS will gone,FreeBSD will import btrfs?

On Tue, Aug 17, 2010 at 12:21:07PM +0800, lhmwzy wrote: opensolaris is gone It appears there will be a fork, but that's not particularly crucial to FreeBSD. ZFS also gone. We're not going to drop ZFS because Oracle's plans are unclear. It remains to be seen how much other community support

  1   2   >