GHC Port on 9-CURRENT

it would be prudent to set CC=gcc and CXX=g++ in the makefile for the time being and mark the port as working again? -- Eric McCorkle Computer Science Ph.D Student, University of Massachusetts Research Intern, IBM Research ___ freebsd-current@freebsd.org

Clang buildworld failure due to multiple definitions of __isnanf

of clang's builtins, actually.) Anyway, I hope this helps someone. PS. Sorry I don't have build logs, assembler output, etc. My FreeBSD machine's wireless card isn't supported (yet). -- Eric McCorkle Computer Science Ph.D Student, University of Massachusetts Research Intern, IBM Research

Re: Clang buildworld failure due to multiple definitions of __isnanf

On 6/27/11 8:29 AM, Dimitry Andric wrote: On 2011-06-27 04:32, Eric McCorkle wrote: I've both seen reports and experienced make buildworld with clang failing in usr.bin/xlint/lint1 (really, make kernel-toolchain is what fails), because lint1 is statically linked, and there is a definition

Re: Clang buildworld failure due to multiple definitions of __isnanf

On 6/28/11 1:42 AM, Benjamin Kaduk wrote: On Tue, 28 Jun 2011, Benjamin Kaduk wrote: On Mon, 27 Jun 2011, Eric McCorkle wrote: make.conf: CPUTYPE?=core2 .if !defined(CC) || ${CC} == cc CC=clang CFLAGS=-Qunused-arguments .endif .if !defined(CXX) || ${CXX} == c++ CXX=clang++ .endif NO_WERROR

Re: GHC Port on 9-CURRENT

On 6/25/11 9:07 PM, Gabor PALI wrote: I would be happy to see the logs. Attached. Sorry it took so long. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to

Re: FreeBSD 9 + ZFS + MPS

On 7/25/11 11:32 AM, Tim Gustafson wrote: I'm seeing some odd behavior on FreeBSD 9 with ZFS and an MPS controller. For two or three weeks, this configuration was working like a champ. It's a Bacula storage daemon server and was getting considerable usage - our backup set is in the

ACPI battery problem and solution

Hello, I'm running 9.0-CURRENT on a MacbookPro 5,5. Following a recent update, I found that the acpi battery functionality had stopped working. I suspect, given the nature of it, that other people may have seen this problem as well. I did some work, and traced the problem to its source. The

Re: ACPI battery problem and solution

On 09/19/11 23:46, Adrian Chadd wrote: Would you mind filing a PR? This kind of thing is important and best not to get lost. :) Done. Identifier is kern/160838. signature.asc Description: OpenPGP digital signature

Re: Boot FreeBSD-current on macbook from USB stick ?

On 09/23/11 15:12, Poul-Henning Kamp wrote: Has anybody managed this on an unadultered MacBook ? I've tried with rEFIt and it sees the FreeBSD, but it doesn't boot for me :-/ I have. There's some information which isn't easy co come by: Macs use a non-standard EFI boot process. They

Re: problems with cvsup on FreeBSD 9 snapshot 201101

, I don't know. -- Eric McCorkle Computer Science Ph.D Student, University of Massachusetts Research Intern, IBM Research ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail

Re: problems with cvsup on FreeBSD 9 snapshot 201101

compiler to Mac OS a couple of years back. -- Eric McCorkle Computer Science Ph.D student, University of Massachusetts Research Intern, IBM Research ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current

Re: problems with cvsup on FreeBSD 9 snapshot 201101

On 6/15/11 10:58 AM, Kostik Belousov wrote: On Wed, Jun 15, 2011 at 10:24:46AM -0400, Eric McCorkle wrote: On 6/15/11 8:23 AM, Holger Kipp wrote: Dear all, I had installed FreeBSD 9 amd64 from snapshot (ISO-image) located here: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201101/FreeBSD-9.0

Re: CFT update day 2

Ok, When I load the module, it the screen blanks for a second as it does when switching framebuffer drivers. However, it looks like this fails, as the last kernel message is *ERROR*: switching to FCLK failed Not sure how I can get more detailed information. > On May 26, 2016, at 19:08, E

Re: CFT update day 2

Letting you know, I had an error in detection. I'm trying to get a change done before code slush, but I will circle back and provide a detailed report On May 23, 2016 4:12:52 AM EDT, Matthew Macy wrote: > >The highlights for today are the following: > >Bug fixes: >- Will

CFT EFI Boot Refactoring

]->name); + if (efi_drivers[i]->init != NULL) + efi_drivers[i]->init(); } + putchar('\n'); try_boot(); /* If we get here, we're out of luck... */ panic("No bootable partitions found!"); } - -/* - * add_device adds a device to the passed devinfo list. - */ -void -add

Re: GELI with UEFI supporting Boot Environments goes to HEAD when?

Right, so basically, the remaining GELI patches are against loader, and most of them can go in independently of the work on removing boot1. There's a unanimous consensus on getting rid of boot1 which includes its original author, so that's going to happen. For GELI, we have the following (not

Re: GELI with UEFI supporting Boot Environments goes to HEAD when?

I'll reply in more detail later on, when I'm not on a phone On November 15, 2017 9:47:54 AM EST, Warner Losh wrote: >On Wed, Nov 15, 2017 at 3:28 AM, Tommi Pernila > >wrote: > >> Hi All, >> >> Anyone have an idea when the GELI with UEFI supporting Boot

Re: GELI with UEFI supporting Boot Environments goes to HEAD when?

loader.efi to function when installed directly to the ESP: https://reviews.freebsd.org/D13497 On 02/20/2018 22:56, Tommi Pernila wrote: > Hi Eric, > > could you provide a brief update how the work is going? > > > Br, > > Tommi > > > On Nov 16, 2017 04:29, &quo

Re: GELI with UEFI supporting Boot Environments goes to HEAD when?

FYI, I just IFC'ed everything, and the current patches are still fine. Also, the full GELI + standalone loader has been deployed on one of my laptops for some time now. On 02/21/2018 18:15, Eric McCorkle wrote: > The GELI work could be merged at this point, though it won't be usable > w

Re: Status of OpenSSL 1.1.1

On 08/01/2018 09:02, Warner Losh wrote: > > > On Wed, Aug 1, 2018, 12:31 PM Eric McCorkle <mailto:e...@metricspace.net>> wrote: > > Hi folks, > > I'm wondering what's the status of OpenSSL 1.1.1 integration into base? > More specifically, is there

Re: Status of OpenSSL 1.1.1

On 08/03/2018 04:44, Warner Losh wrote: > > > On Thu, Aug 2, 2018 at 5:45 PM, Benjamin Kaduk <mailto:ka...@mit.edu>> wrote: > > On Wed, Aug 01, 2018 at 10:05:28AM -0400, Eric McCorkle wrote: > > On 08/01/2018 09:02, Warner Losh wrote: > > >

Status of OpenSSL 1.1.1

Hi folks, I'm wondering what's the status of OpenSSL 1.1.1 integration into base? More specifically, is there a repo or a branch that's started the integration? I'm aware of the wiki page and the list of port build issues, but that seems to be based on replacing the base OpenSSL with a port

Re: GELI with UEFI supporting Boot Environments goes to HEAD when?

PM EDT, Ian Lepore wrote: >On Sun, 2018-07-08 at 21:08 +0200, Oliver Pinter wrote: >> Hi! >> >> Have you or Warner any update on this code? >> >> On Thursday, April 12, 2018, Eric McCorkle >> wrote: >> > >Are you aware of https://reviews.fr

Re: GELI with UEFI supporting Boot Environments goes to HEAD when?

> very constrained. > > Warner > > On Wed, Apr 11, 2018 at 6:02 PM, Eric McCorkle <e...@metricspace.net > <mailto:e...@metricspace.net>> wrote: > > I think the thing to do at this point is to wait for the current work on > loader.efi to land, then adapt

Re: GELI with UEFI supporting Boot Environments goes to HEAD when?

ng the rebase or the inclusion to base > system? > On 3/28/18, Eric McCorkle <e...@metricspace.net > <mailto:e...@metricspace.net>> wrote: > > I'll do another rebase from head just to be sure > > > > On March 28, 2018 3:23:23 PM EDT, W

Re: GELI with UEFI supporting Boot Environments goes to HEAD when?

gt;> Awesome, thanks for the update and the work that you have done! >> >> Now we just need some more reviewers eyes on the code :) >> >> Br, >> >> Tommi >> >> On Thu, 22 Feb 2018 at 2.03, Eric McCorkle <e...@metricspace.net> >wrote: >>

Re: Trouble building world

I'm not sure why nobody else is seeing this, but the files are indeed missing includes of string.h. I have a small patch that adds them, but I'm having unrelated build issues stemming from OpenSSL 1.1.1 On 10/10/18 7:09 AM, Eric McCorkle wrote: > make.conf: > > CPUTYPE?=native > KER

Re: r339289 buildworld stopped in /usr/src/secure/lib/libcrypto

I'm seeing this one, and am dead in the water from it :( On 10/11/18 3:07 PM, Glen Barber wrote: > On Thu, Oct 11, 2018 at 09:05:52AM +0200, Raúl wrote: >> Maybe related to recent Glen's Heads-UP? >> >> https://lists.freebsd.org/pipermail/freebsd-current/2018-October/071581.html >> > > No, this

OpenSSL 1.1.1 Update report (ongoing)

I'm currently in the process of updating my laptop, rebuilding world, then rebuilding *all* ports. I have a large number of ports installed (around 1200), and I tend to select a lot of build options. This report is intended to help shake out issues relating to OpenSSL 1.1.1. I'll be adding to

Re: OpenSSL 1.1.1 Update report (ongoing)

. Currently a little over halfway through. On 10/14/18 9:18 AM, Eric McCorkle wrote: > I'm currently in the process of updating my laptop, rebuilding world, > then rebuilding *all* ports. I have a large number of ports installed > (around 1200), and I tend to select a lot of buil

Re: OpenSSL 1.1.1 Update report (ongoing)

of opal. * ffmpeg: autoconf fails to detect openssl. Probably easily fixable, but the trivial workaround is to tick the GNUTLS option (emacs ends up dragging in GNUTLS anyway, so it doesn't add more packages) On 10/14/18 1:31 PM, Eric McCorkle wrote: > More: > > * ImageMagick (

Re: OpenSSL 1.1.1 Update report (ongoing)

* gnome-vfs: C compile errors related to openssl, no viable mitigation Almost done now, though ptlib and gnome-vfs may cause runtime trouble On 10/14/18 7:13 PM, Eric McCorkle wrote: > * ptlib; Fails to build, due to C compiler errors arising from > source-level incompatibilities. Thi

Re: Trouble building world

WITHOUT_NCP=1 WITHOUT_NIS=1 WITHOUT_OFED=1 WITHOUT_PPP=1 WITHOUT_RADIUS_SUPPORT=1 WITHOUT_RBOOTD=1 WITHOUT_RCMDS=1 WITHOUT_TALK=1 WITHOUT_TELNET=1 WITHOUT_VI=1 I'm doing the standard "make buildworld" On 10/8/18 1:43 AM, Dimitry Andric wrote: > On 7 Oct 2018, at 23:28, Eric McCorkle wro

Trouble building world

I'm having some trouble building world from current. The problem looks to be various tools' c++ files not including string.h, and therefore missing defs. Is there some critical update step I missed somewhere? signature.asc Description: OpenPGP digital signature

FreeBSD and Coreboot

Hello everyone, I'm through enough of my job change that I can start working on FreeBSD again. One thing I've had on my list to examine is using FreeBSD with coreboot, so I wanted to put out a call for anyone who has done work on this, or knows anything about it. Here is what I know: *

Re: FreeBSD and Coreboot

On 5/27/19 5:53 PM, Edward Napierala wrote: > On Mon, 27 May 2019 at 16:14, Eric McCorkle wrote: > > [..] > >> My plan is roughly this: >> >> * Refurbish the GRUB port, get it working again in QEMU (possibly on one >> of my machines), also possibly pus

Re: FreeBSD and Coreboot

On 5/27/19 11:13 AM, Eric McCorkle wrote: > My plan is roughly this: > > * Refurbish the GRUB port, get it working again in QEMU (possibly on one > of my machines), also possibly push a patch to GRUB to use the keybufs > mechanism to pass in GELI keys. I managed to get the grub2

Re: FreeBSD and Coreboot

:nwhiteh...@freebsd.org>> > > wrote: > > > >> > >> On 2019-05-27 15:50, Eric McCorkle wrote: > >>> On 5/27/19 5:53 PM, Edward Napierala wrote: > >>>> On Mon, 27 May 2019 at 16:14, Eric McCorkle >

Re: Working on Zoom port

On 4/13/20 2:59 PM, Pete Wright wrote: > Thanks Eric, I remember trying to get this working several months ago > via the linux compatibility layer and got stuck.  i hope to take another > wack at it based on your repository.  in my ideal world i'd be able to > get this working in a jail via, but

Working on Zoom port

All, Given how Zoom is getting used a lot more these days, I've started working on a port that installs the Zoom linux client. Here is a link to my github if anyone wants to help: https://github.com/emc2/freebsd-ports/tree/zoom I'm not done yet. The zoom linux client installs a bunch of Qt

Re: Working on Zoom port

On 4/12/20 9:58 PM, Rodney W. Grimes wrote: > You are aware of the rather large pile of recent security issues > surronding zoom I hope. > I am. All the same, some of us have to use it for work... signature.asc Description: OpenPGP digital signature

Problem with zfs.ko: lockstat_enabled symbol

I recently updated my other laptop, and now I'm getting a problem loading zfs.ko at boot, relating to the lockstat_enabled symbol not being defined (this happens during kernel boot and prevents mounting root, so I can't get an exact trace) Looking at the new kernel, it seems that only zfs.ko

Re: PAM module for loading ZFS keys on login

Interesting, I wasn't aware of the upstream module. I'd say that's preferable to the one I wrote. I think you would need to wire that into the 'modules' directory under libpam. I can look into doing that. On 9/5/21 11:27 AM, Greg wrote: > > > On September 5, 2021 4:54:26 PM GMT+03

Re: PAM module for loading ZFS keys on login

data after I'm gone.) On 9/6/21 10:01 AM, Steffen Nurpmeso wrote: > Eric McCorkle wrote in > : > |Interesting, I wasn't aware of the upstream module. I'd say that's > > It's existence was the reason i have readded (now optional, and > a tad different) session support for my

Re: PAM module for loading ZFS keys on login

ting that apparently they change the key to the dataset when the user changes their password. Anyway, I've seen enough. I'm going to abandon the review for my PAM module and use the upstream one. I'm going to keep the review for the autounmountd patch live, though. On 9/6/21 2:53 PM, Steff

PAM module for loading ZFS keys on login

All, This patch creates a new PAM module that will load a ZFS key upon a successful login: https://reviews.freebsd.org/D31844. It will use the user's auth token as the key argument to loading a ZFS encryption key on a user-specific ZFS data set. This is the other side of my changeset to have