Build log deceptively incomplete.
ANDY KENNEDY
ANDY.KENNEDY@adtran.com
Mon Mar 14 21:55:00 GMT 2011
> > 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}
> [--SNIP--]
> > 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.
>
> Yep, I hit it as well, and I do not really know how to do it. Maybe
> something much more complex, along the lines of (hehe!):
Or, perhaps just call a CT_DoLog just before so that It shows the
complete command. That's what I ended up doing in my test cases
while attempting to run down my stupid mistake. I inserted something
like:
CT_DoLog <the right tag> CC_FOR_BUILD= <snip>
Though, that puts you building commands twice which is a bit of a pain
if you ever have to go back into the code. So, why bother. ;).
BTW: Glad you feel better. I hate the flu.
Andy
--
For unsubscribe information see http://sourceware.org/lists.html#faq
More information about the crossgcc
mailing list