From: Vladimir 'phcoder' Serbinenko <phcoder@gmail.com>
To: Pavel Roskin <proski@gnu.org>
Cc: grub-devel@gnu.org, bean123ch@gmail.com,
David Miller <davem@davemloft.net>
Subject: Re: powerpc/sparc problems
Date: Mon, 12 Oct 2009 17:45:33 +0200 [thread overview]
Message-ID: <4AD34F1D.2060009@gmail.com> (raw)
In-Reply-To: <1255361384.27987.8.camel@mj>
Pavel Roskin wrote:
> On Mon, 2009-10-12 at 03:28 -0700, David Miller wrote:
>
>>> Do you think we should just revert it?
>>>
>> Probably.
>>
>
> The purpose of the patch was to remove the requirement that the target
> libc development package is present. That's a common situation for
> x86_64 systems that may have a 32-bit capable compiler, and maybe the
> 32-bit libc installed as a dependency of a 32-bit package (e.g. wine),
> but no the files necessary to link against the 32-bit libc.
>
> I don't know why the checks need to be reinstated, but if it's really
> needed to be done, we could use the trick described in the gcc manual:
>
> `-print-libgcc-file-name'
> Same as `-print-file-name=libgcc.a'.
>
> This is useful when you use `-nostdlib' or `-nodefaultlibs' but
> you do want to link with `libgcc.a'. You can do
>
> gcc -nostdlib FILES... `gcc -print-libgcc-file-name`
>
> This way, it should be possible to check if the functions are in libgcc
> without requiring libc.
>
On sparc64, ppc and mips we compile using -nostdlib -lgcc
-static-libgcc. I would prefer to use the same method in check and
actual compile.
Another idea: we could use nm to generate list of functions in libgcc.
This way we acquire robustness against new functions in gcc but it may
increase the kernel size. PPC and sparc are less used and hence more
prone to problems and size on them doesn't matter so much as it does on
i386-pc. So I would prefer to buy robustness at cost of size
I haven't made up my mind for mips(el) yet since the target is to be
burned in flash where space is limited.
Another solution would be to enumerate symbols in all modules and
compare them to libgcc symbols and include only needed ones but it has a
major drawback of potentially breaking external and separately compiled
modules which is especially problematic if core is burned in flash.
--
Regards
Vladimir 'phcoder' Serbinenko
Personal git repository: http://repo.or.cz/w/grub2/phcoder.git
next prev parent reply other threads:[~2009-10-12 15:45 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 8:55 powerpc/sparc problems Felix Zielcke
2009-10-12 9:05 ` David Miller
2009-10-12 9:42 ` Felix Zielcke
2009-10-12 9:56 ` Vladimir 'phcoder' Serbinenko
2009-10-12 10:11 ` David Miller
2009-10-12 10:27 ` Felix Zielcke
2009-10-12 9:26 ` Vladimir 'phcoder' Serbinenko
2009-10-12 9:33 ` Felix Zielcke
2009-10-20 18:07 ` rubisher
2009-10-20 20:24 ` Vladimir 'phcoder' Serbinenko
2009-10-21 15:59 ` rubisher
2009-10-12 9:58 ` Bean
2009-10-12 10:14 ` David Miller
2009-10-12 10:26 ` Vladimir 'phcoder' Serbinenko
2009-10-12 10:28 ` David Miller
2009-10-12 15:29 ` Pavel Roskin
2009-10-12 15:45 ` Vladimir 'phcoder' Serbinenko [this message]
2009-10-12 22:03 ` Pavel Roskin
2009-10-12 23:39 ` David Miller
2009-10-15 11:58 ` Vladimir 'phcoder' Serbinenko
2009-10-15 22:41 ` Pavel Roskin
2009-10-16 12:44 ` David Miller
2009-10-16 14:10 ` Pavel Roskin
2009-10-17 1:21 ` Pavel Roskin
2009-10-17 9:08 ` Vladimir 'phcoder' Serbinenko
2009-10-17 10:11 ` Robert Millan
2009-10-20 21:38 ` [PATCH] auto-generate libgcc.h Robert Millan
2009-10-21 6:28 ` Vladimir 'phcoder' Serbinenko
2009-10-21 15:55 ` rubisher
2009-10-21 21:00 ` Vladimir 'phcoder' Serbinenko
2009-10-23 16:19 ` rubisher
2009-10-12 10:31 ` powerpc/sparc problems Bean
2009-10-12 11:07 ` David Miller
2009-10-12 14:05 ` Bean
2009-10-14 16:37 ` Robert Millan
2009-10-21 16:03 ` rubisher
2009-10-21 20:15 ` Bean
2009-10-28 10:24 ` Felix Zielcke
2009-10-28 10:29 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2009-10-22 9:12 rubisher
2009-10-22 9:31 ` Bean
2009-10-23 20:34 ` rubisher
2009-10-24 6:13 ` Bean
2009-10-25 15:22 ` rubisher
2009-10-25 15:57 ` Bean
2009-10-26 21:06 ` rubisher
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=4AD34F1D.2060009@gmail.com \
--to=phcoder@gmail.com \
--cc=bean123ch@gmail.com \
--cc=davem@davemloft.net \
--cc=grub-devel@gnu.org \
--cc=proski@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.