Adir,

I did not see your original post, so I do not know what errors you encountered. 
 (I do not understand why you are using a CentOS source RPM for a PPC CPU.)  
However, it should be possible to update an old bash to patch the ShellShock 
vulnerability.  I have done it on several of our CentOS and Mac OS X systems 
that are many years old.  I recommend that you stick with the version of bash 
your system already uses, apply the latest patches to that release, and build 
that.  On your target system, enter "bash --version" to display the version.  
For example, on my Mac OS X 10.6 system, the version is 3.2.X.  You can 
download the GNU sources and patches for that version directly from 
https://ftp.gnu.org/pub/gnu/bash.  Alternately, if you have the sources for the 
version you are running (ELDK v4.2), all you will need are the patches since 
that release.  I think in either case you will have to apply the patches you 
need manually.  If you use the GNU sources, there is a configure command that 
will hopefully create a makefile you can use.  If you are patching the ELDK 
v4.2 sources, follow the ELDK instructions to update an application.

For example, for the Mac OS X 10.6 bash, I performed these steps after I 
determined I needed patches 052 through 057 (which was the latest patch at the 
time):

• Download the patch files from gnu.org. These must start with bash32-052, and 
include
     all subsequent patches sequentially:

  $ for patch in 052 053 054 055 056 057
    do
       curl -O https://ftp.gnu.org/pub/gnu/bash/bash-3.2-patches/bash32-${patch}
    done

• Apply the patches in order:

  $ cd bash-92/bash-3.2
  $ for patch in 052 053 054 055 056 057
    do
       patch -p0 <../../bash32-${patch}
    done

• Build the patched version of bash:

This is where you would run either the ELDK build procedure or the GNU 
configure and make.

Larry Baker
US Geological Survey
650-329-5608
[email protected]



On 12 Nov 2014, at 8:42 AM, Wolfgang Denk wrote:

> Dear Adir,
> 
> In message 
> <db100343705343de912bfd7f086bd...@amspr05mb148.eurprd05.prod.outlook.com> you 
> wrote:
>> 
>> I'm trying to build new rpm for eldk4.2 for ppc460 cpu.
>> 
>> I failed while I'm building the source rpm version http://vault.centos.org/
>> 6.5/updates/Source/SPackages/bash-4.1.2-15.el6_5.2.src.rpm
> 
> This is pretty normal, I'm afraid.  ELDK v4.2 was based on bash 3.2 of
> May, 2007 - that's more than 7 years ago.   You must not expect that
> you can just update to pretty recent versions of some software
> package any more.  You will find that you run into a dependency here
> and one there, which in turn will cause other dependencies, and in a
> blink of an eye you will be trapped in a maze of depencencies which
> cover more or less the whole distribution.
> 
> ELDK v4.2 is outdated, and it is practically impossible to update it.
> 
> It was a great release - I think the best we ever did - but now it is
> obsolete, and time to move on.
> 
> I recommend you stop wasting your time on that old stuff, and switch
> to a more recent ELDK v5.x version.
> 
> 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: [email protected]
> The price of curiosity is a terminal experience.
>                         - Terry Pratchett, _The Dark Side of the Sun_
> _______________________________________________
> eldk mailing list
> [email protected]
> http://lists.denx.de/mailman/listinfo/eldk

_______________________________________________
eldk mailing list
[email protected]
http://lists.denx.de/mailman/listinfo/eldk

Reply via email to