Re: How to access SIGWINCH?

In article <20180513201344.ga34...@ptrace.hagen.corp> you write: >I'm wondering how to get access to to the SIGWINCH signal. It is defined in >/usr/include/sys/signal.h and behind the -D__BSD_VISIBLE switch. > >I can compile my code with this switch, but is this the proper way to do it? >I would

Re: cd /sys/amd64/compile/GENERIC;make cleandepend; make cleandepend

Hi, Reference: > From: Ryan Stone > Date: Sun, 13 May 2018 17:00:50 -0400 Thanks for reply :-) Ryan Stone wrote: > Are you building with WITH_LD_IS_LLD=no? Not that I've set anywhere. Unless it comes from make world ? > -CURRENT can no longer be > built

Re: cd /sys/amd64/compile/GENERIC;make cleandepend; make cleandepend

Are you building with WITH_LD_IS_LLD=no? -CURRENT can no longer be built with a GPLv2 ld. You either have to use ldd or install a newer (GPLv3) binutils package. ___ freebsd-current@freebsd.org mailing list

Re: How to access SIGWINCH?

Stefan Hagen wrote: I can compile my code with this switch, but is this the proper way to do it? I would expect something like this behind -D_BSD_SOURCE or -D_XOPEN_SOURCE=700. Answering myself. I had -D_XOPEN_SOURCE=700 defined which essentially blocks access to SIGWINCH. Not defining

How to access SIGWINCH?

Hello, I'm wondering how to get access to to the SIGWINCH signal. It is defined in /usr/include/sys/signal.h and behind the -D__BSD_VISIBLE switch. I can compile my code with this switch, but is this the proper way to do it? I would expect something like this behind -D_BSD_SOURCE or

Re: suspend/resume regression

On 05/13/2018 10:27, Pete Wright wrote: On 05/13/2018 08:58, Theron wrote: Hi! I'm also seeing issues, not as severe as Pete, but after I resume (which works, with drm-next and DMC firmware), the system becomes sluggish.  It feels like I/O takes more time, and graphics are sluggish (very

cd /sys/amd64/compile/GENERIC;make cleandepend; make cleandepend

Hi current@ Any ideas please on a problem with a current kernel from a day or 2 ago, & after a make world: uname -a FreeBSD lapr.js.berklix.net 12.0-CURRENT FreeBSD 12.0-CURRENT #0: Sat May 12 13:37:23 CEST 2018 j...@lapr.js.berklix.net:/data/release/s4/usr/obj/usr/src/amd64.amd64/sys/GENERIC

Re: suspend/resume regression

> On 13. May 2018, at 11:54, Niclas Zeising wrote: > >> On 05/13/18 09:48, Andriy Gapon wrote: >>> On 13/05/2018 05:25, Pete Wright wrote: >>> hi there - i have an amd64 laptop that's been running CURRENT for a while >>> using >>> both drm-next and drm-stable for

Re: suspend/resume regression

On 05/13/2018 08:58, Theron wrote: Hi! I'm also seeing issues, not as severe as Pete, but after I resume (which works, with drm-next and DMC firmware), the system becomes sluggish.  It feels like I/O takes more time, and graphics are sluggish (very sientific, I know, but for instance git

Re: suspend/resume regression

Hi! I'm also seeing issues, not as severe as Pete, but after I resume (which works, with drm-next and DMC firmware), the system becomes sluggish.  It feels like I/O takes more time, and graphics are sluggish (very sientific, I know, but for instance git operations are much slower after a

Re: suspend/resume regression

On 05/13/18 09:48, Andriy Gapon wrote: On 13/05/2018 05:25, Pete Wright wrote: hi there - i have an amd64 laptop that's been running CURRENT for a while using both drm-next and drm-stable for graphics. during the past week or so i've run into issues with suspend resume...well technically resume

Re: suspend/resume regression

On 13/05/2018 05:25, Pete Wright wrote: > hi there - i have an amd64 laptop that's been running CURRENT for a while > using > both drm-next and drm-stable for graphics. during the past week or so i've run > into issues with suspend resume...well technically resume has stopped > working.  > i've