changing the EDLK components

changing the EDLK components

[Murat Artun]

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"

git files from secret lab

[Mead, Joseph]

Hi,=20

I'm trying to download the xilinx patches from  Grant's git repository,
but don't quite understand what I am doing.

I cloned the tree from Linus' tree

git clone
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
(this worked fine)

cd linux-2.6

git fetch git://git.secretlab.ca/git/linux-2.6.git virtex-dev:virtex-dev

I get the error message:
Fatal: unexpected EOF
Fetch failure: git://git.secretlab.ca/git/linux-2.6.git



Thanks,
Joe

Re: git files from secret lab

[Grant Likely]

On 9/26/07, Mead, Joseph <mead@bnl.gov> wrote:
> Hi,
>
> I'm trying to download the xilinx patches from  Grant's git repository,
> but don't quite understand what I am doing.
>
> I cloned the tree from Linus' tree
>
> git clone
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> (this worked fine)
>
> cd linux-2.6

What version of git are you running (git --version).  That tree is
using the virtual hosting feature of newer versions of git.  You need
to be running at least version 1.5.

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

RE: git files from secret lab

[Ming Liu]

You should perhaps update your git tools into a newer version.

BR
Ming


>From: "Mead, Joseph" <mead@bnl.gov>
>To: <linuxppc-embedded@ozlabs.org>
>Subject: git files from secret lab
>Date: Wed, 26 Sep 2007 10:53:32 -0400
>
>Hi,
>
>I'm trying to download the xilinx patches from  Grant's git repository,
>but don't quite understand what I am doing.
>
>I cloned the tree from Linus' tree
>
>git clone
>git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
>(this worked fine)
>
>cd linux-2.6
>
>git fetch git://git.secretlab.ca/git/linux-2.6.git virtex-dev:virtex-dev
>
>I get the error message:
>Fatal: unexpected EOF
>Fetch failure: git://git.secretlab.ca/git/linux-2.6.git
>
>
>
>Thanks,
>Joe
>
>
>
>
>_______________________________________________
>Linuxppc-embedded mailing list
>Linuxppc-embedded@ozlabs.org
>https://ozlabs.org/mailman/listinfo/linuxppc-embedded

_________________________________________________________________
与联机的朋友进行交流，请使用 MSN Messenger:  http://messenger.msn.com/cn  

RE: git files from secret lab

[Mead, Joseph]

>> Hi,
>>
>> I'm trying to download the xilinx patches from  Grant's git
repository,
>> but don't quite understand what I am doing.
>>
>> I cloned the tree from Linus' tree
>>
>> git clone
>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
>> (this worked fine)
>>
>> cd linux-2.6

>What version of git are you running (git --version).  That tree is
>using the virtual hosting feature of newer versions of git.  You need
>to be running at least version 1.5.

>Cheers,
>g.


Thanks, that was the problem...

Re: changing the EDLK components

[Wolfgang Denk]

In message <4e5a3720709260725x6d2e9faemc6a6053379610df8@mail.gmail.com> you wrote:
> 
> 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.

In  principle,  this  is  a  pretty  straightforward  procedure:  you
download   the   source   RPM   (for   example,  from  the  Fedora  7
distribution), and use the "rpmbuild" command on the  native  syustem
(running  with  root  file  system  mounted  over  NFS  or on a local
harddisk) to build the stuff. For example:

$ rpmbuild --rebuild automake17-1.7.9-8.src.rpm

That's in proinciple. In  reality,  you  will  soon  learn  that  the
package  has  a  lot  of  build  dependencies,  which are not exactly
trivial to resolve, as some of them are circular. You can try and find
what's really needed (and not included with the ELDK) by running

$ rpmbuild --rebuild --nodeps automake17-1.7.9-8.src.rpm

but this is just tof ind out how many othe rpackages youw ill need to
build before...

> 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

You don't need a native version of automake for this, as  builing  is
done  in  the  cross  environment,  and  we  assume you have automake
installed on your build host.

> 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

I don't understand why you mention automake here. It is completely
unrelated.

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

The clean way is to adjust the ELDK buld system for the new  version.
This  is  usually  a  non-trivial  job. By doing it you will start to
admire what ELDK gives you and understand at least a bit of how  much
effort is built into it - and you get it all completely for free...



Alternatively, you can just wait for ELDK 4.2, which will include
openssl-0.9.8b-12

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
That Microsoft, the Trabant of the operating  system  world,  may  be
glancing  over the Berlin Wall at the Audis and BMWs and Mercedes. In
their own universe Trabants and Ladas were mainstream too...
                                                   -- Evan Leibovitch

Re: changing the EDLK components

[Murat Artun]

Ok, I have built my library from its source RPM as you have stated.

Specifically, I have followed the procedure in section "3.7.
Rebuilding ELDK Components". First I have installed source RPMs and
then rebuilt the binary target RPM. However, as I have followed the
compiler messages I recognized that host gcc is called instead of
cross gcc.

Considering that my PATH was set following the advice in section "3.7.
Rebuilding ELDK Components" as "<ELDK_root>/usr/ppc-linux/bin"
directory is before "/usr/bin" what could be the problem?

Thanks and regards...

On 9/27/07, Wolfgang Denk <wd@denx.de> wrote:
> In message <4e5a3720709260725x6d2e9faemc6a6053379610df8@mail.gmail.com> you wrote:
> >
> > 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.
>
> In  principle,  this  is  a  pretty  straightforward  procedure:  you
> download   the   source   RPM   (for   example,  from  the  Fedora  7
> distribution), and use the "rpmbuild" command on the  native  syustem
> (running  with  root  file  system  mounted  over  NFS  or on a local
> harddisk) to build the stuff. For example:
>
> $ rpmbuild --rebuild automake17-1.7.9-8.src.rpm
>
> That's in proinciple. In  reality,  you  will  soon  learn  that  the
> package  has  a  lot  of  build  dependencies,  which are not exactly
> trivial to resolve, as some of them are circular. You can try and find
> what's really needed (and not included with the ELDK) by running
>
> $ rpmbuild --rebuild --nodeps automake17-1.7.9-8.src.rpm
>
> but this is just tof ind out how many othe rpackages youw ill need to
> build before...
>
> > 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
>
> You don't need a native version of automake for this, as  builing  is
> done  in  the  cross  environment,  and  we  assume you have automake
> installed on your build host.
>
> > 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
>
> I don't understand why you mention automake here. It is completely
> unrelated.
>
> > 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.
>
> The clean way is to adjust the ELDK buld system for the new  version.
> This  is  usually  a  non-trivial  job. By doing it you will start to
> admire what ELDK gives you and understand at least a bit of how  much
> effort is built into it - and you get it all completely for free...
>
>
>
> Alternatively, you can just wait for ELDK 4.2, which will include
> openssl-0.9.8b-12
>
> Best regards,
>
> Wolfgang Denk
>
> --
> DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
> That Microsoft, the Trabant of the operating  system  world,  may  be
> glancing  over the Berlin Wall at the Audis and BMWs and Mercedes. In
> their own universe Trabants and Ladas were mainstream too...
>                                                    -- Evan Leibovitch
>


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

Re: changing the EDLK components

[Wolfgang Denk]

In message <4e5a3720709270734k54016e93h68ae6606d959cee9@mail.gmail.com> you wrote:
> 
> Specifically, I have followed the procedure in section "3.7.
> Rebuilding ELDK Components". First I have installed source RPMs and
> then rebuilt the binary target RPM. However, as I have followed the
> compiler messages I recognized that host gcc is called instead of
> cross gcc.
> 
> Considering that my PATH was set following the advice in section "3.7.
> Rebuilding ELDK Components" as "<ELDK_root>/usr/ppc-linux/bin"
> directory is before "/usr/bin" what could be the problem?

If you really followed that advice then please explain how the native
gcc could be called at all because the cross compiler will always  be
found first in the PATH?

I recommend checking the documentation again and following it step by
step.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"This is a test of the Emergency Broadcast System. If this had been an
actual emergency, do you really think we'd stick around to tell you?"