daily CVS update output

2023-08-30 Thread NetBSD source update


Updating src tree:
P src/etc/mtree/special
P src/lib/libc/regex/regcomp.c
P src/sys/arch/amiga/conf/MDINSTALL
P src/sys/arch/arc/arc/autoconf.c
P src/sys/arch/arc/arc/interrupt.c
P src/sys/arch/arc/arc/timer.c
P src/sys/arch/arc/arc/timervar.h
P src/sys/arch/arc/isa/opms_isa.c
U src/sys/arch/arm/dts/rk3328-nanopi-r2s.dts
P src/sys/arch/arm/dts/rk3399-rockpro64.dts
P src/sys/arch/atari/dev/fd.c
P src/sys/arch/atari/dev/ser.c
P src/sys/arch/i386/stand/Makefile.inc
P src/sys/arch/i386/stand/bootxx/bootxx_msdos/Makefile
P src/sys/arch/i386/stand/bootxx/bootxx_ustarfs/Makefile
P src/sys/arch/i386/stand/lib/Makefile.inc
P src/sys/arch/macppc/dev/awacs.c
P src/sys/arch/macppc/dev/pmu.c
P src/sys/compat/netbsd32/netbsd32_epoll.c
P src/sys/lib/libkern/Makefile.inc
P src/sys/lib/libsa/Makefile
P src/sys/lib/libsa/Makefile.inc
P src/sys/modules/compat_netbsd32/Makefile

Updating xsrc tree:


Killing core files:




Updating file list:
-rw-rw-r--  1 srcmastr  netbsd  48416884 Aug 31 03:03 ls-lRA.gz


Re: ERROR: No valid Python version

2023-08-30 Thread Greg Troxel
Riccardo Mottola  writes:

> Hi,
>
> Greg Troxel wrote:
>> did you cd to devel/scons (or really the PKGPATH of the installed pkg)
>> and type "make replace".  The pkg_rr man page says, or should say, to do
>> that, and then to deal with that error as if it were not from pkg_rr.
>
> no, I didn't... I thought to have encountered some weird setup
> error. I did now. It fails with a cryptic message:

the man page for pkg_rr asks that people not report "some make replace
that pkg_rr did failed" as a pkg_rr problem, because it's not really
true but mostly because the subset of peopel that don't like pkg_rr then
ignore your report, whereas some of them could perhaps be helpful if it
is properly reported as a simpler failure.

>> perhaps, scons 3 is now limited to py27.
>
> Well it is trying to build the py27 version, also it is more "sane
> now" since it says:
> py27-scons-3.1.2nb7while with pkg_rr it was confused between the py310
> and the "none" version:
>
> RR> Replacing py310-scons-3.1.2nb4
> ===> Cleaning for none-scons-3.1.2nb7
>
> In fact at the moment I have this one installed, according to pkg_info
>
> py310-scons-3.1.2nb4 Python-based, open-source build system
>
> so I suppose pkg_rr was right trying to subdtitute the py3 version

Yes, the basic issue is that new scons3 dropped support for py3, and the
basic solution is to upgrade to 4, but we don't really have support for
that, and 99% people only have scons as a build tool (because somebody
else wrongly thought it was better than autoconf 5 years ago :-).

>> I recommend "pkgin ar" before a rebuild run.
>
> Now it is a little late :-P

You can still do it and continue.   Unless you actually *want* scons3,
removing it is best.  The tools that are needed for other things will
get built.



Re: ERROR: No valid Python version

2023-08-30 Thread Riccardo Mottola

Hi,


Riccardo Mottola wrote:


In fact at the moment I have this one installed, according to pkg_info

py310-scons-3.1.2nb4 Python-based, open-source build system

so I suppose pkg_rr was right trying to subdtitute the py3 version 


right now I found that py310-scons could be removed without breaking 
dependencies, so I removed it and continue pkg_rr


If it is a dependency of one installed package, I suppose it will be 
pulled in again.


Riccardo


Re: modesetting vs intel in 10.0

2023-08-30 Thread nia
On Tue, Jul 11, 2023 at 09:58:51AM +1000, matthew green wrote:
> > But maybe modesetting is mature enough (and intel bad enough)
> > to warrant being the default for Intel GPUs.
> 
> i'm not familiar with the various intel chipsets, i've only had
> a couple of them over the years and besides porting the kabylake
> bits into the older drm version, i've not really touched it much.
> 
> but, you can adjust the list of drivers used by default here in
> the xorg-server sources:
> 
>hw/xfree86/common/xf86pciBus.c:xf86VideoPtrToDriverList()
> 
> where it has a "default:" case for intel of "intel", and if you
> can properly figure out how to change this to "modesetting" for
> the newer ones (only?) that would be fine by me.
> 
> (one way to handle this without having to patch this code would
> be to install the intel driver as some other name, and then make
> a copy of the "ati" front end called "intel" that loads either
> the real intel driver or modesetting, depending.)

It does allow having multiple defaults! This is the case,
for example, for nvidia cards, which try nouveau first then
fall back to to nv.

I think detecting the year of manufacture is too much of a hard
problem - there are simply too many new cards and I have no idea
about a "cutoff point" where modesetting starts being OK (if it
even isn't okay for any old cards at all - it should work as long
as DRM/KMS works AFAIK)


Re: ERROR: No valid Python version

2023-08-30 Thread Riccardo Mottola

Hi,

Greg Troxel wrote:

did you cd to devel/scons (or really the PKGPATH of the installed pkg)
and type "make replace".  The pkg_rr man page says, or should say, to do
that, and then to deal with that error as if it were not from pkg_rr.


no, I didn't... I thought to have encountered some weird setup error. I 
did now. It fails with a cryptic message:


=> Generating post-install file lists
if test -d 
"/usr/pkgsrc/devel/scons/work/.destdir/usr/pkg/lib/python2.7/site-packages/scons-3.1.2-py2.7.egg-info"; 
then  /usr/bin/find 
/usr/pkgsrc/devel/scons/work/.destdir/usr/pkg/lib/python2.7/site-packages/scons-3.1.2-py2.7.egg-info 
-type f  -exec /bin/chmod 644 '{}' +;  fi

=> Checking file-check results for py27-scons-3.1.2nb7
=> Creating binary package 
/usr/pkgsrc/devel/scons/work/.packages/py27-scons-3.1.2nb7.tgz

===> Building binary package for py27-scons-3.1.2nb7
=> Creating binary package /usr/pkgsrc/packages/All/py27-scons-3.1.2nb7.tgz
===> Replacing for py27-scons-3.1.2nb7
*** Error code 1

Stop.
make[1]: stopped in /usr/pkgsrc/devel/scons
*** Error code 1




perhaps, scons 3 is now limited to py27.


Well it is trying to build the py27 version, also it is more "sane now" 
since it says:
py27-scons-3.1.2nb7while with pkg_rr it was confused between the py310 
and the "none" version:


RR> Replacing py310-scons-3.1.2nb4
===> Cleaning for none-scons-3.1.2nb7


In fact at the moment I have this one installed, according to pkg_info

py310-scons-3.1.2nb4 Python-based, open-source build system

so I suppose pkg_rr was right trying to subdtitute the py3 version


I recommend "pkgin ar" before a rebuild run.


Now it is a little late :-P

Riccardo