Just to be clear on this, is it true that re-entrancy is not supported by Zephyr for any of the newlib stdio.h or stdlib.h functions, so not just the likes of strok() but also snprintf() and, more fundamentally, malloc()/free()?

If this is the case, are there any other C libraries (so not newlib) for which Zephyr does support re-entrancy and which fulfil the same functions?

Rob

-- 

Dave Nadler, USA East Coast voice (978) 263-0097, drn@..., Skype 

 Dave.Nadler1

On Mar 11, 2021, at 11:45 AM, Jack Rosenthal <jrosenth@chromium.org> wrote:

The typical way I've seen this done is:

Phase 1: Create the main branch at the same commit hash as master. Repo maintainers make sure that the main branch is synced to master.
Phase 2: Set the default branch to "main". Continue syncing "main" and "master".
Phase 3: Stop syncing "main" and "master". Master goes stale.
Phase 4: Delete the (now stale) master branch.

I'm not sure if GitHub has tools for branch syncing, but it can be done easy enough from the command line by someone with push access.

On Thu, Mar 11, 2021 at 10:38 AM Kumar Gala <kumar.gala@linaro.org> wrote:
Jack,

We are utilizing what GitHub provides and as far as I can tell once we make the change to the default branch from ‘master’ to ‘main’ the ‘master’ branch will no longer exist in the repository.

So downstream users will need to adjust after the change is made.

If you have some means to handle such a synchronization its something that we can discuss.

- k

On Mar 11, 2021, at 10:12 AM, Jack Rosenthal <jrosenth@chromium.org> wrote:

Hi,

Will there be a period of time that we have two main branches ("master" and "main") that are auto-synced to give time for people to adjust their tools?

Thanks,

Jack

On Thu, Mar 11, 2021 at 6:32 AM Kumar Gala <kumar.gala@linaro.org> wrote:
We will be changing the default branch on github from ‘master' to ‘main' on Friday (Mar 11, 2021).

There is no action required for any open PRs, however you’ll need to update your local git clone as follows:

git branch -m master main
git fetch origin
git branch -u origin/main main

Will announce here when this change is made on Friday.

thanks

- k

On Mar 11, 2021, at 12:04 PM, Rob Meades <Rob.Meades@u-blox.com> wrote:

Thanks for the swift response. That's a shame. I will go look at the PR at your link as shifting to the re-entrant versions just for Zephyr is going to be painful.

Rob
-----Original Message-----
From: users@lists.zephyrproject.org <users@lists.zephyrproject.org> On Behalf Of Kumar Gala
Sent: 11 March 2021 17:54
To: Rob Meades <Rob.Meades@u-blox.com>
Cc: users@lists.zephyrproject.org
Subject: Re: [Zephyr-users] C library re-entrancy under Zephyr

*** This is an EXTERNAL email. It was sent from outside of u-blox. ***

Re-entrant support between newlib and zephyr is not currently supported.

There’s an old PR on the subject

https://github.com/zephyrproject-rtos/zephyr/pull/21518

- k

On Mar 11, 2021, at 11:51 AM, Rob Meades via lists.zephyrproject.org <Rob.Meades=u-blox.com@lists.zephyrproject.org> wrote:

Should I expect C library functions (e.g. strtok()) under Zephyr to be re-entrant or must I call the re-entrant versions (i.e. in this case strtok_r())?

I ask because I am building/running nRF52840 (cortex-m4) and strok() _appears_ to NOT be re-entrant: I'd like to understand if this is expected or if I've messed up a configuration somewhere. My prj.conf file is attached in case it is helpful in answering the question.

Rob





<prj.conf>

On Mar 11, 2021, at 11:51 AM, Rob Meades via lists.zephyrproject.org <Rob.Meades=u-blox.com@lists.zephyrproject.org> wrote:

Should I expect C library functions (e.g. strtok()) under Zephyr to be re-entrant or must I call the re-entrant versions (i.e. in this case strtok_r())?

I ask because I am building/running nRF52840 (cortex-m4) and strok() _appears_ to NOT be re-entrant: I'd like to understand if this is expected or if I've messed up a configuration somewhere. My prj.conf file is attached in case it is helpful in answering the question.

Rob





<prj.conf>

On Mar 11, 2021, at 11:51 AM, Rob Meades via lists.zephyrproject.org <Rob.Meades=u-blox.com@lists.zephyrproject.org> wrote:

Should I expect C library functions (e.g. strtok()) under Zephyr to be re-entrant or must I call the re-entrant versions (i.e. in this case strtok_r())?

I ask because I am building/running nRF52840 (cortex-m4) and strok() _appears_ to NOT be re-entrant: I'd like to understand if this is expected or if I've messed up a configuration somewhere. My prj.conf file is attached in case it is helpful in answering the question.

Rob





<prj.conf>

On Mar 11, 2021, at 10:12 AM, Jack Rosenthal <jrosenth@chromium.org> wrote:

Hi,

Will there be a period of time that we have two main branches ("master" and "main") that are auto-synced to give time for people to adjust their tools?

Thanks,

Jack

On Thu, Mar 11, 2021 at 6:32 AM Kumar Gala <kumar.gala@linaro.org> wrote:
We will be changing the default branch on github from ‘master' to ‘main' on Friday (Mar 11, 2021).

There is no action required for any open PRs, however you’ll need to update your local git clone as follows:

git branch -m master main
git fetch origin
git branch -u origin/main main

Will announce here when this change is made on Friday.

thanks

- k

On Mar 11, 2021, at 7:32 AM, Kumar Gala via lists.zephyrproject.org <kumar.gala=linaro.org@lists.zephyrproject.org> wrote:

We will be changing the default branch on github from ‘master' to ‘main' on Friday (Mar 11, 2021).

There is no action required for any open PRs, however you’ll need to update your local git clone as follows:

git branch -m master main
git fetch origin
git branch -u origin/main main

Will announce here when this change is made on Friday.

thanks

- k