date:20220925

Re: My home router, running OpenBSD 7.1, won't boot headlessly

2022-09-25 Thread Ronan Viel

Hi, 

I had the same kind of issue with an Intel NUC some years ago and solved it 
with a fit-Headless HDMI dongle: 
https://www.fit-pc.com/web/products/fit-headless/ 


Regards,
Ronan

> Le 25 sept. 2022 à 14:12, Z. Charles Dziura  a écrit :
> 
> Hello everybody,
> 
> A couple of months ago, I decided to build my own custom router for my home 
> network by following this[1] guide. The machine itself works quite well, 
> except for one glaring flaw: it won't boot up properly unless I have a 
> monitor plugged into one of the display ports. Of course, this makes things a 
> bit difficult to debug.
> 
> I'm curious if anyone else has encountered such a bug in the past; and if so, 
> how did you fix it? Below are the relevant specs of my router.
> 
> Specs:
> - Motherboard: ASUS PRIME H610I-PLUS D4-CSM
> - CPU: Intel Celeron ‎G6900
> - RAM: Patriot Viper Steel DDR4 2x8G
> - SSD: WD Green 240GB
> - NIC: Intel I340-T4
> 
> Any and all help will be gratly appreciated!
> 
> - Zachary
> 
> Sources:
> [1]: https://openbsdrouterguide.net/
> 
>

Re: My home router, running OpenBSD 7.1, won't boot headlessly

2022-09-25 Thread Kastus Shchuka

On Sun, Sep 25, 2022 at 08:12:51AM -0400, Z. Charles Dziura wrote:
> Hello everybody,
> 
> A couple of months ago, I decided to build my own custom router for my home
> network by following this[1] guide. The machine itself works quite well,
> except for one glaring flaw: it won't boot up properly unless I have a
> monitor plugged into one of the display ports. Of course, this makes things
> a bit difficult to debug.
> 
> I'm curious if anyone else has encountered such a bug in the past; and if
> so, how did you fix it? Below are the relevant specs of my router.
> 
> Specs:
> - Motherboard: ASUS PRIME H610I-PLUS D4-CSM
> - CPU: Intel Celeron ‎G6900
> - RAM: Patriot Viper Steel DDR4 2x8G
> - SSD: WD Green 240GB
> - NIC: Intel I340-T4
> 

Seems you need a dummy HDMI plug, similar to what was described in this thread:
https://marc.info/?l=openbsd-misc=165192618008143=2

Re: Libreoffice crashing on Thinkcentre m92p 7.1 FVWM - seems to be a python problem

2022-09-25 Thread Cal Ledsham

Thank you - this is a helpful start and some tips to go on with, and the 
from-terminal opening might be a workaround for now.
-cal.


From: Luke A. Call 
Sent: Monday, 26 September 2022 12:39 AM
To: Cal Ledsham ; misc@openbsd.org 
Subject: Re: Libreoffice crashing on Thinkcentre m92p 7.1 FVWM - seems to be a 
python problem

Details in case it helps:
https://marc.info/?l=openbsd-misc=161280915705719=2
https://marc.info/?l=openbsd-bugs=164814366002554=2

On 2022-09-25 08:24:44-0600, Luke A. Call  wrote:
> I had a similar problem where I could open files with LO if I typed them
> on the command line when launching LO, but File / Open would crash when
> choosing the file and hitting OK.  But I don't think mine was
> python-related.  It seemed that my cleaning up by removing evidently unused 
> packages
> removed something that was required for LO but not explicitly listed in
> its dependencies.  Fortunately I had been logging the output whenever I
> ran pkd_delete, and could use that for reference.  After a long process of
> elimination, reinstalling things to see what would happen, I think it was one
> of these that made it work again (though probably a different one for
> you):
>
> (from most to least likely):  devhelp gsettings-desktop-schemas 
> glib2-networking
> (and probably not, but maybe caused some other package to be installed
> that did it:  gnome-desktop totem)
>
> The relevant email thread at the time is probably in the archives; I
> never got a reply, IIRC.
>
> Good luck :)
>
>
> On 2022-09-25 02:23:00+, Cal Ledsham  wrote:
> > Dear OBSDer's -
> > I am running 7.1 with out of the box FVWM. Since this Sunday morning 
> > libreoffice has crashed whenever I try to either open an existing file or 
> > create a new file in libreoffice writer. When opening it allows file 
> > selection but then crashes.
> >
> > (Below I have put the crash message ex launching terminal, the messages 
> > from a pkg_add -u, and a dmesg).
> >
> > I have tried the following remedies with the same result: opening different 
> > files, updating all packages with doas pkg_add -u (looked promising as 
> > there was a libreoffice update), rebooting a few times, syspatching again 
> > (first attempt at using libreoffice since applying patch 10_expat 
> > yesterday? or Friday?), and also opening the safe mode of libreoffice. The 
> > same result seems to occur. I tried to run an doas EXPORT PYTHONHOME 
> > [:]
> > but have no idea what should be set as  and  and how 
> > the grammar should quite be.
> >
> > In accord with requested convention, there is a dmesg at the end of the 
> > file.
> >
> > Any help gratefully received.
> >
> > (Sorry if this is a stupid problem or if the information here is 
> > unhelpfully insufficient.)
> >
> > regards,
> > Cal
> >
> > message in terminal screen from which libreoffice was invoked:
> >
> > cfl$ libreoffice
> > Warning: failed to launch javaldx - java may not function correctly
> > Could not find platform independent libraries 
> > Consider setting $PYTHONHOME to [:]
> > Python path configuration:
> >  PYTHONHOME = (not set)
> >  PYTHONPATH = '/usr/local/lib/libreoffice/program/../program'
> >  program name = 'python3'
> >  isolated = 0
> >  environment = 1
> >  user site = 1
> >  import site = 1
> >  sys._base_executable = '/usr/local/bin/python3'
> >  sys.base_prefix = '/usr/local'
> >  sys.base_exec_prefix = '/usr/local'
> >  sys.platlibdir = 'lib'
> >  sys.executable = '/usr/local/bin/python3'
> >  sys.prefix = '/usr/local'
> >  sys.exec_prefix = '/usr/local'
> >  sys.path = [
> >'/usr/local/lib/libreoffice/program/../program',
> >'/usr/local/lib/python39.zip',
> >'/usr/local/lib/python3.9',
> >'/usr/local/lib/python3.9/lib-dynload',
> >  ]
> > Fatal Python error: init_fs_encoding: failed to get the Python codec of the 
> > filesystem encoding
> > Python runtime state: core initialized
> > LookupError: no codec search functions registered: can't find encoding
> >
> > Current thread 0x00b1d90594e8 (most recent call first):
> > 
> > pthread_mutex_destroy on mutex with waiters!
> >
>

Re: xine's ffmpegaudio doesn't downmix, sio_getpar() reports 6 channels instead of 2

2022-09-25 Thread adr


On Thu, 22 Sep 2022, adr wrote:

Hi,

first of all, I've never contributed to the xine project, and
I don't have any experience with sndio, so bear with me...

Frustrated with the bad sound playing a 6 channels aac audio I decided to
take a look.  The device is a usb one:

$ dmesg | grep -i audio
uaudio0 at uhub2 port 3 configuration 1 interface 1 "GeneralPlus USB Audio 
Device" rev 1.10/1.00 addr 6

uaudio0: class v1, full-speed, sync, channels: 2 play, 1 rec, 8 ctls
audio0 at uaudio0
uhidev2 at uhub2 port 3 configuration 1 interface 3 "GeneralPlus USB Audio 
Device" rev 1.10/1.00 addr 6


It has only 2 channels for playback.

The file has 5.1 aac audio:
$ ffprobe file.mp4
[...]
Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, 5.1, fltp, 
224 kb/s (default)

[...]

Xine's ffmpegaudio plugin is supposed to do downmix (please, correct
me if I'm wrong), but:

$ xine --verbose=2 file.mp4
[...]
audio_out: ao_open (0x585415540)
audio_sndio_out: ao_sndio_open bits=16 rate=48000, mode=128
audio_sndio_out: ao_sndio_open 6 channels output
[...]

The code in xine-lib-1.2.12/src/audio_out/audio_sndio_out.c by Brad
Smith is following the recommendations at sio_open(3), there is no
problem there.

sio_getpar() is returning 6 channels as valid, so the sound ends
messed up. The right speaker gets mostly ambient sound and the
voices are almost only audible through the left speaker.

mplayer and mpv have means to force downmix, but xine is the only
media player which can play 1080p h264 video with a decent performance
(if the bitrate is not too high) on an rpi4 (no hardware acceleration,
cpu at 2.2Gz)

One workaround for this particular case could be adding the
configuration setting "audio.output.speaker_arrangement" to
audio_sndio_out.c.


This patch does that, following the alsa and oss drivers.
I CC'd it to ports@


Index: src/audio_out/audio_sndio_out.c
--- src/audio_out/audio_sndio_out.c.orig
+++ src/audio_out/audio_sndio_out.c
@@ -37,6 +37,8 @@
 #include 
 #include "bswap.h"

+#include "speakers.h"
+
 #define GAP_TOLERANCEAO_MAX_GAP
 #define PCT_TO_MIDI(p)   (((p) * SIO_MAXVOL + 50) / 100)

@@ -248,11 +250,15 @@ static void ao_sndio_exit(ao_driver_t *this_gen)
 {
   sndio_driver_t *this = (sndio_driver_t *) this_gen;

+  this->xine->config->unregister_callbacks (this->xine->config, 
"audio.output.speaker_arrangement", NULL, this, sizeof (*this));
+
   xprintf (this->xine, XINE_VERBOSITY_DEBUG,
"audio_sndio_out: ao_sndio_exit called\n");

   if (this->hdl != NULL)
 sio_close(this->hdl);
+
+  free (this);
 }

 static int ao_sndio_get_property (ao_driver_t *this_gen, int property)
@@ -316,13 +322,27 @@ static int ao_sndio_ctrl(ao_driver_t *this_gen, int cm
   return 0;
 }

+static void sndio_speaker_arrangement_cb (void *user_data,
+  xine_cfg_entry_t *entry);
+
 static ao_driver_t *open_plugin (audio_driver_class_t *class_gen, const void 
*data)
 {
   sndio_class_t   *class = (sndio_class_t *) class_gen;
+  config_values_t *config = class->xine->config;
   sndio_driver_t  *this;

   lprintf ("audio_sndio_out: open_plugin called\n");

+  AUDIO_DEVICE_SPEAKER_ARRANGEMENT_TYPES;
+  int speakers;
+
+  speakers = config->register_enum (config,
+  "audio.output.speaker_arrangement",
+  STEREO,
+  (char **)speaker_arrangement,
+  AUDIO_DEVICE_SPEAKER_ARRANGEMENT_HELP,
+  0, sndio_speaker_arrangement_cb, this);
+
   this = calloc(1, sizeof (sndio_driver_t));
   if (!this)
 return NULL;
@@ -333,10 +353,16 @@ static ao_driver_t *open_plugin (audio_driver_class_t
* Set capabilities
*/
   this->capabilities = AO_CAP_MODE_MONO | AO_CAP_MODE_STEREO |
-AO_CAP_MODE_4CHANNEL | AO_CAP_MODE_4_1CHANNEL |
-AO_CAP_MODE_5CHANNEL | AO_CAP_MODE_5_1CHANNEL |
 AO_CAP_MIXER_VOL | AO_CAP_MUTE_VOL | AO_CAP_8BITS |
 AO_CAP_16BITS;
+  if (speakers == SURROUND4)
+this->capabilities |= AO_CAP_MODE_4CHANNEL;
+  if (speakers == SURROUND41)
+this->capabilities |= AO_CAP_MODE_4_1CHANNEL;
+  if (speakers == SURROUND5)
+this->capabilities |= AO_CAP_MODE_5CHANNEL;
+  if (speakers == SURROUND51)
+this->capabilities |= AO_CAP_MODE_5_1CHANNEL;

   this->ao_driver.get_capabilities  = ao_sndio_get_capabilities;
   this->ao_driver.get_property  = ao_sndio_get_property;
@@ -352,6 +378,32 @@ static ao_driver_t *open_plugin (audio_driver_class_t
   this->ao_driver.control   = ao_sndio_ctrl;

   return >ao_driver;
+}
+
+static void sndio_speaker_arrangement_cb (void *user_data,
+  xine_cfg_entry_t *entry) {
+  sndio_driver_t *this = (sndio_driver_t *) user_data;
+  int32_t value = entry->num_value;
+  if (value == SURROUND4) {
+this->capabilities |= AO_CAP_MODE_4CHANNEL;
+  } else {
+this->capabilities &= ~AO_CAP_MODE_4CHANNEL;
+  }
+  if (value == SURROUND41) {
+this->capabilities |= AO_CAP_MODE_4_1CHANNEL;
+  } else {
+

Re: Libreoffice crashing on Thinkcentre m92p 7.1 FVWM - seems to be a python problem

2022-09-25 Thread Luke A. Call

Details in case it helps:
https://marc.info/?l=openbsd-misc=161280915705719=2
https://marc.info/?l=openbsd-bugs=164814366002554=2

On 2022-09-25 08:24:44-0600, Luke A. Call  wrote:
> I had a similar problem where I could open files with LO if I typed them
> on the command line when launching LO, but File / Open would crash when
> choosing the file and hitting OK.  But I don't think mine was
> python-related.  It seemed that my cleaning up by removing evidently unused 
> packages
> removed something that was required for LO but not explicitly listed in
> its dependencies.  Fortunately I had been logging the output whenever I
> ran pkd_delete, and could use that for reference.  After a long process of 
> elimination, reinstalling things to see what would happen, I think it was one
> of these that made it work again (though probably a different one for
> you):  
> 
> (from most to least likely):  devhelp gsettings-desktop-schemas 
> glib2-networking
> (and probably not, but maybe caused some other package to be installed
> that did it:  gnome-desktop totem)
> 
> The relevant email thread at the time is probably in the archives; I
> never got a reply, IIRC.
> 
> Good luck :)
> 
> 
> On 2022-09-25 02:23:00+, Cal Ledsham  wrote:
> > Dear OBSDer's -
> > I am running 7.1 with out of the box FVWM. Since this Sunday morning 
> > libreoffice has crashed whenever I try to either open an existing file or 
> > create a new file in libreoffice writer. When opening it allows file 
> > selection but then crashes.
> > 
> > (Below I have put the crash message ex launching terminal, the messages 
> > from a pkg_add -u, and a dmesg).
> > 
> > I have tried the following remedies with the same result: opening different 
> > files, updating all packages with doas pkg_add -u (looked promising as 
> > there was a libreoffice update), rebooting a few times, syspatching again 
> > (first attempt at using libreoffice since applying patch 10_expat 
> > yesterday? or Friday?), and also opening the safe mode of libreoffice. The 
> > same result seems to occur. I tried to run an doas EXPORT PYTHONHOME 
> > [:]
> > but have no idea what should be set as  and  and how 
> > the grammar should quite be.
> > 
> > In accord with requested convention, there is a dmesg at the end of the 
> > file.
> > 
> > Any help gratefully received.
> > 
> > (Sorry if this is a stupid problem or if the information here is 
> > unhelpfully insufficient.)
> > 
> > regards,
> > Cal
> > 
> > message in terminal screen from which libreoffice was invoked:
> > 
> > cfl$ libreoffice
> > Warning: failed to launch javaldx - java may not function correctly
> > Could not find platform independent libraries 
> > Consider setting $PYTHONHOME to [:]
> > Python path configuration:
> >  PYTHONHOME = (not set)
> >  PYTHONPATH = '/usr/local/lib/libreoffice/program/../program'
> >  program name = 'python3'
> >  isolated = 0
> >  environment = 1
> >  user site = 1
> >  import site = 1
> >  sys._base_executable = '/usr/local/bin/python3'
> >  sys.base_prefix = '/usr/local'
> >  sys.base_exec_prefix = '/usr/local'
> >  sys.platlibdir = 'lib'
> >  sys.executable = '/usr/local/bin/python3'
> >  sys.prefix = '/usr/local'
> >  sys.exec_prefix = '/usr/local'
> >  sys.path = [
> >'/usr/local/lib/libreoffice/program/../program',
> >'/usr/local/lib/python39.zip',
> >'/usr/local/lib/python3.9',
> >'/usr/local/lib/python3.9/lib-dynload',
> >  ]
> > Fatal Python error: init_fs_encoding: failed to get the Python codec of the 
> > filesystem encoding
> > Python runtime state: core initialized
> > LookupError: no codec search functions registered: can't find encoding
> > 
> > Current thread 0x00b1d90594e8 (most recent call first):
> > 
> > pthread_mutex_destroy on mutex with waiters!
> > 
>

Re: Libreoffice crashing on Thinkcentre m92p 7.1 FVWM - seems to be a python problem

2022-09-25 Thread Luke A. Call

I had a similar problem where I could open files with LO if I typed them
on the command line when launching LO, but File / Open would crash when
choosing the file and hitting OK.  But I don't think mine was
python-related.  It seemed that my cleaning up by removing evidently unused 
packages
removed something that was required for LO but not explicitly listed in
its dependencies.  Fortunately I had been logging the output whenever I
ran pkd_delete, and could use that for reference.  After a long process of 
elimination, reinstalling things to see what would happen, I think it was one
of these that made it work again (though probably a different one for
you):  

(from most to least likely):  devhelp gsettings-desktop-schemas glib2-networking
(and probably not, but maybe caused some other package to be installed
that did it:  gnome-desktop totem)

The relevant email thread at the time is probably in the archives; I
never got a reply, IIRC.

Good luck :)


On 2022-09-25 02:23:00+, Cal Ledsham  wrote:
> Dear OBSDer's -
> I am running 7.1 with out of the box FVWM. Since this Sunday morning 
> libreoffice has crashed whenever I try to either open an existing file or 
> create a new file in libreoffice writer. When opening it allows file 
> selection but then crashes.
> 
> (Below I have put the crash message ex launching terminal, the messages from 
> a pkg_add -u, and a dmesg).
> 
> I have tried the following remedies with the same result: opening different 
> files, updating all packages with doas pkg_add -u (looked promising as there 
> was a libreoffice update), rebooting a few times, syspatching again (first 
> attempt at using libreoffice since applying patch 10_expat yesterday? or 
> Friday?), and also opening the safe mode of libreoffice. The same result 
> seems to occur. I tried to run an doas EXPORT PYTHONHOME 
> [:]
> but have no idea what should be set as  and  and how the 
> grammar should quite be.
> 
> In accord with requested convention, there is a dmesg at the end of the file.
> 
> Any help gratefully received.
> 
> (Sorry if this is a stupid problem or if the information here is unhelpfully 
> insufficient.)
> 
> regards,
> Cal
> 
> message in terminal screen from which libreoffice was invoked:
> 
> cfl$ libreoffice
> Warning: failed to launch javaldx - java may not function correctly
> Could not find platform independent libraries 
> Consider setting $PYTHONHOME to [:]
> Python path configuration:
>  PYTHONHOME = (not set)
>  PYTHONPATH = '/usr/local/lib/libreoffice/program/../program'
>  program name = 'python3'
>  isolated = 0
>  environment = 1
>  user site = 1
>  import site = 1
>  sys._base_executable = '/usr/local/bin/python3'
>  sys.base_prefix = '/usr/local'
>  sys.base_exec_prefix = '/usr/local'
>  sys.platlibdir = 'lib'
>  sys.executable = '/usr/local/bin/python3'
>  sys.prefix = '/usr/local'
>  sys.exec_prefix = '/usr/local'
>  sys.path = [
>'/usr/local/lib/libreoffice/program/../program',
>'/usr/local/lib/python39.zip',
>'/usr/local/lib/python3.9',
>'/usr/local/lib/python3.9/lib-dynload',
>  ]
> Fatal Python error: init_fs_encoding: failed to get the Python codec of the 
> filesystem encoding
> Python runtime state: core initialized
> LookupError: no codec search functions registered: can't find encoding
> 
> Current thread 0x00b1d90594e8 (most recent call first):
> 
> pthread_mutex_destroy on mutex with waiters!
>

Re: Nat64 and OpenBSD: ipv4 client to ipv6 server

2022-09-25 Thread Stuart Henderson

On 2022-09-24, Pierre Dupond <76nem...@gmx.ch> wrote:
>> You could possibly do it on per-server basis, eg connections to 
>> 192.0.2.3 are redirected to 2001:db8::dead:beef and connections to 
>> 192.0.2.4 are redirected to 2001:db8::c0:ffee.
>> I don't know if pf itself can do it, but you could probably use socat or 
>> even relayd to work as a proxy in userspace to achieve that.
> This is exactly that I want to do. For few specific IPv4 address (non 
> routable)
> I want to redirect the IPv4 address to an IPv6 address. 'relayd' seems to be 
> usable 
> for that case. I will try this solution since, after a short look in the man
> page, it seems possible to relay from an IPv4 address to an IPv6 address.

There should be no need for relayd for this, try something like

pass in to 192.0.2.3 af-to inet6 from (egress) to 2001:db8::dead:beef

> Unfortunately, some IP providers (generally the access provided is free like 
> with the WIFI in the airports) filter
> even the port 443 if it is not strictly used with the https protocol. 
> Probably using deep packet inspection
> method.

They usually just check for TLS not specifically HTTPS (which would
require active mitm rather than passive inspection of the connection/SNI).

So you can often get around this by wrapping the connection in TLS,
which you can do with relayd (or stunnel or socat).

-- 
Please keep replies on the mailing list.

Re: php-gd-8.1.10 broken on OpenBSD 7.1?

2022-09-25 Thread Stuart Henderson

On 2022-09-25, Stuart Longland  wrote:
> Ahh, makes sense… I normally throw that stuff out because it's a
> headless box… but no problems, I'll fetch that and load it in.

Pretty much anything that uses fonts requires X sets.

Re: php-gd-8.1.10 broken on OpenBSD 7.1? [resolved] + Wordpress on OpenBSD notes

2022-09-25 Thread Stuart Longland

On Sun, 25 Sep 2022 16:23:13 +1000
Stuart Longland  wrote:

> On Sun, 25 Sep 2022 16:10:25 +1000
> Jonathan Gray  wrote:
> 
> > fontconfig and freetype are part of the xbase set
> > 
> > to add it after an install
> > # tar -C / -xzphf xbase71.tgz  
> 
> Ahh, makes sense… I normally throw that stuff out because it's a
> headless box… but no problems, I'll fetch that and load it in.

Right… so got it working in the end.  After loading this, I tried
fiddling with `ldconfig` coaxing it to reload the library cache, but
still didn't get `gd` working… however a quick reboot of the box (yes,
MS-inspired solution), got things working.

In short, to install Wordpress I needed these packages:

mariadb-server-10.6.10v1 multithreaded SQL database (server)
pecl81-imagick-3.7.0p0 PHP support for the ImageMagick library
php-8.1.10  server-side HTML-embedded scripting language
php-curl-8.1.10 curl URL library extensions for php
php-gd-8.1.10   image manipulation extensions for php
php-intl-8.1.10 intl library support for php
php-mysqli-8.1.10   mysql database access extensions for php
php-pdo_mysql-8.1.10 PDO mysql database access extensions for php
php-zip-8.1.10  zip functions for php

plus xbase71.tgz.

These were configured as per the relevant README docs.

Some httpd.conf tricks also for "pretty" permalinks -- these may not be
optimal, but it seems to be working for now.  I'll put them here in
case someone else is looking at how to set this stuff up because it
wasn't immediately obvious how to do it.

root "/sites/example.com/htdocs/"   

directory { 

index index.php 

}   

location "/category/*" {

request rewrite "/index.php/$REQUEST_URI"   

fastcgi socket "/run/php-fpm.sock"  

}   

location "/tag/*" { 

request rewrite "/index.php/$REQUEST_URI"   

fastcgi socket "/run/php-fpm.sock"  

}   

location match "/(20.*)/*" {

request rewrite "/index.php/$REQUEST_URI"   

fastcgi socket "/run/php-fpm.sock"  

}   

location "*.php" {  

fastcgi socket "/run/php-fpm.sock"  

}

Many thanks Jonathan.

Regards,
-- 
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
  ...it's backed up on a tape somewhere.

Re: php-gd-8.1.10 broken on OpenBSD 7.1?

2022-09-25 Thread Stuart Longland

On Sun, 25 Sep 2022 16:10:25 +1000
Jonathan Gray  wrote:

> fontconfig and freetype are part of the xbase set
> 
> to add it after an install
> # tar -C / -xzphf xbase71.tgz

Ahh, makes sense… I normally throw that stuff out because it's a
headless box… but no problems, I'll fetch that and load it in.
-- 
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
  ...it's backed up on a tape somewhere.

Re: php-gd-8.1.10 broken on OpenBSD 7.1?

2022-09-25 Thread Jonathan Gray

On Sun, Sep 25, 2022 at 03:34:55PM +1000, Stuart Longland wrote:
> Hi all…
> 
> I'm just in the process of setting up a Wordpress site for development
> purposes on a VPS running OpenBSD 7.1, and I'm seeing this when I try
> to install the `gd` extension:
> 
> vk4msl-bne# pkg_add php-gd-8.1.10 
> quirks-5.5 signed on 2022-09-24T12:39:42Z
> Can't install gd-2.3.2 because of libraries
> |library fontconfig.13.1 not found
> | not found anywhere
> |library freetype.30.1 not found
> | not found anywhere
> Direct dependencies for gd-2.3.2 resolve to tiff-4.4.0p1 png-1.6.37 
> libiconv-1.16p0 libwebp-1.2.2 jpeg-2.1.3v0
> Full dependency tree is libwebp-1.2.2 lz4-1.9.3p0 tiff-4.4.0p1 png-1.6.37 
> xz-5.2.5p1 jpeg-2.1.3v0 giflib-5.1.6 zstd-1.5.2 libiconv-1.16p0
> Can't install php-gd-8.1.10: can't resolve gd-2.3.2
> Couldn't install gd-2.3.2 php-gd-8.1.10
> vk4msl-bne# uname -a
> OpenBSD vk4msl-bne.dmz.longlandclan.id.au 7.1 GENERIC#3 amd64
> 
> gd is needed to manipulate graphics (thumbnail generation, etc).  While
> I can do without, it's far from ideal.

fontconfig and freetype are part of the xbase set

to add it after an install
# tar -C / -xzphf xbase71.tgz

Re: My home router, running OpenBSD 7.1, won't boot headlessly

Re: My home router, running OpenBSD 7.1, won't boot headlessly

Re: Libreoffice crashing on Thinkcentre m92p 7.1 FVWM - seems to be a python problem

Re: xine's ffmpegaudio doesn't downmix, sio_getpar() reports 6 channels instead of 2

Re: Libreoffice crashing on Thinkcentre m92p 7.1 FVWM - seems to be a python problem

Re: Libreoffice crashing on Thinkcentre m92p 7.1 FVWM - seems to be a python problem

Re: Nat64 and OpenBSD: ipv4 client to ipv6 server

Re: php-gd-8.1.10 broken on OpenBSD 7.1?

Re: php-gd-8.1.10 broken on OpenBSD 7.1? [resolved] + Wordpress on OpenBSD notes

Re: php-gd-8.1.10 broken on OpenBSD 7.1?

Re: php-gd-8.1.10 broken on OpenBSD 7.1?

11 matches

Site Navigation

Mail list logo

Footer information