From: "Murat Artun" <artunmurat@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: changing the EDLK components
Date: Wed, 26 Sep 2007 17:25:19 +0300 [thread overview]
Message-ID: <4e5a3720709260725x6d2e9faemc6a6053379610df8@mail.gmail.com> (raw)
Hello,
In fact I have asked a variant of this question before.
I want to learn the way of building a GNU Automake project and adding
it into ELDK. This could be needed because the current version of an
ELDK component is old to meet the requirements or a library which is
not an ELDK component is to be used in our ppc system.
Section "3.7. Rebuilding ELDK Components" gives details of rebuilding
the components whose source rpms are provided with ELDK.
As I said above I asked a variant of this question to understand how
to build a library in a clean way which is not a part of ELDK.
As now, I need to upgrade an ELDK component. Namely, I need version
0.9.8 of OpenSSL, where latest ELDK release has OpenSSL with version
0.9.7f. I want to learn if it is necessary for me to follow the same
procedure stated in documentation in section "3.7. Rebuilding ELDK
Components". If this is the case, could anyone point me to resources
about how to prepare source rpms from an Automake project to prepare
the source rpm of version 0.9.8 of OpenSSL? Of course building the new
version of the component and placing everything by hand is always a
solution, but I want to understand the clean way of doing this.
Thanks and regards...
--
M u r at A r t u n, MSc.
Design Engineer
"be conservative in what you do, be liberal in what you accept from others"
next reply other threads:[~2007-09-26 14:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 14:25 Murat Artun [this message]
2007-09-26 14:53 ` git files from secret lab Mead, Joseph
2007-09-26 15:00 ` Grant Likely
2007-09-26 20:03 ` Mead, Joseph
2007-09-26 18:06 ` Ming Liu
2007-09-26 23:20 ` changing the EDLK components Wolfgang Denk
2007-09-27 14:34 ` Murat Artun
2007-09-27 21:16 ` 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=4e5a3720709260725x6d2e9faemc6a6053379610df8@mail.gmail.com \
--to=artunmurat@gmail.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).