From: Bernhard Walle <bernhard@bwalle.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] host-dtc not compiling
Date: Thu, 20 Dec 2012 17:38:55 +0100 [thread overview]
Message-ID: <20121220163855.GA19341@regiomontanus.your-server.de> (raw)
In-Reply-To: <201212201723.34733.tim01@vlsi.informatik.tu-darmstadt.de>
Hi Tim,
* Tim Sander <tim01@vlsi.informatik.tu-darmstadt.de> [2012-12-20 17:23]:
> > * Tim Sander <tim01@vlsi.informatik.tu-darmstadt.de> [2012-12-20 16:09]:
> > > I have the problem that host-dtc and dtc are not compiling with OSELAS
> > > 2012.12.0 and ptxdist 2012.12.0 (and also 2012.11.0). There are some
> > > bogus messages that variables are initialized but unused. But they are
> > > used later on? I have not found the place where this warning flag of
> > > unused variables is set?
> >
> > Maybe -Werror? In the Makefile of dtc itself? Can you post the error log
> > including the compiler call.
> Its -Werror=unused-but-set-variable but its not set in host-dtc.make
> I didn't found the source of the flags but maybe its from the 2012.12 toolchain?
It's set in the Makefile of dtc:
CPPFLAGS = -I libfdt
WARNINGS = -Werror -Wall -Wpointer-arith -Wcast-qual -Wnested-externs \
-Wstrict-prototypes -Wmissing-prototypes -Wredundant-decls
CFLAGS = -g -Os -fPIC -Werror $(WARNINGS)
Since we're talking about host-dtc, the OSELAS.Toolchain is not used but
the toolchain on your host.
You have to patch the source code and/or the Makefile.
Regards,
Bernhard
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-12-20 16:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 15:09 Tim Sander
2012-12-20 15:14 ` Bernhard Walle
2012-12-20 16:23 ` Tim Sander
2012-12-20 16:38 ` Bernhard Walle [this message]
2012-12-20 20:07 ` Michael Olbrich
2012-12-21 14:59 ` Tim Sander
2012-12-21 15:04 ` Michael Olbrich
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=20121220163855.GA19341@regiomontanus.your-server.de \
--to=bernhard@bwalle.de \
--cc=ptxdist@pengutronix.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