#3388: rtems-tester: possible parsing error for qemuprep-altivec on exclude SMP
configuration
----------------------------+--------------------------
Reporter: Joel Sherrill | Owner: chrisj@…
Type: defect | Status: assigned
Priority: normal | Milestone: 5.1
Component: tool | Version: 5
Severity: normal | Keywords: rtems-tester
Blocked By: | Blocking:
----------------------------+--------------------------
These failures have persisted across all the autoconf changes:
Failures:
powerpc/qemuprep-altivec:
configure --target=powerpc-rtems5 --enable-rtemsbsp=qemuprep-
altivec\
--prefix=/home/joel/rtems-work/bsps --enable-networking --enable-smp
ld/collect2:0 error: no error message found!
powerpc/qemuprep-altivec:
configure --target=powerpc-rtems5 --enable-rtemsbsp=qemuprep-
altivec\
--prefix=/home/joel/rtems-work/bsps --enable-debug --enable-smp
ld/collect2:0 error: no error message found!
powerpc/qemuprep-altivec:
configure --target=powerpc-rtems5 --enable-rtemsbsp=qemuprep-
altivec\
--prefix=/home/joel/rtems-work/bsps --enable-debug --enable-\
networking --enable-smp
ld/collect2:0 error: no error message found!
powerpc/qemuprep-altivec:
configure --target=powerpc-rtems5 --enable-rtemsbsp=qemuprep-
altivec\
--prefix=/home/joel/rtems-work/bsps --enable-smp
ld/collect2:0 error: no error message found!
I checked and it looks like qemuprep-altivec is listed in the smp excludes
section.
It is the only BSP with a - in the name that is in smp-excludes. Could it
be that the
matching fails in this case?
The other is pc586-sse which is SMP excluded also but using a different
mechanism..
--
Ticket URL: <http://devel.rtems.org/ticket/3388>
RTEMS Project <http://www.rtems.org/>
RTEMS Project
_______________________________________________
bugs mailing list
[email protected]
http://lists.rtems.org/mailman/listinfo/bugs
