grub-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: powerpc/sparc problems


From: Vladimir 'phcoder' Serbinenko
Subject: Re: powerpc/sparc problems
Date: Mon, 12 Oct 2009 12:26:04 +0200
User-agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090701)

David Miller wrote:
> From: Bean <address@hidden>
> Date: Mon, 12 Oct 2009 17:58:42 +0800
>
>   
>> Try my branch, it includes the libgcc functions in grub instead of
>> rely on external library. It builds and run properly for
>> powerpc-ieee1275 last time I check.
>>     
>
> Good luck when the compiler changes the interface and/or semantics of
> these routines in a future version.  Will you enumerate your in-tree
> copies by gcc version with ifdefs or similar?
>
> That's why gcc and it's libgcc are distributed together, and gcc
> configures itself to link with a specific libgcc and only that libgcc.
>
> This whole things perfectly fine in GRUB when I implemented the
> necessary machinery to find if these routines exist in libgcc at
> configure time and to reference them properly in the build.
>
> They've merely been broken meanwhile and someone just needs to rectify
> that regression.
>
>
>   
It was removed as a part of following commit
2009-06-10  Pavel Roskin  <address@hidden>

        * configure.ac: Use -nostdlib when probing for the target.  It
        should not be required to have libc for the target.

        * configure.ac: Remove checks for __bswapsi2 and __bswapdi2,
        they fail without libc headers for the target.
        * include/grub/powerpc/libgcc.h: Use weak attribute for all
        exports.
        * include/grub/sparc64/libgcc.h: Likewise.  Don't use
        preprocessor conditionals.

Do you think we should just revert it?
> _______________________________________________
> Grub-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>   


-- 
Regards
Vladimir 'phcoder' Serbinenko
Personal git repository: http://repo.or.cz/w/grub2/phcoder.git 





reply via email to

[Prev in Thread] Current Thread [Next in Thread]