Your Action Required: Email Account Settings

[Luno]

L U N O


Welcome to Luno

Please confirm your email address by clicking the button below.

This is to be sure your profile is active and secure

Confirm Email Address


NOTE: Failure to confirm your email will lead to profile suspension.

Regards,
Team Luno





 This message contains information 
for use only by the intended recipient and may be legally privileged, 
confidential, and/or exempt from disclosure. If you received this message in 
error, notify the sender immediately and permanently delete this message. Any 
unauthorized review, use, disclosure or distribution is strictly prohibited. 
Unless explicitly stated otherwise, this e-mail is not a contract offer, 
amendment, nor acceptance.
___
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"

lint errors in stable/11

[Rick Miller]

Hi all,



Performing a release build via release/release.sh in r331337 of stable/11
errors citing the lack of lint. It’s understood lint was removed from
stable/11 so src.conf includes WITHOUT_LINT, but errors persist. As the
code review alludes to[1], lint is irrelevant here. It seems WITHOUT_LINT
may not be the only thing I’m looking for. What is the best approach for
mitigating these errors?



===> usr.bin/xlint/xlint
(all)

/data/dists/11.1.9.0-amd64-md/usr/src/contrib/apr/atomic/unix/builtins.c:71:53:

warning: passing 'const void *' to parameter of type 'volatile void *'
discards

qualifiers
[-Wincompatible-pointer-types-discards-qualifiers]

return (void*) __sync_val_compare_and_swap(mem, cmp,
with);

^~~

1 warning
generated.

===> usr.bin/xlint/llib
(all)

sh: lint: not
found

--- llib-lposix.ln
---

*** [llib-lposix.ln] Error code
127



make[5]: stopped in
/data/dists/11.1.9.0-amd64-md/usr/src/usr.bin/xlint/llib

1
error



make[5]: stopped in
/data/dists/11.1.9.0-amd64-md/usr/src/usr.bin/xlint/llib



[1] https://reviews.freebsd.org/D13799?id=37644
-- 
Take care
Rick Miller
___
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: lint errors in stable/11

[Rick Miller]

On Thu, May 10, 2018 at 6:35 AM Rick Miller  wrote:

> Hi all,
>
>
>
> Performing a release build via release/release.sh in r331337 of stable/11
> errors citing the lack of lint. It’s understood lint was removed from
> stable/11 so src.conf includes WITHOUT_LINT, but errors persist. As the
> code review alludes to[1], lint is irrelevant here. It seems WITHOUT_LINT
> may not be the only thing I’m looking for. What is the best approach for
> mitigating these errors?
>
>
Here’s the error w/o email munging:

===> usr.bin/xlint/xlint (all)
/data/dists/11.1.9.0-amd64-md/usr/src/contrib/apr/atomic/uni
x/builtins.c:71:53:
warning: passing 'const void *' to parameter of type 'volatile void *'
discards
qualifiers [-Wincompatible-pointer-types-discards-qualifiers]

return (void*) __sync_val_compare_and_swap(mem, cmp, with);

^~~

1 warning generated.

===> usr.bin/xlint/llib (all)

sh: lint: not found

--- llib-lposix.ln ---

*** [llib-lposix.ln] Error code 127


make[5]: stopped in /data/dists/11.1.9.0-amd64-md/usr/src/usr.bin/xlint/llib
1 error


make[5]: stopped in /data/dists/11.1.9.0-amd64-md/usr/src/usr.bin/xlint/llib
  


> [1] https://reviews.freebsd.org/D13799?id=37644
>
-- 
Take care
Rick Miller
___
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: lint errors in stable/11

[Dimitry Andric]

On 10 May 2018, at 12:47, Rick Miller  wrote:
> 
> On Thu, May 10, 2018 at 6:35 AM Rick Miller  wrote:
...
>> Performing a release build via release/release.sh in r331337 of stable/11
>> errors citing the lack of lint. It’s understood lint was removed from
>> stable/11 so src.conf includes WITHOUT_LINT, but errors persist. As the
>> code review alludes to[1], lint is irrelevant here. It seems WITHOUT_LINT
>> may not be the only thing I’m looking for. What is the best approach for
>> mitigating these errors?
>> 
>> 
> Here’s the error w/o email munging:
> 
> ===> usr.bin/xlint/xlint (all)
> /data/dists/11.1.9.0-amd64-md/usr/src/contrib/apr/atomic/uni
> x/builtins.c:71:53:
> warning: passing 'const void *' to parameter of type 'volatile void *'
> discards
> qualifiers [-Wincompatible-pointer-types-discards-qualifiers]
> 
>return (void*) __sync_val_compare_and_swap(mem, cmp, with);
> 
>^~~
> 
> 1 warning generated.
> 
> ===> usr.bin/xlint/llib (all)
> 
> sh: lint: not found

Are you building on a -CURRENT host?  If so, see the previous mail
thread about this:

https://lists.freebsd.org/pipermail/freebsd-stable/2017-November/088092.html

and https://bugs.freebsd.org/223892.

-Dimitry



signature.asc
Description: Message signed with OpenPGP

Re: lint errors in stable/11

[Rick Miller]

On Thu, May 10, 2018 at 8:23 AM Dimitry Andric  wrote:

> On 10 May 2018, at 12:47, Rick Miller  wrote:
> >
> > On Thu, May 10, 2018 at 6:35 AM Rick Miller  wrote:
> ...
> >> Performing a release build via release/release.sh in r331337 of
> stable/11
> >> errors citing the lack of lint. It’s understood lint was removed from
> >> stable/11 so src.conf includes WITHOUT_LINT, but errors persist. As the
> >> code review alludes to[1], lint is irrelevant here. It seems
> WITHOUT_LINT
> >> may not be the only thing I’m looking for. What is the best approach for
> >> mitigating these errors?
> >>
> >>
> > Here’s the error w/o email munging:
> >
> > ===> usr.bin/xlint/xlint (all)
> > /data/dists/11.1.9.0-amd64-md/usr/src/contrib/apr/atomic/uni
> > x/builtins.c:71:53:
> > warning: passing 'const void *' to parameter of type 'volatile void *'
> > discards
> > qualifiers [-Wincompatible-pointer-types-discards-qualifiers]
> >
> >return (void*) __sync_val_compare_and_swap(mem, cmp, with);
> >
> >^~~
> >
> > 1 warning generated.
> >
> > ===> usr.bin/xlint/llib (all)
> >
> > sh: lint: not found
>
> Are you building on a -CURRENT host?  If so, see the previous mail
> thread about this:
>
>
> https://lists.freebsd.org/pipermail/freebsd-stable/2017-November/088092.html
>
> and https://bugs.freebsd.org/223892.
>
> No, the build system is stable/11 r331337 building releng/11.1. The build
system doesn’t include ‘lint’:

# echo $PATH
/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin
# which lint
lint: Command not found.

The mail thread and bug refer to building stable/11 on current where this
case is building releng/11.1 on stable/11. They also do not appear to
provide actionable information on mitigating errors though the code
commit[1] suggests installing a lint will resolve. Ports doesn’t seem to
contain a suitable replacement however. Can lint still be installed on the
build system from the stable/11 source? If so, how is that accomplished?

Do WITH/WITHOUT_LINT have any impact here? The source has been built with
WITH_LINT and WITHOUT_LINT to the same result except that xlint either
builds or doesn’t depending on the option.

This all seems to originate with llib’s dependency on lint as described in
the email thread. It is in building llib where the error occurs.

[1] https://reviews.freebsd.org/D13799

-Rick
-- 
Take care
Rick Miller
___
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: lint errors in stable/11

[Ian Lepore]

On Thu, 2018-05-10 at 14:40 +, Rick Miller wrote:
> On Thu, May 10, 2018 at 8:23 AM Dimitry Andric  wrote:
> 
> > 
> > On 10 May 2018, at 12:47, Rick Miller  wrote:
> > > 
> > > 
> > > On Thu, May 10, 2018 at 6:35 AM Rick Miller  wrote:
> > ...
> > > 
> > > > 
> > > > Performing a release build via release/release.sh in r331337 of
> > stable/11
> > > 
> > > > 
> > > > errors citing the lack of lint. It’s understood lint was removed from
> > > > stable/11 so src.conf includes WITHOUT_LINT, but errors persist. As the
> > > > code review alludes to[1], lint is irrelevant here. It seems
> > WITHOUT_LINT
> > > 
> > > > 
> > > > may not be the only thing I’m looking for. What is the best approach for
> > > > mitigating these errors?
> > > > 
> > > > 
> > > Here’s the error w/o email munging:
> > > 
> > > ===> usr.bin/xlint/xlint (all)
> > > /data/dists/11.1.9.0-amd64-md/usr/src/contrib/apr/atomic/uni
> > > x/builtins.c:71:53:
> > > warning: passing 'const void *' to parameter of type 'volatile void *'
> > > discards
> > > qualifiers [-Wincompatible-pointer-types-discards-qualifiers]
> > > 
> > >    return (void*) __sync_val_compare_and_swap(mem, cmp, with);
> > > 
> > >    ^~~
> > > 
> > > 1 warning generated.
> > > 
> > > ===> usr.bin/xlint/llib (all)
> > > 
> > > sh: lint: not found
> > Are you building on a -CURRENT host?  If so, see the previous mail
> > thread about this:
> > 
> > 
> > https://lists.freebsd.org/pipermail/freebsd-stable/2017-November/088092.html
> > 
> > and https://bugs.freebsd.org/223892.
> > 
> > No, the build system is stable/11 r331337 building releng/11.1. The build
> system doesn’t include ‘lint’:
> 
> # echo $PATH
> /sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin
> # which lint
> lint: Command not found.
> 
> The mail thread and bug refer to building stable/11 on current where this
> case is building releng/11.1 on stable/11. They also do not appear to
> provide actionable information on mitigating errors though the code
> commit[1] suggests installing a lint will resolve. Ports doesn’t seem to
> contain a suitable replacement however. Can lint still be installed on the
> build system from the stable/11 source? If so, how is that accomplished?
> 
> Do WITH/WITHOUT_LINT have any impact here? The source has been built with
> WITH_LINT and WITHOUT_LINT to the same result except that xlint either
> builds or doesn’t depending on the option.
> 
> This all seems to originate with llib’s dependency on lint as described in
> the email thread. It is in building llib where the error occurs.
> 
> [1] https://reviews.freebsd.org/D13799
> 
> -Rick

Releng/11.1 is cast in stone; as I understand it, only security fixes
can get merged into release branches, so the fix I did that added
WITH/WITHOUT_LINT isn't on that branch and never will be. That means
lint has to exist on the build system. If your build system is 11-
stable, then add WITH_LINT=yes to your /etc/src.conf, build and install
world, then that 11-stable system should be able to build the releng
branch. Unfortunately, no such option exists for people trying to build
on 12, because lint was removed completely (although it might be
possible to install a lint port, I'm not sure about that).

-- 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: lint errors in stable/11

[Oliver Pinter]

pro tip: as workaround, create a symlink to lint from /bin/true ;)

On 5/10/18, Rick Miller  wrote:
> On Thu, May 10, 2018 at 8:23 AM Dimitry Andric  wrote:
>
>> On 10 May 2018, at 12:47, Rick Miller  wrote:
>> >
>> > On Thu, May 10, 2018 at 6:35 AM Rick Miller  wrote:
>> ...
>> >> Performing a release build via release/release.sh in r331337 of
>> stable/11
>> >> errors citing the lack of lint. It’s understood lint was removed from
>> >> stable/11 so src.conf includes WITHOUT_LINT, but errors persist. As the
>> >> code review alludes to[1], lint is irrelevant here. It seems
>> WITHOUT_LINT
>> >> may not be the only thing I’m looking for. What is the best approach
>> >> for
>> >> mitigating these errors?
>> >>
>> >>
>> > Here’s the error w/o email munging:
>> >
>> > ===> usr.bin/xlint/xlint (all)
>> > /data/dists/11.1.9.0-amd64-md/usr/src/contrib/apr/atomic/uni
>> > x/builtins.c:71:53:
>> > warning: passing 'const void *' to parameter of type 'volatile void *'
>> > discards
>> > qualifiers [-Wincompatible-pointer-types-discards-qualifiers]
>> >
>> >return (void*) __sync_val_compare_and_swap(mem, cmp, with);
>> >
>> >^~~
>> >
>> > 1 warning generated.
>> >
>> > ===> usr.bin/xlint/llib (all)
>> >
>> > sh: lint: not found
>>
>> Are you building on a -CURRENT host?  If so, see the previous mail
>> thread about this:
>>
>>
>> https://lists.freebsd.org/pipermail/freebsd-stable/2017-November/088092.html
>>
>> and https://bugs.freebsd.org/223892.
>>
>> No, the build system is stable/11 r331337 building releng/11.1. The build
> system doesn’t include ‘lint’:
>
> # echo $PATH
> /sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin
> # which lint
> lint: Command not found.
>
> The mail thread and bug refer to building stable/11 on current where this
> case is building releng/11.1 on stable/11. They also do not appear to
> provide actionable information on mitigating errors though the code
> commit[1] suggests installing a lint will resolve. Ports doesn’t seem to
> contain a suitable replacement however. Can lint still be installed on the
> build system from the stable/11 source? If so, how is that accomplished?
>
> Do WITH/WITHOUT_LINT have any impact here? The source has been built with
> WITH_LINT and WITHOUT_LINT to the same result except that xlint either
> builds or doesn’t depending on the option.
>
> This all seems to originate with llib’s dependency on lint as described in
> the email thread. It is in building llib where the error occurs.
>
> [1] https://reviews.freebsd.org/D13799
>
> -Rick
> --
> Take care
> Rick Miller
> ___
> 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"
>
___
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: Userland PPP on ADSL

[Christoph Moench-Tegeder]

## O'Connor, Daniel (dar...@dons.net.au):

> This worked well for many moons but a while ago I found issues with the
> inbuilt PPP and ended up switching to mpd5 which has so far worked flawlessly.

I did switch from ppp to mpd5 quite a while ago, for performance reasons,
but beyond that, I didn't have any problems (if my notes are corrent,
that was on 10.0 or so).

> May  8 12:27:53 portero ppp[76165]: tun0: LCP: deflink: SendEchoReply(114) 
> state = Opened
> May  8 12:27:54 portero ppp[76165]: tun0: LCP: deflink: SendEchoRequest(38) 
> state = Opened
> May  8 12:27:54 portero ppp[76165]: tun0: LCP: deflink: RecvEchoReply(38) 
> state = Opened

That looks like LCP was still up? Have you tried turning the logging up?

Regards,
Christoph

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

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213

Eugene Grosbein  changed:

   What|Removed |Added

 CC||a...@freebsd.org

--- Comment #35 from Eugene Grosbein  ---
Adding freebsd-acpi@ in hope to gather more people potentialy interested in
this case.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
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"