From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] getting ubifs to run
Date: Mon, 26 Sep 2016 06:38:21 +0200 [thread overview]
Message-ID: <57E8A63D.3040200@denx.de> (raw)
In-Reply-To: <CADRLR4FBF8pV_5afzzgGRWCh+GgsZoh=B=qHqDM_kXaJS-U6aw@mail.gmail.com>
Hello Travis,
Am 21.09.2016 um 22:05 schrieb Travis Waters:
> Hello,
>
> I am working to enable UBIFS for use on the sparc platform and I am running
> into the same linking trouble flagged in this thread:
>
> uboot/fs/ubifs/lpt_commit.c:1232: undefined reference to
> `dbg_chk_lpt_free_spc'
> uboot/fs/ubifs/lpt_commit.c:1235: undefined reference to `dbg_check_ltab'
> fs/built-in.o: In function `layout_cnodes':
> uboot/fs/ubifs/lpt_commit.c:195: undefined reference to `dbg_chk_lpt_sz'
> uboot/fs/ubifs/lpt_commit.c:211: undefined reference to `dbg_chk_lpt_sz'
> uboot/fs/ubifs/lpt_commit.c:219: undefined reference to `dbg_chk_lpt_sz'
> uboot/fs/ubifs/lpt_commit.c:233: undefined reference to `dbg_chk_lpt_sz'
> uboot/fs/ubifs/lpt_commit.c:246: undefined reference to `dbg_chk_lpt_sz'
> fs/built-in.o:uboot/fs/ubifs/lpt_commit.c:254: more undefined references to
> `dbg_chk_lpt_sz' follow
> fs/built-in.o: In function `layout_cnodes':
> uboot/fs/ubifs/lpt_commit.c:322: undefined reference to
> `ubifs_dump_lpt_lebs'
> fs/built-in.o: In function `ubifs_add_bud_to_log':
> uboot/fs/ubifs/log.c:194: undefined reference to `ubifs_commit_required'
> uboot/fs/ubifs/log.c:225: undefined reference to `ubifs_request_bg_commit'
> uboot/fs/ubifs/log.c:265: undefined reference to `ubifs_write_node'
> fs/built-in.o: In function `ubifs_log_end_commit':
> uboot/fs/ubifs/log.c:479: undefined reference to `ubifs_write_master'
> fs/built-in.o: In function `do_write_orph_node':
> uboot/fs/ubifs/orphan.c:248: undefined reference to `ubifs_write_node'
>
>
> What is the status of the patch that was addressing this?
Hmm... my last message to Marco (added to Cc) was, to split the patch
into 2 pieces (one for the sparc fixes and one for the ubifs fixes)
IIRC I saw a fix for the sparc errors, but none for ubifs ...
bye,
Heiko
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2016-09-26 4:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 20:05 [U-Boot] [PATCH] getting ubifs to run Travis Waters
2016-09-26 4:38 ` Heiko Schocher [this message]
2016-09-26 4:43 ` Travis Waters
2016-09-26 4:52 ` Heiko Schocher
2016-09-26 13:28 ` Hoefle Marco
-- strict thread matches above, loose matches on Subject: below --
2016-08-11 9:56 Marco
2016-08-12 5:05 ` Heiko Schocher
2016-08-12 7:24 ` Hoefle Marco
2016-08-15 11:55 ` [U-Boot] WG: " Hoefle Marco
2016-09-01 12:45 ` [U-Boot] " Hoefle Marco
2016-09-02 7:57 ` Heiko Schocher
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=57E8A63D.3040200@denx.de \
--to=hs@denx.de \
--cc=u-boot@lists.denx.de \
/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