From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] How can a file in directory "u-boot-1.1.4\include\configs" be included?
Date: Fri, 21 Apr 2006 08:02:47 -0400 [thread overview]
Message-ID: <4448C9E7.7070104@smiths-aerospace.com> (raw)
In-Reply-To: <20060420220951.907F5353A57@atlas.denx.de>
Wolfgang Denk wrote:
> In message <200604200844.k3K8i3wk016937@scut.edu.cn> you wrote:
>> I'm a beginner at u-boot porting and have a question about how can
>> a file in directory "u-boot-1.1.4\include\configs", say pxa255_idp.h,
>
> There is no such file. Both '\i' and '\c' are undefined escape
> sequences in the C programming language.
Hi Wolfgang,
The context here could be either cpp or shell. Backslash \ is a valid
escape in all shells that are worthy of being used at denx.de (I forgot
if you prefer bash or csh). Either way, your statement is still
correct, there is no file "u-boot-1.1.4includeconfigs" (or
"u-boot-1.1.4includeconfigspxa255_idp.h" to extrapolate the question).
$ ls -l u-boot-1.1.4\include\configs\pxa255_idp.h
/bin/ls: u-boot-1.1.4includeconfigspxa255_idp.h: No such file or directory
$ touch u-boot-1.1.4\include\configs\pxa255_idp.h
$ ls u-boot-1.1.4\include\configs\pxa255_idp.h
u-boot-1.1.4includeconfigspxa255_idp.h
$ cat x.c
/*
* Test escaping in the C compiler
*/
#include "u-boot-1.1.4\include\configs\pxa255_idp.h"
int main(int argc, char *argv[])
{
return(0);
}
$ make x
cc x.c -o x
x.c:4:53: u-boot-1.1.4\include\configs\pxa255_idp.h: No such file or
directory
make: *** [x] Error 1
Geek humor. I gotta get a life! ;-)
gvb
prev parent reply other threads:[~2006-04-21 12:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 8:59 [U-Boot-Users] How can a file in directory "u-boot-1.1.4\include\configs" be included? 陈敏
2006-04-20 10:05 ` Ganesh Ramachandran
2006-04-20 22:09 ` Wolfgang Denk
2006-04-21 12:02 ` Jerry Van Baren [this message]
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=4448C9E7.7070104@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace.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