From: Andrey Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: PPC build failure with undefined symbols __ashldi3, _restgpr_14_x, ...
Date: Fri, 15 Nov 2013 09:19:54 +0400 [thread overview]
Message-ID: <20131115091954.2b642e0b@opensuse.site> (raw)
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.
x86 builds OK.
next reply other threads:[~2013-11-15 5:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 5:19 Andrey Borzenkov [this message]
2013-11-15 11:00 ` PPC build failure with undefined symbols __ashldi3, _restgpr_14_x, Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-15 12:22 ` Andrey Borzenkov
2013-11-15 12:33 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=20131115091954.2b642e0b@opensuse.site \
--to=arvidjaar@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 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.