linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: John W <jmwoo2@yahoo.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Building ELDK 3.0/3.1 from SRPMS
Date: Tue, 31 Oct 2006 00:53:15 +0100	[thread overview]
Message-ID: <20061030235315.7BC2B352658@atlas.denx.de> (raw)
In-Reply-To: Your message of "Sun, 29 Oct 2006 19:38:46 PST." <20061030033846.1930.qmail@web50313.mail.yahoo.com>

Dear John,

in message <20061030033846.1930.qmail@web50313.mail.yahoo.com> you wrote:
> Thanks Wolfgang!  Loading RH7.3 and updating
> everything with YUM seemed to do the trick to building
> ELDK 3.0!

Out of curiosity: may I ask why you invest efforts in this old
version?

> On a another note, I am also trying to build ELDK
> 2.1.0 from SRPMS on the same RH7.3 machine, and I am
> comming across two problems:
> 1.  The SRPM for mount-2.11g-5a.src.rpm from the
> Yellowdog 2.3 release seems to have "bad magic" in
> that when trying to install the SRPM, there is some
> sort of validation problem.  In remeding this, I am
> using mount-2.11g-5a.src.rpm from the Yellowdog 2.2
> release.    It probably isn't safe to to so, but I was
> wondering how you over came this issue.

Exactly the same way you did :-)

> 2.  I'm pretty sure that not all of my applications
> are building in the ELDK2.1.0 release,  for example
...
> /bin/sh: gperf: command not found
> make[1]: *** [keywords.c] Error 127
> make[1]: Leaving directory
> `/opt/eldkv2.1.0/build/ppc-2006-10-27/work/usr/src/de
> nx/BUILD/modutils-2.4.13/genksyms'
> make: *** [all] Error 2
> error: Bad exit status from
> /opt/eldkv2.1.0/build/ppc-2006-10-27/work/var/tmp/rp
> m-tmp.26616 (%build)
> 
> Does mean that I need to go get gperf?

Sorry, I don't have these old logs online any more. Please drop me  a
note if you really want to see these, so I can restore the files from
tape.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
How many Unix hacks does it take to change a light bulb?  Let's  see,
   can you use a shell script for that or does it need a C program?

  reply	other threads:[~2006-10-30 23:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-27 18:21 Building ELDK 3.0/3.1 from SRPMS John W
2006-10-27 21:19 ` Wolfgang Denk
2006-10-30  3:38   ` John W
2006-10-30 23:53     ` Wolfgang Denk [this message]
2006-10-31 18:05       ` John W

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=20061030235315.7BC2B352658@atlas.denx.de \
    --to=wd@denx.de \
    --cc=jmwoo2@yahoo.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).