LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Mikael Starvik" <mikael.starvik@axis.com>
To: "'Adrian Bunk'" <bunk@kernel.org>,
	"Mikael Starvik" <mikael.starvik@axis.com>,
	"Jesper Nilsson" <Jesper.Nilsson@axis.com>
Cc: "'Sam Ravnborg'" <sam@ravnborg.org>, <linux-kernel@vger.kernel.org>
Subject: RE: cris: build creates links in the source directory
Date: Thu, 28 Feb 2008 07:45:00 +0100	[thread overview]
Message-ID: <BFECAF9E178F144FAEF2BF4CE739C66804C404A8@exmail1.se.axis.com> (raw)
In-Reply-To: <BFECAF9E178F144FAEF2BF4CE739C66805B645B0@exmail1.se.axis.com>

That is correct and we have thoughts about using Makfiles and compiler flags
to resolve this instead as done for other architectures.

/Mikael

-----Original Message-----
From: Adrian Bunk [mailto:bunk@kernel.org] 
Sent: Wednesday, February 27, 2008 11:06 PM
To: Mikael Starvik; Jesper Nilsson
Cc: dev-etrax; Sam Ravnborg; linux-kernel@vger.kernel.org
Subject: cris: build creates links in the source directory


Especially when building with a separate object directory the following 
part of arch/cris/Makefile is not so nice since it creates links in the 
source directory:

<--  snip  -->

# Create some links to make all tools happy
$(SRC_ARCH)/.links:
        @rm -rf $(SRC_ARCH)/drivers
        @ln -sfn $(SARCH)/drivers $(SRC_ARCH)/drivers
        @rm -rf $(SRC_ARCH)/boot
        @ln -sfn $(SARCH)/boot $(SRC_ARCH)/boot
        @rm -rf $(SRC_ARCH)/lib
        @ln -sfn $(SARCH)/lib $(SRC_ARCH)/lib
        @rm -f $(SRC_ARCH)/arch/mach
        @rm -rf $(SRC_ARCH)/arch
        @ln -sfn $(SARCH) $(SRC_ARCH)/arch
ifdef CONFIG_ETRAX_ARCH_V32
        @ln -sfn ../$(SARCH)/$(MACH) $(SRC_ARCH)/arch/mach
endif
        @rm -rf $(SRC_ARCH)/kernel/vmlinux.lds.S
        @ln -sfn ../$(SARCH)/vmlinux.lds.S $(SRC_ARCH)/kernel/vmlinux.lds.S
        @rm -rf $(SRC_ARCH)/kernel/asm-offsets.c
        @ln -sfn ../$(SARCH)/kernel/asm-offsets.c
$(SRC_ARCH)/kernel/asm-offsets.c
        @touch $@

# Create link to sub arch includes
$(srctree)/include/asm-$(ARCH)/.arch: $(wildcard 
include/config/arch/*.h)
        @echo '  SYMLINK include/asm-$(ARCH)/arch ->
include/asm-$(ARCH)/$(SARCH)'
        @rm -f $(srctree)/include/asm-$(ARCH)/arch/mach
        @rm -f $(srctree)/include/asm-$(ARCH)/arch
        @ln -sf $(SARCH) $(srctree)/include/asm-$(ARCH)/arch
ifdef CONFIG_ETRAX_ARCH_V32
        @ln -sf $(MACH) $(srctree)/include/asm-$(ARCH)/arch/mach
endif
        @touch $@

<--  snip  -->

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


       reply	other threads:[~2008-02-28  6:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BFECAF9E178F144FAEF2BF4CE739C66805B645B0@exmail1.se.axis.com>
2008-02-28  6:45 ` Mikael Starvik [this message]
2008-02-27 22:05 Adrian Bunk

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=BFECAF9E178F144FAEF2BF4CE739C66804C404A8@exmail1.se.axis.com \
    --to=mikael.starvik@axis.com \
    --cc=Jesper.Nilsson@axis.com \
    --cc=bunk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --subject='RE: cris: build creates links in the source directory' \
    /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

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).