dpv(1) ignores -i & -I flags

[rihad]

By simply overwriting the provided template strings with the default 
ones a bit later.


Here's one possible fix (untested):

--- dpv.c.orig2016-06-16 23:14:00.466195000 +0400
+++ dpv.c2016-06-16 23:15:39.306944000 +0400
@@ -455,12 +455,16 @@

 /* Set status formats and action */
 if (line_mode) {
-config->status_solo = LINE_STATUS_SOLO;
-config->status_many = LINE_STATUS_SOLO;
+if (!config->status_solo)
+config->status_solo = LINE_STATUS_SOLO;
+if (!config->status_many)
+config->status_many = LINE_STATUS_SOLO;
 config->action = operate_on_lines;
 } else {
-config->status_solo = BYTE_STATUS_SOLO;
-config->status_many = BYTE_STATUS_SOLO;
+if (!config->status_solo)
+config->status_solo = BYTE_STATUS_SOLO;
+if (!config->status_many)
+config->status_many = BYTE_STATUS_SOLO;
 config->action = operate_on_bytes;
 }


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

Asia/Baku local time

[rihad]

Hi, Baku (Azerbaijan) canceled the DST shift this year, but yesterday's 
FreeBSD current still has the old data with the local time changing 
accordingly:


$ strings /usr/share/zoneinfo/Asia/Baku
TZif2
BAKT
BAKST
AZST
TZif2
BAKT
BAKST
AZST
AZT-4AZST,M3.5.0/4,M10.5.0/5
$

It should now be AZT with no change in the time displayed.
Can someone more knowledgeable than me fix it and push the change 
upstream? Thanks :)

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

MALLOC_OPTIONS behaviour

[rihad]

Under 5.2-BETA, if I run a program with env MALLOC_OPTIONS=j then all 
the malloc()'ed memory will be zeroed even though I did not ask for it 
(by specifying Z). Also, J (memset to 0xd0) even appears to run a 
somewhat *faster* than j. Why doesn't jz return uninitialized memory 
and isn't the fastest of {jz,J,Z} (where J is the fastest)? I'm new to 
FreeBSD so I don't know if previously this worked as documented in 
malloc(3).

TIA

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

5.1-CURRENT: buildworld fails

[rihad]

For a few past days, after doing make update, buildworld always fails 
when building pam. Couldn't find it on this list! TIA

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: 5.1-CURRENT: buildworld fails

[rihad]

Sebastian Böck wrote:

rihad wrote:

For a few past days, after doing make update, buildworld always fails 
when building pam. Couldn't find it on this list! TIA


Have you set -02 or similar in your /etc/make.conf?
My buildworld also fails if i set any optimizations.
Just a guess


/usr/src/lib/libpam/modules/pam_echo/pam_echo.c is compiled with -Werror 
(treat warnings as errors). And I get:

/usr/src/lib/libpam/modules/pam_echo/pam_echo.c: In function `_pam_echo':
/usr/src/lib/libpam/modules/pam_echo/pam_echo.c:92: warning: 
dereferencing type-punned pointer will break strict-aliasing rules
*** Error code 1

So the build fails.
gcc version 3.3.3 [FreeBSD] 20031106
make.conf does have
CPUTYPE?=p4
CFLAGS= -O2 -pipe
I'll try to build it without -O2, thanks.

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]