Re: [CFT] [X11] graphics/drm-next-kmod now builds, loads and works on FreeBSD-11-stable

[Kevin Oberman]

On Sun, Feb 18, 2018 at 2:36 PM, Hans Petter Selasky 
wrote:

> On 02/18/18 23:27, Kevin Oberman wrote:
>
>> On Sun, Feb 18, 2018 at 12:35 PM, Hans Petter Selasky 
>> wrote:
>>
>> Hi FreeBSD desktop users!
>>>
>>> During the past week and over the weekend all parts needed for building,
>>> loading and using graphics/drm-next-kmod on FreeBSD-11-stable have been
>>> completed!
>>>
>>> A big thanks to all the people contributing to graphics support under
>>> FreeBSD in both kernel and user-space! You'll find their names in the
>>> commit logs including myself :-)
>>>
>>> Links:
>>> https://www.freshports.org/graphics/drm-next-kmod
>>> https://svnweb.freebsd.org/changeset/base/329527
>>>
>>> Issues are reported here:
>>> https://github.com/FreeBSDDesktop/kms-drm/issues
>>>
>>> --HPS
>>>
>>>
> Hi Kevin,
>
>
>> Wow! That is awesome. Thanks to all of the contributors.
>>
>
> Thank you!
>
>
>> Any instructions? Am I right that the mod setting driver should generally
>> be used. None of the links above really covers implementation.
>>
>
> I believe the package when you install it will give you some instructions
> in the pkg-message.
>
> Basically:
>
> portsnap fetch update
>
> Make sure your kernel sources in /usr/src .
> cd /usr/src
> make buildkernel -jX
> make installkernel -jX
>
> cd /usr/ports/graphics/drm-next-kmod
> make all install clean
>
> Edit /etc/rc.conf and add for example:
>
> kld_list="i915kms"
>
> Then reboot and twin your thumbs.
>
> If it fails goto single user mode.
>
> mount -a
>
> Edit /etc/rc.conf and remove the kld_list=...
> Save and type exit.
>
> Before starting X.org you should have the correct xf86-video-xxx drivers
> installed, because then 2D and 3D acceleration will activate.
>
> A quick tip for tear-free video with intel drivers:
>
> cat /usr/local/etc/X11/xorg.conf.d/20-intel.conf
> Section "Device"
>Identifier  "Device0"
>Driver "intel"
>Option "AccelMethod" "sna"
>Option "TearFree" "true"
> EndSection
>
> --HPS
>

Thanks, Hans! I should have looked at the message file. It explained most
of it, though I especially appreciate the tearfree config as I am using
Intel graphics.

This is also the first I have seen of modular config files. Guess I have
some man page reading to do.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Locale problem updating 10.3 to 11.1

[Trond Endrestøl]

On Mon, 19 Feb 2018 00:02+0100, Eivind Nicolay Evensen wrote:

> Hello.
> 
> After upgrading from 10.3 to 11.1 by building source (as of r329364),
> I experienced some problems that seems to be related to locale.
> 
> Using
> > echo $LANG -- $LC_CTYPE
> no_NO.ISO8859-1 -- no_NO.ISO8859-1

That's nb_NO.ISO8859-1.
nb for norsk bokmål.

> ls emitted question mark for Norwegian characters (æøå), the menu
> and title fonts in fvwm2 displayed unknown to me symbols except for
> certain capital letters and yet other programs like the worker filemanager
> truncated filenames at the first Norwegian letter.
> 
> I had to revert to 10.3 because of this but if anybody has some clues
> what may be the reason for this, I'd appreciate it.

-- 
Trond.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: stable/11 r329462 - Meltdown/Spectre MFC questions

[Shawn Webb]

On Sun, Feb 18, 2018 at 10:02:08PM +, Tim Daneliuk wrote:
> On 02/18/2018 09:50 PM, Eric A. Borisch wrote:
> > 
> > On Sun, Feb 18, 2018 at 3:17 PM Tim Daneliuk  > > wrote:
> > 
> > On 02/18/2018 05:47 PM, David Marec wrote:
> > > #cpucontrol??-u??-v??/dev/cpuctl0
> > > cpucontrol: skipping /usr/local/share/cpucontrol/m32306c3_0022.fw 
> > of rev??0x22:??up??to??date
> > 
> > 
> > While we're on the subject ... where does one find these microcode 
> > updates
> > anyway.?? On a 10.4-STABLE system, the command above blows out because
> > there is no director /usr/local/share/cpucontrol ... so I am missing
> > the magic to get it populated.
> > 
> > --
> > 
> > 
> > Tim Daneliuk?? ?? ??tun...@tundraware.com 
> > PGP Key:?? ?? ?? ?? ??http://www.tundraware.com/PGP/
> > 
> > 
> > It???s provided by the sysutils/devcpu-data port.
> > 
> > ??- Eric
> > 
> > 
> 
> 
> Yes thanks, I finally tripped across that myself :)  Do we have any insight on
> whether this addresses the latest vulnerabilities?

The latest Intel microcode gives CPUs affected by Spectre new MSRs,
one of which is to toggle IBRS. Vendors like Dell have started issuing
firmware updates that also applies the new CPU microcode. Check with
your vendor to see if they've shipped such firmware updates.

Having the CPU microcode applied is not enough. The OS needs to
support the new MSRs. FreeBSD 11-STABLE now does after the PTI and
IBRS MFCs.

Thanks,

-- 
Shawn Webb
Cofounder and Security Engineer
HardenedBSD

Tor-ified Signal:+1 443-546-8752
GPG Key ID:  0x6A84658F52456EEE
GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89  3D9E 6A84 658F 5245 6EEE


signature.asc
Description: PGP signature

Locale problem updating 10.3 to 11.1

[Eivind Nicolay Evensen]

Hello.

After upgrading from 10.3 to 11.1 by building source (as of r329364),
I experienced some problems that seems to be related to locale.

Using
> echo $LANG -- $LC_CTYPE
no_NO.ISO8859-1 -- no_NO.ISO8859-1

ls emitted question mark for Norwegian characters (æøå), the menu
and title fonts in fvwm2 displayed unknown to me symbols except for
certain capital letters and yet other programs like the worker filemanager
truncated filenames at the first Norwegian letter.

I had to revert to 10.3 because of this but if anybody has some clues
what may be the reason for this, I'd appreciate it.

Regards


-- 
Eivind
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [CFT] [X11] graphics/drm-next-kmod now builds, loads and works on FreeBSD-11-stable

[Hans Petter Selasky]

On 02/18/18 23:27, Kevin Oberman wrote:

On Sun, Feb 18, 2018 at 12:35 PM, Hans Petter Selasky 
wrote:


Hi FreeBSD desktop users!

During the past week and over the weekend all parts needed for building,
loading and using graphics/drm-next-kmod on FreeBSD-11-stable have been
completed!

A big thanks to all the people contributing to graphics support under
FreeBSD in both kernel and user-space! You'll find their names in the
commit logs including myself :-)

Links:
https://www.freshports.org/graphics/drm-next-kmod
https://svnweb.freebsd.org/changeset/base/329527

Issues are reported here:
https://github.com/FreeBSDDesktop/kms-drm/issues

--HPS



Hi Kevin,



Wow! That is awesome. Thanks to all of the contributors.


Thank you!



Any instructions? Am I right that the mod setting driver should generally
be used. None of the links above really covers implementation.


I believe the package when you install it will give you some 
instructions in the pkg-message.


Basically:

portsnap fetch update

Make sure your kernel sources in /usr/src .
cd /usr/src
make buildkernel -jX
make installkernel -jX

cd /usr/ports/graphics/drm-next-kmod
make all install clean

Edit /etc/rc.conf and add for example:

kld_list="i915kms"

Then reboot and twin your thumbs.

If it fails goto single user mode.

mount -a

Edit /etc/rc.conf and remove the kld_list=...
Save and type exit.

Before starting X.org you should have the correct xf86-video-xxx drivers 
installed, because then 2D and 3D acceleration will activate.


A quick tip for tear-free video with intel drivers:

cat /usr/local/etc/X11/xorg.conf.d/20-intel.conf
Section "Device"
   Identifier  "Device0"
   Driver "intel"
   Option "AccelMethod" "sna"
   Option "TearFree" "true"
EndSection

--HPS
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [CFT] [X11] graphics/drm-next-kmod now builds, loads and works on FreeBSD-11-stable

[Ian Lepore]

On Sun, 2018-02-18 at 14:27 -0800, Kevin Oberman wrote:
> On Sun, Feb 18, 2018 at 12:35 PM, Hans Petter Selasky 
> wrote:
> 
> > 
> > Hi FreeBSD desktop users!
> > 
> > During the past week and over the weekend all parts needed for building,
> > loading and using graphics/drm-next-kmod on FreeBSD-11-stable have been
> > completed!
> > 
> > A big thanks to all the people contributing to graphics support under
> > FreeBSD in both kernel and user-space! You'll find their names in the
> > commit logs including myself :-)
> > 
> > Links:
> > https://www.freshports.org/graphics/drm-next-kmod
> > https://svnweb.freebsd.org/changeset/base/329527
> > 
> > Issues are reported here:
> > https://github.com/FreeBSDDesktop/kms-drm/issues
> > 
> > --HPS
> > 
> Wow! That is awesome. Thanks to all of the contributors.
> 
> Any instructions? Am I right that the mod setting driver should generally
> be used. None of the links above really covers implementation.

+1.  I have the vague notion that drm-next has something to do with
supporting newer graphics hardware.  Since I just bought a new x86 box
whose builtin radeon R6 isn't supported by -current that sounds
interesting to me, where do I find out more about drm-next and how to
try it?

-- Ian 

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [CFT] [X11] graphics/drm-next-kmod now builds, loads and works on FreeBSD-11-stable

[Kevin Oberman]

On Sun, Feb 18, 2018 at 12:35 PM, Hans Petter Selasky 
wrote:

> Hi FreeBSD desktop users!
>
> During the past week and over the weekend all parts needed for building,
> loading and using graphics/drm-next-kmod on FreeBSD-11-stable have been
> completed!
>
> A big thanks to all the people contributing to graphics support under
> FreeBSD in both kernel and user-space! You'll find their names in the
> commit logs including myself :-)
>
> Links:
> https://www.freshports.org/graphics/drm-next-kmod
> https://svnweb.freebsd.org/changeset/base/329527
>
> Issues are reported here:
> https://github.com/FreeBSDDesktop/kms-drm/issues
>
> --HPS
>

Wow! That is awesome. Thanks to all of the contributors.

Any instructions? Am I right that the mod setting driver should generally
be used. None of the links above really covers implementation.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: stable/11 r329462 - Meltdown/Spectre MFC questions

[Tim Daneliuk]

On 02/18/2018 09:50 PM, Eric A. Borisch wrote:
> 
> On Sun, Feb 18, 2018 at 3:17 PM Tim Daneliuk  > wrote:
> 
> On 02/18/2018 05:47 PM, David Marec wrote:
> > #cpucontrol -u -v /dev/cpuctl0
> > cpucontrol: skipping /usr/local/share/cpucontrol/m32306c3_0022.fw 
> of rev 0x22: up to date
> 
> 
> While we're on the subject ... where does one find these microcode updates
> anyway.  On a 10.4-STABLE system, the command above blows out because
> there is no director /usr/local/share/cpucontrol ... so I am missing
> the magic to get it populated.
> 
> --
> 
> 
> Tim Daneliuk     tun...@tundraware.com 
> PGP Key:         http://www.tundraware.com/PGP/
> 
> 
> It’s provided by the sysutils/devcpu-data port.
> 
>  - Eric
> 
> 


Yes thanks, I finally tripped across that myself :)  Do we have any insight on
whether this addresses the latest vulnerabilities?

-- 

Tim Daneliuk tun...@tundraware.com
PGP Key: http://www.tundraware.com/PGP/

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: stable/11 r329462 - Meltdown/Spectre MFC questions

[Eric A. Borisch]

On Sun, Feb 18, 2018 at 3:17 PM Tim Daneliuk  wrote:

> On 02/18/2018 05:47 PM, David Marec wrote:
> > #cpucontrol -u -v /dev/cpuctl0
> > cpucontrol: skipping /usr/local/share/cpucontrol/m32306c3_0022.fw of
> rev 0x22: up to date
>
>
> While we're on the subject ... where does one find these microcode updates
> anyway.  On a 10.4-STABLE system, the command above blows out because
> there is no director /usr/local/share/cpucontrol ... so I am missing
> the magic to get it populated.
>
> --
>
> 
> Tim Daneliuk tun...@tundraware.com
> PGP Key: http://www.tundraware.com/PGP/


It’s provided by the sysutils/devcpu-data port.

 - Eric


>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: stable/11 r329462 - Meltdown/Spectre MFC questions

[Tim Daneliuk]

On 02/18/2018 05:47 PM, David Marec wrote:
> #cpucontrol -u -v /dev/cpuctl0
> cpucontrol: skipping /usr/local/share/cpucontrol/m32306c3_0022.fw of rev 
> 0x22: up to date


While we're on the subject ... where does one find these microcode updates
anyway.  On a 10.4-STABLE system, the command above blows out because
there is no director /usr/local/share/cpucontrol ... so I am missing
the magic to get it populated.

-- 

Tim Daneliuk tun...@tundraware.com
PGP Key: http://www.tundraware.com/PGP/

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[CFT] [X11] graphics/drm-next-kmod now builds, loads and works on FreeBSD-11-stable

[Hans Petter Selasky]

Hi FreeBSD desktop users!

During the past week and over the weekend all parts needed for building, 
loading and using graphics/drm-next-kmod on FreeBSD-11-stable have been 
completed!


A big thanks to all the people contributing to graphics support under 
FreeBSD in both kernel and user-space! You'll find their names in the 
commit logs including myself :-)


Links:
https://www.freshports.org/graphics/drm-next-kmod
https://svnweb.freebsd.org/changeset/base/329527

Issues are reported here:
https://github.com/FreeBSDDesktop/kms-drm/issues

--HPS
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: stable/11 r329462 - Meltdown/Spectre MFC questions

[David Marec]

On 18.02.2018 17:50, Shawn Webb wrote:


Strange thing is that tweaking `hw.ibrs_disable` has no effect on
`hw.ibrs_active` on my side.


Did you install the latest Intel microcode update?



Hum, I thought I did, but I don't know actually if the following is the 
latest revision of the microcode:


#cpucontrol -u -v /dev/cpuctl0
cpucontrol: skipping /usr/local/share/cpucontrol/m32306c3_0022.fw of 
rev 0x22: up to date





--
David Marec
https://lapinbilly.eu/
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: stable/11 r329462 - Meltdown/Spectre MFC questions

[Shawn Webb]

On Sun, Feb 18, 2018 at 05:04:55PM +0100, David Marec wrote:
> On 17.02.2018 20:47, Jeremy Chadwick wrote:
> > hw.ibrs_disable
> >- Description: Disable Indirect Branch Restricted Speculation
> >- Loader tunable and sysctl tunable (read-write)
> >- Integer
> >- Default value: unsure.  Variable declaration has 1 but
> >  SYSCTL_PROC() macro has 0.
> > 
> 
> 
> Strange thing is that tweaking `hw.ibrs_disable` has no effect on
> `hw.ibrs_active` on my side.

Did you install the latest Intel microcode update?

Thanks,

-- 
Shawn Webb
Cofounder and Security Engineer
HardenedBSD

Tor-ified Signal:+1 443-546-8752
GPG Key ID:  0x6A84658F52456EEE
GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89  3D9E 6A84 658F 5245 6EEE


signature.asc
Description: PGP signature

Re: stable/11 r329462 - Meltdown/Spectre MFC questions

[David Marec]

On 17.02.2018 20:47, Jeremy Chadwick wrote:

hw.ibrs_disable
   - Description: Disable Indirect Branch Restricted Speculation
   - Loader tunable and sysctl tunable (read-write)
   - Integer
   - Default value: unsure.  Variable declaration has 1 but
 SYSCTL_PROC() macro has 0.




Strange thing is that tweaking `hw.ibrs_disable` has no effect on 
`hw.ibrs_active` on my side.


--
David Marec
https://lapinbilly.eu/
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Problems building 11-stable/i386 with readonly /usr/src

[Kyle Evans]

On Sun, Feb 18, 2018 at 3:12 AM, Peter Jeremy  wrote:
> Sometime between r329122 and r329157, my 11-stable i386 box stopped
> being able to buildworld with a readonly /usr/src. I've been updating
> regularly but the problem still remains at r329450.  I don't have any
> problems building the same tree on amd64 or building head on i386 or
> amd64.  Does anyone have any ideas?
>
> Starting from an empty /usr/obj, the failure is:
> ...

This would have come in with the recent MFC of imp@'s rototilling. I
seem to recall some build system funkiness that put .OBJDIR inside the
src tree inconsistently before recent-ish changes in head. CC'ing
bdrewery@ and imp@ in hopes they have an idea of how to handle this in
stable/11. The offending ln invocation would be this one:
https://svnweb.freebsd.org/base/stable/11/stand/defs.mk?view=markup#l178
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: stable/11 r329462 - Meltdown/Spectre MFC questions

[Mike Tancsa]

did a few simple buildworlds before and after on an Epyc box, and it had
no significant impact. Its vulnerable just to spectre.  I am just
updating an intel box to see the impact of the Meltdown fixes.  From
what I recall, apps that do a lot of system calls will have the largest
impact.

---Mike


On 2/17/2018 3:38 PM, Pete French wrote:
> 
> 
> On 17/02/2018 20:19, Matt Smith wrote:
> 
>> And thank you for pointing this out. I can now just wait a while to
>> see what comes along rather than accidentally upgrading it and killing
>> the already really slow performance.
>>
> I was just looking at this too, and wondering what (if any) the
> performance impact is on FreeBSD. I had a quick google to see if I could
> fine anything on current about it, but no luck. Anyone done any
> measurements ?
> 
> -pete.
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
> 
> 


-- 
---
Mike Tancsa, tel +1 519 651 3400 x203
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problems building 11-stable/i386 with readonly /usr/src

[Peter Jeremy]

Sometime between r329122 and r329157, my 11-stable i386 box stopped
being able to buildworld with a readonly /usr/src. I've been updating
regularly but the problem still remains at r329450.  I don't have any
problems building the same tree on amd64 or building head on i386 or
amd64.  Does anyone have any ideas?

Starting from an empty /usr/obj, the failure is:
...
>>> stage 4.3: building everything
...
===> stand/zfs (all)
Building /usr/obj/usr/src/stand/zfs/machine
machine -> /usr/src/sys/i386/include
Building /usr/obj/usr/src/stand/zfs/x86
x86 -> /usr/src/sys/x86/include
Building /usr/obj/usr/src/stand/zfs/zfs.o
Building /usr/obj/usr/src/stand/zfs/skein.o
Building /usr/obj/usr/src/stand/zfs/skein_block.o
Building /usr/obj/usr/src/stand/zfs/libzfsboot.a
building static zfsboot library
===> stand/efi (all)
machine -> /usr/src/sys/i386/include
ln: machine: Read-only file system
*** Error code 1

Stop.
make[4]: stopped in /usr/src/stand/efi
.ERROR_TARGET='machine'
.ERROR_META_FILE=''
.MAKE.LEVEL='4'
MAKEFILE=''
.MAKE.MODE='meta missing-filemon=yes missing-meta=yes silent=yes verbose'
_ERROR_CMD='.PHONY'
.CURDIR='/usr/src/stand/efi'
.MAKE='make'
.OBJDIR='/usr/src/stand/efi'
.TARGETS='all'
DESTDIR='/usr/obj/usr/src/tmp'
LD_LIBRARY_PATH=''
MACHINE='i386'
MACHINE_ARCH='i386'
MAKEOBJDIRPREFIX='/usr/obj'
MAKESYSPATH='/usr/src/share/mk'
MAKE_VERSION='20170720'
PATH='/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/bin:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/sbin:/bin:/usr/sbin:/usr/bin'
SRCTOP='/usr/src'
OBJTOP='/usr/src'
.MAKE.MAKEFILES='/usr/src/share/mk/sys.mk /usr/src/share/mk/local.sys.env.mk 
/usr/src/share/mk/src.sys.env.mk /etc/src-env.conf 
/usr/src/share/mk/bsd.mkopt.mk /etc/make.conf /usr/src/share/mk/local.sys.mk 
/usr/src/share/mk/src.sys.mk Makefile /usr/src/share/mk/bsd.init.mk 
/usr/src/share/mk/bsd.opts.mk /usr/src/share/mk/bsd.cpu.mk 
/usr/src/share/mk/local.init.mk /usr/src/share/mk/src.init.mk 
/usr/src/stand/efi/../Makefile.inc /usr/src/stand/efi/../defs.mk 
/usr/src/share/mk/src.opts.mk /usr/src/share/mk/bsd.own.mk 
/usr/src/share/mk/bsd.compiler.mk /usr/src/share/mk/bsd.compiler.mk 
/usr/src/share/mk/bsd.subdir.mk'
.PATH='. /usr/src/stand/efi'
*** Error code 1

-- 
Peter Jeremy


signature.asc
Description: PGP signature