This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Build log deceptively incomplete.


Andy, All,

On Monday 07 March 2011 22:57:36 ANDY KENNEDY wrote:
> > 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}
[--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!):

  CT_DoItInASubShellSoVariablesDoNotEscape
  while true; do
    case "$1" in
      *=*)  eval export "$1"
            CT_DoLogThisFsckingVariable ALL "$1"
            shift
            ;;
      *) break;
    esac
  done
  CT_DoExecLogAsUsualThisCmdlineWithoutVariable ALL "$@"
  CT_ThankYouForYourCooperation

> So, not as it stands, not everything is logged when doing a build.

Yes, maybe this should be documented as a limitation...

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

--
For unsubscribe information see http://sourceware.org/lists.html#faq


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]