From: Nishanth Menon <nm@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot(v2014.04-rc1) make tags reports find error
Date: Thu, 20 Feb 2014 10:05:02 -0600 [thread overview]
Message-ID: <530627AE.1020204@ti.com> (raw)
Doing a make tags after build for OMAP4_panda reports find error as
follows:
"find: `/omap4': No such file or directory"
Full steps:
u-boot$ git clean -fdx >/dev/null
u-boot$ make -j6 CROSS_COMPILE=arm-linux-gnueabi- ARCH=arm
omap4_panda_config >/dev/null
u-boot$ make -j6 CROSS_COMPILE=arm-linux-gnueabi- ARCH=arm >/dev/null
u-boot$ make -j6 CROSS_COMPILE=arm-linux-gnueabi- ARCH=arm tags
ctags -w -o ctags `find -L /omap4 arch/arm/lib board/ common disk
drivers drivers/dma drivers/gpio drivers/i2c drivers/input drivers/mmc
drivers/mtd drivers/mtd/onenand drivers/mtd/spi drivers/net
drivers/net/phy drivers/pci drivers/power drivers/power/battery
drivers/power/fuel_gauge drivers/power/mfd drivers/power/pmic
drivers/serial drivers/spi drivers/usb/eth drivers/usb/gadget
drivers/usb/host drivers/usb/musb-new drivers/usb/musb drivers/usb/phy
drivers/usb/ulpi fs lib lib/libfdt net test tools examples include \
-name '*.[chS]' -print`
find: `/omap4': No such file or directory
u-boot$ ls tags
ls: cannot access tags: No such file or directory
nmenon at kahuna:~/Src/opensource/u-boot$ ls ctags
ctags
u-boot$ ctags --version
Exuberant Ctags 5.9~svn20110310, Copyright (C) 1996-2009 Darren Hiebert
Compiled: Nov 9 2011, 17:42:21
Addresses: <dhiebert@users.sourceforge.net>,
http://ctags.sourceforge.net
Optional compiled features: +wildcards, +regex
--
Regards,
Nishanth Menon
next reply other threads:[~2014-02-20 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 16:05 Nishanth Menon [this message]
2014-02-21 3:59 ` [U-Boot] u-boot(v2014.04-rc1) make tags reports find error Masahiro Yamada
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=530627AE.1020204@ti.com \
--to=nm@ti.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 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.