Re: Problem compiling py-* ports

2023-04-18 Thread Filippo Moretti
 After completing installworld and rebuilding python39 I do get the same error 
as reported previouslyFilippo

On Tuesday, April 18, 2023 at 12:54:33 PM UTC, Mateusz Guzik 
 wrote:  
 
 On 4/18/23, Filippo Moretti  wrote:
> Good morning,                      I run this versione of Frrebsd and al
> py-* ports fail with the following message.sincerelyFilippo
>
> FreeBSD STING 14.0-CURRENT FreeBSD 14.0-CURRENT #6
> main-n261981-63b113af5706: Tue Apr  4 16:57:47 CEST 2023
> filippo@STING:/usr/obj/usr/src/amd64.amd64/sys/STING amd64
>
>

you are on a zfs commit with known data corruption (in fact, 2)

bare minimum you need to update to fresh main and reinstall all python stuff

>
>
>
>    return _bootstrap._gcd_import(name[level:], package,
> level)
>    File "", line 1030, in
> _gcd_import
>
>  File "", line 1007, in
> _find_and_load
>
>  File "", line 972, in
> _find_and_load_unlocked
>
>  File "", line 228, in
> _call_with_frames_removed
>  File "", line 1030, in _gcd_import
>  File "", line 1007, in _find_and_load
>  File "", line 986, in
> _find_and_load_unlocked
>  File "", line 680, in _load_unlocked
>  File "", line 850, in exec_module
>  File "", line 228, in
> _call_with_frames_removed
>  File "/usr/local/lib/python3.9/site-packages/setuptools/__init__.py", line
> 18, in 
>    from setuptools.dist import Distribution
>  File "/usr/local/lib/python3.9/site-packages/setuptools/dist.py", line 34,
> in 
>    from ._importlib import metadata
>  File "/usr/local/lib/python3.9/site-packages/setuptools/_importlib.py",
> line 39, in 
>    disable_importlib_metadata_finder(metadata)
>  File "/usr/local/lib/python3.9/site-packages/setuptools/_importlib.py",
> line 28, in disable_importlib_metadata_finder
>    to_remove = [
>  File "/usr/local/lib/python3.9/site-packages/setuptools/_importlib.py",
> line 31, in 
>    if isinstance(ob, importlib_metadata.MetadataPathFinder)
> AttributeError: module 'importlib_metadata' has no attribute
> 'MetadataPathFinder'
>
> ERROR Backend subprocess exited when trying to invoke
> get_requires_for_build_wheel
> *** Error code 1
>
> Stop.
> make: stopped in /usr/ports/textproc/py-pygments
>
> ===>>> make build failed for textproc/py-pygments@py39
> ===>>> Aborting update
>
> ===>>> Update for textproc/py-pygments@py39 failed
> ===>>> Aborting update
>
>
> ===>>> You can restart from the point of failure with this command line:
>
>
>
>


-- 
Mateusz Guzik 

  

Re: Problem compiling py-* ports

2023-04-18 Thread Filippo Moretti
 
After following the instructions provided I get the following:==>>> All >> 
py39-pygments-2.14.0 (1/9)

===>  Building for py39-pygments-2.15.0
/usr/local/bin/python3.9: No module named build
*** Error code 1

Stop.
make: stopped in /usr/ports/textproc/py-pygments

===>>> make build failed for textproc/py-pygments@py39
===>>> Aborting update

===>>> Update for textproc/py-pygments@py39 failed
===>>> Aborting update



On Tuesday, April 18, 2023 at 09:57:31 AM UTC, Felix Palmen 
 wrote:  
 
 * Marek Zarychta  [20230418 11:41]:
> What is the culprit?

Most likely some leftovers from older package versions (so it's only a
problem when building in the live system. A clean jail won't have the
offending files).

>                      Removing blindly all py- packages for all affected
> hosts with dependent software is not the best solution.

Depending on your situation, it might or might not be faster than trying
to identify the exact offending files and just removing them ;)

-- 
 Felix Palmen     {private}  fe...@palmen-it.de
 -- ports committer (mentee) --            {web}  http://palmen-it.de
 {pgp public key}  http://palmen-it.de/pub.txt
 {pgp fingerprint} 6936 13D5 5BBF 4837 B212  3ACC 54AD E006 9879 F231
  

Problem compiling py-* ports

2023-04-18 Thread Filippo Moretti
Good morning,   I run this versione of Frrebsd and al py-* 
ports fail with the following message.sincerelyFilippo

FreeBSD STING 14.0-CURRENT FreeBSD 14.0-CURRENT #6 main-n261981-63b113af5706: 
Tue Apr  4 16:57:47 CEST 2023 
filippo@STING:/usr/obj/usr/src/amd64.amd64/sys/STING amd64





   return _bootstrap._gcd_import(name[level:], package, level)  
      File "", line 1030, in _gcd_import   
     
  File "", line 1007, in _find_and_load
     
  File "", line 972, in _find_and_load_unlocked
     
  File "", line 228, in _call_with_frames_removed
  File "", line 1030, in _gcd_import
  File "", line 1007, in _find_and_load
  File "", line 986, in _find_and_load_unlocked
  File "", line 680, in _load_unlocked
  File "", line 850, in exec_module
  File "", line 228, in _call_with_frames_removed
  File "/usr/local/lib/python3.9/site-packages/setuptools/__init__.py", line 
18, in 
    from setuptools.dist import Distribution
  File "/usr/local/lib/python3.9/site-packages/setuptools/dist.py", line 34, in 

    from ._importlib import metadata
  File "/usr/local/lib/python3.9/site-packages/setuptools/_importlib.py", line 
39, in 
    disable_importlib_metadata_finder(metadata)
  File "/usr/local/lib/python3.9/site-packages/setuptools/_importlib.py", line 
28, in disable_importlib_metadata_finder
    to_remove = [
  File "/usr/local/lib/python3.9/site-packages/setuptools/_importlib.py", line 
31, in 
    if isinstance(ob, importlib_metadata.MetadataPathFinder)
AttributeError: module 'importlib_metadata' has no attribute 
'MetadataPathFinder'

ERROR Backend subprocess exited when trying to invoke 
get_requires_for_build_wheel
*** Error code 1

Stop.
make: stopped in /usr/ports/textproc/py-pygments

===>>> make build failed for textproc/py-pygments@py39
===>>> Aborting update

===>>> Update for textproc/py-pygments@py39 failed
===>>> Aborting update


===>>> You can restart from the point of failure with this command line:





Re: Problem in userland

2023-01-09 Thread Filippo Moretti
 
Thank you for your prompt answer.I tried your suggestion but did not work:I get 
the same error.Please note however that I have not linux emulation enabled as I 
run no linux program:Firefox was installed from ports and it is the native 
freebsd one.I will switch to another browser if needed.Filippo
On Monday, January 9, 2023 at 04:22:49 PM GMT+1, Warner Losh 
 wrote:  
 
 

On Mon, Jan 9, 2023 at 3:42 AM Filippo Moretti  wrote:

Good morning,   I have two computers running CURRENT when 
launching firefox I get the following error:
[filippo@ROXY ~]$ firefox
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: cannot access 
/sys/bus/pci (t=3.60308) [GFX1-]: glxtest: cannot access /sys/bus/pci
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: cannot access 
/sys/bus/pci (t=3.60308) |[1][GFX1-]: glxtest: VA-API test failed: failed to 
initialise VAAPI connection. (t=4.09897) [GFX1-]: glxtest: VA-API test failed: 
failed to initialise VAAPI connection.

[filippo@ROXY ~]$ uname -a
FreeBSD ROXY 14.0-CURRENT FreeBSD 14.0-CURRENT #0 main-n259682-67e628b7a643: 
Wed Dec 14 22:56:22 CET 2022 
root@ROXY:/usr/obj/usr/src/amd64.amd64/sys/ROXY amd64

On this computer firefox works in spite of the Crash Annotation.
On the other hand on this computer:[filippo@ROXY ~]$ less problem
FreeBSD STING 14.0-CURRENT FreeBSD 14.0-CURRENT #1 main-n259975-4ffe60e6833e: 
Sun Jan  8 17:40:19 CET 2023 
root@STING:/usr/obj/usr/src/amd64.amd64/sys/STING amd64

firefox doen't work at all.I did check and there is no /sys/bus/pci and there 
is no /usr/src/sys/bus/pci.

Not sure why firefox is accessing a linux-specific file. FreeBSD does emulate 
some of it, but only with linsysfs mounted. Generally only linux binaries need 
it.
           mount -t linsysfs linsys /compat/linux/sys
might be useful to see if that's missing?

Warner 
  

Problem in userland

2023-01-09 Thread Filippo Moretti
Good morning,   I have two computers running CURRENT when 
launching firefox I get the following error:
[filippo@ROXY ~]$ firefox
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: cannot access 
/sys/bus/pci (t=3.60308) [GFX1-]: glxtest: cannot access /sys/bus/pci
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: cannot access 
/sys/bus/pci (t=3.60308) |[1][GFX1-]: glxtest: VA-API test failed: failed to 
initialise VAAPI connection. (t=4.09897) [GFX1-]: glxtest: VA-API test failed: 
failed to initialise VAAPI connection.

[filippo@ROXY ~]$ uname -a
FreeBSD ROXY 14.0-CURRENT FreeBSD 14.0-CURRENT #0 main-n259682-67e628b7a643: 
Wed Dec 14 22:56:22 CET 2022 
root@ROXY:/usr/obj/usr/src/amd64.amd64/sys/ROXY amd64

On this computer firefox works in spite of the Crash Annotation.
On the other hand on this computer:[filippo@ROXY ~]$ less problem
FreeBSD STING 14.0-CURRENT FreeBSD 14.0-CURRENT #1 main-n259975-4ffe60e6833e: 
Sun Jan  8 17:40:19 CET 2023 
root@STING:/usr/obj/usr/src/amd64.amd64/sys/STING amd64

firefox doen't work at all.I did check and there is no /sys/bus/pci and there 
is no /usr/src/sys/bus/pci.Any help appreciated,sincerelyFilippo


Re: Problem compiling CURRENT

2022-12-14 Thread Filippo Moretti
 I deleted /usr/obj and restarted world I will see tomorrow the outcome.Filippo

On Wednesday, December 14, 2022 at 02:22:57 PM GMT+1, Filippo Moretti 
 wrote:  
 
  
I downloaded src for current on 13/12 11.20 CEST.I did have the same issues for 
about 5 days I made a few attempts all whit same error.Filippo
On Wednesday, December 14, 2022 at 02:18:20 PM GMT+1, Herbert J. Skuhra 
 wrote:  
 
 On Wed, 14 Dec 2022 14:08:01 +0100, Filippo Moretti wrote:
> 
> FreeBSD ROXY 14.0-CURRENT FreeBSD 14.0-CURRENT #4
> main-n258255-de56ac88099: Wed Sep 28 19:35:24 CEST 2022
> root@ROXY:/usr/obj/usr/src/amd64.amd64/sys/ROXY amd64
> 
> 
> 
> 
> 
> 
> 
> Dear Sir I had the following error while trying to compile CURRENT===> 
> usr.bin/rs (all)
> make[4]: /usr/obj/usr/src/amd64.amd64/usr.bin/rs/.depend.rs.o, 1: ignoring 
> stale .depend for /usr/src/usr.bin/rs/rs.c
> cc -target x86_64-unknown-freebsd14.0 
> --sysroot=/usr/obj/usr/src/amd64.amd64/tmp 
> -B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin  -O2 -pipe -fno-common   -fPIE -g 
> -gz=zlib -MD  -MF.depend.rs.o -MTrs.o -std=gnu99 -Wno-format-zero-length 
> -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W 
> -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes 
> -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow 
> -Wunused-parameter -Wcast-align -Wchar-subscripts -Wnested-externs 
> -Wold-style-definition -Wno-pointer-sign -Wdate-time 
> -Wmissing-variable-declarations -Wthread-safety -Wno-empty-body 
> -Wno-string-plus-int -Wno-unused-const-variable 
> -Wno-error=unused-but-set-variable  -Qunused-arguments    -c 
> /usr/src/usr.bin/rs/rs.c -o rs.o
> *** Error code 1
> 
> Stop.
> make[4]: stopped in /usr/src/usr.bin/rs
> *** Error code 1
> 
> Stop.
> make[3]: stopped in /usr/src/usr.bin
> *** Error code 1
> 
> Stop.
> make[2]: stopped in /usr/src
> *** Error code 1
> 
> Stop.
> make[1]: stopped in /usr/src
> *** Error code 1
> 
> Stop.
> make: stopped in /usr/src

Have you tried to wipe /usr/obj (or at least:
/usr/obj/usr/src/amd64.amd64/usr.bin/rs/)?

--
Herbert



Re: Problem compiling CURRENT

2022-12-14 Thread Filippo Moretti
 
I downloaded src for current on 13/12 11.20 CEST.I did have the same issues for 
about 5 days I made a few attempts all whit same error.Filippo
On Wednesday, December 14, 2022 at 02:18:20 PM GMT+1, Herbert J. Skuhra 
 wrote:  
 
 On Wed, 14 Dec 2022 14:08:01 +0100, Filippo Moretti wrote:
> 
> FreeBSD ROXY 14.0-CURRENT FreeBSD 14.0-CURRENT #4
> main-n258255-de56ac88099: Wed Sep 28 19:35:24 CEST 2022
> root@ROXY:/usr/obj/usr/src/amd64.amd64/sys/ROXY amd64
> 
> 
> 
> 
> 
> 
> 
> Dear Sir I had the following error while trying to compile CURRENT===> 
> usr.bin/rs (all)
> make[4]: /usr/obj/usr/src/amd64.amd64/usr.bin/rs/.depend.rs.o, 1: ignoring 
> stale .depend for /usr/src/usr.bin/rs/rs.c
> cc -target x86_64-unknown-freebsd14.0 
> --sysroot=/usr/obj/usr/src/amd64.amd64/tmp 
> -B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin  -O2 -pipe -fno-common   -fPIE -g 
> -gz=zlib -MD  -MF.depend.rs.o -MTrs.o -std=gnu99 -Wno-format-zero-length 
> -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W 
> -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes 
> -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow 
> -Wunused-parameter -Wcast-align -Wchar-subscripts -Wnested-externs 
> -Wold-style-definition -Wno-pointer-sign -Wdate-time 
> -Wmissing-variable-declarations -Wthread-safety -Wno-empty-body 
> -Wno-string-plus-int -Wno-unused-const-variable 
> -Wno-error=unused-but-set-variable  -Qunused-arguments    -c 
> /usr/src/usr.bin/rs/rs.c -o rs.o
> *** Error code 1
> 
> Stop.
> make[4]: stopped in /usr/src/usr.bin/rs
> *** Error code 1
> 
> Stop.
> make[3]: stopped in /usr/src/usr.bin
> *** Error code 1
> 
> Stop.
> make[2]: stopped in /usr/src
> *** Error code 1
> 
> Stop.
> make[1]: stopped in /usr/src
> *** Error code 1
> 
> Stop.
> make: stopped in /usr/src

Have you tried to wipe /usr/obj (or at least:
/usr/obj/usr/src/amd64.amd64/usr.bin/rs/)?

--
Herbert

  

Problem compiling CURRENT

2022-12-14 Thread Filippo Moretti
FreeBSD ROXY 14.0-CURRENT FreeBSD 14.0-CURRENT #4 main-n258255-de56ac88099: Wed 
Sep 28 19:35:24 CEST 2022 root@ROXY:/usr/obj/usr/src/amd64.amd64/sys/ROXY 
amd64







Dear Sir I had the following error while trying to compile CURRENT===> 
usr.bin/rs (all)
make[4]: /usr/obj/usr/src/amd64.amd64/usr.bin/rs/.depend.rs.o, 1: ignoring 
stale .depend for /usr/src/usr.bin/rs/rs.c
cc -target x86_64-unknown-freebsd14.0 
--sysroot=/usr/obj/usr/src/amd64.amd64/tmp 
-B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin  -O2 -pipe -fno-common   -fPIE -g 
-gz=zlib -MD  -MF.depend.rs.o -MTrs.o -std=gnu99 -Wno-format-zero-length 
-fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W 
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith 
-Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter 
-Wcast-align -Wchar-subscripts -Wnested-externs -Wold-style-definition 
-Wno-pointer-sign -Wdate-time -Wmissing-variable-declarations -Wthread-safety 
-Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable 
-Wno-error=unused-but-set-variable  -Qunused-arguments    -c 
/usr/src/usr.bin/rs/rs.c -o rs.o
*** Error code 1

Stop.
make[4]: stopped in /usr/src/usr.bin/rs
*** Error code 1

Stop.
make[3]: stopped in /usr/src/usr.bin
*** Error code 1

Stop.
make[2]: stopped in /usr/src
*** Error code 1

Stop.
make[1]: stopped in /usr/src
*** Error code 1

Stop.
make: stopped in /usr/src




Re: Problem with Radeon

2022-06-07 Thread Filippo Moretti
 
I did install the ports,thank youFilippo
On Tuesday, June 7, 2022 at 02:15:50 PM GMT+2, Emmanuel Vadot 
 wrote:  
 
 On Tue, 7 Jun 2022 12:10:35 + (UTC)
Filippo Moretti  wrote:

> I have reinstalled CURRENT and I get an error while trying to initialize 
> radeon:it was working fine before reinstalling CURRENT.
> 
> [drm] radeon kernel modesetting enabled.  
>     
> drmn0:  on vgapci0  
>     
> vgapci0: child drmn0 requested pci_enable_io  
>     
> vgapci0: child drmn0 requested pci_enable_io  
>     
> sysctl_warn_reuse: can't re-use a leaf (hw.dri.debug)!
>     
> [drm] initializing kernel modesetting (REDWOOD 0x1002:0x68D8 0x1043:0x0356 
> 0x00)  .  
>      
> [drm ERROR :radeon_atombios_init] Unable to find PCI I/O BAR; using MMIO for 
> ATO  M IIO
>    
> ATOM BIOS: 68D8.12.17.0.4.AS06.U122
> drmn0: VRAM: 1024M 0x - 0x3FFF (1024M used)
> drmn0: GTT: 1024M 0x4000 - 0x7FFF
> [drm] Detected VRAM RAM=1024M, BAR=256M
> [drm] RAM width 128bits DDR
> [TTM] Zone  kernel: Available graphics memory: 8373714 KiB
> [TTM] Zone   dma32: Available graphics memory: 2097152 KiB
> [TTM] Initializing pool allocator
> [drm] radeon: 1024M of VRAM memory ready
> [drm] radeon: 1024M of GTT memory ready.
> [drm] Loading REDWOOD Microcode
> drmn0: could not load firmware image 'radeon/REDWOOD_pfp.bin'
> r600_cp: Failed to load firmware "radeon/REDWOOD_pfp.bin"
> [drm ERROR :evergreen_init] Failed to load firmware!
> drmn0: Fatal error during GPU init
> [drm] radeon: finishing device.
> [TTM] Finalizing pool allocator
> [TTM] Zone  kernel: Used memory at exit: 0 KiB
> [TTM] Zone   dma32: Used memory at exit: 0 KiB
> [drm] radeon: ttm finalized
> Warning: can't remove non-dynamic nodes (dri)!
> device_attach: drmn0 attach returned 2
> acpi_wmi0:  on acpi0
> These are the ports installed:drm-510-kmod-5.10.113_1    DRM drivers 
> modules
> drm-kmod-20220501  Metaport of DRM modules for the linuxkpi-based 
> KMS components
> gpu-firmware-amd-kmod-banks-20220511 Firmware modules for banks AMD GPUs
> gpu-firmware-kmod-20220511,1   Firmware modules for the drm-kmod drivers
> gpu-firmware-radeon-kmod-aruba-20220511 Firmware modules for aruba Radeon GPUs

 "drmn0: could not load firmware image 'radeon/REDWOOD_pfp.bin'"
 You don't have the firmware installed for your card.
 How did you installed the packages ? because I see that you have
gpu-firmware-kmod so it should have installed all of them.
 Anyway, pkg install gpu-firmware-radeon-kmod-redwood should solve your
problems.

> FreeBSD STING 14.0-CURRENT FreeBSD 14.0-CURRENT #1 main-85d7875d42: Mon Jun  
> 6 13:40:11 CEST 2022 filippo@STING:/usr/obj/usr/src/amd64.amd64/sys/STING 
> amd64


-- 
Emmanuel Vadot  

  

Problem with Radeon

2022-06-07 Thread Filippo Moretti
I have reinstalled CURRENT and I get an error while trying to initialize 
radeon:it was working fine before reinstalling CURRENT.

[drm] radeon kernel modesetting enabled.
  
drmn0:  on vgapci0
  
vgapci0: child drmn0 requested pci_enable_io
  
vgapci0: child drmn0 requested pci_enable_io
  
sysctl_warn_reuse: can't re-use a leaf (hw.dri.debug)!  
  
[drm] initializing kernel modesetting (REDWOOD 0x1002:0x68D8 0x1043:0x0356 
0x00)  .
   
[drm ERROR :radeon_atombios_init] Unable to find PCI I/O BAR; using MMIO for 
ATO  M IIO  
     
ATOM BIOS: 68D8.12.17.0.4.AS06.U122
drmn0: VRAM: 1024M 0x - 0x3FFF (1024M used)
drmn0: GTT: 1024M 0x4000 - 0x7FFF
[drm] Detected VRAM RAM=1024M, BAR=256M
[drm] RAM width 128bits DDR
[TTM] Zone  kernel: Available graphics memory: 8373714 KiB
[TTM] Zone   dma32: Available graphics memory: 2097152 KiB
[TTM] Initializing pool allocator
[drm] radeon: 1024M of VRAM memory ready
[drm] radeon: 1024M of GTT memory ready.
[drm] Loading REDWOOD Microcode
drmn0: could not load firmware image 'radeon/REDWOOD_pfp.bin'
r600_cp: Failed to load firmware "radeon/REDWOOD_pfp.bin"
[drm ERROR :evergreen_init] Failed to load firmware!
drmn0: Fatal error during GPU init
[drm] radeon: finishing device.
[TTM] Finalizing pool allocator
[TTM] Zone  kernel: Used memory at exit: 0 KiB
[TTM] Zone   dma32: Used memory at exit: 0 KiB
[drm] radeon: ttm finalized
Warning: can't remove non-dynamic nodes (dri)!
device_attach: drmn0 attach returned 2
acpi_wmi0:  on acpi0
These are the ports installed:drm-510-kmod-5.10.113_1    DRM drivers modules
drm-kmod-20220501  Metaport of DRM modules for the linuxkpi-based 
KMS components
gpu-firmware-amd-kmod-banks-20220511 Firmware modules for banks AMD GPUs
gpu-firmware-kmod-20220511,1   Firmware modules for the drm-kmod drivers
gpu-firmware-radeon-kmod-aruba-20220511 Firmware modules for aruba Radeon GPUs

FreeBSD STING 14.0-CURRENT FreeBSD 14.0-CURRENT #1 main-85d7875d42: Mon Jun  6 
13:40:11 CEST 2022 filippo@STING:/usr/obj/usr/src/amd64.amd64/sys/STING 
amd64


Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

2022-06-06 Thread Filippo Moretti
 
Is it now safe to attempt updating current with UFS?SincerelyFilippo
On Wednesday, June 1, 2022 at 01:07:20 AM GMT+2, Warner Losh 
 wrote:  
 
 

On Tue, May 31, 2022 at 3:55 PM Olivier Cochard-Labbé  
wrote:

Same problem here:- I'm building FreeBSD head on a builder machine, and NFS 
mounting its /usr/src and /usr/obj to 4 others
Results:- 2 of them, UEFI+ZFS machines works great ((Thinkpad T420 and AMD Epyc 
with Tyan motherboard)- 2 of them, BIOS+UFS machines meet this "can't find 
/boot/ua/loader.lua" (HP microserver and PC Engines APU2)
I had to boot from an USB stick, mounting the system partition and "cp 
boot/loader_4th.old boot/loader".

Kirk found that the boot loader defines MAXPHYS to be 128k, which only is for 
the BIOS loader since it's 32-bit. UEFIis 64-bits and just works because it's 
define to 1MB. So the UEFI machines with ZFS are doubly safe. Kirk has a 
changethat relaxes the check and I think we should do this
diff --git a/sys/sys/param.h b/sys/sys/param.h
index 1f720ed31142..8cd9616e872e 100644
--- a/sys/sys/param.h
+++ b/sys/sys/param.h
@@ -176,7 +176,7 @@
 #define DFLTPHYS       (64 * 1024)     /* default max raw I/O transfer size */
 #endif
 #ifndef MAXPHYS                                /* max raw I/O transfer size */
-#ifdef __ILP32__
+#if defined(__ILP32__) && !defined(_STANDALONE) /* Always 1M for loader */
 #define MAXPHYS                (128 * 1024)
 #else
 #define MAXPHYS                (1024 * 1024)

as well to ensure that the loader always assumes a larger MAXPHYS (though I'd 
kinda like the loader to notdefine it at all, but that is a longer conversation 
after reflection not a quick fix to get people back up andrunning).
Warner  

Problem booting current

2022-06-01 Thread Filippo Moretti
I installed CURRENT with memstick of May the 27th.I tired first UEFI and all I 
got was a flashing - on screenI then tried BIOS+ UEFI and I get a mountroot 
prompt 
due tozfs:zroot/ROOT/default failed with error 22  (wich is the same error I 
got from current a few days ago)reported in a previous message.Are there other 
setting I could try?SincerelyFilippo


Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

2022-05-30 Thread Filippo Moretti
 
I have the same issue after installing my custom kernel and I did not run 
gpart bootcode -bIt was never needed before.FilippoIs there a way to recover 
the system?
On Monday, May 30, 2022 at 07:41:50 AM GMT+2, Toomas Soome  
wrote:  
 
 
> On 30. May 2022, at 04:26, David Wolfskill  wrote:
> 
> On Sun, May 29, 2022 at 06:59:34PM -0600, Warner Losh wrote:
>> Sorry for top posting...
>> 
>> Did you upgrade your boot blocks?
> 
> Thanks for the reply!
> 
> Hmmm  Well, every time I rebuild FreeBSD head, the last step
> just after "make installworld" and before the reboot is:
> 
> # gpart bootcode -b /boot/boot /dev/ada0s4
> 
> So *those* get updated.
> 
> I haven't updated from /boot/boot0 recently (and have a requirement that
> whatever is in the MBR is able to boot stable/12, stable/13, and head).
> 
> Is updating (from head's /boot/bot0) recommended at this point?
>> 
> 
> (And in case it wasn't obvious, I made a silly typo in the Subject; it
> should have read:
> 
> | Subject: Re: Loader can't find /boot/lua/loader.lua on UFS after
> |  main-n255828-18054d0220c
> 
> Sorry: I don't have loader messages showing up on serial console on that
> machine at this point, so I had hand-typed it from memory and managed to
> elide a letter.)
> 

Does loader_4th have same issue?

Rgds,
Toomas 

> Peace,
> david
> -- 
> David H. Wolfskill                              da...@catwhisker.org
> "Putin is a paranoid dictator.  Putin must go. He started a senseless war
> and is leading Russia into a ditch." - Egor Polyakov & Alexandra Miroshnikova
> 
> See https://www.catwhisker.org/~david/publickey.gpg for my public key.
  

Re: Problem booting CURRENT

2022-05-30 Thread Filippo Moretti
 After world I can no longer boot my system:cannot open /boot/lua/loader:no 
such file or directory
If I try 
load  /boot/kernel.old/kernel /boot/kernel/kernel
can't find /boot/kernel.old/kernel nor /boot/kernel/kernelIt is rather strange 
I have never found these issues before.Filippo
On Monday, May 30, 2022 at 09:34:43 AM GMT+2, Filippo Moretti 
 wrote:  
 
  I did not use GELI non was the hard disk encrypted.I did try to reinstall 
with snapshot of May the 27th and I had the same problem:I ended up 
reinstalling with UFS instead.Than you 
Filippo 

On Sunday, May 29, 2022 at 11:49:01 PM GMT+2, Graham Perrin 
 wrote:  
 
  On 27/05/2022 10:10, Filippo Moretti wrote:
  
 
 I run into this problem after rebboting my computer with CURRENT 
zfs:zroot/ROOT/default failed with error 22 the mountroot freezes and I have to 
power off to restart. I did not apgrade or any changes since I used it last 
time. Is it possible to recover my system? Filippo
   GELI encrypted?
 

Re: Problem booting CURRENT

2022-05-30 Thread Filippo Moretti
 I did not use GELI non was the hard disk encrypted.I did try to reinstall with 
snapshot of May the 27th and I had the same problem:I ended up reinstalling 
with UFS instead.Than you 
Filippo 

On Sunday, May 29, 2022 at 11:49:01 PM GMT+2, Graham Perrin 
 wrote:  
 
  On 27/05/2022 10:10, Filippo Moretti wrote:
  
 
 I run into this problem after rebboting my computer with CURRENT 
zfs:zroot/ROOT/default failed with error 22 the mountroot freezes and I have to 
power off to restart. I did not apgrade or any changes since I used it last 
time. Is it possible to recover my system? Filippo
   GELI encrypted?
   

Problem booting CURRENT

2022-05-27 Thread Filippo Moretti
I run into this problem after rebboting my computer with 
CURRENTzfs:zroot/ROOT/default failed with error 22the mountroot freezes and I 
have to power off to restart.I did not apgrade or any changes since I used it 
last time.Is it possible to recover my system?Filippo


Problem compiling llvm14

2022-03-26 Thread Filippo Moretti
 File "", line 219, in _call_with_frames_removed  
File "/usr/local/lib/python3.8/site-packages/sphinx/cmd/build.py", line 25, in 
    from sphinx.application import Sphinx  File 
"/usr/local/lib/python3.8/site-packages/sphinx/application.py", line 43, in 
    from sphinx.registry import SphinxComponentRegistry  File 
"/usr/local/lib/python3.8/site-packages/sphinx/registry.py", line 24, in 
    from pkg_resources import iter_entry_points  File 
"/usr/local/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3243, 
in     def _initialize_master_working_set():  File 
"/usr/local/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3226, 
in _call_aside    f(*args, **kwargs)  File 
"/usr/local/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3255, 
in _initialize_master_working_set    working_set = WorkingSet._build_master()  
File "/usr/local/lib/python3.8/site-packages/pkg_resources/__init__.py", line 
570, in _build_master    return cls._build_from_requirements(__requires__)  
File "/usr/local/lib/python3.8/site-packages/pkg_resources/__init__.py", line 
583, in _build_from_requirements    dists = ws.resolve(reqs, Environment())  
File "/usr/local/lib/python3.8/site-packages/pkg_resources/__init__.py", line 
772, in resolve    raise DistributionNotFound(req, 
requirers)pkg_resources.DistributionNotFound: The 'idna<3,>=2.5' distribution 
was not found and is required by requestsninja: build stopped: subcommand 
failed.*** Error code 1
Stop.make[1]: stopped in /usr/ports/devel/llvm14*** Error code 1
Stop.make: stopped in /usr/ports/devel/llvm14
This is the error I have while compiling llvm14 onFreeBSD sting 14.0-CURRENT 
FreeBSD 14.0-CURRENT #70 heads/main-n253908-f9413897cb8: Wed Mar 23 17:24:20 
CET 2022     filippo@sting:/usr/obj/usr/src/amd64.amd64/sys/STING amd64



Error building openoffice in current

2022-02-25 Thread Filippo Moretti
gmake[1]: Leaving directory 
'/usr/ports/editors/openoffice-4/work/aoo-4.1.11/main/sw'
sw deliver
deliver -- version: 275594
COPY: build.lst -> 
/usr/ports/editors/openoffice-4/work/aoo-4.1.11/main/solver/4111/unxfbsdx.pro/inc/sw/build.lst
LOG: writing 
/usr/ports/editors/openoffice-4/work/aoo-4.1.11/main/solver/4111/unxfbsdx.pro/inc/sw/deliver.log
Module 'sw' delivered successfully. 1 files copied, 0 files unchanged

1 module(s): 
    testtools
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making 
/usr/ports/editors/openoffice-4/work/aoo-4.1.11/main/testtools/source/bridgetest

When you have fixed the errors in that module you can resume the build by 
running:

    build --from testtoolsI get this error when trying to update 
openoffice-4any help appreciatedFilippo



Problem compiling firefox

2022-02-08 Thread Filippo Moretti
/usr/local/bin/clang++13 -std=gnu++17 --target=wasm32-wasi 
--sysroot=/usr/local/share/wasi-sysroot -o rlbox.wasm -Wl,--export-all 
-Wl,--stack-first -Wl,-z,stack-size=262144 -Wl,--no-entry -Wl,--growable-table 
ogg_alloc.wasm ogg_bitwise.wasm ogg_framing.wasm xmlparse.wasm xmlrole.wasm 
xmltok.wasm wasm2c_sandbox_wrapper.wasm mozHunspellRLBoxSandbox.wasm 
affentry.wasm affixmgr.wasm csutil.wasm hashmgr.wasm hunspell.wasm phonet.wasm 
replist.wasm suggestmgr.wasm GraphiteExtra.wasm CmapCache.wasm Code.wasm 
Collider.wasm Decompressor.wasm Face.wasm FeatureMap.wasm FileFace.wasm 
Font.wasm GlyphCache.wasm GlyphFace.wasm Intervals.wasm Justifier.wasm 
NameTable.wasm Pass.wasm Position.wasm Segment.wasm Silf.wasm Slot.wasm 
Sparse.wasm TtfUtil.wasm UtfCodec.wasm call_machine.wasm gr_char_info.wasm 
gr_face.wasm gr_features.wasm gr_font.wasm gr_logging.wasm gr_segment.wasm 
gr_slot.wasm json.wasm RLBoxWOFF2Sandbox.wasm table_tags.wasm 
variable_length.wasm woff2_common.wasm woff2_dec.wasm woff2_out.wasm 
-lwasi-emulated-process-clockswasm-ld: error: cannot open 
/usr/local/llvm13/lib/clang/13.0.1/lib/wasi/libclang_rt.builtins-wasm32.a: No 
such file or directoryclang-13: error: linker command failed with exit code 1 
(use -v to see invocation)gmake[5]: *** 
[/usr/ports/www/firefox/work/firefox-97.0/config/rules.mk:498: rlbox.wasm] 
Error 1gmake[5]: Leaving directory 
'/usr/ports/www/firefox/work/.build/security/rlbox'gmake[4]: *** 
[/usr/ports/www/firefox/work/firefox-97.0/config/recurse.mk:72: 
security/rlbox/target-objects] Error 2gmake[4]: Leaving directory 
'/usr/ports/www/firefox/work/.build'gmake[3]: *** 
[/usr/ports/www/firefox/work/firefox-97.0/config/recurse.mk:34: compile] Error 
2gmake[3]: Leaving directory '/usr/ports/www/firefox/work/.build'gmake[2]: *** 
[/usr/ports/www/firefox/work/firefox-97.0/config/rules.mk:352: all] Error 
2gmake[2]: Leaving directory '/usr/ports/www/firefox/work/.build'*** Error code 
1
Stop.make[1]: stopped in /usr/ports/www/firefox*** Error code 1
Stop.make: stopped in /usr/ports/www/firefox[root@sting 
/usr/ports/www/firefox]# 
This is the error I get while  attempting to update firefox from port
[root@sting /usr/ports/www/firefox]# uname -aFreeBSD sting 14.0-CURRENT FreeBSD 
14.0-CURRENT #67 heads/main-n252631-ccf50c1df9c: Tue Jan 25 22:12:38 CET 2022   
  filippo@sting:/usr/obj/usr/src/amd64.amd64/sys/STING  amd64
sincerelyFilippo

Problem compiling ports

2021-11-30 Thread Filippo Moretti via current
error: unable to create target: 'No available targets are compatible with 
triple "wasm32-unknown-wasi"'
1 error generated.
gmake[3]: *** [Makefile:380: 
/usr/ports/devel/wasi-libc/work/wasi-libc-ad5133410f66b93a2381db5b542aad5e0964db96/build/dlmalloc/src/dlmalloc.o]
 Error 1
error: unable to create target: 'No available targets are compatible with 
triple "wasm32-unknown-wasi"'
1 error generated.
gmake[3]: *** [Makefile:440: startup_files] Error 1
gmake[3]: Leaving directory 
'/usr/ports/devel/wasi-libc/work/wasi-libc-ad5133410f66b93a2381db5b542aad5e0964db96'
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1

Stop.
make[2]: stopped in /usr/ports/devel/wasi-libc
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/devel/wasi-libcxx*** Error code 1

Stop.
make: stopped in /usr/ports/www/firefox

===>>> make build failed for www/firefox
===>>> Aborting update


 File "/usr/local/lib/python3.8/site-packages/setuptools/dist.py", line 799, in 

    eps = map(lambda e: e.load(), pkg_resources.iter_entry_points(group))
  File "/usr/local/lib/python3.8/site-packages/pkg_resources/__init__.py", line 
2449, in load
    self.require(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/pkg_resources/__init__.py", line 
2472, in require
    items = working_set.resolve(reqs, env, installer, extras=self.extras)
  File "/usr/local/lib/python3.8/site-packages/pkg_resources/__init__.py", line 
772, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'packaging>=20.0' distribution was not 
found and is required by the application
*** Error code 1

Stop.
make: stopped in /usr/ports/devel/py-pycparser

===>>> make build failed for devel/py-pycparser@py38
===>>> Aborting update

FreeBSD sting 14.0-CURRENT FreeBSD 14.0-CURRENT #62 
heads/main-n251146-d109559ddbf: Mon Nov 29 12:18:48 CET 2021 
root@sting:/usr/obj/usr/src/amd64.amd64/sys/STING  amd64




Problem with newer version of firefox

2021-11-19 Thread Filippo Moretti via current
Good morning,                     after upgrading firefox I get the following 
error:XPCOMGlueLoad error for file /usr/local/lib/firefox/libxul.so:Shared 
object "libmozsqlite3.so" not found, required by "libxul.so"Couldn't load XPCOM.
it is present in the directory /usr/local/lib/firefox/libmozsqlite3.soI then 
symlinked the above to /usr/local/lib and got this error:XPCOMGlueLoad error 
for file 
/usr/local/lib/firefox/libxul.so:/usr/local/lib/firefox/libmozsqlite3.so: 
version libmozsqlite3.so required by /usr/local/lib/firefox/libxul.so not 
defined FreeBSD sting 14.0-CURRENT FreeBSD 14.0-CURRENT #61 
heads/main-n250837-5085153ae4d: Thu Nov 18 21:57:09 CET 2021     
filippo@sting:/usr/obj/usr/src/amd64.amd64/sys/STING  amd64
Any help appreciatedsincerelyFilippo

Error during installkernel

2021-10-26 Thread Filippo Moretti via current
I tried to update my system today everything fine but installkernel:==> zlib 
(install)install -T release -o root -g wheel -m 555 zlib.ko 
/boot/kernel/install -T dbg -o root -g wheel -m 555 zlib.ko.debug 
/usr/lib/debug/boot/kernel/kldxref /boot/kernelfailed to read 
progbitsef_read_entry failed*** Signal 11Stop.make[3]: stopped in 
/usr/src/sys/modules*** Error code 1Stop.make[2]: stopped in 
/usr/obj/usr/src/amd64.amd64/sys/STING*** Error code 1Stop.make[1]: stopped in 
/usr/src*** Error code 1Stop.make: stopped in /usr/src[root@sting /usr/src]# 

[root@sting /usr/src]# uname -aFreeBSD sting 14.0-CURRENT FreeBSD 14.0-CURRENT 
#57 heads/main-n250195-6ba2210ee03: Thu Oct 21 21:19:23 CEST 2021 
filippo@sting:/usr/obj/usr/src/amd64.amd64/sys/STING amd64 Filippo


Error in buildkernel

2021-07-29 Thread Filippo Moretti via current
Good morning,    I have the following error in build 
kernel:ror=unused-function -Wno-error=pointer-sign 
-Wno-error=shift-negative-value -Wno-address-of-packed-member 
-Wno-format-zero-length   -mno-aes -mno-avx  -std=iso9899:1999 -Werror vers.c
ctfconvert -L VERSION -g vers.o
linking kernel.full
ld: error: undefined symbol: xen_clock_init
>>> referenced by pv.c
>>>   pv.o:(xen_pvh_init_ops)

ld: error: undefined symbol: xen_delay
>>> referenced by pv.c
>>>   pv.o:(xen_pvh_init_ops)
*** Error code 1

Stop.
make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/STING
*** Error code 1

Stop.
make[1]: stopped in /usr/src

[root@sting /usr/src]# uname -a
FreeBSD sting 14.0-CURRENT FreeBSD 14.0-CURRENT #43 main-n248147-8539518055d: 
Thu Jul 22 11:36:29 CEST 2021 
root@sting:/usr/obj/usr/src/amd64.amd64/sys/STING  amd64

sincerelyFilippo


Fw: Problem building openoffice

2021-06-30 Thread Filippo Moretti via current
 

   - Forwarded Message - From: Filippo Moretti 
To: off...@freebsd.org Sent: 
Wednesday, June 30, 2021, 10:42:48 AM GMT+2Subject: Problem building openoffice
 Good morning,    I get the following error while 
attempting to update openoffice-4 on amd64 arc on current:1 module(s): 
    sccomp
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making 
/usr/ports/editors/openoffice-4/work/aoo-4.1.10/main/sccomp/source/solver

When you have fixed the errors in that module you can resume the build by 
running:

    build --from sccomp

*** Error code 1

Stop.
make: stopped in /usr/ports/editors/openoffice-4

I never had this problem before and I do not know how to rebuild the module any 
help appreciatedsincrelyFilippo
  

Re: Problem compiling world

2021-05-29 Thread Filippo Moretti via current
 Yes I doFilippo

On Saturday, May 29, 2021, 12:37:46 PM GMT+2, Hans Petter Selasky 
 wrote:  
 
 On 5/29/21 10:25 AM, Filippo Moretti via current wrote:
> I have the following error while compiling world:--- linux_genalloc.o ---In 
> file included from /usr/local/sys/modules/drm-current-kmod/linuxkpi/gplv2/src 
> /linux_genalloc.c:35:In file included from 
> /usr/src/sys/compat/linuxkpi/common/include/linux/interrup t.h:35:In file 
> included from /usr/local/sys/modules/drm-current-kmod/linuxkpi/gplv2/inc 
> lude/linux/device.h:4:In file included from 
> /usr/src/sys/compat/linuxkpi/common/include/linux/device.h :36:In file 
> included from /usr/src/sys/compat/linuxkpi/common/include/linux/kobject. 
> h:36:/usr/local/sys/modules/drm-current-kmod/linuxkpi/gplv2/include/linux/kernel.h:12
>  :10: fatal error: 'linux/kconfig.h' file not found#include 
> ^--- linux_compat.o ---1 error generated.*** [linux_compat.o] 
> Error code 1make[4]: stopped in 
> /usr/local/sys/modules/drm-current-kmod/linuxkpimake[1]: stopped in 
> /usr/srcmake: stopped in /usr/src[root@sting /usr/src]#
> 
> 
> 
> 
> FreeBSD sting 14.0-CURRENT FreeBSD 14.0-CURRENT #38 main-n246776-f17a5900850: 
> Thu May 20 20:40:36 CEST 2021 
> root@sting:/usr/obj/usr/src/amd64.amd64/sys/STING amd64 The error is 
> repeatable and make cleandir did not solve the problem.Filippo
> 

Hi,

Are you using the latest version of the drm-current-kmod from ports?

--HPS

  

Problem compiling world

2021-05-29 Thread Filippo Moretti via current
I have the following error while compiling world:--- linux_genalloc.o ---In 
file included from /usr/local/sys/modules/drm-current-kmod/linuxkpi/gplv2/src 
/linux_genalloc.c:35:In file included from 
/usr/src/sys/compat/linuxkpi/common/include/linux/interrup t.h:35:In file 
included from /usr/local/sys/modules/drm-current-kmod/linuxkpi/gplv2/inc 
lude/linux/device.h:4:In file included from 
/usr/src/sys/compat/linuxkpi/common/include/linux/device.h :36:In file included 
from /usr/src/sys/compat/linuxkpi/common/include/linux/kobject. 
h:36:/usr/local/sys/modules/drm-current-kmod/linuxkpi/gplv2/include/linux/kernel.h:12
 :10: fatal error: 'linux/kconfig.h' file not found#include 
^--- linux_compat.o ---1 error generated.*** [linux_compat.o] 
Error code 1make[4]: stopped in 
/usr/local/sys/modules/drm-current-kmod/linuxkpimake[1]: stopped in 
/usr/srcmake: stopped in /usr/src[root@sting /usr/src]# 




FreeBSD sting 14.0-CURRENT FreeBSD 14.0-CURRENT #38 main-n246776-f17a5900850: 
Thu May 20 20:40:36 CEST 2021 root@sting:/usr/obj/usr/src/amd64.amd64/sys/STING 
amd64 The error is repeatable and make cleandir did not solve the 
problem.Filippo


Re: Problem with Xorg

2021-05-23 Thread Filippo Moretti via current
 
I have installed drm-current-kmod and drm-current-kmod from ports and I have in 
/etc/rc.confkld_list="/boot/modules/radeonkms.ko"sincerelyFilippo
On Saturday, May 22, 2021, 8:25:24 PM GMT+2, Kevin Oberman 
 wrote:  
 
 On Sat, May 22, 2021 at 5:14 AM Filippo Moretti via current 
 wrote:



FreeBSD sting 14.0-CURRENT FreeBSD 14.0-CURRENT #38 main-n246776-f17a5900850: 
Thu May 20 20:40:36 CEST 2021 
root@sting:/usr/obj/usr/src/amd64.amd64/sys/STING  amd64

I get the following error when I start Xorg (xinit)scfb trace probe startscfb 
trace probe doneMESA-LOADER: failed to open r600 (search path 
/usr/local/lib/dri)failed to load driverfailed to open kms-swrastfailed to open 
swrast

This is the directory as currently installed


[root@sting /home/filippo]# ls -la /usr/local/lib/dritotal 209536
drwxr-xr-x   2 root  wheel    15 Apr  2 13:36 .
drwxr-xr-x  68 root  wheel  2102 May 21 01:30 ..
-rwxr-xr-x   4 root  wheel  14255896 Apr  2 13:26 i915_dri.so
-rwxr-xr-x   4 root  wheel  14255896 Apr  2 13:26 i965_dri.so
-rwxr-xr-x   7 root  wheel  19473448 Apr  2 13:26 iris_dri.so
-rwxr-xr-x   7 root  wheel  19473448 Apr  2 13:26 kms_swrast_dri.so
-rwxr-xr-x   4 root  wheel  14255896 Apr  2 13:26 r200_dri.so
-rwxr-xr-x   7 root  wheel  19473448 Apr  2 13:26 r300_dri.so
-rwxr-xr-x   7 root  wheel  19473448 Apr  2 13:26 r600_dri.so
-rwxr-xr-x   2 root  wheel   7073256 Apr  2 13:36 r600_drv_video.so
-rwxr-xr-x   4 root  wheel  14255896 Apr  2 13:26 radeon_dri.so
-rwxr-xr-x   7 root  wheel  19473448 Apr  2 13:26 radeonsi_dri.so
-rwxr-xr-x   2 root  wheel   7073256 Apr  2 13:36 radeonsi_drv_video.so
-rwxr-xr-x   7 root  wheel  19473448 Apr  2 13:26 swrast_dri.so
-rwxr-xr-x   7 root  wheel  19473448 Apr  2 13:26 vmwgfx_dri.so
Any help appreciatedFilippo

Which DRM kernel (drm-kmod) is installed and how is it loaded? Look at 
/var/log/Xorg.0.log for the actual problem if the drm kernel module is not the 
issue. (N.B. DRM, in this context, is Digital Rendering Module, not Digital 
Rights Management.)
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683   

Problem compiling harfbuzz

2021-05-04 Thread Filippo Moretti via freebsd-current
Good morning,    harfbuzz did not compile with he following 
error:  File 
"/usr/local/lib/python3.8/site-packages/mesonbuild/modules/gnome.py", line 449, 
in _get_dependencies_flags
    if use_gir_args and self._gir_has_option('--extra-library'):
  File "/usr/local/lib/python3.8/site-packages/mesonbuild/modules/gnome.py", 
line 498, in _gir_has_option
    p, o, e = Popen_safe(exe.get_command() + ['--help'], 
stderr=subprocess.STDOUT)
  File 
"/usr/local/lib/python3.8/site-packages/mesonbuild/mesonlib/universal.py", line 
1320, in Popen_safe
    p = subprocess.Popen(args, universal_newlines=True, close_fds=False,
  File "/usr/local/lib/python3.8/subprocess.py", line 858, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/local/lib/python3.8/subprocess.py", line 1704, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 
'/usr/local/bin/g-ir-scanner'
===>  Script "configure" failed unexpectedly.
Please report the problem to desk...@freebsd.org [maintainer] and attach the
"/usr/ports/print/harfbuzz/work/harfbuzz-2.8.1/_build/meson-logs/meson-log.txt"
including the output of the failure of your make command. Also, it might be
a good idea to provide an overview of all packages installed 

My setup:FreeBSD STING FreeBSD STING 14.0-CURRENT FreeBSD 14.0-CURRENT #24 
main-n246214-78ffcb86d98: Tue Apr 20 17:51:50 CEST 2021 
root@STING:/usr/obj/usr/src/amd64.amd64/sys/STING  amd64

regardsFilippo


___
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"


base compiler & build options

2021-04-22 Thread Filippo Moretti via freebsd-current
I run FreeBSD STING 14.0-CURRENT FreeBSD 14.0-CURRENT #24 
main-n246214-78ffcb86d98: Tue Apr 20 17:51:50 CEST 2021 
root@STING:/usr/obj/usr/src/amd64.amd64/sys/STING  amd64

will llvm12 be merged on main or should I get it manually?In order to only 
build amd64 is it correct 
toWITHOUT_LLVM_TARGET_ALLWITH_LLVM_TARGET_X86sincerelyFilippo
___
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"


Problem compiling libgit2

2021-04-06 Thread Filippo Moretti via freebsd-current
After moving ports to git I had the following error while updating libgit2:===> 
 Extracting for libgit2-1.1.0
=> ===>  Extracting for libgit2-1.1.0
=> SHA256 Checksum OK for libgit2-1.1.0.tar.gz.
===>  Patching for libgit2-1.1.0
sed: 
/usr/ports/devel/libgit2/work/libgit2-1.1.0/cmake/Modules/SelectHTTPSBackend.cmake:
 No such file or directory
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/devel/libgit2
*** Error code 1

Stop.
make: stopped in /usr/ports/devel/libgit2


my system:root@STING /usr/ports/devel/libgit2]# uname -a
FreeBSD STING 14.0-CURRENT FreeBSD 14.0-CURRENT #23 main-n245729-51cc31088bf: 
Tue Mar 30 18:58:45 CEST 2021 
root@STING:/usr/obj/usr/src/amd64.amd64/sys/STING  amd64

Filippo
___
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: On 14-CURRENT: no ports options anymore?

2021-03-13 Thread Filippo Moretti via freebsd-current
 > Rebuilding the port (ports-mgmt/dialog4ports) solved it for me,for me too
Thank youFilippo

On Saturday, March 13, 2021, 9:13:46 PM GMT+1, Michael Butler via 
freebsd-current  wrote:  
 
 On 3/13/21 3:00 PM, Hartmann, O. wrote:
> On Sat, 13 Mar 2021 19:52:47 + (UTC)
> Filippo Moretti via freebsd-current  wrote:
> 
>>  
>> I had the same problem in console modeFiippo
>>      On Saturday, March 13, 2021, 8:33:57 PM GMT+1, Stefan Esser 
>> wrote:
>>
>>  Am 13.03.21 um 20:17 schrieb Hartmann, O.:
>>> Since I moved on to 14-CURRENT, I face a very strange behaviour when trying 
>>> to set
>>> options via "make config" or via poudriere accordingly. I always get "===> 
>>> Options
>>> unchanged" (when options has been already set and I'd expect a dialog menu).
>>> This misbehaviour is throughout ALL 14-CURRENT systems (the oldest is at 
>>> FreeBSD
>>> 14.0-CURRENT #49 main-n245422-cecfaf9bede9: Fri Mar 12 16:08:09 CET 2021 
>>> amd64).
>>>
>>> I do not see such a behaviour with 13-STABLE, 12-STABLE, 12.2-RELENG.
>>>
>>> How to fix this? What happened?
>>
>> Hi Oliver,
>>
>> please check your TERM setting and test with a trivial setting
>> if it is not one of xterm, vt100 or vt320 (for example).
>>
>> I had this problem when my TERM variable was xterm-color, which
>> used to be supported but apparently no longer is.
>>
>> Regards, STefan
> 
> [...]
> 
> on one of the hosts (non-X11), loged in via ssh, the settings are:
> 
> # echo $TERM
> xterm
> cd /usr/ports/www/apache24
> make config
> ===> Options unchanged (no menu popping up)
> 

I ran into something similar where dialog4ports would dump core after an 
upgrade. Rebuilding the port (ports-mgmt/dialog4ports) solved it for me,

    imb


___
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"
  
___
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: On 14-CURRENT: no ports options anymore?

2021-03-13 Thread Filippo Moretti via freebsd-current
 
I had the same problem in console modeFiippo
On Saturday, March 13, 2021, 8:33:57 PM GMT+1, Stefan Esser 
 wrote:  
 
 Am 13.03.21 um 20:17 schrieb Hartmann, O.:
> Since I moved on to 14-CURRENT, I face a very strange behaviour when trying 
> to set
> options via "make config" or via poudriere accordingly. I always get "===> 
> Options
> unchanged" (when options has been already set and I'd expect a dialog menu).
> This misbehaviour is throughout ALL 14-CURRENT systems (the oldest is at 
> FreeBSD
> 14.0-CURRENT #49 main-n245422-cecfaf9bede9: Fri Mar 12 16:08:09 CET 2021 
> amd64).
> 
> I do not see such a behaviour with 13-STABLE, 12-STABLE, 12.2-RELENG.
> 
> How to fix this? What happened?

Hi Oliver,

please check your TERM setting and test with a trivial setting
if it is not one of xterm, vt100 or vt320 (for example).

I had this problem when my TERM variable was xterm-color, which
used to be supported but apparently no longer is.

Regards, STefan

  
___
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: Problem compiling gcc10

2021-03-06 Thread Filippo Moretti via freebsd-current
 This is the output from MAKE_JOBS_UNSAFE=yes





checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... configure: error: in 
`/usr/ports/lang/gcc10/work/.build/x86_64-portbld-freebsd14.0/32/libgcc':
configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details
gmake[4]: *** [Makefile:17191: configure-stage1-target-libgcc] Error 1
gmake[4]: Leaving directory '/usr/ports/lang/gcc10/work/.build'
gmake[3]: *** [Makefile:22903: stage1-bubble] Error 2
gmake[3]: Leaving directory '/usr/ports/lang/gcc10/work/.build'
gmake[2]: *** [Makefile:23235: bootstrap-lean] Error 2
gmake[2]: Leaving directory '/usr/ports/lang/gcc10/work/.build'
*** Error code 1

Stop.


On Friday, March 5, 2021, 9:28:52 PM GMT+1, Dimitry Andric 
 wrote:  
 
 On 5 Mar 2021, at 18:19, Filippo Moretti via freebsd-current 
 wrote:
> 
> The following is the error while compiling on:
> [root@sting /usr/ports]# uname -aFreeBSD sting 14.0-CURRENT FreeBSD 
> 14.0-CURRENT #32 main-n245104-dfff1de729b: Fri Feb 26 12:08:40 CET 2021 
> root@sting:/usr/obj/usr/src/amd64.amd64/sys/STING amd64
> 
> gmake[6]: *** [Makefile:1212: multi-do] Error 1gmake[6]: Leaving directory 
> '/usr/ports/lang/gcc10/work/.build/x86_64-portbld-fr 
> eebsd14.0/libgcc'gmake[5]: *** [Makefile:127: all-multi] Error 2gmake[5]: *** 
> Waiting for unfinished jobsgmake[5]: Leaving directory 
> '/usr/ports/lang/gcc10/work/.build/x86_64-portbld-fr 
> eebsd14.0/libgcc'gmake[4]: *** [Makefile:17599: all-stage1-target-libgcc] 
> Error 2gmake[4]: Leaving directory 
> '/usr/ports/lang/gcc10/work/.build'gmake[3]: *** [Makefile:22903: 
> stage1-bubble] Error 2gmake[3]: Leaving directory 
> '/usr/ports/lang/gcc10/work/.build'gmake[2]: *** [Makefile:23235: 
> bootstrap-lean] Error 2gmake[2]: Leaving directory 
> '/usr/ports/lang/gcc10/work/.build'===> Compilation failed unexpectedly.Try 
> to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure tothe 
> maintainer.*** Error code 1Stop.make[1]: stopped in /usr/ports/lang/gcc10*** 
> Error code 1

Hi Filippo,

Unfortunately the actual error is earlier in the build, so it is not
shown, and your log is wrapped very strangely. Can you run the build
under script(1) and upload a full build log somewhere?

Alternatively, you can set MAKE_JOBS_UNSAFE=yes so it would use a single
job make, and it should then show the error more clearly at the end. But
this is likely to take a bit longer to build.

-Dimitry

  

signature.asc
Description: PGP signature
___
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"


Problem compiling gcc10

2021-03-05 Thread Filippo Moretti via freebsd-current
The following is the error while compiling on:
[root@sting /usr/ports]# uname -aFreeBSD sting 14.0-CURRENT FreeBSD 
14.0-CURRENT #32 main-n245104-dfff1de729b: Fri Feb 26 12:08:40 CET 2021 
root@sting:/usr/obj/usr/src/amd64.amd64/sys/STING amd64





gmake[6]: *** [Makefile:1212: multi-do] Error 1gmake[6]: Leaving directory 
'/usr/ports/lang/gcc10/work/.build/x86_64-portbld-fr eebsd14.0/libgcc'gmake[5]: 
*** [Makefile:127: all-multi] Error 2gmake[5]: *** Waiting for unfinished 
jobsgmake[5]: Leaving directory 
'/usr/ports/lang/gcc10/work/.build/x86_64-portbld-fr eebsd14.0/libgcc'gmake[4]: 
*** [Makefile:17599: all-stage1-target-libgcc] Error 2gmake[4]: Leaving 
directory '/usr/ports/lang/gcc10/work/.build'gmake[3]: *** [Makefile:22903: 
stage1-bubble] Error 2gmake[3]: Leaving directory 
'/usr/ports/lang/gcc10/work/.build'gmake[2]: *** [Makefile:23235: 
bootstrap-lean] Error 2gmake[2]: Leaving directory 
'/usr/ports/lang/gcc10/work/.build'===> Compilation failed unexpectedly.Try to 
set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure tothe 
maintainer.*** Error code 1Stop.make[1]: stopped in /usr/ports/lang/gcc10*** 
Error code 1
___
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: Problem with drm

2021-01-15 Thread Filippo Moretti
 
Yes the port is up to date and I did rebuild from ports drm-current-kmod 
gpu-firmware-kmod and drm-kmodFilippo
On Friday, January 15, 2021, 10:29:38 AM GMT+1, Hans Petter Selasky 
 wrote:  
 
 On 1/15/21 10:11 AM, Filippo Moretti wrote:
> After upgrading my custom kernel I get the following error (that did not 
> occur before hid):hidbus0:  on usbhid0
> link_elf_obj: symbol linux_pci_get_class undefined
> Warning: memory type debugfsint leaked memory on destroy (2 allocations, 80 
> bytes leaked).
> linker_load_file: /boot/modules/radeonkms.ko - unsupported file type
> 
> Also the generic kernel was working fine before I upgraded my kernel STING 
> now it no longer works and Xorg start with scfb instead of radeon kms.After 
> completing installworld I always rebuild from ports drm-current-kmod 
> gpu-firmware-kmod drm-kmod.SincerelyFilippo

Is your ports updated to the latest?

Looks like radeonkms was not re-build after upgrading and installing the 
sources.

--HPS

___
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"
  
___
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"


Problem with drm

2021-01-15 Thread Filippo Moretti
After upgrading my custom kernel I get the following error (that did not occur 
before hid):hidbus0:  on usbhid0
link_elf_obj: symbol linux_pci_get_class undefined
Warning: memory type debugfsint leaked memory on destroy (2 allocations, 80 
bytes leaked).
linker_load_file: /boot/modules/radeonkms.ko - unsupported file type

Also the generic kernel was working fine before I upgraded my kernel STING now 
it no longer works and Xorg start with scfb instead of radeon kms.After 
completing installworld I always rebuild from ports drm-current-kmod 
gpu-firmware-kmod drm-kmod.SincerelyFilippo
___
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"


Problem compiling drm-current-kmod

2021-01-13 Thread Filippo Moretti
Good morning,    my system:[root@STING 
/usr/ports/graphics/drm-current-kmod]# uname -a
FreeBSD STING 13.0-CURRENT FreeBSD 13.0-CURRENT #16 main-c255860-g2903606b606: 
Tue Jan 12 04:59:16 CET 2021 
root@STING:/usr/obj/usr/src/amd64.amd64/sys/STING  amd64

I get the following error while trying to upgrade drm-current-kmod from 
ports:/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.62_6/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:4009:6:
 error: implicit declaration of function 'pci_is_root_bus' is invalid in C99 
[-Werror,-Wimplicit-function-declaration]
    if (pci_is_root_bus(adev->pdev->bus)) {
    ^
/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.62_6/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:4009:6:
 note: did you mean 'pci_set_bus'?
/usr/src/sys/dev/pci/pcivar.h:385:1: note: 'pci_set_bus' declared here
PCI_ACCESSOR(bus,   BUS,    uint8_t)
^
/usr/src/sys/dev/pci/pcivar.h:371:2: note: expanded from macro 'PCI_ACCESSOR'
    __BUS_ACCESSOR(pci, var, PCI, ivar, type)
    ^
/usr/src/sys/sys/bus.h:812:22: note: expanded from macro '__BUS_ACCESSOR'
static __inline void varp ## _set_ ## var(device_t dev, type t) \
 ^
:77:1: note: expanded from here
pci_set_bus
^
1 error generated.*** Error code 1

Stop.
make[4]: stopped in 
/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.62_6/amd/amdgpu
*** Error code 1
*** Error code 1
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/graphics/drm-current-kmod
*** Error code 1

Stop.
make: stopped in /usr/ports/graphics/drm-current-kmod

Filippo
___
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"


Problem compiling custom kernel

2021-01-09 Thread Filippo Moretti
I tried to compile my custom kernel but I did get the following error,I enclose 
the beginning of dmesg output.So far I could always build kernel STING.I did 
switch to git and previously I could build it without issues.sincerelyFilippo

Copyright (c) 1992-2021 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
    The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 13.0-CURRENT #2 main-c255755-g6815909abda: Sat Jan  9 14:38:37 CET 2021
    root@sting:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64
FreeBSD clang version 11.0.1 (g...@github.com:llvm/llvm-project.git 
llvmorg-11.0.1-rc2-0-g43ff75f2c3f)
WARNING: WITNESS option enabled, expect reduced performance.
VT(vga): resolution 640x480
CPU: AMD Phenom(tm) II X4 965 Processor (3411.42-MHz K8-class CPU)
  Origin="AuthenticAMD"  Id=0x100f43  Family=0x10  Model=0x4  Stepping=3
  
Features=0x178bfbff
  Features2=0x802009
  AMD 
Features=0xee500800
  AMD 
Features2=0x37ff
  SVM: NP,NRIP,NAsids=64








--- kernel.full ---linking kernel.full
ld: error: undefined symbol: hid_is_keyboard
>>> referenced by ukbd.c:957 (/usr/src/sys/dev/usb/input/ukbd.c:957)
>>>   ukbd.o:(ukbd_probe)
ld: error: undefined symbol: hid_is_mouse
>>> referenced by ukbd.c:958 (/usr/src/sys/dev/usb/input/ukbd.c:958)
>>>   ukbd.o:(ukbd_probe)
ld: error: undefined symbol: hid_report_size_max
>>> referenced by ukbd.c:988 (/usr/src/sys/dev/usb/input/ukbd.c:988)
>>>   ukbd.o:(ukbd_parse_hid)
>>> referenced by ukbd.c:1038 (/usr/src/sys/dev/usb/input/ukbd.c:1038)
>>>   ukbd.o:(ukbd_parse_hid)
ld: error: undefined symbol: hid_locate
>>> referenced by ukbd.c:992 (/usr/src/sys/dev/usb/input/ukbd.c:992)>>> 
>>>   ukbd.o:(ukbd_parse_hid)
>>> referenced by ukbd.c:1001 (/usr/src/sys/dev/usb/input/ukbd.c:1001)
>>>   ukbd.o:(ukbd_parse_hid)
>>> referenced by ukbd.c:1011 (/usr/src/sys/dev/usb/input/ukbd.c:1011)
>>>   ukbd.o:(ukbd_parse_hid)
>>> referenced 4 more times
ld: error: undefined symbol: hid_get_data
>>> referenced by ukbd.c:695 (/usr/src/sys/dev/usb/input/ukbd.c:695)
>>>   ukbd.o:(ukbd_intr_callback)
>>> referenced by ukbd.c:700 (/usr/src/sys/dev/usb/input/ukbd.c:700)
>>>   ukbd.o:(ukbd_intr_callback)
>>> referenced by ukbd.c:734 (/usr/src/sys/dev/usb/input/ukbd.c:734)
>>>   ukbd.o:(ukbd_intr_callback)
ld: error: undefined symbol: hid_get_udata
>>> referenced by ukbd.c:722 (/usr/src/sys/dev/usb/input/ukbd.c:722)
>>>   ukbd.o:(ukbd_intr_callback)
ld: error: undefined symbol: hid_put_udata
>>> referenced by ukbd.c:830 (/usr/src/sys/dev/usb/input/ukbd.c:830)
>>>   ukbd.o:(ukbd_set_leds_callback)
>>> referenced by ukbd.c:821 (/usr/src/sys/dev/usb/input/ukbd.c:821)>>> 
>>>   ukbd.o:(ukbd_set_leds_callback)
>>> referenced by ukbd.c:839 (/usr/src/sys/dev/usb/input/ukbd.c:839)
>>>   ukbd.o:(ukbd_set_leds_callback)
*** [kernel.full] Error code 1

make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/STING
--- modules-all ---
ctfconvert -L VERSION -g cxgb_sge.o
*** [modules-all] Error code 2

make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/STING
2 errors

make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/STING


___
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: Reinstalling libncurses.so.9

2021-01-07 Thread Filippo Moretti
 
Thank you Herbert,   your instructions allowed me 
to recover all the applications so farFilippo
On Thursday, January 7, 2021, 1:35:13 PM GMT+1, David Wolfskill 
 wrote:  
 
 On Thu, Jan 07, 2021 at 03:58:07AM -0800, David Wolfskill wrote:
> ...
> > I think the commit message explains everything:
> > 
> > https://cgit.freebsd.org/src/commit/?id=821aa63a09402935da0a73abf20ba0441562aa07
> > 
> 
> Seems to me that an update to the misc/compat12x port might be in order:
> 

I was wrong about that; sorry.  As the commit message notes:

|  Since the .9 version only lived in the dev branch and never ended in a
|  release, it is simply removed and not added to any binary compat
|  package.

Peace,
david
-- 
David H. Wolfskill                              da...@catwhisker.org
"President Donald Trump caused this insurrection with his lies and
conspiracy theories about the election process being rigged against him."
 - Scott Jennings

See https://www.catwhisker.org/~david/publickey.gpg for my public key.  
___
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: Reinstalling libncurses.so.9

2021-01-07 Thread Filippo Moretti
 
I installed bash via pkg install and I get the following errorld-elf.so.1 
Shared object "lincurses.so.9" not found required by "bash"Filippo
On Thursday, January 7, 2021, 11:30:33 AM GMT+1, Filippo Moretti 
 wrote:  
 
  
I also tried to rebuld the ports but I got errors from dependency.Maybe I 
should rebuild using pkgs?Filippo
On Thursday, January 7, 2021, 11:28:09 AM GMT+1, Filippo Moretti 
 wrote:  
 
  The following do not work bash,mc,xterm I did try to symlink 
libncursessw.so.9 libncurses.so.9 but it did not helpthank you 
Filippo

On Thursday, January 7, 2021, 11:24:56 AM GMT+1, Herbert J. Skuhra 
 wrote:  
 
 On Thu, 07 Jan 2021 11:07:57 +0100, Filippo Moretti wrote:
> 
> I just upgraded current and was prompted to delete libncurses.so.9
> which I did.I could not find another version in lib so I need to
> reinstall libncurses.so.9.Let me please know hot tothank youFilippo

Why? What's broken?

I think the commit message explains everything:

https://cgit.freebsd.org/src/commit/?id=821aa63a09402935da0a73abf20ba0441562aa07

--
Herbert
___
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"
  
___
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: Reinstalling libncurses.so.9

2021-01-07 Thread Filippo Moretti
 
I also tried to rebuld the ports but I got errors from dependency.Maybe I 
should rebuild using pkgs?Filippo
On Thursday, January 7, 2021, 11:28:09 AM GMT+1, Filippo Moretti 
 wrote:  
 
  The following do not work bash,mc,xterm I did try to symlink 
libncursessw.so.9 libncurses.so.9 but it did not helpthank you 
Filippo

On Thursday, January 7, 2021, 11:24:56 AM GMT+1, Herbert J. Skuhra 
 wrote:  
 
 On Thu, 07 Jan 2021 11:07:57 +0100, Filippo Moretti wrote:
> 
> I just upgraded current and was prompted to delete libncurses.so.9
> which I did.I could not find another version in lib so I need to
> reinstall libncurses.so.9.Let me please know hot tothank youFilippo

Why? What's broken?

I think the commit message explains everything:

https://cgit.freebsd.org/src/commit/?id=821aa63a09402935da0a73abf20ba0441562aa07

--
Herbert
___
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"

___
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"


Reinstalling libncurses.so.9

2021-01-07 Thread Filippo Moretti
I just upgraded current and was prompted to delete libncurses.so.9 which I 
did.I could not find another version in lib so I need to reinstall 
libncurses.so.9.Let me please know hot tothank youFilippo
___
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: Problem compiling git from ports

2021-01-03 Thread Filippo Moretti
 Thank you Michal,   I upgraded ruby26-gems to 
ruby27-gems:I did early upgraded to ruby27 but ruby-gems was inadvertently 
omittedsincerelyFilippo

On Saturday, January 2, 2021, 10:23:13 PM GMT+1, Michal Meloun 
 wrote:  
 
 

On 01.01.2021 21:19, Filippo Moretti wrote:
>  
> It worked thank youFilippo
>      On Friday, January 1, 2021, 5:25:10 PM GMT+1, Milan Obuch 
> wrote:
>  
>  On Fri, 1 Jan 2021 16:11:52 +0000 (UTC), Filippo Moretti
>  wrote:
> 
>>    
>> I run again portmaster and I have the same error as previously
>> reportedFilippo On Friday, January 1, 2021, 4:05:18 PM GMT+1, Filippo
>> Moretti  wrote:
>>    Ufs
>> It exits with a different error:
>> ===> Installing contributed scripts
>> /bin/mkdir -p
>> /usr/ports/devel/git/work-default/stage/usr/local/share/git-core/contrib
>> cp -f -R /usr/ports/devel/git/work-default/git-2.30.0/contrib/*
>> /usr/ports/devel/git/work-default/stage/usr/local/share/git-core/contrib
>> ln:
>> /usr/ports/devel/git/work-default/stage/usr/local/etc/bash_completion.d//git-completion.bash:
>> File exists *** Error code 1
>>
>> Stop.
>> make[1]: stopped in /usr/ports/devel/git
>> *** Error code 1
>>
>> Stop.
>> make: stopped in /usr/ports/devel/git
>>
> 
> I remember seeing this too. I worked around that using options:
> 
> cat /var/db/ports/devel_git/options
> # This file is auto-generated by 'make config'.
> # Options for git-2.29.2
> _OPTIONS_READ=git-2.29.2
> _FILE_COMPLETE_OPTIONS_LIST=CONTRIB CURL CVS GITWEB GUI HTMLDOCS ICONV NLS P4 
> PERL SEND_EMAIL SUBTREE SVN PCRE PCRE2 OPTIONS_FILE_SET+=CONTRIB
> OPTIONS_FILE_SET+=CURL
> OPTIONS_FILE_SET+=CVS
> OPTIONS_FILE_UNSET+=GITWEB
> OPTIONS_FILE_UNSET+=GUI
> OPTIONS_FILE_UNSET+=HTMLDOCS
> OPTIONS_FILE_SET+=ICONV
> OPTIONS_FILE_UNSET+=NLS
> OPTIONS_FILE_SET+=P4
> OPTIONS_FILE_SET+=PERL
> OPTIONS_FILE_SET+=SEND_EMAIL
> OPTIONS_FILE_UNSET+=SUBTREE
> OPTIONS_FILE_UNSET+=SVN
> OPTIONS_FILE_SET+=PCRE
> OPTIONS_FILE_UNSET+=PCRE2
> 
> Regards,
> Milan

This is not related to cache fast lookup, but it is  dependency bug of 
ruby ports.
My portmaster -ad session failed with the same issue. I noticed that 
rubby has been update
from 2.6 to 2.7 as part of this sesion.


# pkg which /usr/local/bin/asciidoctor
/usr/local/bin/asciidoctor was installed by package 
rubygem-asciidoctor-2.0.10

# ls -l /usr/local/bin/asciidoctor
-rwxr-xr-x  1 root  wheel  560 Jun  7  2020 /usr/local/bin/asciidoctor

# /usr/local/bin/asciidoctor
/usr/local/bin/asciidoctor: Command not found

# ls -l /usr/local/bin/asciidoctor
-rwxr-xr-x  1 root  wheel  560 Jun  7  2020 /usr/local/bin/asciidoctor

root@tegra210:/usr/ports # more  /usr/local/bin/asciidoctor
#!/usr/local/bin/ruby26
#
# This file was generated by RubyGems.
#
# The application 'asciidoctor' is installed as part of a gem, and
# this file is here to facilitate running it.
#
...

# ls -l /usr/local/bin/ruby26
ls: /usr/local/bin/ruby26: No such file or directory

# portmaster -d rubygem-asciidoctor-2.0.10
...
Installing ruby27-gems-3.0.8...
pkg-static: ruby27-gems-3.0.8 conflicts with ruby26-gems-3.0.8 (installs 
files into the same place).  Problematic file: /usr/local/bin/gem
...

# pkg info | grep ruby26
ruby26-gems-3.0.8              Package management framework for the Ruby 
language

# pkg delete -f ruby26-gems
# portmaster -d rubygem-asciidoctor-2.0.10

# /usr/local/bin/asciidoctor
Usage: asciidoctor [OPTION]... FILE...



Michal

...
___
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"
  
___
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: Problem compiling git from ports

2021-01-01 Thread Filippo Moretti
 
It worked thank youFilippo
On Friday, January 1, 2021, 5:25:10 PM GMT+1, Milan Obuch 
 wrote:  
 
 On Fri, 1 Jan 2021 16:11:52 + (UTC), Filippo Moretti
 wrote:

>  
> I run again portmaster and I have the same error as previously
> reportedFilippo On Friday, January 1, 2021, 4:05:18 PM GMT+1, Filippo
> Moretti  wrote: 
>  Ufs 
> It exits with a different error:
> ===> Installing contributed scripts  
> /bin/mkdir -p
> /usr/ports/devel/git/work-default/stage/usr/local/share/git-core/contrib
> cp -f -R /usr/ports/devel/git/work-default/git-2.30.0/contrib/*
> /usr/ports/devel/git/work-default/stage/usr/local/share/git-core/contrib
> ln:
> /usr/ports/devel/git/work-default/stage/usr/local/etc/bash_completion.d//git-completion.bash:
> File exists *** Error code 1
> 
> Stop.
> make[1]: stopped in /usr/ports/devel/git
> *** Error code 1
> 
> Stop.
> make: stopped in /usr/ports/devel/git
> 

I remember seeing this too. I worked around that using options:

cat /var/db/ports/devel_git/options 
# This file is auto-generated by 'make config'.
# Options for git-2.29.2
_OPTIONS_READ=git-2.29.2
_FILE_COMPLETE_OPTIONS_LIST=CONTRIB CURL CVS GITWEB GUI HTMLDOCS ICONV NLS P4 
PERL SEND_EMAIL SUBTREE SVN PCRE PCRE2 OPTIONS_FILE_SET+=CONTRIB
OPTIONS_FILE_SET+=CURL
OPTIONS_FILE_SET+=CVS
OPTIONS_FILE_UNSET+=GITWEB
OPTIONS_FILE_UNSET+=GUI
OPTIONS_FILE_UNSET+=HTMLDOCS
OPTIONS_FILE_SET+=ICONV
OPTIONS_FILE_UNSET+=NLS
OPTIONS_FILE_SET+=P4
OPTIONS_FILE_SET+=PERL
OPTIONS_FILE_SET+=SEND_EMAIL
OPTIONS_FILE_UNSET+=SUBTREE
OPTIONS_FILE_UNSET+=SVN
OPTIONS_FILE_SET+=PCRE
OPTIONS_FILE_UNSET+=PCRE2

Regards,
Milan
___
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"
  
___
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: Problem compiling git from ports

2021-01-01 Thread Filippo Moretti
 
I run again portmaster and I have the same error as previously reportedFilippo
On Friday, January 1, 2021, 4:05:18 PM GMT+1, Filippo Moretti 
 wrote:  
 
  Ufs 
It exits with a different error:
===> Installing contributed scripts
/bin/mkdir -p 
/usr/ports/devel/git/work-default/stage/usr/local/share/git-core/contrib
cp -f -R /usr/ports/devel/git/work-default/git-2.30.0/contrib/* 
/usr/ports/devel/git/work-default/stage/usr/local/share/git-core/contrib
ln: 
/usr/ports/devel/git/work-default/stage/usr/local/etc/bash_completion.d//git-completion.bash:
 File exists
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/devel/git
*** Error code 1

Stop.
make: stopped in /usr/ports/devel/git

Thank youFilippo
On Friday, January 1, 2021, 3:52:33 PM GMT+1, Mateusz Guzik 
 wrote:  
 
 What filesystem is this?

Does it work if you sysctl vfs.cache_fast_lookup=0 ?

On 1/1/21, Filippo Moretti  wrote:
> I could not update git from 2.29 in my system
> [root@STING /usr/ports/devel/git]# uname -a
> FreeBSD STING 13.0-CURRENT FreeBSD 13.0-CURRENT #14
> main-c255423-gee938b20335: Wed Dec 30 10:41:00 CET 2020
> root@STING:/usr/obj/usr/src/amd64.amd64/sys/STING  amd64
>
>
>
>
> This is the error which can be duplicatedsincerelyFilippo
>
>
>
> [root@STING /usr/ports/devel/git]# gmake[3]: 'GIT-VERSION-FILE' is up to
> date.
> gmake[3]: Leaving directory '/usr/ports/devel/git/work-default/git-2.30.0'
> sed -e '1s|#!.*/sh|#!/bin/sh|' git-subtree.sh >git-subtree
> chmod +x git-subtree
> install -d -m 755
> /usr/ports/devel/git/work-default/stage/usr/local/libexec/git-core
> install -m 755 git-subtree
> /usr/ports/devel/git/work-default/stage/usr/local/libexec/git-core
> asciidoctor -b docbook -d manpage  \
>        -agit_version=2.30.0 -I../../Documentation -rasciidoctor-extensions
> -alitdd='' git-subtree.txt
> gmake[2]: asciidoctor: No such file or directory
> gmake[2]: *** [Makefile:86: git-subtree.xml] Error 127
> gmake[2]: Leaving directory
> '/usr/ports/devel/git/work-default/git-2.30.0/contrib/subtree'
> *** Error code 2
>
> Stop.
> make[1]: stopped in /usr/ports/devel/git
> *** Error code 1
>
> Stop.
> make: stopped in /usr/ports/devel/git
> [root@STING /usr/ports/devel/git]#
>
> ___
> 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"
>


-- 
Mateusz Guzik 
___
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"

___
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"


Problem compiling git from ports

2021-01-01 Thread Filippo Moretti
I could not update git from 2.29 in my system
[root@STING /usr/ports/devel/git]# uname -a
FreeBSD STING 13.0-CURRENT FreeBSD 13.0-CURRENT #14 main-c255423-gee938b20335: 
Wed Dec 30 10:41:00 CET 2020 
root@STING:/usr/obj/usr/src/amd64.amd64/sys/STING  amd64




This is the error which can be duplicatedsincerelyFilippo



[root@STING /usr/ports/devel/git]# gmake[3]: 'GIT-VERSION-FILE' is up to date.
gmake[3]: Leaving directory '/usr/ports/devel/git/work-default/git-2.30.0'
sed -e '1s|#!.*/sh|#!/bin/sh|' git-subtree.sh >git-subtree
chmod +x git-subtree
install -d -m 755 
/usr/ports/devel/git/work-default/stage/usr/local/libexec/git-core
install -m 755 git-subtree 
/usr/ports/devel/git/work-default/stage/usr/local/libexec/git-core
asciidoctor -b docbook -d manpage  \
    -agit_version=2.30.0 -I../../Documentation -rasciidoctor-extensions 
-alitdd='' git-subtree.txt
gmake[2]: asciidoctor: No such file or directory
gmake[2]: *** [Makefile:86: git-subtree.xml] Error 127
gmake[2]: Leaving directory 
'/usr/ports/devel/git/work-default/git-2.30.0/contrib/subtree'
*** Error code 2

Stop.
make[1]: stopped in /usr/ports/devel/git
*** Error code 1

Stop.
make: stopped in /usr/ports/devel/git
[root@STING /usr/ports/devel/git]# 

___
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: HEADS UP: FreeBSD src repo transitioning to git this weekend

2020-12-17 Thread Filippo Moretti
 
I tried cloning with the following result:
[root@STING /home/filippo]# git clone -o freebsd -b main 
https://git.freebsd.org/src.git /usr/src
Cloning into '/usr/src'...
fatal: repository 'https://git.freebsd.org/src.git/' not found

Should I wait past the weekend to clone?Filippo
On Thursday, December 17, 2020, 8:53:22 PM GMT+1, Alan Somers 
 wrote:  
 
 On Thu, Dec 17, 2020 at 12:06 PM Warner Losh  wrote:

> On Thu, Dec 17, 2020 at 12:01 PM Nathan Whitehorn 
> wrote:
>
> >
> >
> > On 12/16/20 7:46 PM, Warner Losh wrote:
> > > Greetings,
> > >
> > > The FreeBSD project will be moving it's source repo from subversion to
> > git
> > > starting this this weekend. The docs repo was moved 2 weeks ago. The
> > ports
> > > repo will move at the end of March, 2021 due to timing issues.
> > >
> > > The short version is that we're switching the version control we're
> > using.
> > > This switch will preserve much of the current FreeBSD development
> > workflow.
> > > After the switch, the subversion repo will become almost read-only. All
> > > future work will be done in git, however as a transition aide we'll be
> > > replaying the MFCs to stable/11, stable/12 and the related releng
> > branches
> > > for the life of those branches.
> > >
> > > For more detailed information, please see
> > > https://github.com/bsdimp/freebsd-git-docs/ for the current
> > documentation.
> > >
> > > Please see https://wiki.freebsd.org/git for the latest detailed
> schedule
> > > (please note that this schedule is subject to change).
> > >
> > > Warner
> > > ___
> > > 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"
> > >
> >
> > One question I didn't see in the (excellent!) docs is whether we should
> > be PGP-signing commits or not. Is that encouraged?
> >
>
> We've not started doing that in general. I don't think signing would cause
> issues, but since it is a bit of an unknown, we've not taken a position on
> this.
>
> Warner (on behalf of the git working group)
>

I hope we don't have to start signing all commits.  saltstack/salt has that
policy, and it's extremely annoying.
-Alan
___
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"
  
___
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: in -current is svn still canonical?

2020-11-17 Thread Filippo Moretti
 For  user will git be in the base system or should we install from 
ports/pkg?Filippo

On Tuesday, November 17, 2020, 12:38:00 PM GMT+1, David Wolfskill 
 wrote:  
 
 On Mon, Nov 16, 2020 at 10:32:38PM -0700, Warner Losh wrote:
> ...
> However, when you make the switch to git (either due to the flag day and
> tracking -current, or jumping from svn on a stable branch), there's no tool
> to convert the subversion checked out tree to a git tree. The needed
> information needed to create the git tree isn't easily available from the
> subversion checkout, so you'll need to do a git clone. If bandwidth is a
> problem, you can do a shallow clone that omits all the history and just
> grabs the branch of interest. Git is a bit more link efficient than
> subversion, which is helpful. Git also has ways to help you share one local
> repo across checked out versions, which can also help if you have to track
> multiple branches.
> 

Folks in that position might want to consider making the switch (for a
given repo -- src; ports; doc) in two stages over a period of time: the
first, to get an initial copy, then (the first of a series of)
incremental updates.  The duration of the first need not be especially
critical.  Of course, this presumes adequate local storage space.

(I am currently testing my approach, using cgit-beta.freebsd.org for
each of the three repos; the approach I am using is described in
http://www.catwhisker.org/~david/FreeBSD/repo-sync.html, in case that's
of use.  Please note that I am actually using both svn & git, relying on
svn for now, as it is the Source of Truth.)

Peace,
david
-- 
David H. Wolfskill                              da...@catwhisker.org
Trump's continuing malfeasance is costing lives -- and 72M voted for this??!?

See http://www.catwhisker.org/~david/publickey.gpg for my public key.  
___
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: Problem compiling world amd64

2020-09-18 Thread Filippo Moretti
 Thank you very much buildworld worked properly
sincerelyFilippo

On Friday, September 18, 2020, 10:20:58 AM GMT+2, Yasuhiro KIMURA 
 wrote:  
 
 From: Filippo Moretti 
Subject: Problem compiling world amd64
Date: Fri, 18 Sep 2020 07:57:40 + (UTC)

> [filippo@sting ~]$ uname -a
> FreeBSD sting 13.0-CURRENT FreeBSD 13.0-CURRENT #11 r365578: Thu Sep 10 
> 19:38:51 CEST 2020 root@sting:/usr/obj/usr/src/amd64.amd64/sys/STING  
> amd64
> 
(snip)
> --- beforedepend ---
> mkdir -p xlocale arpa;  for i in a.out.h assert.h elf.h limits.h nlist.h 
> setjmp.h stddef.h stdbool.h string.h strings.h time.h unistd.h uuid.h; do  ln 
> -sf /usr/src/include/$i $i;  done;  ln -sf 
> /usr/src/sys/amd64/include/stdarg.h stdarg.h;  ln -sf 
> /usr/src/sys/sys/errno.h errno.h;  ln -sf /usr/src/sys/sys/stdint.h stdint.h; 
>  ln -sf /usr/src/include/arpa/inet.h arpa/inet.h;  ln -sf 
> /usr/src/include/arpa/tftp.h arpa/tftp.h;  for i in _time.h _strings.h 
> _string.h; do  [ -f  xlocale/$i ] || cp /dev/null xlocale/$i;  done;  for i 
> in ctype.h fcntl.h signal.h stdio.h stdlib.h; do  ln -sf 
> /usr/src/stand/libsa/stand.h $i;  done
> cp: /dev/null: Invalid argument
> *** [beforedepend] Error code 1
> 
> make[4]: stopped in /usr/src/stand/libsa
> --- all_subdir_secure ---
> --- all_subdir_share ---
> --- all_subdir_lib ---
> 
> The error is recurringFilippo

1. Update source tree to r365643 or later.
2. cd /usr/src/bin/cp
3. make
4. make install
5. cd /usr/src
6. make buildworld

---
Yasuhiro KIMURA
___
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"
  
___
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"


Problem compiling world amd64

2020-09-18 Thread Filippo Moretti
[filippo@sting ~]$ uname -a
FreeBSD sting 13.0-CURRENT FreeBSD 13.0-CURRENT #11 r365578: Thu Sep 10 
19:38:51 CEST 2020 root@sting:/usr/obj/usr/src/amd64.amd64/sys/STING  amd64

I have the following error during buildworld:ed '1s/\/bin\//\/rescue\//' 
/usr/src/rescue/rescue/../../sbin/reboot/nextboot.sh > nextboot_FIXED
--- dhclient_FIXED ---
sed '1s/\/bin\//\/rescue\//' 
/usr/src/rescue/rescue/../../sbin/dhclient/dhclient-script > dhclient_FIXED
--- all_subdir_stand ---
===> stand (all)
--- all_subdir_stand/libsa ---
===> stand/libsa (all)
--- include/machine ---
include/machine -> /usr/src/sys/amd64/include
--- include/x86 ---
include/x86 -> /usr/src/sys/x86/include
--- beforedepend ---
mkdir -p xlocale arpa;  for i in a.out.h assert.h elf.h limits.h nlist.h 
setjmp.h stddef.h stdbool.h string.h strings.h time.h unistd.h uuid.h; do  ln 
-sf /usr/src/include/$i $i;  done;  ln -sf /usr/src/sys/amd64/include/stdarg.h 
stdarg.h;  ln -sf /usr/src/sys/sys/errno.h errno.h;  ln -sf 
/usr/src/sys/sys/stdint.h stdint.h;  ln -sf /usr/src/include/arpa/inet.h 
arpa/inet.h;  ln -sf /usr/src/include/arpa/tftp.h arpa/tftp.h;  for i in 
_time.h _strings.h _string.h; do  [ -f  xlocale/$i ] || cp /dev/null 
xlocale/$i;  done;  for i in ctype.h fcntl.h signal.h stdio.h stdlib.h; do  ln 
-sf /usr/src/stand/libsa/stand.h $i;  done
cp: /dev/null: Invalid argument
*** [beforedepend] Error code 1

make[4]: stopped in /usr/src/stand/libsa
--- all_subdir_secure ---
--- all_subdir_share ---
--- all_subdir_lib ---

The error is recurringFilippo

___
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"


Problem compiling chromium

2020-08-02 Thread Filippo Moretti
This is the last eror I get attempting to compile chromium on amd64 arch 
R363570[263/38159] python ../../mojo/public/tools/mojom/mojom_parser.py 
--input-root /usr/ports/www/chromium/work/chromium-84.0.4147.105/ --input-root 
/usr/ports/www/chromium/work/chromium-84.0.4147.105/out/Release/gen 
--output-root 
/usr/ports/www/chromium/work/chromium-84.0.4147.105/out/Release/gen 
--mojom-file-list=__mojo_public_mojom_base_base__parser___build_toolchain_linux_clang_x64__rule..rsp
 --check-imports 
/usr/ports/www/chromium/work/chromium-84.0.4147.105/out/Release/gen/mojo/public/mojom/base/base.build_metadata
 --enable-feature file_path_is_string --enable-feature is_posix 
--enable-feature is_linux
[264/38159] python ../../tools/licenses.py --target-os=freebsd --depfile 
gen/components/resources/about_credits.d credits 
gen/components/resources/about_credits.html
FAILED: gen/components/resources/about_credits.html 
python ../../tools/licenses.py --target-os=freebsd --depfile 
gen/components/resources/about_credits.d credits 
gen/components/resources/about_credits.html
Traceback (most recent call last):
  File "../../tools/licenses.py", line 807, in 
    sys.exit(main())
  File "../../tools/licenses.py", line 792, in main
    args.gn_target, args.depfile): File "../../tools/licenses.py", line 720, in 
GenerateCredits
    license_file_list + ['build.ninja'])
  File 
"/usr/ports/www/chromium/work/chromium-84.0.4147.105/build/android/gyp/util/build_utils.py",
 line 619, in WriteDepfile
    inputs = ComputePythonDependencies() + inputs
  File 
"/usr/ports/www/chromium/work/chromium-84.0.4147.105/build/android/gyp/util/build_utils.py",
 line 557, in ComputePythonDependencies
    p for p in abs_module_paths if p.startswith(abs_dir_source_root)
  File 
"/usr/ports/www/chromium/work/chromium-84.0.4147.105/build/android/gyp/util/build_utils.py",
 line 557, in 
    p for p in abs_module_paths if p.startswith(abs_dir_source_root)
  File 
"/usr/ports/www/chromium/work/.bin/../../../../../local/lib/python3.7/posixpath.py",
 line 378, in abspath
    path = os.fspath(path)
TypeError: expected str, bytes or os.PathLike object, not NoneType
ninja: build stopped: subcommand failed.
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/www/chromium
___
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: Problem compiling Chromium

2020-06-08 Thread Filippo Moretti
 Thank you,  compile error follows:


[829/38881] python ../../chrome/test/chromedriver/embed_extension_in_cpp.py 
--dromedriver/chrome ../../chrome/test/chromedriver/extension/background.js 
../../tension/manifest.json
FAILED: gen/chrome/test/chromedriver/chrome/embedded_automation_extension.cc 
gechrome/embedded_automation_extension.h 
python ../../chrome/test/chromedriver/embed_extension_in_cpp.py --directory 
genhrome ../../chrome/test/chromedriver/extension/background.js 
../../chrome/test/fest.json
Traceback (most recent call last):
  File "../../chrome/test/chromedriver/embed_extension_in_cpp.py", line 11, in 
    import StringIO
ModuleNotFoundError: No module named 'StringIO'
ninja: build stopped: subcommand failed.
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/www/chromium
*** Error code 1

Stop.
make: stopped in /usr/ports/www/chromium

  

On Monday, June 8, 2020, 8:41:15 AM GMT+2, Kevin Oberman 
 wrote:  
 
 On Sun, Jun 7, 2020 at 9:49 AM bob prohaska  wrote:

> Don't know about AMD, but on ARM failures that resemble this are
> common. In some cases the actual error message is tens or a hundred
> lines prior to the last make output.
>
> If you search for the string Error: or maybe error: does anything
> show up? Including the colon : helps to reduce irrelevant hits.
>
> Good luck,
>
> bob prohaska
>

The correct way to do this is to build aagain without doing a make clean
and with MAKE_JOBS_UNSAFE. This will use only a single build stream and the
error(s) will be at the end. The instructions after the failure mention
this, but not why. (Actually there are a couple of reasons.) Doing a make
clean will result in a build from the beginning and will take a very, very
long time in a single stream.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683

>
> On Sun, Jun 07, 2020 at 04:27:24PM +, Filippo Moretti wrote:
> > Good evening, FreeBSD
> sting 13.0-CURRENT FreeBSD 13.0-CURRENT #2 r361787: Sun Jun?? 7 15:02:09
> CEST 2020 root@sting:/usr/obj/usr/src/amd64.amd64/sys/STING??
> amd64
> >
> > the build fails with the following
> message/common/extensions/api/action.json
> ../../chrome/common/extensions/api/browser_action.json
> ../../chrome/common/extensions/api/browsing_data.json
> ../../chrome/common/extensions/api/extension.json
> ../../chrome/common/extensions/api/idltest.idl
> ../../chrome/common/extensions/api/page_action.json
> ../../chrome/common/extensions/api/top_sites.json
> > ninja: build stopped: subcommand failed.
> > ===> Compilation failed unexpectedly.
> > Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure
> to
> > the maintainer.
> > *** Error code 1
> >
> > Stop.
> > make: stopped in /usr/ports/www/chromium
> >
> > ===>>> make build failed for www/chromium
> > ===>>> Aborting update
> >
> > I enclose the list of packages installedsincerelyFilippo
>
>
> > ___
> > 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"
>
> ___
> 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"
>
___
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"
  
___
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"


Problem compiling Chromium

2020-06-07 Thread Filippo Moretti
Good evening, FreeBSD sting 13.0-CURRENT FreeBSD 
13.0-CURRENT #2 r361787: Sun Jun  7 15:02:09 CEST 2020 
root@sting:/usr/obj/usr/src/amd64.amd64/sys/STING  amd64

the build fails with the following message/common/extensions/api/action.json 
../../chrome/common/extensions/api/browser_action.json 
../../chrome/common/extensions/api/browsing_data.json 
../../chrome/common/extensions/api/extension.json 
../../chrome/common/extensions/api/idltest.idl 
../../chrome/common/extensions/api/page_action.json 
../../chrome/common/extensions/api/top_sites.json
ninja: build stopped: subcommand failed.
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1

Stop.
make: stopped in /usr/ports/www/chromium

===>>> make build failed for www/chromium
===>>> Aborting update

I enclose the list of packages installedsincerelyFilippo


pkg_list
Description: Binary data
___
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"


Xorg question

2020-05-09 Thread Filippo Moretti
I run the latest current and I have the following packages 
installed>xf86-input-keyboard-1.9.0_4 
xf86-input-libinput-0.28.2_1  
xf86-input-mouse-1.9.3_3 Should I keep all of them or may I keep 
xf86-input-libinputThank youFilippo
___
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: llvm 10 libomp build error

2020-03-12 Thread Filippo Moretti
 Same problem yesterdayFilippo

On Thursday, March 12, 2020, 08:59:17 AM GMT+1, Ronald Klop 
 wrote:  
 
 Hi,

Clean build after svn update gives:

cc: error: no such file or directory:  
'/data/src/freebsd-current/contrib/llvm-pr
oject/openmp/runtime/src/thirdparty/ittnotify/ittnotify_static.c'
cc: error: no input files
*** [ittnotify_static.pico] Error code 1

make[5]: stopped in /data/src/freebsd-current/lib/libomp

The file ittnotify_static.c does indeed not exist. A .cpp version does  
exist.


[builder@sjakie ~]$ more /etc/src.conf
KERNCONF?=GENERIC-NODEBUG
# Don't build these
WITHOUT_LLVM_TARGET_ALL=true
WITHOUT_LPR=true
WITHOUT_PROFILE=true
WITHOUT_SENDMAIL=true
WITHOUT_TESTS=true


What is the advice? Currently rebuilding with -j 1, but that will hours  
for building the new clang again.

Ronald.
___
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"
  
___
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"


NCURSES

2020-03-03 Thread Filippo Moretti
Dear Sir,  I would like to update my CURRENT-AMD64.The ports that 
depend from ncurses should be rebuilt.How do I find out which ports I need to 
rebuild?Thank youFilippo
___
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"


Problem updating xorg-server

2020-02-22 Thread Filippo Moretti
> You cannot select multiple options from the CONF radio=> Only one of 
these must be defined: DEVD UDEV*** Error code 1
Stop.make[1]: stopped in /usr/ports/x11-servers/xorg-server*** Error code 1
Stop.make: stopped in /usr/ports/x11-servers/xorg-server
===>>> make build failed for x11-servers/xorg-server===>>> Aborting update
This is the error I get while attempting the upgrade.I did choose UDEV but I 
keep getting an errorsincerelyFilippo
___
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"


Problem compiling rust

2018-10-06 Thread Filippo Moretti
  extracting 
cargo-0.29.0-x86_64-unknown-freebsd/cargo/share/doc/cargo/README.md  extracting 
cargo-0.29.0-x86_64-unknown-freebsd/cargo/manifest.in  extracting 
cargo-0.29.0-x86_64-unknown-freebsd/cargo/etc/bash_completion.d/cargo  
extracting cargo-0.29.0-x86_64-unknown-freebsd/cargo/bin/cargo  extracting 
cargo-0.29.0-x86_64-unknown-freebsd/cargo/share/zsh/site-functions/_cargorunning:
 
/usr/ports/lang/rust/work/rustc-1.29.1-src/build/x86_64-unknown-freebsd/stage0/bin/cargo
 build --manifest-path 
/usr/ports/lang/rust/work/rustc-1.29.1-src/src/bootstrap/Cargo.toml 
--frozenTraceback (most recent call last):  File 
"/usr/ports/lang/rust/work/rustc-1.29.1-src/x.py", line 20, in     
bootstrap.main()  File 
"/usr/ports/lang/rust/work/rustc-1.29.1-src/src/bootstrap/bootstrap.py", line 
843, in main    bootstrap(help_triggered)  File 
"/usr/ports/lang/rust/work/rustc-1.29.1-src/src/bootstrap/bootstrap.py", line 
819, in bootstrap    build.build_bootstrap()  File 
"/usr/ports/lang/rust/work/rustc-1.29.1-src/src/bootstrap/bootstrap.py", line 
646, in build_bootstrap    run(args, env=env, verbose=self.verbose)  File 
"/usr/ports/lang/rust/work/rustc-1.29.1-src/src/bootstrap/bootstrap.py", line 
148, in run    raise RuntimeError(err)RuntimeError: failed to run: 
/usr/ports/lang/rust/work/rustc-1.29.1-src/build/x86_64-unknown-freebsd/stage0/bin/cargo
 build --manifest-path 
/usr/ports/lang/rust/work/rustc-1.29.1-src/src/bootstrap/Cargo.toml --frozen*** 
Error code 1
Stop.make[1]: stopped in /usr/ports/lang/rust*** Error code 1
Stop.make: stopped in /usr/ports/lang/rust[root@sting /usr/ports/lang/rust]# I 
always had this problem trying to compiling rust (amd64 alpha3),as I only need 
it to compile firefox I wonder if it is possible to disable its building.Thanks 
Filippo
___
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: (231884) rmn0:error:no GEM object associated to handle …(was: Problem starting Xorg)

2018-10-06 Thread Filippo Moretti
 
I had to portdowngrade to the previous ati driver and now it 
workssincerelyFilippoOn Saturday, October 6, 2018, 12:09:10 PM GMT+2, 
Filippo Moretti  wrote:  
 
  I cannot start X no matter,maybe we should ask the port maintainer to revert 
to the previous ati portthanksFilippo
On Saturday, October 6, 2018, 3:14:50 AM GMT+2, Graham Perrin 
 wrote:  
 
 On 10/2/18 7:02 PM, Filippo Moretti wrote:
>> I get the following error while attemptong to start xorg,that did work until 
>> today,amd64 alpha3drmn0:error:no GEM object associated to handle 0x0400 
>> can't  create framebufferany help appreciatedFilippo

Try:

231884 – x11-drivers/xf86-video-ati stops working after update to 18.1.0,1
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231884>

___
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"

___
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"


Fw: Problem starting Xorg

2018-10-04 Thread Filippo Moretti
 

   - Forwarded Message - From: Filippo Moretti 
To: Niclas Zeising Sent: 
Wednesday, October 3, 2018, 9:46:59 AM GMT+2Subject: Re: Problem starting Xorg
  My mobo is a asus M4A87TD I enclose the files requiredthank youFilippo

On Tuesday, October 2, 2018, 8:28:32 PM GMT+2, Niclas Zeising 
 wrote:  
 
 On 10/2/18 7:02 PM, Filippo Moretti wrote:
> I get the following error while attemptong to start xorg,that did work until 
> today,amd64 alpha3drmn0:error:no GEM object associated to handle 0x0400 
> can't  create framebufferany help appreciatedFilippo

Hi!
Can you provde your Xorg log, as well as information about the hardware 
you are using, and which ports you have installed, and the output of 
kldstat -v | grep drm.  Thank you!
Regards
-- 
Niclas
___
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"


rc.conf
Description: Binary data


dmesg
Description: Binary data


kldstat
Description: Binary data


pkgs
Description: Binary data
___
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"


Problem starting Xorg

2018-10-02 Thread Filippo Moretti
I get the following error while attemptong to start xorg,that did work until 
today,amd64 alpha3drmn0:error:no GEM object associated to handle 0x0400 
can't  create framebufferany help appreciatedFilippo
___
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: ntpd as ntpd user question

2018-07-23 Thread Filippo Moretti
 
It does not matter the system no longer boot.
Filippo
On Monday, July 23, 2018, 6:00:04 PM GMT+2, Filippo Moretti 
 wrote:  
 
  I have ntpd both in etc(passwd and /etc/group but installworld fail saying 
that user ntpd is missing can you please let me know how
to manually edit the entries for ntpd in both files.Etcupdate fails
.It is rather odd because with the same hardware using ufs I did not run into 
problem with zfs system I get this error
Filippo

On Monday, July 23, 2018, 1:00:10 PM GMT+2, Niclas Zeising 
 wrote:  
 
 On 07/21/18 19:56, RW wrote:
> On Sat, 21 Jul 2018 11:14:45 -0600
> Ian Lepore wrote:
> 
> 
>> There's a "pre-world" stage of mergemaster (-Fp option I think) which
>> isn't needed often, but one of the times it is needed is apparently
>> when new user ids are added.
> 
> I wish mergemaster had an option to just add new users and groups,
> rather than merging the files.

etcupdate is usually pretty good at automatically merge updates to files 
without user interaction, even when the files are locally edited as 
well.  For instance, I had no problem merging /etc/master.passwd and 
/etc/group for the ntp change.
Regards
-- 
Niclas
___
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"

___
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: ntpd as ntpd user question

2018-07-23 Thread Filippo Moretti
 I have ntpd both in etc(passwd and /etc/group but installworld fail saying 
that user ntpd is missing can you please let me know how
to manually edit the entries for ntpd in both files.Etcupdate fails
.It is rather odd because with the same hardware using ufs I did not run into 
problem with zfs system I get this error
Filippo

On Monday, July 23, 2018, 1:00:10 PM GMT+2, Niclas Zeising 
 wrote:  
 
 On 07/21/18 19:56, RW wrote:
> On Sat, 21 Jul 2018 11:14:45 -0600
> Ian Lepore wrote:
> 
> 
>> There's a "pre-world" stage of mergemaster (-Fp option I think) which
>> isn't needed often, but one of the times it is needed is apparently
>> when new user ids are added.
> 
> I wish mergemaster had an option to just add new users and groups,
> rather than merging the files.

etcupdate is usually pretty good at automatically merge updates to files 
without user interaction, even when the files are locally edited as 
well.  For instance, I had no problem merging /etc/master.passwd and 
/etc/group for the ntp change.
Regards
-- 
Niclas
___
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"
  
___
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"


Problem with Current amd64

2018-07-18 Thread Filippo Moretti
I installed from the latest snapshot,made buildworld with custom 
kernel,installed bash and mc from ports.It was the first time I used zfs on 1 
Tb sata III disk.When I rebooted the system I got a nasty surprise:my home 
directory,ports and src are no longer there.This never happened to me.Should I 
reinstall or any other suggestion really appreciated
Sincerely
Filippo
___
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"


Problem compiling rust

2018-04-17 Thread Filippo Moretti
I have the folloing error while compiling rust on i386 current of April the 9th


rust_error
Description: Binary data
___
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"


problem with buildworld

2018-02-05 Thread Filippo Moretti
Buildworld failed with libpam/modules error.I tried to delete /usr/obj/usr but 
I get the following error[root@sting /usr/src]# rm -rf /usr/obj/usrrm: 
/usr/obj/usr/src/i386.i386/lib/libpam/modules/pam_opieaccess/pam_opieaccess.so.6.debug:
 Bad file descriptorrm: 
/usr/obj/usr/src/i386.i386/lib/libpam/modules/pam_opieaccess: Directory not 
emptyrm: /usr/obj/usr/src/i386.i386/lib/libpam/modules: Directory not emptyrm: 
/usr/obj/usr/src/i386.i386/lib/libpam: Directory not emptyrm: 
/usr/obj/usr/src/i386.i386/lib: Directory not emptyrm: 
/usr/obj/usr/src/i386.i386: Directory not emptyrm: /usr/obj/usr/src: Directory 
not emptyrm: /usr/obj/usr: Directory not empty[root@sting /usr/src]# Any help 
would be appreciatedsincerelyFilippo
___
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"


Fw: Problem with buildkernel

2017-09-30 Thread Filippo Moretti
 

   - Forwarded Message - From: Filippo Moretti 
<filippom...@yahoo.com>To: FreeBSD Current <freebsd-current@freebsd.org>Sent: 
Friday, September 29, 2017, 6:42:26 PM GMT+2Subject: Problem with buildkernel
 After buildworld of yesterday the buildkernel fails with the following 
message:r/src/tmp/usr/bin -c -O2 -pipe -fno-strict-aliasing -nostdinc -I. 
-I/usr/src/sys -I/usr/src/sys/contrib/libfdt -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -MD  -MF.depend.if_hn.o 
-MTif_hn.o -mno-mmx -mno-sse -msoft-float -ffreestanding -fwrapv 
-fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes 
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef 
-Wno-pointer-sign -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs 
-fdiagnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compare 
-Wno-error-empty-body -Wno-error-parentheses-equality 
-Wno-error-unused-function -Wno-error-pointer-sign 
-Wno-error-shift-negative-value -Wno-error-address-of-packed-member -mno-aes 
-mno-avx -std=iso9899:1999 -Werror /usr/src/sys/dev/hyperv/netvsc/if_hn.c*** 
Error code 1Stop.make[2]: stopped in /usr/obj/usr/src/sys/STING_VT*** Error 
code 1Stop.make[1]: stop
 ped in /usr/src*** Error code 1Stop.make: stopped in /usr/src~
[root@sting /home/filippo]# uname -aFreeBSD sting 12.0-CURRENT FreeBSD 
12.0-CURRENT #4 r322877M: Fri Aug 25 19:11:32 CEST 2017 
root@sting:/usr/obj/usr/src/sys/STING_VT i386sincerelyFilippo
  
___
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"


Problem with buildkernel

2017-09-29 Thread Filippo Moretti
After buildworld of yesterday the buildkernel fails with the following 
message:r/src/tmp/usr/bin -c -O2 -pipe -fno-strict-aliasing -nostdinc -I. 
-I/usr/src/sys -I/usr/src/sys/contrib/libfdt -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -MD  -MF.depend.if_hn.o 
-MTif_hn.o -mno-mmx -mno-sse -msoft-float -ffreestanding -fwrapv 
-fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes 
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef 
-Wno-pointer-sign -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs 
-fdiagnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compare 
-Wno-error-empty-body -Wno-error-parentheses-equality 
-Wno-error-unused-function -Wno-error-pointer-sign 
-Wno-error-shift-negative-value -Wno-error-address-of-packed-member -mno-aes 
-mno-avx -std=iso9899:1999 -Werror /usr/src/sys/dev/hyperv/netvsc/if_hn.c*** 
Error code 1Stop.make[2]: stopped in /usr/obj/usr/src/sys/STING_VT*** Error 
code 1Stop.make[1]: stopp
 ed in /usr/src*** Error code 1Stop.make: stopped in /usr/src~
[root@sting /home/filippo]# uname -aFreeBSD sting 12.0-CURRENT FreeBSD 
12.0-CURRENT #4 r322877M: Fri Aug 25 19:11:32 CEST 2017 
root@sting:/usr/obj/usr/src/sys/STING_VT i386sincerelyFilippo
___
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"


Userland problems in 12-CURRENT

2017-08-09 Thread Filippo Moretti
FreeBSD sting 12.0-CURRENT FreeBSD 12.0-CURRENT #2 r321685M: Sun Jul 30 
08:49:42 CEST 2017 root@sting:/usr/obj/usr/src/sys/STING_VT  i386
I have a problems with chromium and smtube bott exit with segmentation fault 
chromium does'n produce any core.Smtube corefollows:GNU gdb (GDB) 8.0 [GDB v8.0 
for FreeBSD]
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i386-portbld-freebsd12.0".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/local/bin/smtube...(no debugging symbols 
found)...done.
[New LWP 100652]
[New LWP 100938]
[New LWP 100939]
[New LWP 100940]
[New LWP 100941]
[New LWP 100942]
Core was generated by `smtube'.Program terminated with signal SIGSEGV, 
Segmentation fault.
#0  0x2a5c4d55 in ?? () from /usr/local/lib/qt5/libQt5WebKit.so.5
[Current thread is 1 (LWP 100652)]
(gdb) where
#0  0x2a5c4d55 in ?? () from /usr/local/lib/qt5/libQt5WebKit.so.5
#1  0x28def484 in ?? () from /usr/local/lib/qt5/libQt5WebKit.so.5
#2  0x2910da99 in ?? () from /usr/local/lib/qt5/libQt5WebKit.so.5
#3  0x290f7ff8 in ?? () from /usr/local/lib/qt5/libQt5WebKit.so.5
#4  0x290f51fe in ?? () from /usr/local/lib/qt5/libQt5WebKit.so.5
#5  0x290f7c62 in ?? () from /usr/local/lib/qt5/libQt5WebKit.so.5
#6  0x28e02694 in QWebFrameAdapter::load(QNetworkRequest const&, 
QNetworkAccessManager::Operation, QByteArray const&) ()
   from /usr/local/lib/qt5/libQt5WebKit.so.5
#7  0x280fa6b7 in QWebFrame::load(QUrl const&) ()
   from /usr/local/lib/qt5/libQt5WebKitWidgets.so.5
#8  0x28107ad8 in QWebView::load(QUrl const&) ()
   from /usr/local/lib/qt5/libQt5WebKitWidgets.so.5#9  0x0807d768 in ?? ()
#10 0x08089054 in ?? ()
#11 0x0805853a in ?? ()
#12 0x080583f8 in ?? ()
#13 0x in ?? ()

Further I did succesfully install a PAE kernel but the OS only finds the same 
3G ram as standard kernel insted of the 4 G available.Are there other 
procedures in order to enable the 4G ram available?ThanksFilippo

___
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"

Userland problems in i386 current

2017-08-03 Thread Filippo Moretti
I have problems with chrome and smtube in i386_CURRENT bot segmentation fault.I 
enclose a gdb analysis for smtube,no core for chrome.sincerelyFilippo


smtube.eror
Description: Binary data
___
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"

Fw: Re: Problem with make installworld et alii

2017-07-16 Thread Filippo Moretti



- Forwarded Message -From: Michael Butler 
<i...@protected-networks.net>To: Filippo Moretti <filippom...@yahoo.com>; 
Current <curr...@freebsd.org>Sent: Sunday, July 9, 2017, 4:50:13 PM 
GMT+2Subject: Re: Problem with make installworld et alii
You need to a build newer than SVN r320652 to fix this ..

On 07/09/17 10:43, Filippo Moretti wrote:
> FreeBSD sting 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r320360: Mon Jun 26 
> 15:49:29 UTC 2017    
> r...@releng3.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  i386After 
> compiling world and kernel I cannot make install world with the following 
> error:Fatal error cannot allocate read line in initial thread at line 392 in 
> file /use/src/lib/libthr/thread/thr_init.c (errorno=12)PID 42315 (cc) uid 0: 
> exited on signal 6 (core dumped)
> make:  "/usr/src/share/mk/bsd.compiler.mk" line 145 : Unable to determine 
> compiler type for CC=cc . Consider settingCOMPILER_TYPE

This error is still present with r321039MsincerelyFilippo
___
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"

Problem with make installworld et alii

2017-07-09 Thread Filippo Moretti
FreeBSD sting 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r320360: Mon Jun 26 15:49:29 
UTC 2017 r...@releng3.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  
i386After compiling world and kernel I cannot make install world with the 
following error:Fatal error cannot allocate read line in initial thread at line 
392 in file /use/src/lib/libthr/thread/thr_init.c (errorno=12)PID 42315 (cc) 
uid 0: exited on signal 6 (core dumped)
make:  "/usr/src/share/mk/bsd.compiler.mk" line 145 : Unable to determine 
compiler type for CC=cc . Consider settingCOMPILER_TYPE





This is the report of the crash I experienced with my custom kernel while 
running xinit (all the operations in console mode worked).I can succesfully 
start X using GENERIC.My kernel Worked fine until I reinstalled this snapshot.


Jul  8 08:41:53 sting kernel: 
Jul  8 08:41:53 sting kernel: 
Jul  8 08:41:53 sting kernel: Fatal trap 12: page fault while in kernel mode
Jul  8 08:41:53 sting kernel: cpuid = 1; apic id = 01
Jul  8 08:41:53 sting kernel: fault virtual address = 0xa4c8c67d
Jul  8 08:41:53 sting kernel: fault code= supervisor read, page 
not present
Jul  8 08:41:53 sting kernel: instruction pointer   = 0x20:0xc7f86218
Jul  8 08:41:53 sting kernel: stack pointer = 0x28:0xf0b828e0
Jul  8 08:41:53 sting kernel: frame pointer = 0x28:0xf0b8290c
Jul  8 08:41:53 sting kernel: code segment  = base 0x0, limit 
0xf, type 0x1b
Jul  8 08:41:53 sting kernel: = DPL 0, pres 1, def32 1, gran 1
Jul  8 08:41:53 sting kernel: processor eflags  = interrupt enabled, resume, 
IOPL = 0
Jul  8 08:41:53 sting kernel: current process   = 798 (Xorg)
Jul  8 08:41:53 sting kernel: trap number   = 12
Jul  8 08:41:53 sting kernel: panic: page fault
Jul  8 08:41:53 sting kernel: cpuid = 1
Jul  8 08:41:53 sting kernel: time = 1499495998
Jul  8 08:41:53 sting kernel: KDB: stack backtrace:
Jul  8 08:41:53 sting kernel: #0 0xc07d92df at kdb_backtrace+0x4f
Jul  8 08:41:53 sting kernel: #1 0xc079ad33 at vpanic+0x133
Jul  8 08:41:53 sting kernel: #2 0xc079abfb at panic+0x1b
Jul  8 08:41:53 sting kernel: #3 0xc0a7a73e at trap_fatal+0x31e
Jul  8 08:41:53 sting kernel: #4 0xc0a7a783 at trap_pfault+0x33
Jul  8 08:41:53 sting kernel: #5 0xc0a79e8e at trap+0x2be
Jul  8 08:41:53 sting kernel: #6 0xc0a68d6a at calltrap+0x6
Jul  8 08:41:53 sting kernel: #7 0xc0823df8 at unp_connect2+0x88
Jul  8 08:41:53 sting kernel: #8 0xc0823a9b at unp_connectat+0x40b
Jul  8 08:41:53 sting kernel: #9 0xc0821000 at uipc_connect+0x40
Jul  8 08:41:53 sting kernel: #10 0xc081dac6 at kern_connectat+0x116
Jul  8 08:41:53 sting kernel: #11 0xc081d999 at sys_connect+0x99
Jul  8 08:41:53 sting kernel: #12 0xc0a7b104 at syscall+0x5b4
Jul  8 08:41:53 sting kernel: #13 0xc0a68dee at Xint0x80_syscall+0x2e
Jul  8 08:41:53 sting kernel: Uptime: 2m10s
Jul  8 08:41:53 sting kernel: Physical memory: 2929 MB
Jul  8 08:41:53 sting kernel: Dumping 109 MB: 94 78 62 46 30 14
Jul  8 08:41:53 sting kernel: Dump complete
Jul  8 08:41:53 sting kernel: Automatic reboot in 15 seconds - press a key on 
the console to abort
Jul  8 08:41:53 sting kernel: --> Press a key on the console to reboot,
Jul  8 08:41:53 sting kernel: --> or switch off the system now.
Jul  8 08:41:53 sting kernel: Rebooting...
Jul  8 08:41:53 sting kernel: cpu_reset: Restarting BSP
Jul  8 08:41:53 sting kernel: cpu_reset_proxy: Stopped CPU 1
I also get these messages in console

Jul  8 08:45:31 sting kernel: 1st 0xc6114bb8 bufwait (bufwait) @ 
/usr/src/sys/kern/vfs_bio.c:3539
Jul  8 08:45:31 sting kernel: 2nd 0xd0391800 dirhash (dirhash) @ 
/usr/src/sys/ufs/ufs/ufs_dirhash.c:281
Jul  8 08:45:31 sting kernel: stack backtrace:
Jul  8 08:45:31 sting kernel: #0 0xc0cbbbd1 at witness_debugger+0x81
Jul  8 08:45:31 sting kernel: #1 0xc0cbbaf1 at witness_checkorder+0xd11
Jul  8 08:45:31 sting kernel: #2 0xc0c60154 at _sx_xlock+0x64
Jul  8 08:45:31 sting kernel: #3 0xc0f5d3b0 at ufsdirhash_add+0x40
Jul  8 08:45:31 sting kernel: #4 0xc0f6010a at ufs_direnter+0x47a
Jul  8 08:45:31 sting kernel: #5 0xc0f6a07f at ufs_makeinode+0x5af
Jul  8 08:45:31 sting kernel: #6 0xc0f695a6 at ufs_symlink+0x36
Jul  8 08:45:31 sting kernel: #7 0xc123be43 at VOP_SYMLINK_APV+0xd3
Jul  8 08:45:31 sting kernel: #8 0xc0d301a4 at kern_symlinkat+0x274
Jul  8 08:45:31 sting kernel: #9 0xc0d2ff21 at sys_symlink+0x31
Jul  8 08:45:31 sting kernel: #10 0xc120719e at syscall+0x6de
Jul  8 08:45:31 sting kernel: #11 0xc11f2bee at Xint0x80_syscall+0x2e
Jul  8 08:46:07 sting kernel: lock order reversal:
Jul  8 08:46:07 sting kernel: 1st 0xd18c9914 ufs (ufs) @ 
/usr/src/sys/kern/vfs_syscalls.c:3362
Jul  8 08:46:07 sting kernel: 2nd 0xc6114bb8 bufwait (bufwait) @ 
/usr/src/sys/ufs/ffs/ffs_vnops.c:280
Jul  8 08:46:07 sting kernel: 3rd 0xd1af3c68 ufs (ufs) @ 
/usr/src/sys/kern/vfs_subr.c:2602
Jul  8 08:46:07 sting kernel: stack backtrace:
Jul  8 08:46:07 sting kernel: #0 0xc0cbbbd1 at witness_debugger+0x81
Jul  8 08:46:07 

Problem with pkg

2017-02-27 Thread Filippo Moretti
After a blackout caused by my wife I only get a few pkg shown with the command 
pkg info while they should be hundreds.I also get this error message when 
trying to install packages by pkg installpkg: Repository FreeBSD load error: 
access repo file(/var/db/pkg/repo-FreeBSD.sqlite) failed: No such file or 
directory(I do have a file name local.sqlite)Is there a way to recover the pkg 
database or should I reinstall the OS.Filippo


___
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"


Problem compiling akonadi

2017-02-21 Thread Filippo Moretti



 

 While trying to compile akonadi I get the following error:
===> Installing for qtchooser-39===> Checking if qtchooser already 
installed===> Registering installation for qtchooser-39 as automaticInstalling 
qtchooser-39...pkg-static: qtchooser-39 conflicts with qt4-dbus-4.8.7 (installs 
files into the same place). Problematic file: /usr/local/bin/qdbus*** Error 
code 70 
Stop.make[5]: stopped in /usr/ports/misc/qtchooser*** Error code 1Stop.make[4]: 
stopped in /usr/ports/devel/qt4-qmake*** Error code 1Stop.make[3]: stopped in 
/usr/ports/devel/qt4-moc*** Error code 1Stop.make[2]: stopped in 
/usr/ports/devel/automoc4*** Error code 1Stop.make[1]: stopped in 
/usr/ports/databases/akonadi*** Error code 1Stop.make: stopped in 
/usr/ports/databases/akonadi 
sincerelyFilippo


   
___
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"


Problem compiling akonadi

2017-02-20 Thread Filippo Moretti
While trying to compile akonadi I get the following error:
===> Installing for qtchooser-39===> Checking if qtchooser already 
installed===> Registering installation for qtchooser-39 as automaticInstalling 
qtchooser-39...pkg-static: qtchooser-39 conflicts with qt4-dbus-4.8.7 (installs 
files into the same place). Problematic file: /usr/local/bin/qdbus*** Error 
code 70 
Stop.make[5]: stopped in /usr/ports/misc/qtchooser*** Error code 1Stop.make[4]: 
stopped in /usr/ports/devel/qt4-qmake*** Error code 1Stop.make[3]: stopped in 
/usr/ports/devel/qt4-moc*** Error code 1Stop.make[2]: stopped in 
/usr/ports/devel/automoc4*** Error code 1Stop.make[1]: stopped in 
/usr/ports/databases/akonadi*** Error code 1Stop.make: stopped in 
/usr/ports/databases/akonadi 
sincerelyFilippo
___
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"


Problem with x.org

2017-02-13 Thread Filippo Moretti
root@sting:~ # uname -a
FreeBSD sting 12.0-CURRENT FreeBSD 12.0-CURRENT #5 r313678M: Sun Feb 12 
18:37:07 CET 2017 root@sting:/usr/obj/usr/src/sys/STING_VT  i386After 
upgrading to the latest x.org server I cannot start X as a normal user but only 
as a root.I enclose the error in Xorg.0.log.oldFilippops I checked permission 
of /usr/local/bin/Xorg and are correct


Xorg.0.log.old
Description: Binary data
___
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"