From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Using PTXdist on Mac OS 10.7
Date: Mon, 10 Dec 2012 09:48:18 +0100 [thread overview]
Message-ID: <20121210084818.GI26985@pengutronix.de> (raw)
In-Reply-To: <BE31DE3F-6BFA-406E-9164-12BA97A0F894@etit.tu-chemnitz.de>
On Sat, Dec 08, 2012 at 04:43:56PM +0100, Daniel Kriesten wrote:
> Dear all,
>
> So today I did a fresh build of ptxdist on my mac using
> Mac OS X 10.7.5
> XCode 4.5.2 (4G2008a)
>
> and (nearly) following the guide of Bernhard. Only, I use the git-Version as of today (08f738f9).
>
> In addition to the tools mentioned in the guide, I had to install autoconf and automake.
>
> Then I did:
> ./autogen.sh
> ./configure --prefix=/usr/local/ptxdist --with-bash-completion=/usr/local/etc/bash_completion.d
> make
>
> This ends in the following error:
> ----- 8< -----
> gcc -g -O2 -DCURSES_LOC="<curses.h>" -DKBUILD_NO_NLS -DPACKAGE='"ptxdist"' -DCONFIG_='"PTXCONF_"' -c mconf.c -o mconf.o
> mconf.c: In function ‘search_conf’:
> mconf.c:378: error: invalid initializer
> make[1]: *** [mconf.o] Error 1
> make: *** [kconfig] Error 2
> ----- >8 -----
>
> Happily, clang is more nosy on the error:
> ----- 8< -----
> clang -g -O2 -DCURSES_LOC="<curses.h>" -DKBUILD_NO_NLS -DPACKAGE='"ptxdist"' -DCONFIG_='"PTXCONF_"' -c mconf.c -o mconf.o
> mconf.c:378:25: warning: implicit declaration of function 'CIRCLEQ_HEAD_INITIALIZER' is invalid in C99 [-Wimplicit-function-declaration]
> struct jk_head head = CIRCLEQ_HEAD_INITIALIZER(head);
> ^
> mconf.c:378:18: error: initializing 'struct jk_head' with an expression of incompatible type 'int'
> struct jk_head head = CIRCLEQ_HEAD_INITIALIZER(head);
> ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 1 warning and 1 error generated.
> ----- >8 -----
>
> So the solution is to add "missing.h" to mconf.c, when compiling on a mac. But I'm not sure, what's the pretty way to do that in a platform independent way. But I'm sure you may lend me a hand here?
Just include it unconditionally "missing.h" only defines things that are
actually missing. If it breaks anything, then it's a bug in "missing.h".
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-12-10 8:48 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 17:11 [ptxdist] Using PTXdist on Mac OS Bernhard Walle
2012-04-09 17:48 ` Juergen Beisert
2012-04-10 9:37 ` Bernhard Walle
2012-04-09 18:01 ` Andreas Bießmann
2012-04-09 18:59 ` Bernhard Walle
2012-04-09 19:47 ` Juergen Beisert
2012-04-09 20:04 ` Andreas Bießmann
2012-04-09 20:48 ` Andreas Bießmann
2012-04-10 9:04 ` Bernhard Walle
2012-04-10 18:35 ` Bernhard Walle
2012-04-17 11:08 ` Daniel Kriesten
2012-04-17 11:24 ` Michael Olbrich
2012-04-17 11:45 ` Bernhard Walle
2012-04-17 11:59 ` Daniel Kriesten
2012-04-17 12:03 ` Bernhard Walle
2012-04-17 12:32 ` Daniel Kriesten
2012-04-18 8:29 ` Michael Olbrich
2012-04-18 11:25 ` Daniel Kriesten
2012-04-18 14:16 ` Michael Olbrich
2012-04-18 14:28 ` Daniel Kriesten
2012-04-19 10:41 ` Daniel Kriesten
2012-04-19 11:29 ` Andreas Bießmann
2012-04-19 12:04 ` Daniel Kriesten
2012-04-19 12:25 ` Andreas Bießmann
2012-04-19 13:12 ` Daniel Kriesten
2012-04-19 13:27 ` Michael Olbrich
2012-04-19 14:03 ` Andreas Bießmann
2012-04-19 20:13 ` Bernhard Walle
2012-12-08 15:31 ` Daniel Kriesten
2012-12-08 15:43 ` [ptxdist] Using PTXdist on Mac OS 10.7 Daniel Kriesten
2012-12-10 8:48 ` Michael Olbrich [this message]
2012-12-10 8:46 ` [ptxdist] Using PTXdist on Mac OS Michael Olbrich
2012-12-11 15:00 ` Daniel Kriesten
2012-12-12 11:00 ` Michael Olbrich
2012-04-17 11:48 ` Bernhard Walle
2012-04-17 12:04 ` Daniel Kriesten
2012-04-17 12:18 ` Bernhard Walle
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=20121210084818.GI26985@pengutronix.de \
--to=m.olbrich@pengutronix.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