Could you please answer the other parts of the email you cut because it would
help understand this stuff?
Specifically the opt* and user options. When is an option optional and when is
an option an option but not optional?
On 21/10/21 7:09 pm, Sebastian Huber wrote:
> On 21/10/2021 10:06, Chris
On 21/10/2021 10:06, Chris Johns wrote:
KeyError: '/cpukit/optlibddebugger'
You have to admit this is a horrible error message. It provides no insight into
problem or the solution.
Looks like a typo. Maybe use optlibdebugger?
--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178
Hi everyone,
is there any macro defined while compiling rtems-libbsd with the commit hash of
the current commit?
Thx!
Gabriel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
On 21/10/2021 10:36, Chris Johns wrote:
Could you please answer the other parts of the email you cut because it would
help understand this stuff?
Specifically the opt* and user options. When is an option optional and when is
an option an option but not optional?
The option item files are used
On Thu, Oct 21, 2021, 2:22 AM wrote:
> Hi everyone,
>
> is there any macro defined while compiling rtems-libbsd with the commit
> hash of the current commit?
>
Not as far as I know. If you cloned it, there is always git log.
There is an RTEMS version method for RTEMS itself. I don't think
On 22/10/21 1:21 am, Sebastian Huber wrote:
> On 21/10/2021 10:36, Chris Johns wrote:
>> Could you please answer the other parts of the email you cut because it would
>> help understand this stuff?
>>
>> Specifically the opt* and user options. When is an option optional and when
>> is
>> an
From: Chris Johns
Closes #4533
---
spec/build/cpukit/cpuopts.yml | 2 ++
spec/build/cpukit/libdebugger.yml | 2 +-
spec/build/cpukit/optlibdebugger.yml | 16
spec/build/testsuites/libtests/debugger01.yml | 4 +---
4 files changed, 20
