powerpc-linux-gnuspe progress (2)

[Steve Papacharalambous]

Hi Clemens,

For some reason it seems like the initial patches aren't getting applied 
correctly.  To apply them try using the following:

[snip]
tar zxvf crosstool-0.28-rc37.tar.gz

cd crosstool-0.28-rc37

bzcat <path to e500 patches>/crosstool-0.28-extra-patches.patch.bz2 | 
patch -p1

bzcat <path to e500 patches>/crosstool-0.28-rc37-e500.patch.bz2 | patch -p1
[/snip]

At this point the following additions should have been applied to crosstool:

- demo-e500.sh

- gcc-3.4.3-e500-glibc-2.3.3-spe.dat

- patches/binutils-2.15-spe

- patches/gcc-3.4.1-spe

- patches/gcc-3.4.2-spe

- patches/glibc-2.3.2-spe

- patches/glibc-2.3.3-spe

- Modified getandpatch.sh which looks at the environment variable 
EXTRA_PATCHES


If these aren't present then the e500 toolchain won't build successfully.

Once these patches have been successfully applied to crosstool, future 
builds using the patched crosstool can be run with the -nounpack option.

Note that these extra patches are temporary and should be incorporated 
into the next release of crosstool.  If this happens you won't need to 
apply the e500 extra patches in future releases.

Best regards,

Steve

Clemens Koller wrote:
> Hello, Steve ... and all the others.
> Good morning!
> 
> Thank you for your assistance.
> (Sorry for my brute force methods)
> 
> Steve Papacharalambous wrote:
> 
>> Hi Clemens,
>>
>> 1) You don't need to create the spe directory in glibc, it should get 
>> created automatically.  If this doesn't happen then there has been an 
>> error with the patching process.
> 
> 
> Another day, another luck:
> Yes, I see, there seems to be something wrong during the initial patching.
> 
>> You _cannot_ use the -nounpack option to all.sh otherwise the spe 
>> patches will not get applied.
> 
> 
> I guess, I understood that. I always started without --nounpack.
> Just when I want to re-run all.sh (after my tries to fix an error),
> I added --nounpack to it to save time.
> 
> Maybe it would be a good idea to add some build-milestones to give
> non-crosstoolers a hint in which part it fails to know, and if it's
> possible to re-start with a --nounpack?
> 
>>  Try running the demo-e500.sh without any modifications, this is known 
>> to build an e500 cross toolchain for x86 hosts.
>>
>> Before you run demo-e500.sh apply the following patches to crosstool:
>>
>> crosstool-0.28-rc37-e500.patch.bz2
>> crosstool-0.28-extra-patches.patch.bz2
> 
> 
> That's what I did... but now as you wrote...
> 
>> Now check that the following directory is present:
>>
>> crosstool-0.28-rc37/patches/glibc-2.3.3-spe
> 
> 
> Okay... I think there is something broken in my source/patch trees.
> The patch got applied without any rejections... but they seem
> to be at the wrong place... okay... let me see...
> 
>> If this directory isn't present then the e500 toolchain build will 
>> fail as it contains the glibc spe additions needed for the e500 
>> toolchain.
>>
>> When the glibc-2.3.3 sources are unpacked and patched by crosstool 
>> there should be an spe directory under glibc-2.3.3, if not then an 
>> error has occurred with the patching.
> 
> 
> It's missing... now I know where it needs to be and now i can
> check why it isn't there. :-)
> 
>> Hope that this helps,
> 
> 
> YES, thank you a lot!
> 
> Clemens Koller
> _______________________________
> R&D Imaging Devices
> Anagramm GmbH
> Rupert-Mayer-Str. 45/1
> 81379 Muenchen
> Germany
> 
> http://www.anagramm.de
> Phone: +49-89-741518-50
> Fax: +49-89-741518-19
> 
> 
> ------
> Want more information?  See the CrossGCC FAQ, 
> http://www.objsw.com/CrossGCC/
> Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
> 
> 




------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com