what's an ifunc?
___
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"
On 4 Nov 2018, at 08:43, Julian Elischer wrote:
>
> what's an ifunc?
This is a GNU extension, an "indirect function". It allows you to
provide multiple different implementations of the same function, for
instance optimized for specific CPU types, and choose between them at
dynamic link time (e.
On 03/11/2018 10:56, Jan Beich wrote:
> …
> Why not update? Mk/bsd.gecko.mk hasn't changed incompatibly yet.
> 1. Drop PORTREVISION line
> 2. Bump 56.2.3 to 56.2.5
> 3. Run "make makesum"
> 4. Run "make all deinstall install clean"
That's a pleasant surprise, I had no idea I could go with 56.2.5.
I'm trying to build -CURRENT, AMD64, r340113, but get an error when "make
buildworld" tries to build usr.sbin/pkg.
===
cc -O2 -pipe -I/usr/src/contrib/libucl/include -g -std=gnu99
-fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W
-Wno-unused-parameter -Wstrict-prototype
> -Original Message-
> From: owner-freebsd-curr...@freebsd.org curr...@freebsd.org> On Behalf Of Marie Helene Kvello-Aune
> Sent: søndag 4. november 2018 12:18
> To: freebsd-current@freebsd.org
> Subject: base/head r340113: usr.sbin/pkg fails to build, doesn't grok
> FreeBSD.conf
>
> I'm
On Sun, Nov 04, 2018 at 12:43:34AM -0700, Julian Elischer wrote:
> what's an ifunc?
>
A special kind of relocation, controlled by the user code.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To un
On Sun, Nov 4, 2018 at 12:55 AM Poul-Henning Kamp
wrote:
> With the 12.0-BETA3 BEAGLEBONE image, I very often see this panic
> when I plug a USB attached SSD disk in.
>
...
>umass0 on uhub0
> umass0:
> on usbus1
> umass0: SCSI over Bulk-Only; quirks = 0x8100
> u
===> libexec/dma/dma-mbox-create (all)
Building
/usr/obj/usr/src/amd64.amd64/libexec/dma/dma-mbox-create/dma-mbox-create.o
In file included from /usr/src/contrib/dma/dma-mbox-create.c:51:
/usr/obj/usr/src/amd64.amd64/tmp/usr/include/capsicum_helpers.h:161:1:
error: all paths through this function w
Confirmed to be fixed by SVN r340134 - thanks!
On 11/4/18 1:50 PM, Michael Butler wrote:
> ===> libexec/dma/dma-mbox-create (all)
> Building
> /usr/obj/usr/src/amd64.amd64/libexec/dma/dma-mbox-create/dma-mbox-create.o
> In file included from /usr/src/contrib/dma/dma-mbox-create.c:51:
> /usr/obj/us
On Sun, Nov 04, 2018 at 01:50:31PM -0500, Michael Butler wrote:
> ===> libexec/dma/dma-mbox-create (all)
> Building
> /usr/obj/usr/src/amd64.amd64/libexec/dma/dma-mbox-create/dma-mbox-create.o
> In file included from /usr/src/contrib/dma/dma-mbox-create.c:51:
> /usr/obj/usr/src/amd64.amd64/tmp/usr/
I have a set of older machines (e.g. AMD Phenom II, Radeon HD3300
gpu) which will be updated from 11. to 12.0 once 12 is out
and the initial round of bugs are squashed.
One system is being done now, to allow time to catch any major
problems and then plan the update process.
Hi,
Haven't seen this reported yet, so here it is. Found on last week's
world, rebuild last night and still there. Worth filing a bug?
storm~;uname -a
FreeBSD storm 13.0-CURRENT FreeBSD 13.0-CURRENT r339863 GENERIC amd64
Trying to run unbound, and:
storm~;sudo unbound -dd
ld-elf.so.1: /usr/sbi
On 11/4/18 8:29 PM, Robert Huff wrote:
I have a set of older machines (e.g. AMD Phenom II, Radeon HD3300
gpu) which will be updated from 11. to 12.0 once 12 is out
and the initial round of bugs are squashed.
One system is being done now, to allow time to catch any major
problems
I'm currently working on creating and updating the ESP (EFI System Partition)
for UEFI booting during installation and installworld.
During installation, with my changes it gets mounted on /boot/efi and
loader.efi
copied into /boot/efi/EFI/FreeBSD and /boot/efi/EFI/BOOT. An entry gets added
t
On 2018-11-04 16:20, Rebecca Cran wrote:
> I'm currently working on creating and updating the ESP (EFI System Partition)
> for UEFI booting during installation and installworld.
>
> During installation, with my changes it gets mounted on /boot/efi and
> loader.efi
> copied into /boot/efi/EFI/F
On Sunday, 4 November 2018 14:25:26 MST Allan Jude wrote:
> I wouldn't depend on the /etc/fstab entry existing. I am not sure I want
> installworld randomly fobbing around in my EFI partition. Especially if,
> for example, my EFI/BOOT is not FreeBSD, but rEFInd or something.
I tend to agree. I ha
> On 4 Nov 2018, at 23:25, Allan Jude wrote:
>
> On 2018-11-04 16:20, Rebecca Cran wrote:
>> I'm currently working on creating and updating the ESP (EFI System
>> Partition)
>> for UEFI booting during installation and installworld.
>>
>> During installation, with my changes it gets mounted
On Sunday, 4 November 2018 14:36:13 MST Toomas Soome wrote:
> it is reasonable to have efi/freebsd directory, the efi/boot/bootx64.efi is
> hard one of course. But then again, it is problem only when we can not
> setup EFI bootmanager variables ? the bootx64.efi is default when bootmgr
> is not se
On 11/4/18, Rebecca Cran wrote:
> On Sunday, 4 November 2018 14:36:13 MST Toomas Soome wrote:
>
>> it is reasonable to have efi/freebsd directory, the efi/boot/bootx64.efi
>> is
>> hard one of course. But then again, it is problem only when we can not
>> setup EFI bootmanager variables ? the bootx
Baptiste Daroussin wrote:
> On Sun, Nov 04, 2018 at 09:35:48AM +0300, Yuri Pankov wrote:
>> Hi,
>>
>> Looking through https://wiki.freebsd.org/DevSummit/201810, I noticed the
>> following entry:
>>
>> - Make C.UTF-8 the default locale (conrad, dteske(installer))
>>
>> As this sort of change is bett
On Sun, Nov 4, 2018 at 2:43 PM Rebecca Cran wrote:
> On Sunday, 4 November 2018 14:36:13 MST Toomas Soome wrote:
>
> > it is reasonable to have efi/freebsd directory, the efi/boot/bootx64.efi
> is
> > hard one of course. But then again, it is problem only when we can not
> > setup EFI bootmanager
On Sun, Nov 4, 2018 at 2:27 PM Allan Jude wrote:
> On 2018-11-04 16:20, Rebecca Cran wrote:
> > I'm currently working on creating and updating the ESP (EFI System
> Partition)
> > for UEFI booting during installation and installworld.
> >
> > During installation, with my changes it gets mounted o
On Sunday, 4 November 2018 15:56:25 MST Warner Losh wrote:
> I think that's a really really bad idea. We should *NEVER* create them by
> default. We are only sliding by on the coat-tails of compatibility by using
> efi/boot/boot*.efi. We shouldn't use those at all, unless there's a
> compelling re
On Sun, Nov 4, 2018 at 4:10 PM Rebecca Cran wrote:
> On Sunday, 4 November 2018 15:56:25 MST Warner Losh wrote:
>
> > I think that's a really really bad idea. We should *NEVER* create them by
> > default. We are only sliding by on the coat-tails of compatibility by
> using
> > efi/boot/boot*.efi.
On Sunday, 4 November 2018 16:07:17 MST Warner Losh wrote:
> Finally, I have a /dev/efi/esp pseudo label support coded up for geom
> (along with /dev/efi/boot for the putative root device). There's some
> issues with it, so I set it aside some time ago to work on other higher
> priority things. We
On Sun, Nov 4, 2018 at 12:15 PM Niclas Zeising wrote:
> On 11/4/18 8:29 PM, Robert Huff wrote:
> >
> > I have a set of older machines (e.g. AMD Phenom II, Radeon HD3300
> > gpu) which will be updated from 11. to 12.0 once 12 is out
> > and the initial round of bugs are squashed.
> > O
Thanks John. I tried building a kernel with these changes and things are
working good. I could able to boot without any tunables.
Thanks again.
On Fri, Nov 2, 2018 at 12:05 AM John Baldwin wrote:
> On 10/30/18 1:22 AM, Rajesh Kumar wrote:
> > Hi John,
> >
> > Thanks for your updates. I assume
27 matches
Mail list logo
