From: John W <jmwoo2@yahoo.com>
To: linuxppc-embedded@ozlabs.org
Subject: Building ELDK 3.0/3.1 from SRPMS
Date: Fri, 27 Oct 2006 11:21:14 -0700 (PDT) [thread overview]
Message-ID: <20061027182114.24662.qmail@web50315.mail.yahoo.com> (raw)
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 Im 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 Im using to setup my
development environment for ELDK 3.0
#Make build directory
mkdir /opt/eldkv3.0
#checkout tarballs & build. One caveat is that Im
behind a proxy server, and Im 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)
Im not exactly sure that by fixing this problem will
install libstdc++ correctly, infact, Im 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
next reply other threads:[~2006-10-27 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-27 18:21 John W [this message]
2006-10-27 21:19 ` Building ELDK 3.0/3.1 from SRPMS Wolfgang Denk
2006-10-30 3:38 ` John W
2006-10-30 23:53 ` Wolfgang Denk
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=20061027182114.24662.qmail@web50315.mail.yahoo.com \
--to=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).