#1217 closed defect (fixed)

targ-include not being set up correctly

Reported by: Ralf Corsepius Owned by: Ralf Corsepius
Priority: normal Milestone: 2
Component: tool/newlib Version: unspecified
Severity: normal Keywords:
Cc: Blocked By:
Blocking:

Description

Occasonally, newlib doesn't set up targ-include correctly.

The symptoms resemble to those described in:
http://sourceware.org/ml/newlib/2006/msg00502.html

The ugly thing about this:

  • This bug doesn't always happen (cause unknown).

ATM (2007-01-31), all gcc-newlib builts succeed on my local FC6 systems, but fail on england's mock.

  • This bug doesn't necessarily have any visible effects
  • Building rtems-newlibs < 20070130 can silently succeed using a bogus set of headers
  • Building rtems-newlib >= 20070130 fails on those occasions the bug hits.
  • This bug only shows in mock or on systems which do not have an earlier version of the toolchain to be built installed (In this case, the installed headers will be used instead of the headers from targ-include).

Change History (1)

comment:1 Changed on Feb 9, 2007 at 1:16:55 PM by Ralf Corsepius

Resolution: fixed
Status: newclosed

Should be fixed with today's and yesterdays releases of the rtems-4.8/rtems-4.7 toolchains.

Note: See TracTickets for help on using tickets.