[RTEMS Project] #2071: The object-file suffixes for default-bsp-post-link in leaf.cfg don't work with make-exe...

RTEMS trac trac at rtems.org
Thu Dec 18 11:14:45 UTC 2014


#2071: The object-file suffixes for default-bsp-post-link in leaf.cfg don't work
with make-exe...
----------------------+-----------------------------
 Reporter:  cynt6007  |       Owner:  ralf.corsepius
     Type:  defect    |      Status:  new
 Priority:  normal    |   Milestone:  5.0
Component:  build     |     Version:  4.11
 Severity:  major     |  Resolution:
 Keywords:            |
----------------------+-----------------------------
Changes (by sebastian.huber):

 * milestone:  4.11 => 5.0


Old description:

> Would it be proper to change the suffix of the input in default-bsp-post-
> link in rtems/make/leaf.cfg ?
>
> Namely changing:
>
> define default-bsp-post-link
> -        $(NM) -g -n $@ > $(basename $@).num
> -        $(SIZE) $@
> endef
>
> define default-bsp-post-link
> +        $(NM) -g -n $@.o > $(basename $@).num
> +        $(SIZE) $@.o
> endef
>
> I'm working on the application side of RTEMS (as opposed to the source),
> but here are the errors I encountered, what I did to find the problem,
> and the results.
>
> I kept getting errors when I ran the BuildTests.sh...
>
> ~/rtems-addon-packages/examples/openldap$
> ...
> i386-rtems4.11-nm o-optimize/slapd-addel
> i386-rtems4.11-nm: 'o-optimize/slapd-addel': No such file
> ...
> ~/rtems-addon-packages/examples/openldap$
> ...
> i386-rtems4.11-size o-optimize/slapd-addel
> i386-rtems4.11-size: 'o-optimize/slapd-addel': No such file
>

> After looking at the Makefile it looks like they were called by: “make-
> exe”.
>
> Doing
>         grep -r “make-exe” /opt
> revealed “make-exe” is defined in /opt/rtems-4.11/make/leaf.cfg, which
> calls bsp-post-link, (which is exactly the stage of the build process
> giving errors).
>
> According to man, nm and size work on object files.  So, I changed the
> suffixes in /opt/rtems-4.11/make/leaf.cfg and the errors went away.
> After making the change, the following additional objects appeared in
> o-optimize:
>
> *.bin and *.ralf, with an approximate size of 570,000.  The sizes vary
> slightly...
>
> If changing the suffixes in /opt/rtems-4.11/make/leaf.cfg makes sense,
> would it make sense to change them for rtems/make/leaf.cfg ?  Also, there
> are other target.cfg's in the different bsp s that may have similar
> problems.
>
> Thanks,
> Cynthia Rempel

New description:

 Would it be proper to change the suffix of the input in default-bsp-post-
 link in rtems/make/leaf.cfg ?

 Namely changing:

 define default-bsp-post-link
 -        $(NM) -g -n $@ > $(basename $@).num
 -        $(SIZE) $@
 endef

 define default-bsp-post-link
 +        $(NM) -g -n $@.o > $(basename $@).num
 +        $(SIZE) $@.o
 endef

 I'm working on the application side of RTEMS (as opposed to the source),
 but here are the errors I encountered, what I did to find the problem, and
 the results.

 I kept getting errors when I ran the BuildTests.sh...

 ~/rtems-addon-packages/examples/openldap$
 ...
 i386-rtems4.11-nm o-optimize/slapd-addel
 i386-rtems4.11-nm: 'o-optimize/slapd-addel': No such file
 ...
 ~/rtems-addon-packages/examples/openldap$
 ...
 i386-rtems4.11-size o-optimize/slapd-addel
 i386-rtems4.11-size: 'o-optimize/slapd-addel': No such file


 After looking at the Makefile it looks like they were called by: “make-
 exe”.

 Doing
         grep -r “make-exe” /opt
 revealed “make-exe” is defined in /opt/rtems-4.11/make/leaf.cfg, which
 calls bsp-post-link, (which is exactly the stage of the build process
 giving errors).

 According to man, nm and size work on object files.  So, I changed the
 suffixes in /opt/rtems-4.11/make/leaf.cfg and the errors went away.  After
 making the change, the following additional objects appeared in
 o-optimize:

 *.bin and *.ralf, with an approximate size of 570,000.  The sizes vary
 slightly...

 If changing the suffixes in /opt/rtems-4.11/make/leaf.cfg makes sense,
 would it make sense to change them for rtems/make/leaf.cfg ?  Also, there
 are other target.cfg's in the different bsp s that may have similar
 problems.

 Thanks,
 Cynthia Rempel

--

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


More information about the bugs mailing list