On Fri, Oct 16, 2020 at 04:36:05PM +0100, Jessica Clarke wrote:
> Given GCC 10 is the latest GCC release so this is already a bit
> outdated (though perhaps GCC 9 is still the recommended version for
> FreeBSD now?)
In possibly unrelated news, there are still about 25 ports which do
not build on
On Fri, Sep 04, 2020 at 02:15:04PM -0400, Andrew Gallatin wrote:
> and I also anticipate it will cause problems with MFCs
And existing PRs and DRs.
mcl
___
svn-src-all@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-all
To
On Sat, Jun 06, 2020 at 06:21:20AM +, Warner Losh wrote:
> Document all the sysctl values for the nda devices.
Thank you.
mcl
___
svn-src-all@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any
Defining it to MAGIC_UNROUTED_IP_ADDRESS or something would have obviated
our questions :-)
mcl
___
svn-src-all@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to
On Mon, Apr 13, 2020 at 08:26:11AM +, Alexander V. Chernikov wrote:
> Remove tcp_rtlookup6() function signature.
>The function itself was removed in r122922 16 years ago.
I nominate this for "most amusing commit of the month" :-)
Who knows what other cobwebs lurk in our src tree ...
On Thu, Apr 02, 2020 at 10:02:51AM +0200, Stefan Eßer wrote:
> You are aware that this commit message came from and
> only applied to some parallel universe ...
If it's better than the one we are currently in: Beam Me Up
Scotty.
mcl
___
On Wed, Apr 01, 2020 at 05:53:14AM +, Glen Barber wrote:
> Update head to 14.0-CURRENT in order to prevent having
> a 13.0-RELEASE.
You forgot to update the Porter's Handbook.
mcl
___
svn-src-all@freebsd.org mailing list
On Tue, Jan 14, 2020 at 10:10:46PM -0800, Gleb Smirnoff wrote:
> void
> epoch_call(epoch_t epoch, epoch_context_t ctx,
> void (*callback)(epoch_context_t));
>
> void
> epoch_call(epoch_t epoch, epoch_context_t ctx,
> void (*callback)(epoch_context_t));
I'm
On Sun, Jan 05, 2020 at 12:17:21PM -0600, Warner Losh wrote:
> I'd expect that once the issues [on powerpc] are resolved with clang,
> or that platform migrates to an external toolchain
AFAIK there never was a fallback plan to migrate powerpc to an external
toolchain; powerpc64-head (at least)
On Sun, Jan 05, 2020 at 01:11:30PM -0600, Warner Losh wrote:
> This total lack of work on sparc64 may result in an accelerated
> timeline for its removal.
IMHO it's time to just let it go.
mcl
___
svn-src-all@freebsd.org mailing list
On Sun, Jan 05, 2020 at 02:47:56AM +, Ed Maste wrote:
> Do not build GCC 4.2.1 by default for any CPU architecture
And there was much rejoicing :-)
(but plz not to MFC tnx)
mcl
___
svn-src-all@freebsd.org mailing list
On Sat, Jan 04, 2020 at 03:15:34AM +, Jeff Roberson wrote:
> Use a separate lock for the zone and keg.
Out of curiosity, will there be measurable real-world speedups from
this an similar work, or will this mostly apply to edge cases, or ... ?
mcl
On Wed, Oct 16, 2019 at 09:10:34PM -0700, Cy Schubert wrote:
> I'm replying using my phone (K-9 mail), trimming is so time consuming
> and error prone (one wrong finger movement and you start over again,
> especially while riding the bus to work -- one bump in the road and
> I'm guaranteed
On Fri, Mar 29, 2019 at 09:49:03AM +, Alexey Dokuchaev wrote:
> P.S. Boot tag of a healthy human is "Copyright (c) 1992-2018 The FreeBSD
> Project".
ITYM 2019.
mcl
___
svn-src-all@freebsd.org mailing list
On Sun, Sep 01, 2019 at 12:32:34PM -0700, Cy Schubert wrote:
> This probably requires a __FreeBSD_version bump.
Since it affects FreeBSD ports, yes, please.
mcl
___
svn-src-all@freebsd.org mailing list
On Fri, Mar 29, 2019 at 09:49:03AM +, Alexey Dokuchaev wrote:
> P.S. Boot tag of a healthy human is "Copyright (c) 1992-2018 The FreeBSD
> Project".
ITYM 2019.
mcl
___
svn-src-all@freebsd.org mailing list
On Tue, Feb 12, 2019 at 08:31:52AM -0800, Rodney W. Grimes wrote:
> If all of our process was better documented and laid down
> we would have less of this type of discussion on a much less
> frequent basis.
And much more discussion about how the process is over-specified,
onerous, doesn't take
On Mon, Nov 12, 2018 at 06:00:19AM -0800, Rodney W. Grimes wrote:
> it is not the change that I am ranting about, but the fact that the
> process is broken.
If the "process" must be followed absolutely, then FreeBSD has already
failed. This was a text file, advisory to users only; no executable
On Wed, Nov 07, 2018 at 08:59:24AM -0800, Rodney W. Grimes wrote:
> freebsd-geom is also probably a pretty short list.
IMHO it's one of our mailing lists that became obsolete once the initial
work was done. The bugbusters still assign to these lists, however.
ISTM that some of these assignee
On Mon, Jul 16, 2018 at 06:53:28PM +, Pedro F. Giffuni wrote:
> Update libstdc++ configuration.
Will FreeBSD version be incremented for this?
mcl
___
svn-src-all@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-all
To
On Tue, Jul 03, 2018 at 10:51:59AM +, Ruslan Bukin wrote:
> Add GCC 8.1.0 compiler warning flags.
I'm sorry, but that is a "what" not a "why".
As someone who tries to fix ports on tier-2, I really need to
understand the "why".
mcl
___
On Thu, Jun 21, 2018 at 12:33:26PM -0600, Ian Lepore wrote:
> Hiding work in patchsets and reviews and alternate branches and other
> shadowy places because it's not perfect
I do not consider bugzilla and phabricator to be "shadowy places";
therefore, I reject this argument.
Although I don't
On Fri, May 25, 2018 at 09:27:43PM -0700, Matthew Macy wrote:
> So we should have added an Ultra II off of ebay to our test matrix?
You've made your point. Next.
mcl
___
svn-src-all@freebsd.org mailing list
On Thu, May 24, 2018 at 12:22:37PM -0700, Matthew Macy wrote:
> All you need to know about sparc64 vitality is that HEAD didn't boot
> for 3 months until last week.
All you need to know is that -11 works fine, but, after so much drama
from various places, I haven't even bothered upgrading any of
On Thu, May 24, 2018 at 11:18:38AM -0500, Pedro Giffuni wrote:
> And while I like to see sparc64s still kicking around, they are stopping us
> from getting rid of GCC once and for all.
False. mips and powerpc still build with gcc.
I understand there will be an effort at BSDCan to work out the
On Wed, May 23, 2018 at 09:56:00AM -0700, Matthew Macy wrote:
> Thanks updated for 1200064. Someone(tm) needs to do 1200063.
done.
mcl
___
svn-src-all@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send
On Wed, May 23, 2018 at 11:14:59AM -0700, Rodney W. Grimes wrote:
> And some of us buy 2 year old hardware because it is cheap,
Some of us don't have that kind of budget anymore.
mcl
___
svn-src-all@freebsd.org mailing list
On Wed, May 23, 2018 at 12:05:24PM -0600, Ian Lepore wrote:
> Well, they're supposed to be.
>From my own experience, they are often not.
> I think it would be more likely to happen if you didn't have to get
> intimate with xml code to add a simple note to a file.
It's cut-and-paste.
Or, it's
On Wed, May 23, 2018 at 10:41:17AM -0700, Gleb Smirnoff wrote:
> If end of sales and support is enough to remove 10g driver from the kernel,
> can we please delete all 10Mbit, 100Mbit 10+ year old drivers from the kernel?
Depends on how many existing users we want to screw over. Not everyone
On Tue, Apr 03, 2018 at 04:32:11AM +, Warner Losh wrote:
> All depends on which ports are broken... would be nice to have a list...
It's only a matter of a few hours' work.
mcl
___
svn-src-all@freebsd.org mailing list
So, the takeaway is, this change stays, and stable/11 users that build
their own ports are on their own?
Whatever happened to POLA?
mcl
___
svn-src-all@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send
On Sat, Mar 31, 2018 at 06:44:01PM +0200, Dimitry Andric wrote:
> I am very disappointed that it apparently takes more than 3 months
> (half the lifecycle of a complete upstream llvm release!) to fix
> broken ports. Don't maintainers read their email, or care about
> their ports?
Number of
fwiw the effect of the introduction of clang6 to armv6 on head on the
cluster, before/after:
103 failures_armv6_p457578_s327371.txt
514 failures_armv6_p460069_s328457.txt
I expect stable/11 to follow these statistics.
mcl
___
On Sat, Mar 31, 2018 at 02:42:01PM +0200, Dimitry Andric wrote:
> It's been almost 3 months now since clang 6 landed in head, and if
> those ports require USE_CXXSTD=gnu++98 to be fixed, why haven't those
> already been changed already?
Because it takes a lot of time and effort to do it?
This
This is addressed to developers in general, not just rgrimes, but he
made the comments, so ...
On Thu, Mar 29, 2018 at 09:33:44AM -0700, Rodney W. Grimes wrote:
> It seems that the Phabricator review system is somewhat dysfunctional
> in that actual review is only happening in some cases. Some
On Sat, Mar 10, 2018 at 08:27:43AM +, Alexey Dokuchaev wrote:
> one can update their machines and go back easily if things went south.
After wasting time, like I did most of Thursday.
mcl
___
svn-src-all@freebsd.org mailing list
On Mon, Mar 05, 2018 at 11:13:58AM -0500, Mark Johnston wrote:
> The growing divergence with stable/11 makes it rather painful to
> maintain a port, depending on libcasper, that aims to work on both 11
> and head.
Even an MFC won't help you, in the medium-term.
e.g. via
I can confirm that this fixes the build on sparc64.
mcl
___
svn-src-all@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
On Tue, May 23, 2017 at 05:39:50PM -0400, Allan Jude wrote:
> The project also includes fixing a number of other long-standing-
> because-of-ABI changes, like the max length of a mountpoint is now
> 1024 instead of some small value (60 or 80 or something it was before)
It was around 80. I hit
At this point is there anything that the gdb port does
not do, that the base version does? I know a lot of work
has gone into making it a strict superset.
mcl
___
svn-src-all@freebsd.org mailing list
On Sat, Apr 15, 2017 at 05:01:10PM -0700, Conrad Meyer wrote:
> Can you tone down the condescension, Rod? Being rude doesn't help you
> make your case.
I'm going to have to +1 this.
We're a huge community now. Comments that might be appropriate among a
handful of people aren't as appropriate
On Sun, Apr 16, 2017 at 10:35:59AM -0600, Ian Lepore wrote:
> (The most basic rule would be "notify me about every new change put
> up for review", which seems like it would be a real spam generator,
> but at least one person uses such a rule.)
I tried the latter once, as a test. I doubt many
On Tue, Feb 28, 2017 at 01:30:44PM -0800, Gleb Smirnoff wrote:
> How can I check the __FreeBSD_version in a port Makefile? My understanding
> is that there is no standard way for such thing.
There are hundreds of examples in port Makefiles. I suppose the PH will need
to be updated to include
On Thu, Feb 02, 2017 at 06:07:23PM +1100, Peter Jeremy wrote:
> It clearly states to users that their system is unsupported and
> explains how they can bypass the check if they know what they are
> doing.
It also prevents us from making a promise that we have no intention
of keeping (e.g.,
On Wed, Feb 01, 2017 at 08:09:50PM +0300, Slawa Olhovchenkov wrote:
> Also, I am think current ports don't build on 4.x.
I will personally guarantee, in writing, that current ports do not build
on 4.x, nor have they done so for years. I personally removed the legacy
cruft when 4.11 finally went
On Tue, Jan 31, 2017 at 04:36:04PM -0700, Warner Losh wrote:
> ISA-only attachments would be a good place to start. My quick glance
> shows this would be le(4), aha(4), cm(4), mse(4), and joy(4). There's
> maybe half a dozen EISA-only drivers in the tree that I was planning
> on retiring in 12,
On Thu, Dec 01, 2016 at 09:32:07AM -0700, Ian Lepore wrote:
> On Wed, 2016-11-30 at 19:07 -0800, Ngie Cooper wrote:
> > Really?? I wish you hadn't added me to this list.. I don't in any way
> > endorse the way that you went about dealing with this disagreement.
>
> Really? Well then feel free to
On Thu, Nov 24, 2016 at 03:39:35PM +, Alexey Dokuchaev wrote:
> It is good for the community and for FreeBSD.
Only if we wish to forever remain a closed, cliquish, group of developers.
mcl
___
svn-src-all@freebsd.org mailing list
I thought the src/MAINTAINERS mechanism was designed for exactly this.
mcl
___
svn-src-all@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
On Sat, Aug 20, 2016 at 07:51:55AM -0700, John Baldwin wrote:
> - aha (ISA)
> - bt (ISA / EISA / PCI)
If anyone complains, tell them I'll ship them cards.
If they consider that a threat ... so be it :-)
(I *am* in the middle of a big decluttering, you know. I can find
them ...)
mcl
On Tue, Jan 12, 2016 at 05:49:30PM +0100, Gary Jennejohn wrote:
> Maybe his name should be changed to melbel, which would eliminate
> the me/me@ kerfuffle.
Or just start using the convention 'self' in commits.
mcl
___
svn-src-all@freebsd.org mailing
On Fri, Oct 23, 2015 at 08:09:35AM -0700, Conrad Meyer wrote:
> What is __FreeBSD_version and why would it be bumped?
__FreeBSD_version was introduced in the following commit:
https://svnweb.freebsd.org/base/head/sys/sys/param.h?r1=34924=36260
where it has been ever since:
On Sun, Jun 21, 2015 at 09:35:58AM -0500, Pedro Giffuni wrote:
You have a point there: I tried to get the core team to at least
deprecate gcc = 2.8.1 and they didn't reach an agreement. :(
When was this?
mcl
___
svn-src-all@freebsd.org mailing list
On Wed, Jun 17, 2015 at 10:44:28PM +, Gleb Smirnoff wrote:
Log:
o Un-inline vm_pager_get_pages(), vm_pager_get_pages_async().
o Provide an extensive set of assertions for input array of pages.
o Remove now duplicate assertions from different pagers.
Out of curiosity, what is the
On Fri, Mar 27, 2015 at 01:00:14PM +0300, Slawa Olhovchenkov wrote:
Alpha 21064 support EISA.
Alpha is no longer supported in FreeBSD.
mcl
___
svn-src-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe,
On Sat, Mar 21, 2015 at 03:01:20PM +, Konstantin Belousov wrote:
Somewhat modernize the SysV shm code:
Interesting.
Is my understanding correct that postgres still uses shm? If so,
has someone benchmarked the speedup?
mcl
___
On Wed, Dec 31, 2014 at 09:25:51PM -0700, Warner Losh wrote:
This change is wrong. bsd.sys.mk was eliminated on purpose, dammit.
Aw, our first bikeshed of the year. Sniff. I may cry ...
Wait? The message is still dated 2014???
hg ...
oh wait, the *commit* is UTC.
I win
mcl
(in
On Sat, Dec 20, 2014 at 04:57:46AM +, Neel Natu wrote:
Various 8259 device model improvements:
While I am glad to see this particular commit ...
... I have to say that I am depressed seeing the string 8259 in 2014.
That chip was a hack in its time, which was a long time ago. (For those
On Wed, Dec 17, 2014 at 11:12:35AM -0800, Steve Kargl wrote:
I'm always afraid of statements like these, as they can be brought to
the table to prevent any changes from being made. The fact that
someone else (be it Android or openlibm) uses our code should not
limit us as a project to make
On Thu, Nov 27, 2014 at 08:12:13PM +, Ed Maste wrote:
Copy elftoolchain binutils replacements from vendor branch
sweet!
mcl
___
svn-src-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any
On Sun, Aug 24, 2014 at 02:44:14PM -0700, Peter Wemm wrote:
I suspect that there's a story here that needs to be told..
Pull the string! The story must be told!
mcl
___
svn-src-all@freebsd.org mailing list
On Tue, Jul 15, 2014 at 07:13:44PM -0700, dte...@freebsd.org wrote:
destroying all vestiges of that environment purely for the sake of
saying it's clean seems counter to the UNIX pathos.
I think you mean ethos here, but frankly I like it better this way.
mcl
On Fri, May 30, 2014 at 06:55:46AM -0500, Pedro Giffuni wrote:
I consider this a bug fix; I think ports should already be respecting
standards.
Hahahahahahaha
You haven't looked at much ports code, I see :-)
Should I consider a FreeBSD_version bump JIC?
Please.
mcl
On Thu, May 15, 2014 at 11:30:17AM +, Baptiste Daroussin wrote:
Log:
Add the missing coma
I thought a coma was what happened from reading mailing lists.
mcl
___
svn-src-all@freebsd.org mailing list
On Fri, Apr 25, 2014 at 03:00:45PM -0700, Adrian Chadd wrote:
I've found a bunch of BIOSes on recent hardware that seems to assume
GPTs == EFI booting, and just plain don't boot your system.
Suggestion? Put a list of these on the wiki so that other people know
not to get burned, too.
mcl
On Fri, Apr 11, 2014 at 02:18:38PM -0600, Warner Losh wrote:
So attacking that there was fallout is really out of line.
+1
___
svn-src-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to
On Fri, Mar 21, 2014 at 11:39:55AM -0700, Adrian Chadd wrote:
Which LORs? I actively chase down and squish net80211/ath LORs when
it's not too difficult (and I know of some rather-difficult ones I'm
still trying to solve.) But besides the handful of filesystem LORs
that are claimed to be fine,
On Tue, Jul 23, 2013 at 10:23:43AM +, David Chisnall wrote:
A surprising number of configure checks rely on this. It was broken by recent
cleanups to math.h.
Once you have the experiences with the ports tree that I have had, you
will no longer assume anything about how ports configure
On Sun, Dec 30, 2012 at 11:31:05AM +0100, Pawel Jakub Dawidek wrote:
I wonder how many 3rd-party kernel modules do we have in ports.
http://www.freebsd.org/ports/kld.html
mcl
___
svn-src-all@freebsd.org mailing list
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
___
svn-src-all@freebsd.org mailing list
The style in bsd.port.mk is not consistent. (I know, this is shocking
for something that's at r1.706.)
Here's what I recall seeing in it, that I found readable:
.if defined(USE_GL)
. if ${USE_GL:L} == yes
USE_GL= glu
. endif
. for _component in ${USE_GL}
. if
I had kind of hoped that before support was dropped, we had generated
a strategy for dealing with the port breakages that my -exp run detected.
This is disappointing.
mcl
___
svn-src-all@freebsd.org mailing list
On Wed, Dec 28, 2011 at 04:40:49PM +0100, Ulrich Spörlein wrote:
It's better to have one person
(Xin LI) figure out if the change is needed or a no-op and do the
upgrade to match our version to upstream's version, than to have a
discrepancy between the two and cause half a dozen developers
On Tue, May 31, 2011 at 04:52:10PM +0100, Ben Laurie wrote:
Now I'm back from my travels someone's going to have to tell me what I
need to do!
Now you understand the reason not to leave the room: someone just
volunteers you to do stuff, when you do.
mcl
On Sun, May 29, 2011 at 08:46:54PM +, Nathan Whitehorn wrote:
Add some error handling here: if a sensor returns an error code (a negative
Kelvin temperature, which is impossible except for some contrived magnetic
spin systems), use the previous measurement from that sensor instead of
On Sun, May 22, 2011 at 10:22:56PM +0200, Roman Divacky wrote:
The problem here is deeper in my opinion. What FreeBSD calls
amd64 the rest of the world (ie. linux) calls x86_64, I think
that instead of this we should teach llvm/clang about amd64.
Maybe as a FreeBSD-only diff.
If we move away
On Sat, May 14, 2011 at 05:44:12PM +, Colin Percival wrote:
Encourage Ben Laurie to finish getting his commit bit by appointing him
as the OpenSSL maintainer.
Cool! (both parts)
mcl
___
svn-src-all@freebsd.org mailing list
On Fri, Nov 05, 2010 at 01:21:03AM +, Alexander Best wrote:
maybe, because nearly all PRs (most of them including patches) they
have submitted via GNATS in the past remain unnoticed and thus they've
gotten tired of reporting issues and submitting patches if nobody
seems to care? ;)
We
On Thu, Jun 17, 2010 at 12:36:51PM -0700, Doug Barton wrote:
every time this is discussed it's the bikeshed from
$CULTURALLY_RELEVANT_PLACE_OF_TORMENT.
On occasion I'm attempted to close incoming PRs with the following text:
Administer your system.
The upside of FreeBSD being so
On Thu, Mar 18, 2010 at 06:44:45PM -0700, Julian Elischer wrote:
If I'm not mistaken this means that the install CDs will no longer even
boot on a lot of machines.
I wonder how much RAM most of those systems have ...
mcl
___
svn-src-all@freebsd.org
On Fri, Mar 12, 2010 at 11:53:46PM -0300, Carlos A. M. dos Santos wrote:
Thanks God we have you, the holy committers to protect us from our
own ignorance.
Please remember that in most cases, FreeBSD committers do so merely for
the feeling of a job well done. Rhetoric like this takes away part
On Sun, Feb 28, 2010 at 05:19:22PM +, Konstantin Belousov wrote:
Mark msdosfs as mpsafe.
wow, excellent work.
mcl
___
svn-src-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to
Thank you.
mcl
___
svn-src-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to svn-src-all-unsubscr...@freebsd.org
On Wed, Sep 02, 2009 at 02:12:07AM +, Alfred Perlstein wrote:
MFC: r196489,196498
Critical USB bugfixes for 8.0
Will this change anything for ports?
mcl
___
svn-src-all@freebsd.org mailing list
On Mon, Mar 09, 2009 at 03:27:05PM -0700, Steve Kargl wrote:
When Mark Linimon, a member of portmgr, posts on Feb 26th
(http://lists.freebsd.org/pipermail/freebsd-ports/2009-February/053282.html
There appears to be a disconnect with USB2 development and the
rest of FreeBSD.
Within 2 days
On Mon, Mar 09, 2009 at 07:19:26PM -0700, Steve Kargl wrote:
Ed gave a month or more headsup that a new TTY layer was coming. He
enumerated the drivers that were broken and actively solicited people
with the affected hardware for help. He furthermore helped those
people fix as many driver as
86 matches
Mail list logo