[RTEMS Project] #4904: Application build with vendor target toolchain fails with rtems make build support

[RTEMS trac]

#4904: Application build with vendor target toolchain fails with rtems make build
support
--------------------------------+---------------------
 Reporter:  Martin Erik Werner  |       Owner:  (none)
     Type:  defect              |      Status:  new
 Priority:  normal              |   Milestone:
Component:  build               |     Version:  5
 Severity:  normal              |  Resolution:
 Keywords:                      |  Blocked By:
 Blocking:                      |
--------------------------------+---------------------

Comment (by Martin Erik Werner):

 My build system does not touch RTEMS_TARGET, I'm using a Makefile based on
 the Makefile.leaf template:

 {{{
 !#make
 # C source names, if any, go here -- minus the .c
 C_PIECES=foo
 C_FILES=$(C_PIECES:%=%.c)
 C_O_FILES=$(C_PIECES:%=${ARCH}/%.o)

 SRCS=$(C_FILES) $(CC_FILES) $(H_FILES) $(S_FILES)
 OBJS=$(C_O_FILES) $(CC_O_FILES) $(S_O_FILES)

 PGMS=${ARCH}/foo.exe

 include $(RTEMS_MAKEFILE_PATH)/Makefile.inc
 include $(RTEMS_CUSTOM)
 include $(RTEMS_ROOT)/make/leaf.cfg

 all:    ${ARCH} $(SRCS) $(PGMS)

 # The following links using C rules.
 ${ARCH}/foo.exe: ${OBJS} ${LINK_FILES}
         $(make-exe)
 }}}

 and pointing RTEMS_MAKEFILE_PATH to a compiled and installed version of an
 RTEMS BSP.

 The sparc-gaisler-rtems5 triplet is given by the toolchain, in my case
 this is taken directly from rcc-1.3.1-gcc from
 https://www.gaisler.com/index.php/products/operating-systems/rtems .

 However I would guess that this problem would apply to any toolchain with
 a vendor in its name (even "unknown").

--
Ticket URL: <http://devel.rtems.org/ticket/4904#comment:2>
RTEMS Project <http://www.rtems.org/>
RTEMS Project