From: maximilian attems <max@stro.at>
To: dash@vger.kernel.org
Cc: klibc@zytor.com
Subject: dash klibc DEBUG compile trouble
Date: Thu, 8 Jul 2010 10:48:34 +0200 [thread overview]
Message-ID: <20100708084834.GB6829@stro.at> (raw)
on top of the two easy patches I sent I am seeing this one:
usr/dash/exec.c: In function ‘find_command’:
usr/dash/exec.c:290: error: storage size of ‘statb’ isn’t known
usr/dash/exec.c:299: warning: implicit declaration of function ‘stat64’
usr/dash/exec.c:290: warning: unused variable ‘statb’
make[2]: *** [usr/dash/exec.o] Error 1
hmm which include is exec.c missing?
netbsd ash seems to have evolved using stat and no longer stat64,
any hint what I should do here to make this compile:
~/src/klibc$ make KLIBCKERNELSRC=`pwd`/../linux-2.6 EXTRA_KLIBCCFLAGS="-DDEBUG=1"
it be cool to be able to compile klibc again with global debug on. :)
next reply other threads:[~2010-07-08 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 8:48 maximilian attems [this message]
2010-07-08 13:04 ` dash klibc DEBUG compile trouble Herbert Xu
2010-07-08 13:17 ` maximilian attems
2010-07-08 13:51 ` Herbert Xu
2010-07-08 16:20 ` maximilian attems
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=20100708084834.GB6829@stro.at \
--to=max@stro.at \
--cc=dash@vger.kernel.org \
--cc=klibc@zytor.com \
/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