Something screwed up in PROJECT_ROOT or PROJECT_TOPdir

Joel Sherrill <joel@OARcorp.com> joel.sherrill at OARcorp.com
Tue Feb 22 15:41:58 UTC 2005


Peter .. how do you run the attachment and what do you
expect to be output?

FYI I suspect you need a --enable-rtemsbsp=XXX option
specified.  When someone builds the dmv177 BSP I am
surprised. Do you really want that one? :)

--joel

Peter Dufault wrote:
> 
> On Feb 19, 2005, at 11:31 AM, Ralf Corsepius wrote:
> 
>> On Sat, 2005-02-19 at 10:12 -0500, Peter Dufault wrote:
>>
> 
> 
>> * As you seem to be using rtems-cvs, I strongly recommend you to use
>>  maintainer-mode (configure --enable-maintainer-mode).
> 
> 
> Will do.
> 
>>
>> * The CFLAGS you are using are dubious:
>> -mcpu=750 -D__ALTIVEC__ -Wa,-m7450
>>
>> Seems to me as if you are trying to outsmart an older GCC, which does
>> not support the 7450, to "fake" the m7500.
> 
> 
> OK, which gcc should I use?  Can I look up which versions of the tools 
> are in use for which versions of RTEMS?  That would help a lot.  (This 
> was gcc 3.4.0 from the RTEMS site).
> 
>>
>>> Host info, configuration, etc, in the attachment.
>>
>> I'd recommend you to start anew (remove the build directory),
>> bootstrap the source-tree and configure with --enable-maintainer-mode.
>> Also make sure not to have set any PROJECT_* variable in your
>> environment or in your <BSP>.cfg.
> 
> 
> Will do.
> 
>>
>>> XXX Compilation failure:
>>>
>>> if powerpc-rtems-gcc --pipe -B../../../lib/ -B../../../mvme5500/lib/ -
>>> specs bsp_specs -qrtems -DPACKAGE_NAME=\"rtems-c-src\" -
>>> DPACKAGE_TARNAME=\"rtems-c-src\" -DPACKAGE_VERSION=\"4.6.99.1\" -
>>> DPACKAGE_STRING=\"rtems-c-src\ 4.6.99.1\" -DPACKAGE_BUGREPORT=\"rtems-
>>> bugs at rtems.com\"  -I.
>>> -I../../../../../../tools/rtems-4.7/c/src/optman
>>> -isystem ../../../mvme5500/lib/include
>>>
>>>   -Wall -mcpu=750 -D__ALTIVEC__
>>> -Dmpc750 -mmultiple -mstring -mstrict-align -Wa,-m7450 -O4 -MT
>>> sapi/no_ext_rel-no-ext.o -MD -MP -MF "sapi/.deps/no_ext_rel-no-
>>> ext.Tpo" -c -o sapi/no_ext_rel-no-ext.o `test -f 'sapi/no-ext.c' ||
>>> echo '../../../../../../tools/rtems-4.7/c/src/optman/'`sapi/no-ext.c;
>>> \
>>> then mv -f "sapi/.deps/no_ext_rel-no-ext.Tpo" "sapi/.deps/no_ext_rel-
>>> no-ext.Po"; else rm -f "sapi/.deps/no_ext_rel-no-ext.Tpo"; exit 1; fi
>>> ../../../../../../tools/rtems-4.7/c/src/optman/sapi/no-ext.c:15:26:
>>> rtems/system.h: No such file or directory
>>> ../../../../../../tools/rtems-4.7/c/src/optman/sapi/no-ext.c:16:32:
>>> rtems/rtems/status.h: No such file or directory
>>
>>
>> Symptoms of a failed "make preinstall".
>>
>>> XXX Layout of include files in build directory:
>>> XXX Note the two lib/includes.
>>>
>>> ./mvme5500/lib/include
>>
>> Where does this come from? This is not supposed to be there.
> 
> 
> I know, it has all the files in it that should be one level lower down.
> 
>>
>>> ./powerpc-rtems/c/mvme5500/cpukit/score/include
>>> ./powerpc-rtems/c/mvme5500/lib/libcpu/powerpc/shared/include
>>> ./powerpc-rtems/c/mvme5500/lib/libbsp/powerpc/mvme5500/include
>>> ./powerpc-rtems/mvme5500/lib/include
>>
>> This one is the only one which is of any importance.
> 
> 
> Right, where the files should be.  That's why I thought something with 
> lots of ".." in it was messed up.
> 
>>
>>> /usr/home/dufault/work/rtems_builder/powerpc-rtems/rtems-4.7/powerpc-
>>> rtems/c/mvme5500/lib/libcpu/powerpc/shared
>>>
>>> XXX Configuration
>>>
>>>   $ ../../tools/rtems-4.7/configure --target=powerpc-rtems --
>>> prefix=/opt/rtems-4.7 --enable-posix --enable-networking --enable-cxx
>>> --enable-rtems-debug --disable-itron --enable-rtemsbsp=mvme5500
>>
>> I can't reproduce your issue.
>>
>>> FreeBSD
>>
>> Wasn't it you who had problems with a broken m4?
> 
> 
> Yes, with m4 1.4.2 straight from gnu.org.  All the tools I'm using are 
> from the RTEMS website or GNU, and I've had success building things in 
> December and last summer (but never MVME5500). If you're willing to 
> build gm4 1.4.2 with debugging I've attached a .gdbinit that will tell 
> us if the problem is there (sprintf %-349s into 256 bytes on the stack) 
> on other hosts but just not causing a core dump.
> 
> I'll give up and go to 4.6.2 soon with the Brookhaven patches for 
> MVME5500 but I'll try a little more with 4.7.
> 
> Peter
> 
> Peter Dufault
> HD Associates, Inc.
> 
> 
> ------------------------------------------------------------------------
> 
> cd tools/rtems-4.7/c/src/lib/libbsp/powerpc/dmv177
> set args --nesting-limit=1024 --include=/usr/local/share/autoconf259 --debug=aflq --fatal-warning --error-output=autom4te.cache/traces.2t --trace=AC_CANONICAL_HOST --trace=AC_CANONICAL_SYSTEM --trace=AC_CHECK_FUNCS --trace=AC_CHECK_HEADERS --trace=AC_CHECK_LIB --trace=AC_CHECK_MEMBERS --trace=AC_CHECK_TYPES --trace=AC_CONFIG_AUX_DIR --trace=AC_CONFIG_FILES --trace=AC_CONFIG_HEADERS --trace=AC_CONFIG_LIBOBJ_DIR --trace=AC_CONFIG_LINKS --trace=AC_CONFIG_SUBDIRS --trace=AC_C_CONST --trace=AC_C_INLINE --trace=AC_C_VOLATILE --trace=AC_DECL_SYS_SIGLIST --trace=AC_DEFINE_TRACE_LITERAL --trace=AC_DEFUN --trace=AC_DEFUN_ONCE --trace=AC_FUNC_ALLOCA --trace=AC_FUNC_CHOWN --trace=AC_FUNC_CLOSEDIR_VOID --trace=AC_FUNC_ERROR_AT_LINE --trace=AC_FUNC_FORK --trace=AC_FUNC_FSEEKO --trace=AC_FUNC_GETGROUPS --trace=AC_FUNC_GETLOADAVG --trace=AC_FUNC_GETMNTENT --trace=AC_FUNC_GETPGRP --trace=AC_FUNC_LSTAT --trace=AC_FUNC_LSTAT_FOLLOWS_SLASHED_SYMLINK --trace=AC_FUNC_MALLOC --trace=AC_FUNC_MBRTO
WC --trace=AC_FUNC_MEMCMP --trace=AC_FUNC_MKTIME --trace=AC_FUNC_MMAP --trace=AC_FUNC_OBSTACK --trace=AC_FUNC_REALLOC --trace=AC_FUNC_SELECT_ARGTYPES --trace=AC_FUNC_SETPGRP --trace=AC_FUNC_SETVBUF_REVERSED --trace=AC_FUNC_STAT --trace=AC_FUNC_STRCOLL --trace=AC_FUNC_STRERROR_R --trace=AC_FUNC_STRFTIME --trace=AC_FUNC_STRNLEN --trace=AC_FUNC_STRTOD --trace=AC_FUNC_UTIME_NULL --trace=AC_FUNC_VPRINTF --trace=AC_FUNC_WAIT3 --trace=AC_HEADER_DIRENT --trace=AC_HEADER_MAJOR --trace=AC_HEADER_STAT --trace=AC_HEADER_STDC --trace=AC_HEADER_SYS_WAIT --trace=AC_HEADER_TIME --trace=AC_INIT --trace=AC_LIBSOURCE --trace=AC_PATH_X --trace=AC_PROG_AWK --trace=AC_PROG_CC --trace=AC_PROG_CPP --trace=AC_PROG_CXX --trace=AC_PROG_GCC_TRADITIONAL --trace=AC_PROG_INSTALL --trace=AC_PROG_LEX --trace=AC_PROG_LIBTOOL --trace=AC_PROG_LN_S --trace=AC_PROG_MAKE_SET --trace=AC_PROG_RANLIB --trace=AC_PROG_YACC --trace=AC_REPLACE_FNMATCH --trace=AC_STRUCT_ST_BLOCKS --trace=AC_STRUCT_TIMEZONE --trace=AC_STRU
CT_TM --trace=AC_SUBST --trace=AC_TYPE_MODE_T --trace=AC_TYPE_OFF_T --trace=AC_TYPE_PID_T --trace=AC_TYPE_SIGNAL --trace=AC_TYPE_SIZE_T --trace=AC_TYPE_UID_T --trace=AH_OUTPUT --trace=AM_AUTOMAKE_VERSION --trace=AM_AUX_DIR_EXPAND --trace=AM_CONDITIONAL --trace=AM_DEP_TRACK --trace=AM_GNU_GETTEXT --trace=AM_INIT_AUTOMAKE --trace=AM_MAINTAINER_MODE --trace=AM_MAKE_INCLUDE --trace=AM_MISSING_HAS_RUN --trace=AM_MISSING_PROG --trace=AM_OUTPUT_DEPENDENCY_COMMANDS --trace=AM_PROG_CC_C_O --trace=AM_PROG_INSTALL_SH --trace=AM_PROG_INSTALL_STRIP --trace=AM_PROG_MKDIR_P --trace=AM_RUN_LOG --trace=AM_SANITY_CHECK --trace=AM_SET_CURRENT_AUTOMAKE_VERSION --trace=AM_SET_DEPDIR --trace=AM_SET_LEADING_DOT --trace=AU_DEFUN --trace=RTEMS_ARG_VAR --trace=RTEMS_BSPOPTS_HELP --trace=RTEMS_BSPOPTS_SET --trace=RTEMS_BSP_CONFIGURE --trace=RTEMS_CANONICALIZE_TOOLS --trace=RTEMS_CANONICAL_TARGET_CPU --trace=RTEMS_CHECK_CUSTOM_BSP --trace=RTEMS_CHECK_MULTIPROCESSING --trace=RTEMS_CHECK_NETWORKING --trac
e=RTEMS_CHECK_TOOL --trace=RTEMS_ENABLE_MULTILIB --trace=RTEMS_ENABLE_MULTIPROCESSING --trace=RTEMS_ENABLE_NETWORKING --trace=RTEMS_ENABLE_RTEMSBSP --trace=RTEMS_ENV_RTEMSBSP --trace=RTEMS_GCC_ISYSTEM --trace=RTEMS_GCC_PIPE --trace=RTEMS_GCC_SPECS --trace=RTEMS_PPC_EXCEPTIONS --trace=RTEMS_PROG_CC --trace=RTEMS_PROG_CCAS --trace=RTEMS_PROG_CC_FOR_TARGET --trace=RTEMS_PROJECT_ROOT --trace=RTEMS_TOP --trace=RTEMS_VERSIONING --trace=_AC_AM_CONFIG_HEADER_HOOK --trace=_AM_DEPENDENCIES --trace=_AM_IF_OPTION --trace=_AM_MANGLE_OPTION --trace=_AM_OUTPUT_DEPENDENCY_COMMANDS --trace=_AM_PROG_TAR --trace=_AM_SET_OPTION --trace=_AM_SET_OPTIONS --trace=_RTEMS_CHECK_CUSTOM_BSP --trace=_m4_warn --trace=include --trace=jm_MAINTAINER_MODE --trace=m4_include --trace=m4_pattern_allow --trace=m4_pattern_forbid --trace=m4_sinclude --reload-state=/usr/local/share/autoconf259/autoconf/autoconf.m4f /usr/local/share/aclocal19/amversion.m4 /usr/local/share/aclocal19/auxdir.m4 /usr/local/share/aclocal1
9/cond.m4 /usr/local/share/aclocal19/depend.m4 /usr/local/share/aclocal19/depout.m4 /usr/local/share/aclocal19/init.m4 /usr/local/share/aclocal19/install-sh.m4 /usr/local/share/aclocal19/lead-dot.m4 /usr/local/share/aclocal19/maintainer.m4 /usr/local/share/aclocal19/make.m4 /usr/local/share/aclocal19/missing.m4 /usr/local/share/aclocal19/mkdirp.m4 /usr/local/share/aclocal19/options.m4 /usr/local/share/aclocal19/runlog.m4 /usr/local/share/aclocal19/sanity.m4 /usr/local/share/aclocal19/strip.m4 /usr/local/share/aclocal19/tar.m4 ../../../../aclocal/bsp-configure.m4 ../../../../aclocal/bspopts.m4 ../../../../aclocal/canonical-target-name.m4 ../../../../aclocal/canonicalize-tools.m4 ../../../../aclocal/check-custom-bsp.m4 ../../../../aclocal/check-multiprocessing.m4 ../../../../aclocal/check-networking.m4 ../../../../aclocal/check-tool.m4 ../../../../aclocal/enable-multiprocessing.m4 ../../../../aclocal/enable-networking.m4 ../../../../aclocal/enable-rtemsbsp.m4 ../../../../acloca
l/env-rtemsbsp.m4 ../../../../aclocal/gcc-isystem.m4 ../../../../aclocal/gcc-pipe.m4 ../../../../aclocal/gcc-specs.m4 ../../../../aclocal/multilib.m4 ../../../../aclocal/ppc.m4 ../../../../aclocal/prog-cc.m4 ../../../../aclocal/prog-ccas.m4 ../../../../aclocal/project-root.m4 ../../../../aclocal/rtems-top.m4 ../../../../aclocal/version.m4 configure.ac
> break format
> ignore 1 13
> run
> until 727
> printf "sizeof(str) is %d and the format is \"%s\"\n", sizeof(str), fstart
> 
> 
> ------------------------------------------------------------------------
> 
> 


-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel at OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
    Support Available             (256) 722-9985




More information about the users mailing list