Re: Trouble building world

2018-10-07 Thread Dimitry Andric 
On 7 Oct 2018, at 23:28, Eric McCorkle  wrote:
> 
> 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?

If the headers are there, usually the problem is that you are overriding
CFLAGS and/or CXXFLAGS in a way so that makefiles can't add or remove
flags.  What are the contents of your /etc/make.conf and /etc/src.conf, and how
are you exactly invoking buildworld?

-Dimitry



signature.asc
Description: Message signed with OpenPGP

Trouble building world

2018-10-07 Thread Eric McCorkle 
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

Re: dmesg submission service -- please submit today

2018-10-07 Thread Warner Losh 
On Sun, Oct 7, 2018 at 3:49 AM Konstantin Belousov 
wrote:

> On Sat, Oct 06, 2018 at 11:40:36PM -0600, Warner Losh wrote:
> > On Sat, Oct 6, 2018 at 12:48 PM Warner Losh  wrote:
> >
> > > Greetings,
> > >
> > > As you can tell, the project is looking to clear some of the deadwood
> from
> > > its driver lists. One problem is that we have to guess what's in used
> based
> > > on our personal experience. This has proven to be less reliable than
> hoped
> > > in the 10/100 discussions that are going on now.
> > >
> > > So, to that end, I'd like to request as many people as possible submit
> > > their current dmesg to the service at
> http://dmesgd.nycbug.org/index.cgi
> > > so that we have a better basis for future preliminary lists of drivers
> for
> > > other parts of the tree. Please take the time to make these submissions
> > > regardless of what your current hardware is. Please submit for any
> machine
> > > you'd like to upgrade to FreeBSD 12 or 13. Identifying information is
> > > generally masked out.
> > >
> > > This is just a request by me. I'll be using the data in about a month
> to
> > > look at old parallel scsi driver use. Though not definitive, it will be
> > > suggestive of what's in use. The data is currently a bit thin, so I
> thought
> > > I'd see what a message like this could do to improve that situation.
> This
> > > should be viewed as a personal suggestion right now...
> > >
> > > Warner
> > >
> > > P.S. I know there's other user generated data sites out there, but this
> > > appears to be the only one that's actually still working.
> > >
> >
> > This one-liner works to submit, though you'll need to change username,
> > email and maybe tweak the description if your system doesn't have decent
> > smbios entries. It's also x86 centric, since other systems won't have
> this
> > information as readily available.
> >
> > curl -v -d "nickname=$USER" -d "email=$USER@$(hostname)" -d
> > "description=FreeBSD/$(uname -m) on $(kenv smbios.system.maker) $(kenv
> > smbios.system.product)" -d "do=addd" --data-urlencode
> > 'dmesg@/var/run/dmesg.boot'
> > http://dmesgd.nycbug.org/index.cgi
>
> FWIW, on my NUC smbios part looks like this:
> nuc% kenv | grep smbios.system\|smbios.planar
>~
> smbios.planar.location="To be filled by O.E.M."
> smbios.planar.maker="Intel Corporation"
> smbios.planar.product="NUC5CPYB"
> smbios.planar.serial="GEPY645001G0"
> smbios.planar.tag=" "
> smbios.planar.version="H61145-407"
> smbios.system.family=" "
> smbios.system.maker=" "
> smbios.system.product=" "
> smbios.system.serial=" "
> smbios.system.sku=" "
> smbios.system.uuid="96091100-727a-11e3-b004-f44d30670aa1"
> smbios.system.version=" "
>

Yes. It seems that some systems have it in planar, and others in system. I
suspect we'll need a simple shell script to do this (The perl one I was
given simply doesn't work even though it says it does).

Warner
___
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"

Re: dmesg submission service -- please submit today

2018-10-07 Thread Warner Losh 
On Sun, Oct 7, 2018 at 2:16 AM Dhananjay Balan  wrote:

> On Sat, Oct 06, 2018 at 11:40:36PM -0600, Warner Losh wrote:
> > On Sat, Oct 6, 2018 at 12:48 PM Warner Losh  wrote:
> >
> > > Greetings,
> > >
> > > As you can tell, the project is looking to clear some of the deadwood
> from
> > > its driver lists. One problem is that we have to guess what's in used
> based
> > > on our personal experience. This has proven to be less reliable than
> hoped
> > > in the 10/100 discussions that are going on now.
> > >
> > > So, to that end, I'd like to request as many people as possible submit
> > > their current dmesg to the service at
> http://dmesgd.nycbug.org/index.cgi
> > > so that we have a better basis for future preliminary lists of drivers
> for
> > > other parts of the tree. Please take the time to make these submissions
> > > regardless of what your current hardware is. Please submit for any
> machine
> > > you'd like to upgrade to FreeBSD 12 or 13. Identifying information is
> > > generally masked out.
> > >
> > > This is just a request by me. I'll be using the data in about a month
> to
> > > look at old parallel scsi driver use. Though not definitive, it will be
> > > suggestive of what's in use. The data is currently a bit thin, so I
> thought
> > > I'd see what a message like this could do to improve that situation.
> This
> > > should be viewed as a personal suggestion right now...
> > >
> > > Warner
> > >
> > > P.S. I know there's other user generated data sites out there, but this
> > > appears to be the only one that's actually still working.
> > >
> >
> > This one-liner works to submit, though you'll need to change username,
> > email and maybe tweak the description if your system doesn't have decent
> > smbios entries. It's also x86 centric, since other systems won't have
> this
> > information as readily available.
> >
> > curl -v -d "nickname=$USER" -d "email=$USER@$(hostname)" -d
> > "description=FreeBSD/$(uname -m) on $(kenv smbios.system.maker) $(kenv
> > smbios.system.product)" -d "do=addd" --data-urlencode
> > 'dmesg@/var/run/dmesg.boot'
> > http://dmesgd.nycbug.org/index.cgi
>
> When I try to submit (with the oneliner or web form), it fails with
>  "Sorry, this is an unsupported OS. If you feel it should be added, please
> contact admin."
>
> dmesg is from FreeBSD 12.0-ALPHA8 r339174=b24b22909(master).
>

Oh right. There's a known bug I should have mentioned: If your uname
doesn't have a '#' in it, the script will reject it. You can add #0+ after
the ALPHA8 and before the r339174 and it will work. I've reported this to
the dmesg guys.

Warner
___
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"

Re: Dependencies – drm-kmod, drm-stable-kmod and drm-next-kmod

2018-10-07 Thread Niclas Zeising 

On 10/7/18 7:17 AM, Graham Perrin wrote:

According to :

- for drm-kmod, drm-stable-kmod is the sole runtime dependency.

Below, I see -next- (not -stable-):

$ pkg rquery %dn graphics/drm-kmod
drm-next-kmod
drm-next-kmod
$

– is that contrary to what's at FreshPorts? (Do I misunderstand something?)



More:

$ pkg rquery %rn graphics/drm-kmod
$

$ pkg rquery %dn graphics/drm-stable-kmod
gpu-firmware-kmod
gpu-firmware-kmod
$ pkg rquery %rn graphics/drm-stable-kmod
$

$ pkg rquery %dn graphics/drm-next-kmod
gpu-firmware-kmod
gpu-firmware-kmod
$ pkg rquery %rn graphics/drm-next-kmod
drm-kmod
drm-kmod
$

– is there _truly_ intended to be some dependency between drm-next-kmod and 
drm-kmod?



Hi!
The version of drm-*-kmod that's pulled in is dependent on your FreeBSD 
version.  The dependenvy shown on FreshPorts is probably based on the 
version of FreeBSD FreshPorts is using to parse the ports tree.


gpu-firmware-kmod is a dependency of all drm-*-kmod ports, but it's not 
a direct dependency of drm-kmod.


Regards
--
Niclas Zeising
___
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"

[regression] drm-stable-kmod doesn't work in i386 jail on amd64 host

2018-10-07 Thread Jan Beich 
I often test Firefox on 10.4 i386 and sometimes play games via Wine.
Both require working OpenGL for COMPAT_FREEBSD32. My GPU is Skylake
which worked fine a few weegs ago i.e., before r338990.

Any clue?

$ uname -a
... FreeBSD 12.0-ALPHA8 #0 r339218M: Sun Oct  7 11:26:25 UTC 2018 
foo@bar:/tmp/usr/src/amd64.amd64/sys/MYKERNEL amd64

$ sysctl kern.conftxt | fgrep COMPAT_
options COMPAT_FREEBSD11
options COMPAT_FREEBSD10
options COMPAT_FREEBSD32

$ pkg info -x drm.\*kmod
drm-stable-kmod-g20180822

$ pkg install mesa-dri mesa-demos
$ LIBGL_DEBUG=verbose glxgears
MESA-LOADER: failed to retrieve device information
libGL: OpenDriver: trying /usr/local/lib/dri/i915_dri.so
libGL: Can't open configuration file /home/foo/.drirc: No such file or 
directory.
libGL: Using DRI2 for screen 0
libGL: Can't open configuration file /home/foo/.drirc: No such file or 
directory.
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
Segmentation fault
___
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"

Re: dmesg submission service -- please submit today

2018-10-07 Thread Konstantin Belousov 
On Sat, Oct 06, 2018 at 11:40:36PM -0600, Warner Losh wrote:
> On Sat, Oct 6, 2018 at 12:48 PM Warner Losh  wrote:
> 
> > Greetings,
> >
> > As you can tell, the project is looking to clear some of the deadwood from
> > its driver lists. One problem is that we have to guess what's in used based
> > on our personal experience. This has proven to be less reliable than hoped
> > in the 10/100 discussions that are going on now.
> >
> > So, to that end, I'd like to request as many people as possible submit
> > their current dmesg to the service at http://dmesgd.nycbug.org/index.cgi
> > so that we have a better basis for future preliminary lists of drivers for
> > other parts of the tree. Please take the time to make these submissions
> > regardless of what your current hardware is. Please submit for any machine
> > you'd like to upgrade to FreeBSD 12 or 13. Identifying information is
> > generally masked out.
> >
> > This is just a request by me. I'll be using the data in about a month to
> > look at old parallel scsi driver use. Though not definitive, it will be
> > suggestive of what's in use. The data is currently a bit thin, so I thought
> > I'd see what a message like this could do to improve that situation. This
> > should be viewed as a personal suggestion right now...
> >
> > Warner
> >
> > P.S. I know there's other user generated data sites out there, but this
> > appears to be the only one that's actually still working.
> >
> 
> This one-liner works to submit, though you'll need to change username,
> email and maybe tweak the description if your system doesn't have decent
> smbios entries. It's also x86 centric, since other systems won't have this
> information as readily available.
> 
> curl -v -d "nickname=$USER" -d "email=$USER@$(hostname)" -d
> "description=FreeBSD/$(uname -m) on $(kenv smbios.system.maker) $(kenv
> smbios.system.product)" -d "do=addd" --data-urlencode
> 'dmesg@/var/run/dmesg.boot'
> http://dmesgd.nycbug.org/index.cgi

FWIW, on my NUC smbios part looks like this:
nuc% kenv | grep smbios.system\|smbios.planar ~
smbios.planar.location="To be filled by O.E.M."
smbios.planar.maker="Intel Corporation"
smbios.planar.product="NUC5CPYB"
smbios.planar.serial="GEPY645001G0"
smbios.planar.tag=" "
smbios.planar.version="H61145-407"
smbios.system.family=" "
smbios.system.maker=" "
smbios.system.product=" "
smbios.system.serial=" "
smbios.system.sku=" "
smbios.system.uuid="96091100-727a-11e3-b004-f44d30670aa1"
smbios.system.version=" "
___
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"

Re: dmesg submission service -- please submit today

2018-10-07 Thread Gary Jennejohn 
On Sat, 6 Oct 2018 12:48:25 -0600
Warner Losh  wrote:

> Greetings,
> 
> As you can tell, the project is looking to clear some of the deadwood from
> its driver lists. One problem is that we have to guess what's in used based
> on our personal experience. This has proven to be less reliable than hoped
> in the 10/100 discussions that are going on now.
> 
> So, to that end, I'd like to request as many people as possible submit
> their current dmesg to the service at http://dmesgd.nycbug.org/index.cgi so
> that we have a better basis for future preliminary lists of drivers for
> other parts of the tree. Please take the time to make these submissions
> regardless of what your current hardware is. Please submit for any machine
> you'd like to upgrade to FreeBSD 12 or 13. Identifying information is
> generally masked out.
> 

Verbose or normal?  Or doesn't it matter?

[snip]

-- 
Gary Jennejohn
___
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"

Re: dmesg submission service -- please submit today

2018-10-07 Thread Gary Jennejohn 
On Sat, 6 Oct 2018 23:40:36 -0600
Warner Losh  wrote:

[snip original post]

> This one-liner works to submit, though you'll need to change username,
> email and maybe tweak the description if your system doesn't have decent
> smbios entries. It's also x86 centric, since other systems won't have this
> information as readily available.
> 
> curl -v -d "nickname=$USER" -d "email=$USER@$(hostname)" -d
> "description=FreeBSD/$(uname -m) on $(kenv smbios.system.maker) $(kenv
> smbios.system.product)" -d "do=addd" --data-urlencode
> 'dmesg@/var/run/dmesg.boot'
> http://dmesgd.nycbug.org/index.cgi
> 

On my system I would have to use smbios.planar.maker and
smbios.planar.product because the corresponding smbios.system values
are not filled in.  Just a heads up for other users.

This should be easy enough to check, since kenv will dump all its
values, which allows a user to check what is really set.

> Hope helps facilitate submission of entries.  Thanks to Charles Sprickman
> for the idea of using a curl one-liner.
> 

-- 
Gary Jennejohn
___
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"

Re: dmesg submission service -- please submit today

2018-10-07 Thread Thomas Mueller 
I can submit a dmesg even if I'm in NetBSD at the time: mount the FreeBSD 
partition and get the latest /mount-point/var/run/dmesg.boot .

Question is what about those devices that don't work in FreeBSD but work in 
NetBSD, or which work in neither FreeBSD nor NetBSD?  I'm thinking of re, where 
one Ethernet works in NetBSD but not FreeBSD.  Also, wireless rsu and athn.  
Maybe I can also think of others.

I noticed a lot of SCSI cards listed in GENERIC, but most these have gone out 
of production long ago as USB and SATA have taken over.

Tom

___
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"

Re: dmesg submission service -- please submit today

2018-10-07 Thread Dhananjay Balan 
On Sat, Oct 06, 2018 at 11:40:36PM -0600, Warner Losh wrote:
> On Sat, Oct 6, 2018 at 12:48 PM Warner Losh  wrote:
> 
> > Greetings,
> >
> > As you can tell, the project is looking to clear some of the deadwood from
> > its driver lists. One problem is that we have to guess what's in used based
> > on our personal experience. This has proven to be less reliable than hoped
> > in the 10/100 discussions that are going on now.
> >
> > So, to that end, I'd like to request as many people as possible submit
> > their current dmesg to the service at http://dmesgd.nycbug.org/index.cgi
> > so that we have a better basis for future preliminary lists of drivers for
> > other parts of the tree. Please take the time to make these submissions
> > regardless of what your current hardware is. Please submit for any machine
> > you'd like to upgrade to FreeBSD 12 or 13. Identifying information is
> > generally masked out.
> >
> > This is just a request by me. I'll be using the data in about a month to
> > look at old parallel scsi driver use. Though not definitive, it will be
> > suggestive of what's in use. The data is currently a bit thin, so I thought
> > I'd see what a message like this could do to improve that situation. This
> > should be viewed as a personal suggestion right now...
> >
> > Warner
> >
> > P.S. I know there's other user generated data sites out there, but this
> > appears to be the only one that's actually still working.
> >
> 
> This one-liner works to submit, though you'll need to change username,
> email and maybe tweak the description if your system doesn't have decent
> smbios entries. It's also x86 centric, since other systems won't have this
> information as readily available.
> 
> curl -v -d "nickname=$USER" -d "email=$USER@$(hostname)" -d
> "description=FreeBSD/$(uname -m) on $(kenv smbios.system.maker) $(kenv
> smbios.system.product)" -d "do=addd" --data-urlencode
> 'dmesg@/var/run/dmesg.boot'
> http://dmesgd.nycbug.org/index.cgi

When I try to submit (with the oneliner or web form), it fails with 
 "Sorry, this is an unsupported OS. If you feel it should be added, please 
contact admin."

dmesg is from FreeBSD 12.0-ALPHA8 r339174=b24b22909(master).

> 
> Hope helps facilitate submission of entries.  Thanks to Charles Sprickman
> for the idea of using a curl one-liner.
> 
> Warner
> ___
> 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"
___
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"

Dependencies – drm-kmod, drm-stable-kmod and drm-next-kmod

2018-10-07 Thread Graham Perrin 
According to :

- for drm-kmod, drm-stable-kmod is the sole runtime dependency.

Below, I see -next- (not -stable-):

$ pkg rquery %dn graphics/drm-kmod
drm-next-kmod
drm-next-kmod
$

– is that contrary to what's at FreshPorts? (Do I misunderstand something?)



More:

$ pkg rquery %rn graphics/drm-kmod
$

$ pkg rquery %dn graphics/drm-stable-kmod
gpu-firmware-kmod
gpu-firmware-kmod
$ pkg rquery %rn graphics/drm-stable-kmod
$

$ pkg rquery %dn graphics/drm-next-kmod
gpu-firmware-kmod
gpu-firmware-kmod
$ pkg rquery %rn graphics/drm-next-kmod
drm-kmod
drm-kmod
$

– is there _truly_ intended to be some dependency between drm-next-kmod and 
drm-kmod?
___
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"

Re: dmesg submission service -- please submit today

2018-10-07 Thread Warner Losh 
On Sat, Oct 6, 2018 at 12:48 PM Warner Losh  wrote:

> Greetings,
>
> As you can tell, the project is looking to clear some of the deadwood from
> its driver lists. One problem is that we have to guess what's in used based
> on our personal experience. This has proven to be less reliable than hoped
> in the 10/100 discussions that are going on now.
>
> So, to that end, I'd like to request as many people as possible submit
> their current dmesg to the service at http://dmesgd.nycbug.org/index.cgi
> so that we have a better basis for future preliminary lists of drivers for
> other parts of the tree. Please take the time to make these submissions
> regardless of what your current hardware is. Please submit for any machine
> you'd like to upgrade to FreeBSD 12 or 13. Identifying information is
> generally masked out.
>
> This is just a request by me. I'll be using the data in about a month to
> look at old parallel scsi driver use. Though not definitive, it will be
> suggestive of what's in use. The data is currently a bit thin, so I thought
> I'd see what a message like this could do to improve that situation. This
> should be viewed as a personal suggestion right now...
>
> Warner
>
> P.S. I know there's other user generated data sites out there, but this
> appears to be the only one that's actually still working.
>

This one-liner works to submit, though you'll need to change username,
email and maybe tweak the description if your system doesn't have decent
smbios entries. It's also x86 centric, since other systems won't have this
information as readily available.

curl -v -d "nickname=$USER" -d "email=$USER@$(hostname)" -d
"description=FreeBSD/$(uname -m) on $(kenv smbios.system.maker) $(kenv
smbios.system.product)" -d "do=addd" --data-urlencode
'dmesg@/var/run/dmesg.boot'
http://dmesgd.nycbug.org/index.cgi

Hope helps facilitate submission of entries.  Thanks to Charles Sprickman
for the idea of using a curl one-liner.

Warner
___
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"