Building ELDK 3.0/3.1 from SRPMS

Building ELDK 3.0/3.1 from SRPMS

[John W]

Hello-

I having trouble rebuilding ELDK 3.0 & ELDK 3.1 from
the source RPMS.  I have spent a great deal of time on
this, and I have a feeling that maybe I’m just not
doing something correctly (setting up the build
environment, retrieving source/specs from CVS..
etc..).  My build machine is Red Hat 9.0 without any
updates (Kernel 2.4.20-8, the Shrike release).

The following is the process I’m using to setup my
development environment for ELDK 3.0

#Make build directory
mkdir /opt/eldkv3.0

#checkout tarballs & build.  One caveat is that I’m
behind a proxy server, and I’m having to check these
files out on remote computer, and tar -czvf the
directories up, and copying the files to the build
computer. I would imagine that this is functionally
equivalent.

cd /opt/eldkv3.0
cvs -d :pserver:anonymous@www.denx.de:/cvsroot login
cvs -z6 -d :pserver:anonymous@www.denx.de:/cvsroot co
-rELDK_3_0 -P eldk_tarballs
cvs -z6 -d :pserver:anonymous@www.denx.de:/cvsroot co
-rELDK_3_0 -P eldk_build

#get yellowdog 3.0 prestine SRPMS
cd /opt/eldkv3.0
mkdir SRPMS
cd /opt/eldkv3.0/SRPMS
wget -r -nd -np -l1 -A ‘*.rpm’
http://ydl.osuosl.org/releases/yellowdog-3.0/en/os/SRPMS/
wget -r -nd -np -l1 -A ‘*.rpm’
http://ydl.osuosl.org/updates/yellowdog-3.0/SRPMS/

#export the prefix & target architecture
export ELDK_PREFIX=/opt/eldkv3.0
export TARGET_CPU_FAMILY_LIST=”4xx”

#execute build process
cd /opt/eldkv3.0/build
./ELDK_BUILD

Executing ELDK_BUILD seems to build almost everything,
but there seems to be a lot of packages missing,
namely libstdc++.so.  When checking the logs, I see
something suspicious while build the make RPM in that
it shows the following failure:
/opt/eldkv3.0/build/ppc-2006-10-27/logs/build_make.log:
….
checking for waitpid... yes
checking for wait3... yes
checking for union wait... no
checking for sys_siglist declaration in signal.h or
unistd.h... yes
checking for library containing getpwnam... none
required
checking for location of SCCS get command... get
checking if system libc has GNU glob... yes
updating cache ./config.cache
creating ./config.status
creating build.sh
creating Makefile
creating glob/Makefile
creating i18n/Makefile
creating config.h
+ make
cd . && aclocal
cd . && automake --gnu --include-deps Makefile
Makefile.am: required file `./depcomp' not found
make: *** [Makefile.in] Error 1
error: Bad exit status from
/opt/eldkv3.0/build/ppc-2006-10-27/work/var/tmp/rpm-tmp.54649
(%build)


RPM build errors:
    Bad exit status from
/opt/eldkv3.0/build/ppc-2006-10-27/work/var/tmp/rpm-tmp.54649
(%build)

I’m not exactly sure that by fixing this problem will
install libstdc++ correctly, infact, I’m not exactly
sure why ELDK is not completely building everything. 
In trying to remedy this problem, I have upgraded my
system to use autoconf 2.60, automake 1.9 and m4
1.4.7, but none of those seems to help.  The only
other thing I can think of is upgrading my version of
bison.

I have also tried the same type of method to build
ELDK 3.1 from SRPMS, and have received the same error
from the build_make.log file.

Any help would be greatly appreciated!

John M. Woo
jmwoo2 <at> yahoo.com


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: Building ELDK 3.0/3.1 from SRPMS

[Wolfgang Denk]

Dear John,

in message <20061027182114.24662.qmail@web50315.mail.yahoo.com> you wrote:
> 
> I having trouble rebuilding ELDK 3.0 & ELDK 3.1 from
> the source RPMS.  I have spent a great deal of time on
> this, and I have a feeling that maybe I=92m just not
> doing something correctly (setting up the build
> environment, retrieving source/specs from CVS..
> etc..).  My build machine is Red Hat 9.0 without any
> updates (Kernel 2.4.20-8, the Shrike release).

This will not work; to build ELDK 3.x from scratch you need a  RH-7.3
box *with* all updates installed.

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
e-credibility: the non-guaranteeable likelihood that  the  electronic
data you're seeing is genuine rather than somebody's made-up crap.
- Karl Lehenbauer

Re: Building ELDK 3.0/3.1 from SRPMS

[John W]

Thanks Wolfgang!  Loading RH7.3 and updating
everything with YUM seemed to do the trick to building
ELDK 3.0!

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.

2.  I'm pretty sure that not all of my applications
are building in the ELDK2.1.0 release,  for example
when I check out the log for
/build/ppc-2006-10-27/logs/ppc_4xx/build_modutils.log,
it has the following error:
gperf -a -C -E -g -H is_reserved_hash -k 1,3,$ -N
is_reserved_word -p -t keyword
s.gperf > keywords.c.tmp
/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?

Thanks for the help!

John Woo


--- Wolfgang Denk <wd@denx.de> wrote:

> Dear John,
> 
> in message
> <20061027182114.24662.qmail@web50315.mail.yahoo.com>
> you wrote:
> > 
> > I having trouble rebuilding ELDK 3.0 & ELDK 3.1
> from
> > the source RPMS.  I have spent a great deal of
> time on
> > this, and I have a feeling that maybe I=92m just
> not
> > doing something correctly (setting up the build
> > environment, retrieving source/specs from CVS..
> > etc..).  My build machine is Red Hat 9.0 without
> any
> > updates (Kernel 2.4.20-8, the Shrike release).
> 
> This will not work; to build ELDK 3.x from scratch
> you need a  RH-7.3
> box *with* all updates installed.
> 
> 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
> e-credibility: the non-guaranteeable likelihood that
>  the  electronic
> data you're seeing is genuine rather than somebody's
> made-up crap.
> - Karl Lehenbauer
> 



 
____________________________________________________________________________________
Get your email and see which of your friends are online - Right on the New Yahoo.com 
(http://www.yahoo.com/preview) 

Re: Building ELDK 3.0/3.1 from SRPMS

[Wolfgang Denk]

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?

Re: Building ELDK 3.0/3.1 from SRPMS

[John W]

Wolfgang,

> Out of curiosity: may I ask why you invest efforts
> in this old
> version?
There are a number of people on my team that have been
using ELDK 2.1.0 gcc toolchain to compile their kernel
modules, and userspace programs for a number of years.
 I would love to use ELDK 3.x, but if there are
problems during kernel compilation, user space library
incompatability, etc., I would like to have ELDK 2.1.0
built from source as a "Plan B".  I'm doing my very
best to convince people to upgrade to a newer version
of the gcc toolchain & kernel version.  The only
problem is that I have to prove that ELDK 3.x will
satisfy all of their needs before making such a vast
upgrade. Unfortuantely I work in a place where
"change" does not happen very fast.

> 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.
Thanks.  Let me try and recompile everything first,
and if that doesn't work, then I'll politely ask you
for those logs.  It will take me a few days to track
down the right versions of software and complete this
task.

You have been tremendously helpful!  Thank you very
much.

John M. Woo




--- Wolfgang Denk <wd@denx.de> wrote:

> 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?
> 



 
____________________________________________________________________________________
Access over 1 million songs - Yahoo! Music Unlimited 
(http://music.yahoo.com/unlimited)