Build log deceptively incomplete.
ANDY KENNEDY
ANDY.KENNEDY@adtran.com
Mon Mar 7 21:57:00 GMT 2011
> On 03/07/11 20:57, ANDY KENNEDY wrote:
> > Looking through the scripts and the build.log together, I find that,
> > whereas the build log _LOOKS_ like the complete commands are there,
in
> > fact these aren't. For example, the following snippet from
> > scripts/build/cc/gcc.sh:
> >
> > CC_FOR_BUILD="${CT_BUILD}-gcc" \
> > CFLAGS="${CT_CFLAGS_FOR_HOST}" \
> > LDFLAGS="${final_LDFLAGS[*]}" \
> > CFLAGS_FOR_TARGET="${CT_TARGET_CFLAGS}" \
> > CXXFLAGS_FOR_TARGET="${CT_TARGET_CFLAGS}" \
> > LDFLAGS_FOR_TARGET="${CT_TARGET_LDFLAGS}" \
> > CT_DoExecLog CFG \
> > "${CT_SRC_DIR}/gcc-${CT_CC_VERSION}/configure" \
> > --build=${CT_BUILD} \
> > --host=${CT_HOST} \
> > --target=${CT_TARGET} \
> > --prefix="${CT_PREFIX_DIR}" \
> > ${CC_SYSROOT_ARG} \
> > "${extra_config[@]}" \
> > --with-local-prefix="${CT_SYSROOT_DIR}" \
> > --disable-nls \
> > --enable-symvers=gnu \
> > --enable-c99 \
> > --enable-long-long \
> > ${CT_CC_EXTRA_CONFIG}
> >
> > Now, when viewing this in the log, it omits the ENV definitions.
> >
> > My question is was this intentional? Why not make the build command
> > along the lines:
> >
> > CT_DoExecLog CFG \
> > CC_FOR_BUILD="${CT_BUILD}-gcc" \
> > CFLAGS="${CT_CFLAGS_FOR_HOST}" \
> > LDFLAGS="${final_LDFLAGS[*]}" \
> > CFLAGS_FOR_TARGET="${CT_TARGET_CFLAGS}" \
> > CXXFLAGS_FOR_TARGET="${CT_TARGET_CFLAGS}" \
> > LDFLAGS_FOR_TARGET="${CT_TARGET_LDFLAGS}" \
> > "${CT_SRC_DIR}/gcc-${CT_CC_VERSION}/configure" \
> > --build=${CT_BUILD} \
> > --host=${CT_HOST} \
> > --target=${CT_TARGET} \
> > --prefix="${CT_PREFIX_DIR}" \
> > ${CC_SYSROOT_ARG} \
> > "${extra_config[@]}" \
> > --with-local-prefix="${CT_SYSROOT_DIR}" \
> > --disable-nls \
> > --enable-symvers=gnu \
> > --enable-c99 \
> > --enable-long-long \
> > ${CT_CC_EXTRA_CONFIG}
> >
> > So that the ENV params that are set during the build get included
> > into the log?
> >
> > If there was a good reason to not do this, then I'm okay with the
> > above syntax.
> >
> > Andy
> >
Bummer, cannot do that (without a fairly substantial rewrite to
CT_DoExecLog). The problem is that the sh call attempts to run
the CC_FOR_BUILD as a command.
So, not as it stands, not everything is logged when doing a build.
Andy
--
For unsubscribe information see http://sourceware.org/lists.html#faq
More information about the crossgcc
mailing list