Hi pin,
I tested out a build with build.sh ... -V HAVE_MESA_VER=21 and after
some changes, it works on all my GPUs (that use DRM).
Feel free to give it a shot, perhaps we can switch the default soon.
On Wed, Apr 17, 2024 at 11:51:05AM +, pin wrote:
> Hi,
>
> Sorry if this is the wrong list,
On Mon, Aug 31, 2020 at 12:38:57AM +, Taylor R Campbell wrote:
> > Date: Mon, 31 Aug 2020 00:25:52 +
> > From: m...@netbsd.org
> >
> > The following script fails to compile, it shouldn't.
> >
> > #!/bin/sh
> >
> > cat << EOF > test.c
> > #include
> > #include
> >
> > void f1(void)
>
On Sun, Aug 30, 2020 at 07:50:59PM +0200, Joerg Sonnenberger wrote:
> On Sun, Aug 30, 2020 at 05:18:43PM +, m...@netbsd.org wrote:
> > On Sun, Aug 30, 2020 at 06:09:47PM +0200, Joerg Sonnenberger wrote:
> > > On Sun, Aug 30, 2020 at 12:00:33PM +, co...@sdf.org wrote:
> > > > Move the big "i
On Sun, Aug 30, 2020 at 06:09:47PM +0200, Joerg Sonnenberger wrote:
> On Sun, Aug 30, 2020 at 12:00:33PM +, co...@sdf.org wrote:
> > Move the big "if _NETBSD_SOURCE" chunk to the "Implementation defined"
> > section.
> > Makes "at_quick_exit" and others visible for strict C/C++.
>
> alloca is
On Tue, May 12, 2020 at 12:37:57PM +, nia wrote:
> These use arandom exclusively on NetBSD:
> - gnutls (via nettle _rnd_get_system_entropy)
> Prefers getentropy and only uses getrandom if there's no getentropy.
> - openssl (syscall_random)
> Prefers getentropy and only uses getrandom if the
On Sun, May 10, 2020 at 10:25:50PM +, Taylor R Campbell wrote:
> > Date: Sun, 10 May 2020 22:10:55 +
> > From: m...@netbsd.org
> >
> > I still don't find the getrandom man page you provided to be good, it
> > talks about "/dev/random behaviour" which is something you've changed to
> > not
> That issue is why I'm not really happy about the getentropy API: it
> was originally defined to never block, and some systems have made it
> block for reasons that don't really mean very much.
>
> This is an argument for providing just getrandom -- the API contract
> is is clearer and doesn't re
On Sat, May 09, 2020 at 10:56:51PM +, Taylor R Campbell wrote:
> Given that, I think it is reasonable to implement getentropy(...) as
> an alias for getrandom(..., GRND_INSECURE) == read from /dev/urandom
> == sysctl kern.arandom (as nia@ just committed the other day), which
> is consistent wi
On Fri, May 08, 2020 at 06:23:01PM -0400, Thor Lancelot Simon wrote:
> On Fri, May 08, 2020 at 10:03:06AM +0200, Kamil Rytarowski wrote:
> > On 08.05.2020 02:14, Thor Lancelot Simon wrote:
> > >
> > > Not without performance penalty for every atomic operation, unless you
> > > propose
> > > to do
On Fri, May 08, 2020 at 04:09:02PM +0200, Kamil Rytarowski wrote:
> I object to opinions that libatomic is generally broken, if that would
> be the cause, it wouldn't be available and used on relatively all
> relevant generic purpose Operating Systems. Personally, I already
> received last year a f
On Thu, May 07, 2020 at 08:14:57PM -0400, Thor Lancelot Simon wrote:
> On Fri, May 08, 2020 at 01:51:16AM +0200, Kamil Rytarowski wrote:
> > A runtime detection could be a part of ifunc (is it ready for NetBSD?).
> >
> > The standard C/C++ feature is to detect whether atomic operations are
> > rea
I am under the impression that (at least GCC) compilers will not emit
intrinsic calls if they are guaranteed to be available on the target.
This means libatomic needs to:
- Optimize: we can runtime detect, which emitted code cannot do.
Note that this means providing this libatomic will cause us
On Sat, May 02, 2020 at 02:27:31PM +0200, Martin Husemann wrote:
> On Sat, May 02, 2020 at 12:22:20PM +, m...@netbsd.org wrote:
> > Having compat shims in libc is as good as having compat shims in syscall
> > because it isn't possible to share raw syscall code between NetBSD and
> > other opera
For the previous discussion about it:
http://mail-index.netbsd.org/tech-crypto/2018/06/21/msg000763.html
This discussion calls for only having one interface, the
getrandom(...,0) one, which is the path other operating systems
took with their /dev/{,u}random.
The getrandom interface intentionally
On Mon, Aug 19, 2019 at 09:58:32AM +0200, Jaromir Dolecek wrote:
> Please wait with any possible type switch couple more days, I’ll be back from
> vacations on Wednesday and I will check this by then.
>
ping
On Sun, Aug 11, 2019 at 07:38:21PM +0200, Kamil Rytarowski wrote:
> It used to break C ones too, but we have introduced a cast to workaround it.
>
> As we fix it for C ones, I think we should fix it for C++ ones as well.
>
> 3 solutions:
>
> - Keep patching it on caller level for C++
> - Keep
How is this for a proposed patch?
Provide a fallback definition for _Static_assert for when the compiler
doesn't provide it (it doesn't have to for pre-C11).
Fixes https://rt.perl.org/Public/Bug/Display.html?id=134023
Index: cdefs.h
=
perl is not broken. providing a broken macro and hoping nobody uses it
on GCC is.
This is definition is causing problems.
Bug report: https://rt.perl.org/Ticket/Display.html?id=134023
Standalone test case:
#!/bin/sh
cat << EOF > AAAtest.cpp
#include
#ifndef static_assert
#define static_assert theoretical fallback definition that doesnt happen
#endif
int main() {
stat
We can also force define -D_REETRANT if building with sanitizers.
It became a bikeshed about 15 replies in. 100 replies later, we're
pretty deep. I took a short break from reading this thread to port a
programming language to NetBSD and it's already merged upstream. I
wonder if I can do a second one before this thread is over, some people
mentioned liking Swift.
On Fri, Feb 15, 2019 at 07:11:59PM -0800, John Nemeth wrote:
> On Feb 16, 3:16am, Kamil Rytarowski wrote:
> } On 16.02.2019 03:03, Christian Groessler wrote:
> } > On 2/16/19 2:35 AM, Kamil Rytarowski wrote:
> } >> On 16.02.2019 02:14, m...@netbsd.org wrote:
> } >>> There's a topic on peace-keepin
There's a topic on peace-keeping in a large project.
There are two types of feedback:
- "this change makes the code simpler and twice as fast" (it's
objectively better)
- "I like colorful terminals" (my personal opinion)
Objecting to a diff like this causes friction. I like Rin, and I don't
wa
Add to ~/.Xresources:
! show red as green
*.color1: #D7005F
*.color9: #D7005F
xrdb -merge ~/.Xresources (I do this with ~/.xinitrc)
On Fri, Feb 15, 2019 at 10:16:47PM +0100, Christian Groessler wrote:
> On 2/15/19 9:47 PM, Kamil Rytarowski wrote:
> > On 15.02.2019 17:58, Christian Groessler wrote:
> > > Please not. Red (esp. dark read) will be difficult to read for me. I'm
> > > color blind.
> > export TERM=vt100 (or similar)
>
On Fri, Feb 15, 2019 at 10:17:55PM +0100, Christian Groessler wrote:
> On 2/15/19 8:15 PM, m...@netbsd.org wrote:
> > For the record I support the change. I don't think it's very hard not
> > to turn on colors. You can turn them off even in linux.
>
>
> "You can turn them off even in linux."
>
>
On Fri, Feb 15, 2019 at 08:04:13PM +0100, Hauke Fath wrote:
> At 18:29 Uhr + 15.02.2019, Christos Zoulas wrote:
> >>That's why I have to install XEmacs, tcsh and uucp from pkgsrc. Which is
> >>fine.
> >
> >So the question then becomes: "Is something that you presumably need,
> >since you use ev
Adding to the previous:
- I will personally use it (especially if fish knows to automatically
use it)
- I know several netbsd developers who either have variations of colorls
or use GNU ls purely for its support of color.
For the record I support the change. I don't think it's very hard not
to turn on colors. You can turn them off even in linux.
I think having ls -G is a bit redundant, but compatibility with either
one is probably worth it.
I don't expect netbsd will ever change its defaults unless forked, you
hav
On Fri, Feb 15, 2019 at 04:43:24AM +0100, Kamil Rytarowski wrote:
> I don't have stronger opinion on dynamic linking, but maybe dlopen(3)
> for libterminfo can be used as microptimization? Recently we were
> optimizing similarly sh(1).
That wasn't committed.
I'd be really unhappy if much of netbsd
On Wed, Feb 13, 2019 at 11:51:01AM +0100, Joerg Sonnenberger wrote:
> On Mon, Feb 11, 2019 at 07:36:03PM +0700, Robert Elz wrote:
> > One assumes that a (much smaller) staticly linked /bin/sh would be
> > slightly faster still - but doing that isn't really what I think we
> > should be doing (that
Unrelated to yes/no, I feel like we should dig into why it makes a
big difference.
In theory lazy symbol lookup should take care of the big cost associated
with it.
Disabling the partial relro for libc/libterminfo/libedit/sh did not seem
to make a noticeable difference, so I guess it is not so bad
Hi Rhialto,
PuTTY is also in pkgsrc :-) from patches/
$NetBSD: patch-unix_uxpgnt.c,v 1.2 2017/03/17 11:55:53 maya Exp $
BSD setpgrp has parameters. POSIX says it is undefined whether
setpgrp(0,0) == setpgrp() and it should use setpgid.
Use setpgid without parameters on non-BSD
--- unix
John, you get everything you could possibly get: we're definitely not
deleting telnet. Please stop poking people in this thread which has gone
on for too long.
On Thu, Dec 20, 2018 at 09:24:35AM +0900, Rin Okuyama wrote:
> On 2018/12/20 7:08, Hisashi T Fujinaka wrote:
> > On Wed, 19 Dec 2018, David Holland wrote:
> >
> > > On Wed, Dec 19, 2018 at 01:36:48PM -0800, Hisashi T Fujinaka wrote:
> > > > Telnet is used every day and most of the use cases can us
On Wed, Dec 19, 2018 at 10:14:47PM +, m...@netbsd.org wrote:
> Relax, the end conclusion was not to delete it. To maintain it until a
> replacement comes in. Please help test the replacement if it is written,
> to ensure it works for your case.
- Given an exploit, it's still going to be an uni
Relax, the end conclusion was not to delete it. To maintain it until a
replacement comes in. Please help test the replacement if it is written,
to ensure it works for your case.
On Sun, Dec 16, 2018 at 08:11:09PM +, David Holland wrote:
> I have found the 0.18pre1 tarballs if anyone wants them.
Please share :-)
On Sun, Dec 16, 2018 at 01:54:24PM -0500, Christos Zoulas wrote:
> On Dec 16, 6:05pm, dholland-t...@netbsd.org (David Holland) wrote:
> -- Subject: Re: Moving telnet/telnetd from base to pkgsrc
>
> | On Sat, Dec 15, 2018 at 04:37:30PM +, Christos Zoulas wrote:
> | > I have already started fi
On Sun, Dec 16, 2018 at 06:14:37PM +, m...@netbsd.org wrote:
> On Sun, Dec 16, 2018 at 06:05:55PM +, David Holland wrote:
> > On Sat, Dec 15, 2018 at 04:37:30PM +, Christos Zoulas wrote:
> > > I have already started fixing the telnet client code. There is not
> > > so much of it...
>
On Sun, Dec 16, 2018 at 06:05:55PM +, David Holland wrote:
> On Sat, Dec 15, 2018 at 04:37:30PM +, Christos Zoulas wrote:
> > I have already started fixing the telnet client code. There is not
> > so much of it...
>
> Good luck with that.
>
> You want the diffs from my attempts twenty y
On Sun, Dec 16, 2018 at 10:33:25AM -0500, Greg Troxel wrote:
> Taylor R Campbell writes:
>
> > Given that a large fraction of respondents (though not all) indicated
> > that their primary use of telnet is to test reachability of a server
> > or manually enter SMTP or HTTP requests over the intern
On Sun, Dec 16, 2018 at 10:30:22AM -0500, Greg Troxel wrote:
> > What's the deal wiht IPSEC?
>
> The protoocol is called IPsec (and often miscapitalized), and our kernel
> option is IPSEC.
>
> > I've never used it, but I was under the impression it gives encryption
> > for free for things that ot
On Sat, Dec 15, 2018 at 10:38:10PM +0100, Anders Magnusson wrote:
> Den 2018-12-15 kl. 22:11, skrev Marc Balmer:
> > Whatever.
> >
> > Please keep telnet and telnetd in base. They have their valid use cases.
> >
> Yes please. I have used both kerberized telnet and plain telnet last 12
> months
On Sat, Dec 15, 2018 at 09:55:34PM +0100, Marc Balmer wrote:
> Is telnet / telnetd less of a risk to our users if it is in pkgsrc rather
> than in base?
>
> Is pkgsrc the toilet for software you don‘t want to see in base?
>
> Is pkgsrc your personal toilet?
>
> I have good use for telnet and te
A new version is easier to do without the promise of compatibility.
Anyway, I get it, another case of "please maintain legacy code forever
and never make significant changes to it".
On Sat, Dec 15, 2018 at 01:45:04PM +0700, Robert Elz wrote:
> Date:Fri, 14 Dec 2018 21:28:34 -0800
> From:John Nemeth
> Message-ID: <201812150528.wbf5syhr025...@server.cornerstoneservice.ca>
>
> | As kre noted, it is probably the oldest network application
> | aro
On Sat, Dec 15, 2018 at 01:45:04PM +0700, Robert Elz wrote:
> Date:Fri, 14 Dec 2018 21:28:34 -0800
> From:John Nemeth
> Message-ID: <201812150528.wbf5syhr025...@server.cornerstoneservice.ca>
>
> | As kre noted, it is probably the oldest network application
> | aro
On Tue, Sep 25, 2018 at 04:32:03PM +1000, Simon Burge wrote:
> Should you be allowed to call dirname(3) on the results of a previous
> dirname(3) call?
This is about minidlna, right? if it works, please feel free to add
SSP_SUPPORTED= no
to the makefile.
it's a hack, but it'll give us the ability
You're complaining loudly at someone for changing code you believe is
sacred.
- We don't want to have any code in netbsd that is too sacred to touch.
- kre is ridiculously fucking nice.
- we really, really like kre.
It's like everyone has a score. You can do negative and positive things.
Positive
On Wed, Aug 15, 2018 at 08:29:29PM +, m...@netbsd.org wrote:
> I would be defending him even if the criticism was about sh making my
> own system unbootable. And it isn't.
Keep in mind all these changes occur in -current. -current has random
breakage, it happens (and it usually doesn't come fr
On Tue, Aug 14, 2018 at 04:27:34PM -0400, Izaac wrote:
> On Thu, Jul 13, 2017 at 09:01:26AM -0400, Izaac wrote:
> > On Thu, Jul 13, 2017 at 07:46:39AM +0700, Robert Elz wrote:
> > > So, opinions?
> >
> > Stop.
> >
> > Leave /bin/sh alone.
>
> And here we are.
I for one strongly appreciate that:
I applied this.
On Tue, Jul 17, 2018 at 09:06:53AM -0400, D'Arcy Cain wrote:
> On 2018-07-17 08:41 AM, Christos Zoulas wrote:
> > Well, the comment needs to be amended, since you don't need to close the
> > fd's anymore. Other than that it looks fine.
>
> Great! I went ahead.
>
> Do you think that this is a can
On Thu, Jun 21, 2018 at 09:42:17AM -0400, Greg Troxel wrote:
>
> Paul Goyette writes:
>
> > On Thu, 21 Jun 2018, Kamil Rytarowski wrote:
> >
> >> Module Name: src
> >> Committed By: kamil
> >> Date: Thu Jun 21 11:02:48 UTC 2018
> >>
> >> Modified Files:
> >>src/extern
On Thu, Jun 07, 2018 at 05:54:57PM +, co...@sdf.org wrote:
> Hi folks.
>
> I like to read my email. I don't like needing to use python scripts to
> parse it. So this diff worked for me.
>
> Index: i18n/esdb/ISO-8859/ISO-8859.alias
>
On Sun, May 27, 2018 at 06:40:39PM +0100, Sevan Janiyan wrote:
> Hello,
> When building Lua modules bsd.sys.mk gets included in bsd.lua.mk. In
> bsd.sys.mk -Wmissing-prototypes is enabled via CFLAGS. This forces the
> declaration of prototypes where it would not be a show stopper if it
> wasn't, fo
On Fri, May 18, 2018 at 12:20:20AM +0100, Alexander Nasonov wrote:
> David Holland wrote:
> > On Thu, May 17, 2018 at 03:41:26PM +0200, Marc Balmer wrote:
> > > One more thing: When we imported Lua into base, we very clearly
> > > decided that pkgsrc Lua and base Lua should be two separate things
Any chance we can remove this from libc before releasing 8.0?
it has one user, and the implementation is very specific for a certain
use-case.
having a DIY one use case function in libc is actually harming the
ability to upstream this, aside from the implementation choices.
This sounds related:
https://v4.freshbsd.org/commit/netbsd/src/ipHBgqsQ9q17WJVz
oops, I just tested badly. adding gettext as a dependency the right way
makes it work. :-)
oooh. cool. I've switched a bunch of pkgsrc mirrors to default to HTTP
because of how bad that was on a high latency connection, would be neat
if we can avoid it!
For just using GNU utilities and update-alternatives like:
Note PATH is searched right to left, so if your PATH starts with:
/usr/local/bin:/usr/pkg/gnu/bin:...
It will search those paths first, and if you grab sysutils/coreutils
from pkgsrc, 'ls' will be the GNU one. It's not expected to cause
p
tac.1
--- /dev/null 1 Jan 1970 00:00:00 -
+++ tac.1 1 Oct 2017 19:22:32 -
@@ -0,0 +1,54 @@
+.\"$NetBSD$
+.\"
+.\" Copyright (c) 2017 The NetBSD Foundation, Inc.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to The Net
There are systems that have followed this policy of not touching basic
tools, it looks really ugly after 20 years of being done. You have to
explain to a newcomer that his command isn't working because rm can't
delete files over 2GB, and people will rationalize it saying that 'maybe
someone's scrip
If people like the program, it comes with the library, too.
It's 8600 lines of code, MIT-licensed, and can do more than HTTP:
http://w3.impa.br/~diego/software/luasocket/reference.html
sure, I could parse that part...
On Wed, Jul 12, 2017 at 06:42:57PM +0700, Robert Elz wrote:
> Whether it works or not (I have no current means to test it either)
> parrt of the issue is that it needs to work using only what is available
> in NetBSD release - so starting with #!/usr/pkg/bin/lua5.2 is not a good
> sign!
>
Yeah, d
On Tue, Jul 11, 2017 at 10:31:59PM -0400, Thor Lancelot Simon wrote:
> Captive-portal login is a very real problem. How best to solve it otherwise?
> Remember, small embedded systems (easily supported by adding additional sets
> using our existing framework) are within scope.
If anyone wants to t
On Tue, Jul 11, 2017 at 10:31:59PM -0400, Thor Lancelot Simon wrote:
> Captive-portal login is a very real problem. How best to solve it otherwise?
> Remember, small embedded systems (easily supported by adding additional sets
> using our existing framework) are within scope.
I can create a simpl
To reply to your points:
- Debian doesn't ship ifconfig because it considers it a legacy tool and
expects you to use 'ip'.
- We already have a package tool.
Do you think pkg_* are doing poorly on file ownership? I don't intend
to port apt-get.
- I assume the open coding of file ownership is
I don't like such changes because I think netbsd's base is bad at
handling software. it bunches a pile of unrelated things in a single
tarball, garbage collection is done with a 2600 line shell script, and
adding just a single file requires me to add an entry to a set list
that requires a full rele
we are lacking int128_t, log1pl, etc., a whole bunch of long double
stuff, etc.
one of the libc shlib major items is "stop using errnos in math
functions altogether"
72 matches
Mail list logo
