From: Masahiro Yamada <yamada.m@jp.panasonic.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 0/6] Second step towards Kbuild: Descend down like Kbuild
Date: Fri, 04 Oct 2013 19:37:53 +0900 [thread overview]
Message-ID: <20131004193752.EEAB.AA925319@jp.panasonic.com> (raw)
In-Reply-To: <CAPnjgZ2c6wBPhFber68gURn2xMs=CRLzRPM-6q2PueHyOjytPw@mail.gmail.com>
Hello Simon
> Can you please explain why you need to change the .lds files - sorry it is
> not obvious to me.
This series changes how objects are linked.
Before this series,
drivers/bios_emulator/libatibiosemu.o
drivers/block/libblock.o
drivers/pcmcia/libpcmcia.o
...
are directly linked into ./u-boot at the final link stage.
After this series,
drivers/bios_emulator/built-in.o
drivers/block/built-in.o
drivers/pcmcia/built-in.o
...
are combined into drivers/libdrivers.o
and then drivers/libdrivers.o is linked into ./u-boot.
This means that all symbols in
drivers/bios_emulator/built-in.o
drivers/block/built-in.o
drivers/pcmcia/built-in.o
...
are also included in drivers/libdrivers.o
> --- a/board/tqc/tqm8xx/u-boot.lds
> +++ b/board/tqc/tqm8xx/u-boot.lds
> @@ -23,8 +23,8 @@ SECTIONS
> board/tqc/tqm8xx/libtqm8xx.o (.text*)
> disk/libdisk.o (.text*)
> drivers/net/libnet.o (.text*)
> - drivers/pcmcia/libpcmcia.o (.text.pcmcia_on)
> - drivers/pcmcia/libpcmcia.o (.text.pcmcia_hardware_enable)
> + drivers/libdrivers.o (.text.pcmcia_on)
> + drivers/libdrivers.o (.text.pcmcia_hardware_enable)
>
> . = DEFINED(env_offset) ? env_offset : .;
> common/env_embedded.o (.ppcenv*)
This is to avoid multiple definition error at the link stage.
.test.pcmcia_on and .text.pcmcia_hardware_enable
are included in both drivers/pcmcia/built-in.o and drivers/libdrivers.o
so I replaced the former with the latter.
> diff --git a/board/LEOX/elpt860/u-boot.lds b/board/LEOX/elpt860/u-boot.lds
> index f9c2beb..b30b667 100644
> --- a/board/LEOX/elpt860/u-boot.lds
> +++ b/board/LEOX/elpt860/u-boot.lds
> @@ -34,7 +34,6 @@ SECTIONS
> arch/powerpc/cpu/mpc8xx/libmpc8xx.o (.text*)
> board/LEOX/elpt860/libelpt860.o (.text*)
> arch/powerpc/lib/libpowerpc.o (.text*)
> -/* drivers/rtc/librtc.o (.text*) */
>
> . = env_offset;
> common/env_embedded.o
Becuase only a comment line is deleted,
this change has no impact and I might not have needed to touch it actually.
I deleted it just because we don't have drivers/rtc/librtc.c any more.
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2013-10-04 10:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 8:23 [U-Boot] [PATCH v3 0/6] Second step towards Kbuild: Descend down like Kbuild Masahiro Yamada
2013-09-30 8:23 ` [U-Boot] [PATCH v3 1/6] Makefile: support descending down to subdirectories Masahiro Yamada
2013-09-30 8:23 ` [U-Boot] [PATCH v3 2/6] drivers: move some drivers to drivers/Makefile Masahiro Yamada
2013-09-30 8:23 ` [U-Boot] [PATCH v3 3/6] fs: move some file system to fs/Makefile Masahiro Yamada
2013-09-30 8:23 ` [U-Boot] [PATCH v3 4/6] ARM: tegra: move Tegra specific code under arch/arm/ Masahiro Yamada
2013-09-30 8:23 ` [U-Boot] [PATCH v3 5/6] ARM: omap: move OMAP " Masahiro Yamada
2013-09-30 8:23 ` [U-Boot] [PATCH v3 6/6] ARM: s5pc, exynos: move Samsung ARM SoC " Masahiro Yamada
2013-10-03 23:51 ` [U-Boot] [PATCH v3 0/6] Second step towards Kbuild: Descend down like Kbuild Simon Glass
2013-10-04 10:37 ` Masahiro Yamada [this message]
2013-10-04 15:52 ` Simon Glass
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=20131004193752.EEAB.AA925319@jp.panasonic.com \
--to=yamada.m@jp.panasonic.com \
--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