All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Build failures at bb3bcfa2
Date: Wed, 16 Dec 2009 13:00:34 +0100	[thread overview]
Message-ID: <200912161300.34427.sr@denx.de> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB59301E157B034@dbde02.ent.ti.com>

On Wednesday 16 December 2009 12:49:09 Premi, Sanjeev wrote:
> > >  envcrc crc32.o env_embedded.o envcrc.o sha1.o /usr/bin/ld: crc32.o:
> > >  Relocations in generic ELF (EM: 40)
> > > crc32.o: could not read symbols: File in wrong format
> > > collect2: ld returned 1 exit status
> > > make[1]: *** [envcrc] Error 1
> > > make[1]: Leaving directory `/home/premi/u-boot/tools'
> > > make: *** [tools] Error 2
> >
> > Most likely the same problem I stumbled upon a few days ago.
> > Here my thread:
> >
> > http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/71125/f
> > ocus=72327
> >
> > Do you by any chance have a copy of/link to crc32.c,
> > env_embedded.c, etc.
> > sitting in your tools directory?
> 
> Yes. I do have them. I looked at the thread; and the problem is same.
> 
> One question: Theses links were not manually created. They would have
> been created earlier by some script; and or specific patch.

I have to admit that I don't know how those files/links were created.
 
> If they are not needed; is it possible to remove them by a
> make distclean/mrproper - I had tried both.
> 
> If it makes sense; I can attempt making a quick patch.

git could help here. "git clean" should remove those files/links for you.

Cheers,
Stefan

--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de

  reply	other threads:[~2009-12-16 12:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-16  9:52 [U-Boot] Build failures at bb3bcfa2 Premi, Sanjeev
2009-12-16 10:03 ` Stefan Roese
2009-12-16 11:49   ` Premi, Sanjeev
2009-12-16 12:00     ` Stefan Roese [this message]
2009-12-16 15:17     ` Wolfgang Denk
2009-12-16 15:19       ` Premi, Sanjeev
2009-12-16 21:07         ` Wolfgang Denk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200912161300.34427.sr@denx.de \
    --to=sr@denx.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.