Agreed!
The dev list is the only official way to communicate with all users of
NuttX. I would think ALL important discussions need to occur there.
Github is for developers; dev is for everyone.
On 3/7/2023 11:43 AM, Nathan Hartman wrote:
On Tue, Mar 7, 2023 at 12:27 PM Alan C. Assis wrote:
On Tue, Mar 7, 2023 at 12:27 PM Alan C. Assis wrote:
> Some important things to keep in mind to avoid these kind of frustration:
>
> 1) NuttX development is on GitHub, although this mailing list has dev@ in
> its name, the development is not here. In the past Greg used to accept
> patches over ma
Some important things to keep in mind to avoid these kind of frustration:
1) NuttX development is on GitHub, although this mailing list has dev@ in
its name, the development is not here. In the past Greg used to accept
patches over mailing list. But now NuttX is an Apache project TLP;
2) You cann
Greg,
Thanks. The commit link is there:
https://github.com/apache/nuttx/commit/e6227e19433c4999d500437d0a8a5c05f476ceb1
Here is the pull request
https://github.com/apache/nuttx/pull/8623
This pull request was written and reviewed by xiaomi (again) and only
ONE independent review (thanks for
Hi,
I agree with Nathan. The "V=0" -- seems to be an explicit option for "no
verbose" compilation (in other worlds should suppress all the outputs
except errors I hope).
Best regards,
Petro
вт, 7 бер. 2023 р. о 15:59 Nathan Hartman пише:
> On Tue, Mar 7, 2023 at 8:12 AM Sebastien Lorquet
> wr
On Tue, Mar 7, 2023 at 8:12 AM Sebastien Lorquet
wrote:
> Hi,
>
> Do your realize how counter-intuitive this is?
>
> I would have NEVER imagined that V=0 is not the exact contrary of V=1!
I agree. I think it should be:
* No V argument: Make behaves as originally
* V=0: Make's current behavior
It is likely that the issue with the SIGNAL number was introduced by
commit e6227e19433c4999d500437d0a8a5c05f476ceb1
Author: chenrun1
Date: Wed Feb 1 17:17:43 2023 +0800
include/signal.h:Expanding SIGNAL to be consistent with Linux
There is nothing inherently wrong with the
GitHub, I find, is not
too hard to keep on top of as at least I am committing PRs, now, fairly
regularly.
Perhaps it needs a policy decision on what the two platforms intent is?
Just my two penny's worth :)
From: Sebastien Lorquet
Sent: 07 March 2023 13:12
To: dev@nuttx.apache.org
Sub
ubject: Re: Build system is broken
Hi,
Do your realize how counter-intuitive this is?
I would have NEVER imagined that V=0 is not the exact contrary of V=1!
Can this silent mode be made optional in a config setting please? It is really
a non-feature. it's just a fantasy to please some commit
mars 2023 14:12
To: dev@nuttx.apache.org
Subject: Re: Build system is broken
Hi,
Do your realize how counter-intuitive this is?
I would have NEVER imagined that V=0 is not the exact contrary of V=1!
Can this silent mode be made optional in a config setting please? It is really
a non-feature. it&#
Hi,
Do your realize how counter-intuitive this is?
I would have NEVER imagined that V=0 is not the exact contrary of V=1!
Can this silent mode be made optional in a config setting please? It is
really a non-feature. it's just a fantasy to please some committer, and
should have never been acce
On Tue, Mar 7, 2023 at 7:23 AM Tomek CEDRO wrote:
> On Tue, Mar 7, 2023 at 9:24 AM Sebastien Lorquet wrote:
> > No
> > V=1 is an entirely different thing.
> > I dont want to see the output mangled with tons of arm-none-eabi-gcc
> > command lines.
> > This stuff is another breakage
> > Sebastien
On Tue, Mar 7, 2023 at 9:24 AM Sebastien Lorquet wrote:
> No
> V=1 is an entirely different thing.
> I dont want to see the output mangled with tons of arm-none-eabi-gcc
> command lines.
> This stuff is another breakage
> Sebastien
Well if the build is silent and you do not know what happens then
No
V=1 is an entirely different thing.
I dont want to see the output mangled with tons of arm-none-eabi-gcc
command lines.
This stuff is another breakage
Sebastien
On 3/7/23 09:22, Marco Casaroli wrote:
Try
make V=1
On Tue, 7 Mar 2023 at 09:18, Sebastien Lorquet wrote:
Hi,
This morn
Try
make V=1
On Tue, 7 Mar 2023 at 09:18, Sebastien Lorquet wrote:
> Hi,
>
> This morning I updated my working copy, ran git pull origin master and
> rebuilt my OS
>
> Now when I run make I get no output. But the cpu fan works.
>
> Only the last line of the console shows text, there is no log m
Hi,
This morning I updated my working copy, ran git pull origin master and
rebuilt my OS
Now when I run make I get no output. But the cpu fan works.
Only the last line of the console shows text, there is no log makefile
anymore.
This is AWFUL!
What happened?
Was make updated by linux min
16 matches
Mail list logo
