From: Vladimir 'phcoder' Serbinenko <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: bean123ch@gmail.com, David Miller <davem@davemloft.net>,
Robert Millan <rmh@aybabtu.com>
Subject: Re: [PATCH] auto-generate libgcc.h
Date: Wed, 21 Oct 2009 23:00:24 +0200 [thread overview]
Message-ID: <4ADF7668.30104@gmail.com> (raw)
In-Reply-To: <4ADF2EE4.2020008@scarlet.be>
rubisher wrote:
> Vladimir 'phcoder' Serbinenko wrote:
>> Robert Millan wrote:
>>> This should be a much cleaner option than maintaining libgcc.h by
>>> hand. Only
>>> tested on sparc, but it should also cast out the build problems on
>>> powerpc.
>>>
>>>
>> 1) Doesn't work in cross-compiler environment. You confused CC and
>> TARGET_CC
>
> Tbh, when I look in the libgcc.h, excepted the header, it was empty.
> It seems that the forked sh doesn't known anything about CC, so I tried:
> + CC=$(TARGET_CC) /bin/sh $< > $@ || (rm -f $@; exit 1)
>
>> 2) Symbols don't get included into symlist.c so it's unlikely to work.
> Well, finaly it doesn't help a lot, the dpkg-build... still failed at
> the same place:
>
> _restgpr_29_x in boot is not defined
>
> Just note that it's not any more _restgpr_31_x(), I presume just
> because nm list it first?
>
If _restgpr_31_x is really GOT table and building system pulls it from
some library it will create bugs (all kind of bugs you can imagine
caused by bad linking)
>> I'll test on imac g3 today
>> 3) Even if it works it would result in a largely bloated kernel.img due
>> to unused libgcc routines
>>
>>
> Well, whatever src tree (svn 2641, 2642, dpkg 1.9-beta3, 1.9-beta4)
> which I reach to all build with gcc-4.3, it always failed to boot:
>
> Welcome to GRUB!
>
> the symbol `__lshrdi3' not found
> Aborted. Press any key to exit.
>
> As I am newbe to grub2 (and have few programming knowledge), can you
> advise me if it's a well known issue?
>
> Thanks for all effort,
> J.
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
--
Regards
Vladimir 'phcoder' Serbinenko
Personal git repository: http://repo.or.cz/w/grub2/phcoder.git
next prev parent reply other threads:[~2009-10-21 21:00 UTC|newest]
Thread overview: 39+ 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
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 [this message]
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
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=4ADF7668.30104@gmail.com \
--to=phcoder@gmail.com \
--cc=bean123ch@gmail.com \
--cc=davem@davemloft.net \
--cc=grub-devel@gnu.org \
--cc=rmh@aybabtu.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox