Hello Nick,
I checked in the part of this patch. For the libmisc
stuff, please send a separate patch if these changes are still
necessary. The dl02 problems should be fixed with an up to date rtems-ld.
On 10/12/15 10:04, Nick Withers wrote:
Hi all,
Attached is a patch for master similar to
Hello Nick,
thanks for the update. I will test this once the next Newlib release is
available.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
P
Hi Sebastian,
Here's an updated patch.
On Tue, 2015-12-15 at 09:13 +0100, Sebastian Huber wrote:
> Hello Nick,
>
> I checked in the shell changes separately. With them I can build the
> latest Newlib with --disable-networking. It should be sufficient to
> remove the from libnetworking.
Now t
Hello Nick,
I checked in the shell changes separately. With them I can build the
latest Newlib with --disable-networking. It should be sufficient to
remove the from libnetworking.
On 14/12/15 10:09, Sebastian Huber wrote:
Hello Nick,
this patch needs an update once this is committed to New
We should try to get everything fixed before the next Newlib release end
of the year. Once it is released, we should force a tool chain upgrade
for git master users.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax
Hello Nick,
this patch needs an update once this is committed to Newlib:
https://sourceware.org/ml/newlib/2015/msg00905.html
On 10/12/15 10:04, Nick Withers wrote:
Hi all,
Attached is a patch for master similar to that I posted to the Newlib
mailing list in https://sourceware.org/ml/newlib/20
On 12/11/15 17:39, Sebastian Huber wrote:
Since we have now the RSB, I prefer to avoid autoconf stuff and instead
force users of the master branch to update their tool chain.
I agree. Easy to add, difficult to remove.
The
difficult part is to set up your development host to be able to build
t
Since we have now the RSB, I prefer to avoid autoconf stuff and instead
force users of the master branch to update their tool chain. The
difficult part is to set up your development host to be able to build
the tools with RSB the first time, but to build the tools a second time
is easy, you jus
I think it is quite common to need tool updates on the master for
either a change in newlib or a change in RTEMS. At least I can think
of about 6 times during 4.11, so I guess at least yearly it happens.
Maybe that isn't common...
On Thu, Dec 10, 2015 at 8:08 AM, Joel Sherrill wrote:
>
> On Dec 1
After each release branch is cut, there is a period where the frozen tools
continue to work. But usually this doesn't last long as backed up newlib or
gcc changes force a tool update.
On top of that, it is the development master and the tools will evolve and
update. Sometimes causing breakage.
On
Nick,
We occasionally "break master" by updating newlib or gcc. This is
fine, but yes it deserves a shout-out.
On Thu, Dec 10, 2015 at 4:40 AM, Nick Withers wrote:
> Hullo again,
>
> On Thu, 2015-12-10 at 20:04 +1100, Nick Withers wrote:
>> Hi all,
>>
>> Attached is a patch for master similar to
Hullo again,
On Thu, 2015-12-10 at 20:04 +1100, Nick Withers wrote:
> Hi all,
>
> Attached is a patch for master similar to that I posted to the Newlib
> mailing list in https://sourceware.org/ml/newlib/2015/msg00888.html *
> .
>
> It chases Newlib changes to sys/types.h / sys/select.h and allow
Hi all,
Attached is a patch for master similar to that I posted to the Newlib
mailing list in https://sourceware.org/ml/newlib/2015/msg00888.html *.
It chases Newlib changes to sys/types.h / sys/select.h and allows us to
use Newlib's sys/select.h directly rather than rolling our own.
A few notes
13 matches
Mail list logo
