mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de, oselas@community.pengutronix.de
Subject: Re: [ptxdist] [oselas] 2012.06.0 mini2440 BSP compile error on shiboken package
Date: Mon, 27 Aug 2012 15:58:25 +0200	[thread overview]
Message-ID: <20120827135825.GD13798@pengutronix.de> (raw)
In-Reply-To: <201208271110.00915.jbe@pengutronix.de>

Hi,

On Mon, Aug 27, 2012 at 11:10:00AM +0200, Juergen Beisert wrote:
> david wrote:
> > I'm getting an error compiling up the 2012.06 release of the mini2440 BSP,
> > everything compiles up with the exception of the shiboken package for
> > pyside. The error message returned:
> >
> > [...]
> 
> Same here:
> 
> $ ptxdist compile host-shiboken
> [...]
> CMakeFiles/shiboken.dir/qtdoc/qtdocgenerator.cpp.o: In function `DoxygenParser':
> /home/jbe/work/temp/OSELAS.BSP-Pengutronix-Mini2440-2012.06.0/platform-mini2440/build-host/shiboken-1.1.1/ApiExtractor/doxygenparser.h:32: undefined 
> reference to `DocParser::DocParser()'
> /home/jbe/work/temp/OSELAS.BSP-Pengutronix-Mini2440-2012.06.0/platform-mini2440/build-host/shiboken-1.1.1/ApiExtractor/doxygenparser.h:32: undefined 
> reference to `vtable for DoxygenParser'
> CMakeFiles/shiboken.dir/qtdoc/qtdocgenerator.cpp.o: In function `QtDocParser':
> /home/jbe/work/temp/OSELAS.BSP-Pengutronix-Mini2440-2012.06.0/platform-mini2440/build-host/shiboken-1.1.1/ApiExtractor/qtdocparser.h:32: undefined reference 
> to `DocParser::DocParser()'
> /home/jbe/work/temp/OSELAS.BSP-Pengutronix-Mini2440-2012.06.0/platform-mini2440/build-host/shiboken-1.1.1/ApiExtractor/qtdocparser.h:32: undefined reference 
> to `vtable for QtDocParser'
> collect2: error: ld returned 1 exit status
> make[3]: *** [generator/shiboken] Error 1
> 
> I'm not an expert for this package, but can you try:
> 
> Add the line:
> 
>  -DDISABLE_DOCSTRINGS:BOOL=ON \
> 
> to the PTXdist's rules/host-shiboken.make below the existing
> "-DBUILD_TESTS:BOOL=OFF \" (line 30). After that a
> "ptxdist clean host-shiboken; ptxdist go". Maybe it helps. This define will
> disable some feature in the shiboken package. Here it compiles again, but I'm
> not sure if then some important feature is missing in the package. This should
> re-check someone who knows more about shiboken.
> 
> @Michael: What would be the correct solution?

This is indeed the correct solution. This just disables some API doc
generation tool. There is some cmake check to handle this automatically,
but it's broken. I've committed a fix for this in ptxdist master

Regards,
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

  reply	other threads:[~2012-08-27 13:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAPoHKVytywXZvi2Sh0wAmvr+N+Qyjf8DHGCEYvrEJzGxvg5LMw@mail.gmail.com>
2012-08-27  9:10 ` Juergen Beisert
2012-08-27 13:58   ` Michael Olbrich [this message]
2012-08-27 19:33     ` david

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=20120827135825.GD13798@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=oselas@community.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