From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: PPC build failure with undefined symbols __ashldi3, _restgpr_14_x, ...
Date: Fri, 15 Nov 2013 13:33:07 +0100 [thread overview]
Message-ID: <52861483.70807@gmail.com> (raw)
In-Reply-To: <20131115162200.2c18d0d0@opensuse.site>
[-- Attachment #1: Type: text/plain, Size: 2848 bytes --]
On 15.11.2013 13:22, Andrey Borzenkov wrote:
> В Fri, 15 Nov 2013 12:00:49 +0100
> Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com> пишет:
>
>> On 15.11.2013 06:19, Andrey Borzenkov wrote:
>>> Sources at 6fcec439545c817fbc8e2f51c667a70037a34a76
>>>
>>> Building RPM for PPC (32 or 64 bits) I get
>>>
>>> [ 187s] cat syminfo.lst | sort | gawk -f ../../grub-core/genmoddep.awk > moddep.lst || (rm -f moddep.lst; exit 1)
>>> [ 187s] __ashldi3 in affs is not defined
>>> [ 187s] _restgpr_14_x in affs is not defined
>>> [ 187s] _restgpr_20_x in affs is not defined
>>> [ 187s] _restgpr_25_x in affs is not defined
>>> [ 187s] _restgpr_27_x in affs is not defined
>>> [ 187s] _restgpr_28_x in affs is not defined
>>> [ 187s] _restgpr_30_x in affs is not defined
>>> ...
>>>
>>> for a long list of them.
>>>
>>> Full build logs are available as
>>> https://build.opensuse.org/build/home:arvidjaar:grub2-next/openSUSE_Factory_PowerPC/ppc/grub2/_log
>>> https://build.opensuse.org/build/home:arvidjaar:grub2-next/openSUSE_Factory_PowerPC/ppc64/grub2/_log
>>>
>>> I do not myself have access to any PPC system nor any experience with
>>> them.
>>>
>> You don't have multilib installed.
>
> Could you elaborate? This is native build on PPC system. It has both 64
> and 32 bit of gcc and libgcc installed:
>
> [ 12s] libgcc_s1-32bit-4.8.1_20130909-5.1 ########################################
> [ 10s] libgcc_s1-4.8.1_20130909-5.1 ########################################
> [ 17s] gcc48-4.8.1_20130909-5.1 ########################################
> [ 17s] gcc48-32bit-4.8.1_20130909-5.1 ########################################
>
> This did build successfully until some recent changes (grub2 *is* part
> of openSUSE for PPC). I compared logs for x86 and ppc and both say
>
> [ 119s] checking for __bswapsi2... no
> [ 119s] checking for __bswapdi2... no
> [ 119s] checking for __ashldi3... no
> [ 120s] checking for __ashrdi3... no
> [ 120s] checking for __lshrdi3... no
> [ 120s] checking for __ucmpdi2... no
> [ 120s] checking for _restgpr_14_x... no
>
> unfortunately I'm stuck here. For all I can tell it should either fail
> or succeed in both cases.
>
It should say all "no" on x86 and almost all "yes" on ppc. This output
indicates that link with libgcc failed. You can look how exactly the
test failed in config.log. Can you send me config.log ?
>>> x86 builds OK.
>>>
>>> _______________________________________________
>>> Grub-devel mailing list
>>> Grub-devel@gnu.org
>>> https://lists.gnu.org/mailman/listinfo/grub-devel
>>>
>>
>>
>
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]
next prev parent reply other threads:[~2013-11-15 12:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 5:19 PPC build failure with undefined symbols __ashldi3, _restgpr_14_x, Andrey Borzenkov
2013-11-15 11:00 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-15 12:22 ` Andrey Borzenkov
2013-11-15 12:33 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-11-15 13:43 ` Andrey Borzenkov
2013-11-15 14:02 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-15 14:35 ` Andrey Borzenkov
2013-11-15 14:41 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-15 14:53 ` Andrey Borzenkov
2013-11-16 4:49 ` [PATCH] restore -nostdlib for libgcc symbols tests Andrey Borzenkov
2013-11-16 12:51 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=52861483.70807@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).