On Fri, Aug 16, 2019 at 08:57:13AM +0300, nonamel...@ukr.net wrote:
> I see the same thing with base /usr/bin/ld and /usr/local/bin/ld from
> binutils.
Yes but a direct ld use is very rare. When it is needed, usually the
level of hackery applied is already high enough for the user to already
know
On 15/08/2019 17:48, Konstantin Belousov wrote:
> Please look at https://reviews.freebsd.org/D21060
> I propose to stop installing /usr/bin/clang, clang++, clang-cpp.
>
> It probably does not matter when all your software comes from ports or
> packages, but is actually very annoying when developin
This seems to be sort of a FAQ, and I had a chance to spend a couple of
quality minutes with one of these devices.
The fundamental problem is that they come up as a CD device, with Windows
software to do whatever it takes.
Sending them a magic USB command enables other interfaces, including
seria
On Fri, Aug 16, 2019 at 09:47:41AM +0100, David Chisnall wrote:
> On 15/08/2019 17:48, Konstantin Belousov wrote:
> > Please look at https://reviews.freebsd.org/D21060
> > I propose to stop installing /usr/bin/clang, clang++, clang-cpp.
> >
> > It probably does not matter when all your software
> On Fri, Aug 16, 2019 at 08:57:13AM +0300, nonamel...@ukr.net wrote:
> > I see the same thing with base?/usr/bin/ld and?/usr/local/bin/ld from
> > binutils.
> Yes but a direct ld use is very rare. When it is needed, usually the
> level of hackery applied is already high enough for the user to alr
On Fri, Aug 16, 2019 at 02:14:38AM -0700, Rodney W. Grimes wrote:
> > On Fri, Aug 16, 2019 at 08:57:13AM +0300, nonamel...@ukr.net wrote:
> > > I see the same thing with base?/usr/bin/ld and?/usr/local/bin/ld from
> > > binutils.
> > Yes but a direct ld use is very rare. When it is needed, usually
> On Fri, Aug 16, 2019 at 09:47:41AM +0100, David Chisnall wrote:
> > On 15/08/2019 17:48, Konstantin Belousov wrote:
> > > Please look at https://reviews.freebsd.org/D21060
> > > I propose to stop installing /usr/bin/clang, clang++, clang-cpp.
> > >
> > > It probably does not matter when all y
On 2019-08-16 11:07, Poul-Henning Kamp wrote:
The remaining issue is: How to get FreeBSD do send the magic string?
FreeBSD USB has several quirks for these devices:
See for example:
/sys/dev/usb/usb_msctest.c:usb_msc_auto_quirk(struct usb_device *udev, uint8_t
iface_index)
/sys/dev/usb/usb_
I tried to build a kernel today and it failed in modules-all even
though I had LOCAL_MODULES="" in /etc/src.conf, as recommended by
jhb.
That's wrong. It has to be LOCAL_MODULES=, otherwise
/sys/conf/kern.post.mk seems to conclude that there should be a
module under /usr/local/sys/modules with th
On 16/08/2019 10:10, Konstantin Belousov wrote:
You did not read neither review summary nor followups.
This is needlessly insulting and this kind of attitude from you towards
people on the mailing lists is one of the main reasons that my
engagement with the FreeBSD project tends to be in br
On Thu, Aug 15, 2019 at 7:09 PM Mark Millard wrote:
>
> My attempt to have -r351102 rebuild itself via devel/llvm90 (rc2)
> got:
>
> --- all_subdir_stand ---
> --- boot2.out ---
> ld.lld: error: undefined symbol: __ashldi3
> >>> referenced by ufsread.c:234 (/usr/src/stand/libsa/ufsread.c:234)
> >>
On 8/15/19 9:21 AM, Sean Eric Fagan wrote:
> I get:
>
> Loading kernel...
> /boot/kernel/kernel text=0x16c493c data=0x1c8b38+0x819238
> syms=[0x8+0x180c18+0x8+0x19df0b]
> Loading configured modules...
> can't find '/boot/entropy'
> \
>
> Note that
>I think vm-bhyve hides stderr output from bhyve by default, but there might
>be a flag to make it display the stderr output. Can you try doing that to see
>if bhyve is reporting an error? Alternatively, can you see if the bhyve
>process is still running?
The log file from it is below. bhyve wa
Could you test with larger memory setup - instead of 512M, 1-2G?
rgds,
toomas
> On 16 Aug 2019, at 22:00, Sean Eric Fagan wrote:
>
>> I think vm-bhyve hides stderr output from bhyve by default, but there might
>> be a flag to make it display the stderr output. Can you try doing that to
>> see
>Could you test with larger memory setup - instead of 512M, 1-2G?
I tried multiple vcpus and 1G of RAM; it made no difference (to either my
attempting to boot the system I built, or the ISO; just confirmed the ISO with
1G).
Sean.
___
freebsd-current@fre
Ok, with debug=yes I see that it *is* running the VM -- but I have no
serial console? This may be operator error here, which is a big relief.
An update after I get back from the vet :). Thanks!
Sean.
___
freebsd-current@freebsd.org mailing list
https:
On 8/14/19 3:40 PM, Daniel Eischen wrote:
> I've lost the original thread, but would the sources in
> /usr/local/sys/modules get built regardless of what MAKEOBJDIRPREFIX is?
> And, now that sources may be installed by a port, what is the method for
> _just_ updating the sources? Why do I even
On 8/14/19 1:19 PM, Ian Lepore wrote:
> On Wed, 2019-08-14 at 13:59 -0600, Warner Losh wrote:
>> On Wed, Aug 14, 2019 at 1:56 PM Ian Lepore wrote:
>>
>>> On Wed, 2019-08-14 at 12:00 -0700, John Baldwin wrote:
On 8/14/19 11:06 AM, Kyle Evans wrote:
> LOCAL_MODULES="" does seem like a sensi
> On 8/14/19 3:40 PM, Daniel Eischen wrote:
> > I've lost the original thread, but would the sources in
> > /usr/local/sys/modules get built regardless of what MAKEOBJDIRPREFIX is?
> > And, now that sources may be installed by a port, what is the method for
> > _just_ updating the sources? Why
Ok, if I run the bhyve commands manually, then I get a serial console.
So something is just borked with vm-bhyve and its use of tmux. Whew.
(Now I don't know *what*, but that's at least progress in my diagnosis!)
___
freebsd-current@freebsd.org mailing
Graham, I loaded yesterday's new 13.0 Current r351067 snapshot and
re-installed FreeBSD. The basic install went well, and I gave my user
operator, wheel, & video permissions. I loaded Xorg via the pkg install
route, all 172 packages. I installed the drm-kmod pkg too. I rebooted and
ran startx as us
On August 16, 2019 2:51:22 PM PDT, "Rodney W. Grimes"
wrote:
>> On 8/14/19 3:40 PM, Daniel Eischen wrote:
>> > I've lost the original thread, but would the sources in
>/usr/local/sys/modules get built regardless of what MAKEOBJDIRPREFIX
>is? And, now that sources may be installed by a port, what
On Fri, 16 Aug 2019 15:40:24 -0700
Cy Schubert wrote:
> On August 16, 2019 2:51:22 PM PDT, "Rodney W. Grimes"
> wrote:
> >> On 8/14/19 3:40 PM, Daniel Eischen wrote:
> >> > I've lost the original thread, but would the sources in
> >/usr/local/sys/modules get built regardless of what MAKEOBJD
> On Fri, 16 Aug 2019 15:40:24 -0700
> Cy Schubert wrote:
>
> > On August 16, 2019 2:51:22 PM PDT, "Rodney W. Grimes"
> > wrote:
> > >> On 8/14/19 3:40 PM, Daniel Eischen wrote:
> > >> > I've lost the original thread, but would the sources in
> > >/usr/local/sys/modules get built regardless
On Fri, 16 Aug 2019 16:32:18 -0700 (PDT)
"Rodney W. Grimes" wrote:
> > > >> > I've lost the original thread, but would the sources in
> > > >/usr/local/sys/modules get built regardless of what
> > > >MAKEOBJDIRPREFIX is? And, now that sources may be installed by
> > > >a port, what is the me
On 8/16/19 3:52 PM, Rozhuk Ivan wrote:
> On Fri, 16 Aug 2019 15:40:24 -0700
> I use better way:
> /etc/make.conf:
> # Modules to build with kernel.
> PORTS_MODULES+= graphics/drm-fbsd12.0-kmod graphics/gpu-firmware-kmod
This doesn't work for folks who use pre-built packages.
--
John Baldwin
On August 16, 2019 4:32:18 PM PDT, "Rodney W. Grimes"
wrote:
>> On Fri, 16 Aug 2019 15:40:24 -0700
>> Cy Schubert wrote:
>>
>> > On August 16, 2019 2:51:22 PM PDT, "Rodney W. Grimes"
>> > wrote:
>> > >> On 8/14/19 3:40 PM, Daniel Eischen wrote:
>> > >> > I've lost the original thread, but wo
On Fri, 16 Aug 2019 17:23:08 -0700
John Baldwin wrote:
> > I use better way:
> > /etc/make.conf:
> > # Modules to build with kernel.
> > PORTS_MODULES+= graphics/drm-fbsd12.0-kmod
> > graphics/gpu-firmware-kmod
>
> This doesn't work for folks who use pre-built packages.
>
I update mine /usr/
On 8/16/19 2:51 PM, Rodney W. Grimes wrote:
>> On 8/14/19 3:40 PM, Daniel Eischen wrote:
>>> I've lost the original thread, but would the sources in
>>> /usr/local/sys/modules get built regardless of what MAKEOBJDIRPREFIX is?
>>> And, now that sources may be installed by a port, what is the meth
On 8/16/19 3:05 AM, Gary Jennejohn wrote:
> I tried to build a kernel today and it failed in modules-all even
> though I had LOCAL_MODULES="" in /etc/src.conf, as recommended by
> jhb.
>
> That's wrong. It has to be LOCAL_MODULES=, otherwise
> /sys/conf/kern.post.mk seems to conclude that there s
On Fri, Aug 16, 2019 at 6:37 PM John Baldwin wrote:
> On 8/16/19 2:51 PM, Rodney W. Grimes wrote:
> >> On 8/14/19 3:40 PM, Daniel Eischen wrote:
> >>> I've lost the original thread, but would the sources in
> /usr/local/sys/modules get built regardless of what MAKEOBJDIRPREFIX is?
> And, now that
The below installworld material was after an apparently successful
buildworld buildkernel then installkernel . Wrong stage for a cc
producing loader_lua.sym ? (This was a normal, system-clang based
build context, attempting an upgrade from head -r351102 .)
--- realinstall_subdir_stand ---
cc -targ
I upgraded to head -r351153 and then attempted a buildworld
buildkernel via devel/llvm90 (rc2 via ports head -r509054),
but that (from scratch) build attempt got:
--- gptboot.bin ---
objcopy: elf_update() failed: Layout constraint violation
*** [gptboot.bin] Error code 1
make[5]: *** gptboot.bin r
Ian Lepore wrote:
>On Sun, 2019-08-11 at 09:12 -0600, Alan Somers wrote:
>> On Sun, Aug 11, 2019 at 8:57 AM Ian Lepore wrote:
>> >
>> > On Sun, 2019-08-11 at 09:04 +0200, Gary Jennejohn wrote:
>> > > On Sun, 11 Aug 2019 02:03:10 +
>> > > Rick Macklem wrote:
>> > >
>> > > > Hi,
>> > > >
>> > >
34 matches
Mail list logo
