hello. If you put a gpt label on a raid set and add partitions to it,
those partitions
will show up as dkn devices automatically, when the raid set is configured.
This is true
whether the raid set is configured automatically by the kernel at boot or
manually via raidctl
-C or -c.
This
Hello. Are there pros to having the kernel do the CPU switching? You
don't seem to list
any, but there must be trade-offs. What are they?
-thanks
-Brian
hello. I believe I have reliably reproduced this behavior with the
following steps:
1. Take a working raid1 set and deliberately fail one of the components.
2. Take the broken component and create it as part of a new raid1 raid
set.
3. Reboot.
Notes: Before step 1, you had a work
hello. what if you put a line like:
!sleep 30
in your /etc/ifconfig.* files to make sure the interfaces are up before
you try to bind to them?
Still a hack, but not as bad as the cron job.
-Brian
On Aug 17, 10:35am, "John D. Baker" wrote:
} Subject: Re: named unable to bind to address?
}
Hello. Did you mistype, did I misread or did you really mean to say
that the parent pid (ppid) is 0 on the offending zombie process? that
could be a clue. The ppid should be 1, not 0. I wonder how, if that is
the case, the ppid of 0 gets assigned instead of 1?
-thanks
-Brian
On Sep 30,
hello. Just as a point of reference, the command is still vnconfig in
NetBSD-5.2, so the name change is pretty recent. I wonder why the name
change was thought to be necessary?
On Nov 5, 7:06pm, Paul Goyette wrote:
} Subject: Error on vndconfig(8) man page
} This man page is installed as
hello. Is there a reason to lose it? I have some scripts that, I
believe, use that compatibility syntax.
-thanks
-Brian
On Oct 7, 5:22pm, Thomas Klausner wrote:
} Subject: dump(8) 4.3BSD syntax
} dump still supports, but doesn't document, the 4.3BSD style syntax.
}
} Is there someone
Hello. I'm sure this problem is pilot error on my part, but I'm
having trouble figuring out where the build process is picking up the user
postgres in the destination build environent.
I'm hosting the build on a NetBSD-5.2/i386 system. The build command looks
like:
./build.sh -D /var/t
hello. thanks for the feedback. The earlier post about looking at
the mtree source code gave a clue about what to do. The build is running
as root and not in a chrooted environment. So, mtree is doing lookups
against the host's password and group files. My uid for user postgres was
the
hello David. I wonder if you're running into another manifestation
of kern/54724, which shows zfs corrupting kernel memory in NetBSD-9. I
show the problem having to do with xen, but I now believe the problem is
entirely with zfs and it was only coincidental that I ran into it with xen.
I
hello. My recollection may be slightly wrong here since I'm still
running NetBSD-5 in most cases, but my understanding is that ehci(4)
connected devices are all USB-2.0 and for slower devices, the uhci(4) or
ohci(4) hub drivers provide service. Do these bar code scanners attach as
either
hello. If you reboot again, the raid2 will probably look as you
expect. The general procedure for disk replacement is;
1. raidctl -a /dev/newdisk raidset
2. raidctl -F /dev/baddisk raidset (fails the bad disk, uses the spare and
reconstructs to it)
3. Raid is left with a used_spar
Hello. I agree with Mouse, except that I also think it would be very
helpful and useful to have a serial console on USB only devices. I wonder
if we could make the console a virtual device which is attached dynamically
to a USB serial port if and when available. that would let the syste
hello. In my case, there are times when I want a serial console, for
set up or troubleshooting, but cannot use the built-in display for various
reasons. So, I think it would be useful in more situations than might
first appear. Yes, it wouldn't give you DDB on that console, but for
envir
ng boot
} On Mon, Jul 06, 2020 at 07:55:29AM -0700, Brian Buhrow wrote:
} > hello. In my case, there are times when I want a serial console, for
} > set up or troubleshooting, but cannot use the built-in display for various
} > reasons. So, I think it would be useful in more situ
hello. I'm pretty sure fpritf can return an error that means there
was an i/o error or that something about the underlying file descriptor
needs investigating.
-Brian
On Aug 29, 8:25am, Rob Newberry wrote:
} Subject: Re: NetBSD bug/misbehavior in vdprintf
} >>> NetBSD's implementation of
hello. I'm trying to get a 10G interface working on a
NetBSD-9.0_stable/amd64 machine. I'm able to receive packets on this
interface, but appear to be unable to send packets, though the driver
doesn't report any errors. Is this a known issue? Version and driver
details below. This is w
hello. I have not. The machine is remotely located from me and I'm
not sure we have anything but Fiberstore SFP+ modules in stock.
-thanks
-Brian
--- Forwarded mail from SAITOH Masanobu
Have you tried any other SFP+ modules?
hello. I have a bunch of NetBSD-5.2 machines networked together using
the etherip(4) protocol. I'm interested in beginning to think about how to
upgrade that fleet of devices to NetBSD-9 in hopes of capturing better
network performance. I know the etherip(4) driver was removed from
NetBS
hello David. In the absence of other variables, I'd suggest using
wedges. That gives you the ability to replace disks that go bad with
differently sized disks in the future, while still retaining your zfs vdev
sizes, something zfs likes a lot.
Also, I'm pretty sure zfs recovers
hello. I'm trying to use lynx, pkgsrc/www/lynx, with NetBSD-9 and
NetBSD-current,
under the window(1), misc/window package, and I'm having trouble similar to the
trouble
described in lib/54263. I use the -showcursor option to lynx, so the
cursor tracks the links on the page. Under NetBS
Hello. Thanks for the feedback. Some followup questions:
1. How do I get pkgsrc/www/lynx to compile using -ncurses instead of the
native curses
library? I tried setting various options in /etc/mk.conf, but it looks like
it really wants
to compile using the native curses library. I
hello. Thanks again for the tip. After reading the terminfo library
sources, I realized
that while I had a terminfo description of the terminal, it wasn't being used
because, even
though the library opens a plain text file containing the terminal description,
it only uses
the compiled
hello. Just to clarify. Right now, the cursor is tracking properly
when displaying
regular screens, but when select popup menus are in use, the cursor goes to the
bottom of the
screen. I think this is, again, probably due to a translation error between
the termcap spec
for the termina
hello. The PREFER.curses=pkgsrc
workd fine to get lynx to link against the ncurses library.
the ncurses library uses a terminfo database, but it's incompatible
with the NetBSD
libterminfo library. Fortunately, the NetBSD libterminfo library can exist
with just a file
called .t
hello. I have what is probably a simple question on my new NetBSD-9
system.
I have a machine with two sound cards in it -- the native audio chip
built onto the
motherboard, and a USB audio device that plugs into one of the USB ports.
When ever the
terminal bell rings on the
hello. Since upgrading my kernel to -.99.77 a couple of weeks ago,
I've noticed a strange
problem with my USB keyboard. If I'm in vi, editing a file, if I try to scroll
down the file
using the j key rapidly, instead of scrolling, I get usage errors from vi. In
most cases, I'm
editing
hello Roy and Brett. As usual in these cases, there was a bit of noise
in the beginning
of this process while I figured out what was wrong and what I was doing wrong.
Here is my
current understanding of the situation:
1. By default, terminfo reads the TERMCAP environment variable and
hello Greg. Zfs seems to be much more stable in -current than 9.x. In
particular, if
you're using xen, then you definitely want -current because ZFS and xen under
9.x use different
maxphys values for data transfers, which leads to a lot of corruption and
crashes when using
zfs as backi
Hello. As I understand it, Greg ran into this problem on a xen domu. In
checking my NetBSD-9
system running as a domu under xen-4.14.1, there is no rdrand or rdseed feature
exposed to
domu's by xen. This observation is confirmed by looking at the xen command
line reference
page: https://xenbi
hello. Have you tried running a ktrace on the sendmail process, and
its children, to see
where things are getting stuck? One other test I can think of is to connect to
your ISP's
smtp port using openssl from the bad sparc machine and see if you can start up
a ssl session
using the s_cl
hello John. Just for completeness, and perhaps I'm mistaken, but it
looks like your new
setup isn't actually using tls in its smtp transactions at the moment, see
below. Since I'm not
familir with your setup, I could be completely mistaken, but I note it here in
case you want to
veri
hello. This must be some kind of regression that's ben around a
while. I'm runing a xen
dom0 with NetBSD-5.2 and xen-3.3.2, very old, but vnd(4) does expose the entire
file to the
domu's including FreeBSD 11 and 12 without any corruption or booting issues.
Do you know when this trouble
hello. The difference between UEFI and legacy booting is significant.
I'm not sure about
the current state of NetBSD and xen-dom0, but with FreeBSD, legacy booting is
required unless
you're running 13-current. I think NetBSD/xen-dom0 supports UEFI booting, but
it requires you
use mult
hello. I just got two panics on a system running NetBSD-9.99.77/amd64.
Unfortunately, I
didn't have enough swap configured to capture a dump file. However, I did
figure out that the
problem is in thread 6 of the kernel process, process 0. However, I am
having trouble
figuring out w
Hello. It looks like there is a problem in the comsoft() routine in
sys/dev/ic/com.c. When a panic occurred, I was using com0 on the machine in
question, and
the port was sending and receiving data at a baud rate of 115200
simultaneously. It's been a
long time since I touched this com.c code,
hello Patrick. Are you using a custom kernel with the console defined
in it? That
overrides any settings in the boot.cfg file. Another thing to check. Are you
using a machine
that has had NetBSD on it for a long time? Is it possible the boot block on
the boot disk is
old enough tha
hello. Because of the BIOS mixup on your serial port numbering, what
happens if you
change the com1 to com0 on the boot.cfg line where you tell xen to use com1?
(Leave the
consdev com0 alone for the NetBSD kernel). It may not work, but it might give
you more
information.
-Brian
hello. In thinking about your issue with the LSI SCSI controller a
bit, I have the following questions:
1. What drives do you have attached to the LSI controller?
2. How do the controller and drives probe under Linux which you say works
fine?
3. What happens if you boot the system wi
On Aug 8, 7:49pm, Dave Huang wrote:
} Subject: Any way to "bridge" only IPv6 packets?
}
} is there any way to have the NetBSD box do its current =
} NAT/IPsec/firewall/etc... for IPv4 traffic, but transparently pass IPv6 =
} packets between its two interfaces? E.g., router solicitation packets =
Hello. Could you provide an example of what you expect an /etc/fstab
file entry to look like before and after your suggested edits?
-thanks
-Brian
On Aug 18, 2:28am, Christos Zoulas wrote:
} Subject: Wedges enabled on -current
} Hi,
}
} Now that we have branched 7, I am planning to enab
Hello. I agree that ldap should be retained in base. as pointed out
earlier in thread it's used by ssh, postfix and amd. Having the libraries
installed into the base also means we can install our own software into our
company distributed appliances and not hav to install a lot of pkgsrc
hello. I'd suggest capturing the output of netstat -An. The first
column of that output should be the address of the socket associated with
each of the connections. For each connection in time_wait state, you
should be able to perform an fstat |grep for the address in column 1 of the
net
Hello. The output from the sample netstat indicates that some process
on the machine from which this output was taken is opening up a bunch of
connections to remote sites on port 53. I think it would be interesting to
know if all of these connections are generated from the same process o
hello Brett. I'm wondering if you saw my feedback to the PR you worked
on regarding the
libcurses issue?
Here it is, in case you missed it.
-thanks
-Brian
--- Forwarded mail from "Brian Buhrow"
From: Brian Buhrow
Date: Tue, 10 Aug 2021 11:48:09 -0
Hello. If that is the problem, why does lynx not demonstrate this
problem when linked
against libncurses?
-thanks
-Brian
On Sep 16, 8:57am, RVP wrote:
} Subject: Re: Help with libcurses and lynx under NetBSD-9 and -current?
} On Wed, 15 Sep 2021, Brian Buhrow wrote:
}
} This
hello. Okay. I tried -nocolor with lynx + ncurses. It works fine and
doesn't
demonstrate the same problem. This is a different problem -- the select
choices in the pop-up
window are not rendered at all, it's not that they're rendered in a transparent
color, they're
just not there. I
hello. No. the .lss file change doesn't work because there's no text
rendered to
highlight. The showcursor problem is a different one and I think that one has
been solved with
Brett's current fix, but until the current non-rendering of pop-up selections
is fixed, I can't
say for
Hello. Without going and reading the probe routines, I wonder if we
can create some sort
of hybrid approach? Specifically, probe with the shorter delays, then, if we
get a timeout,
reset and probe with the longer delays? That wil cause hardware that doesn't
exhibit the
behavior to wor
hello. I recently ran into this problem. To get around it, I built
devel/libffi by
hand, , installed it, then rebuilt all the packages that depend on libffi,
incluting
gobject-introspection. In order for me to do this, I needed to pkg_delete the
existing version
of gobject-introspect
hello. I'm wondering if someone could comment on the state of using
NET_MPSAFE kernels?
Is it ready for production use yet?
-thanks
-Brian
hello. Thanks for the reply. I'll check out the document.
Good to know TCP and UDP aren't yet MP safe.
-Brian
hello. I'm trying to update some of our very old Sunfire X2200-M2
servers from NetBSD-5.2
to NetBSD-current/amd64. These are the machines with ELOM/BMc modules on one
of the Broadcom
ethernet ports which share the physical port with the host machine.
the latest commit for NetBSD-5.2 f
hello. Following up on this post, I can now more succinctly describe
the problem.
The issue appears to be that when the port is configured at boot time, the
media autoselect
code selects 10baset-fdx on the port with ASF running even though the actual
speed should be
100baset-fdx. Typ
hello. The bug is similar to, but not the same as, kern/32767. The
ASF firmware provides
a virtual console and IPMI management tools for the server on the same physical
port as one of
the hosts ethernet ports. When the system boots, it knocks the IPMI board off
the net by
virtue of th
an
option because the
machine in question is remotely located and cannot be physically accessed in a
timely manner.
So, any thoughts would be helpful in tracking this issue down.
-thanks
-Brian
On Apr 20, 11:02pm, Brian Buhrow wrote:
} Subject: Re: Using NetBSD-current/amd64 on Sunfire
chive
__
* To: source-changes%NetBSD.org@localhost
* Subject: CVS commit: src/sys/dev/pci
* From: "Brian Buhrow"
* Date: Thu, 19 May 2022 04:43:43 +
__
Module Name:src
Committed By
hello. The MAC address confusion is explainable. The MAC address on
the virtual domain
(domu) cannot match the MAC address on the corresponding interface that's
created on the dom0
to service the domu. To solve this problem, the xen backend driver increments
the fourth octet
of the do
Hello. What version of openssh are you using? I just tested between
NetBSD-5.2 and
-current as of 99.77. Those versions are:
5.2: OpenSSH_5.0 NetBSD_Secure_Shell-20080403-hpn13v1
99.77: OpenSSH_8.4 NetBSD_Secure_Shell-20201204-hpn13v14-lpk,
your command, with a nested directory, works
Hello. While this is orthogonal to the task you're working on in this
e-mail, I'll note
that you'll get much better read-write performance if you create a standard zfs
filesystem for
your time machine backup, then create a regular file in it which you export via
iscsi. I
discovered thi
hello. Yes, I was vaguely aware of the lack of extended attributes for
NetBSD-Zfs, but
what I was suggesting was just using a flat file, exported via iscsi through
istgt or your
initiator of choice, on top of zfs, rather than a zvol, because you'll find the
read/write speed
to be so muc
My read/write performance jumped by a factor of 5,
which really
astounded me.
-thanks
-Brian
On Jul 16, 10:32pm, Brad Spencer wrote:
} Subject: Re: iscsi target on a zfs zvol?
} Brian Buhrow writes:
}
} > hello. Yes, I was vaguely aware of the lack of extended attributes for
NetBSD-Zfs,
hello. I just spun up a Linode server, which I think is also running a
Q35 virtual chip
set and it seems to work just fine, except that in paravirtual mode it doesn't
detect all the
disks. Is that the issue you all are seeing?
-thanks
-Brian
NetBSD 9.99.77 (LINODE) #0: Fri Aug 12 20:
hello. If you want to use zfs for your storage, which I strongly
recommend, lose the
zvols and use flat files inside zfs itself. I think you'll find your storage
performance goes
up by orders of magnetude. I struggled with this on FreeBSD for over a year
before I found the
myriad of t
hello. that's interesting. Do the cores used for the vms also get
used for the host os?
Can you arrange things so that the host os gets dedicated cores that the vms
can't use? If you
do that, do you still see a performance drop when you add cores to the vms?
-thanks
-Brian
hello. Refresh my memory. Is it the case that the HPN code
only runs if both ends
of the ssh connection support HPN and have it turned on? I've been using it
for a very long
time under NetBSD-5, but I notice that newer versions of openssh as shipped on
FreeBSD don't
show HPN s
hello. How hard would it be to add ssh/scp to the install image that
gets brafted into the
netbsd-INSTALL kernel? Is it not there because we don't have room on the
install image?
Not having ssh capabilities from the install miniroot environment is becoming a
real impediment
to doing ne
hello. I'm using both the text consoles and the X display on my
NetBSD-9 based machine
and I'm running into an issue with the keyboard that I think should be simple
to figure out,
but which I'm finding a bit confusing.
Using a USB attached keyboard, when I'm running in the consoles, the
hello. Thanks for the pointers. The following lines in my .Xresources
file fixed things
up, mostly. It looks like all is working as I expect, except I can't seem to
generate
an alt-return key sequence. I just get a bell when I try to do this and the
application I'm
using doesn't rece
hello. Is anyone using the audio(4) driver for recording successfully
under -current?
I'm using an an admittedly older -current (9.99.77), but a browsing of the cvs
logs doesn't
suggest any fixes have been committed since the version I'm runing, audio.c,
rev 1.86. The
symptom is that
der -current?
} On Tue, 25 Oct 2022, Brian Buhrow wrote:
}
} > Is anyone using the audio(4) driver for recording successfully under
-current?
} >
}
} audiorecord worked for me on 9.99.102:
}
} ```
} hdaudio0 at pci0 dev 27 function 0: HD Audio Controller
} hdaudio0: interrupting at msi1 v
hello. Just to clarify, I'm not trying to use two audio devices for
recording at the same
time. What I was doing was something like:
#set up the audio device first
audioctl -d /dev/sound2 -w record.rate=44100 record.channels=2
record.precision=16 \
record.encoding=slinear_le
#Now, th
hello. The hdaudio driver I'm using is a locally patched version to
work around an issue
where the driver doesn't configure the headphone jack correctly. Specifically,
it seems
the default configuration configures the jack for use with a microphone, rather
than with just
a headset, wh
hello Michael. Here is a demonstration of the issue I'm seeing, using
audiorecord with
two audio devices on the same machine. The audio1 device is a USB C-Media
audio dongle.
The audio0 device is a Realtek, Product ID: 0255, built into this Dell Optiplex
5050 desktop
machine.
hello Brad. In reading about your panics on day 6 of uptime, I wonder
if the issue might
be related to memory allocation? Specifically, by day 6, I expect that memory
allocations in
the system are pretty fragmented and thus more CPU time is spent doing things
like cleaning
memory, free
hello. I really don't know what's wrong, but I wonder if the xen logs
show the domu
runing some instruction that's trapped by xen, flagged as dangerous and xen is
then faulting
the vcpu with an illegal instruction error? I would expect to see that error
in the xen log
for the specific
Hello. I've seen this issue and I believe I understand the problem,
though I don't have
a driver fix at this time.
The issue is that the audio output jack on modern Reltek sound chips
can be configured for
a number of purposes: mono or stereo, line out or speaker out. Some chip
hello. Actually, on the server side, where you get the "host is down"
message, that is a
system error from the network stack itself. I've seen it when the arp cache
times out and
can't be refreshed in a timely manner. What happens if you run an extended
ping session
between the dom0 a
hello. My understanding is that the arp caching mechanism works
regardless of whether
you use static MAC addresses or dynamically generated ones. The reason is that
arp bridges the
gap between the layer 2 network, i.e. the MAC addresses, and the layer 3
network, i.e. the IP
addresses t
Hello. The ARP cache timeout used to be 1200 seconds or 20 minutes,
hard coded. Now, it
looks like it's either 1200 seconds or 300 seconds, I'm not sure after a quick
romp through the
kernel source. In any case, The fact that you're getting regular delays on
your pings suggests
there
Hello. Here are the network configuration settings I've been using for
a number of years,
all the way through -current.
net.inet.tcp.recvbuf_auto=1
net.inet.tcp.sendbuf_auto=1
net.inet.tcp.sendbuf_max=16777216
net.inet.tcp.recvbuf_max=16777216
-thanks
-Brian
hello. A couple of quick questions based on the convrsation and the
snippets of logs
shown in the e-mails.
1. Is the MAC address shown in the ARP replies the correct one for the dom0?
No reason it
should be wrong, but it's worth verifying, just in case there is an unknown
host replyi
hello. Yes, this behavior is expected. It ensures that there is no
conflict between the
device on the domu end of the vif port and the device on the dom0 end. This is
more
sane behavior than FreeBSD, which zeros out the MAC address on the dom0 side of
the vif.
-thanks
-Brian
Hello Taylor. Just as a point of reference, smtp clients that connect
to domains hosted by
Microsoft, i.e. outlook.com and any other domains that use their infrastructure
for e-mail, will
have to present a valid SSL certificate in order to submit mail to their smtp
servers. But
that is
hello Ken. It may be that the RFC says the client need not present a
valid certificate, but
I have found that smtp clients I manage that want to send mail to Microsoft
managed domains
cannot set up an SSL encrypted smtp session unless the client presents a valid
certificate as
part of t
hello Ken. Yes, I missed that part of what you were trying to say.
You're right, I
didn't try that. I'm not sure that's possible when configuring SSL with
sendmail. I elected
to arrange for sendmail to hav access to valid public certificates so it could
present a
certificate both as
hello. Perhaps I don't understand what this change means, exactly,
but if this change goes forward, will one still be able to specify a
specific device as the root disk even if it is not the boot disk? For
example, specifying a raid5 set as the root when booting from a single
disk, or, se
hello. My suggestion is to have two windows open to the box while
you're debugging this. In the first window, run the command that blocks.
In the second, do a ps -l of the process ID of the blocking process.
That should tell you right where, inside the kernel, your process is stuck.
The f
hello Robert. Given this code fragment and the discussion you raise
about it, allow me to ask what perhaps is a naive question. If the sample
you quote is incorrect, what is the correct way to accomplish the same
task?
-thanks
-Brian
On Mar 13, 6:27pm, Robert Elz wrote:
} Subject: Re: z
hello. Does the server on which you're running Xen have a BMC
controller that keeps track of hardware conditions and the like? If it
does, then, if mcelog is too hard to port, you might be able to get the
details you want from ipmitool through the BMC.
To answer your question, i
hello. If I were looking at this issue, I'd be looking at the perl
process stuck in bioloc, to see what it's doing. As I understand it,
processes stuck in tstile are a symptom, rather than a cause. that is, any
process that is waiting for access to some subsystem in an indirect manner
wi
hello. What happens with xen consoles or serial consoles?
-thanks
-Brian
hello. Yes, raidctl -C with the original config file that created the
raid, or one you faked up for the occasion, should get you going again.
Once you configure the raid with raidctl -C, you can then run parity
checks and filesystem checks without a problem. I've done this sort of
thing
hello. My Dell Latitude 400 has an Atheros mini-pci wifi card in it
that runs great with NetBSD-5.2 in hostap mode, serving 802.11BG clients. I
believe it's using the open source HAL code. While this isn't 802.11N or
802.11AC, I use it regularly in this mode to "tether" devices wishing t
hello. I'm working to build release of netBSD-9 on a NetBSD-5.2
system. Among other errors, documented elsewhere, I'm seeing the error
shown below.
The problem seems to be triggered by a commit Jason made to
usr.sbin/installboot/Makefile V1.52. It looks like this conditional block
of c
hello. I'm in the process of building NetBSD-9.0 systems in an effort
to consider upgrading from my fleet of NetBSD-5.2 systems to NetBSD-9. As
a long time window(1) user, I have a termcap entry for the window terminal
type that I use on systems that I ssh into from window(1) panes. It i
hello Roy. I must have been tired when I looked at the problem before
writing my message. Brad suggested I look at the captoinfo program in the
ncurses package again to make sure it actually produced binary output
instead of terminfo source. In the ncurses package I'm using, from 2016,
c
hello. I'm trying to build devel/cmake from the pkgsrc using the
pkgsrc-2019Q3 branch of the pkgsrc tree. I'm building on a
NetBSD-9.0/amd64 system. The system has xbase and xcomp sets installed
from the snapshots on nyftp.netbsd.org from October 17 or so, and the rest
of the OS is buil
hello. I'm experimenting with a NetBSD-9 Xen server running zfs
volumes as domU disks. While runing a zfs receive of a snapshot of a domU
disk from another server, I experienced the following crash. While this
could be zfs related, I've been running zfs receives numerous times on the
sys
hello. I'm running into the following build error when trying to
build pkgsrc/lang/gcc48 using pkgsrc-2019Q3 sources. The problem appears
to be that libgcc_s.so, which is in /lib on the machine on which I'm
building, isn't included in the LDFLAGS argument. Either that, or a
locally built
1 - 100 of 142 matches
Mail list logo
