mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] ptxdist go abort when trying to link qt against libstdc++
Date: Fri, 11 Apr 2014 08:23:45 +0200	[thread overview]
Message-ID: <20140411062343.GB5058@omega> (raw)
In-Reply-To: <53469A1B.6000204@railtec-systems.ch>

On Thu, Apr 10, 2014 at 03:18:19PM +0200, Marc Michalewicz, Railtec Systems GmbH wrote:
> Hello,
> 
> i try to build a ptxdist systeme - the first time.
> My Cross-Toolchain - target i686, host x86_64 - was built successfully in
> the end
> but now I am really stuck at this point during the "ptxdist go" - stage:
> 
> <snip>
> g++ -o "/home/marc/svn/ptxdist/ptxdist_CPU/platform/build-host/qt-everywhere-opensource-src-4.7.3-build/bin/qmake"
> project.o property.o main.o makefile.o unixmake2.o unixmake.o mingw_make.o
> option.o winmakefile.o projectgenerator.o meta.o makefiledeps.o
> metamakefile.o xmloutput.o pbuilder_pbx.o borland_bmake.o msvc_vcproj.o
> msvc_vcxproj.o msvc_nmake.o msvc_objectmodel.o msbuild_objectmodel.o
> symmake.o initprojectdeploy_symbian.o symmake_abld.o symmake_sbsv2.o
> symbiancommon.o registry.o epocroot.o qtextcodec.o qutfcodec.o qstring.o
> qtextstream.o qiodevice.o qmalloc.o qglobal.o qbytearray.o
> qbytearraymatcher.o qdatastream.o qbuffer.o qlist.o qfile.o
> qfsfileengine_unix.o qfsfileengine_iterator_unix.o qfsfileengine.o
> qfsfileengine_iterator.o qregexp.o qvector.o qbitarray.o qdir.o
> qdiriterator.o quuid.o qhash.o qfileinfo.o qdatetime.o qstringlist.o
> qabstractfileengine.o qtemporaryfile.o qmap.o qmetatype.o qsettings.o
> qlibraryinfo.o qvariant.o qvsnprintf.o qlocale.o qlinkedlist.o qurl.o
> qnumeric.o qcryptographichash.o qxmlstream.o qxmlutils.o  -m32
> /usr/bin/ld: skipping incompatible
> /usr/lib/gcc/x86_64-linux-gnu/4.7/libstdc++.so when searching for -lstdc++
> /usr/bin/ld: skipping incompatible
> /usr/lib/gcc/x86_64-linux-gnu/4.7/libstdc++.a when searching for -lstdc++
> <snip>
> 
> As I guess, it seems the hostcompiler is used to link some qt-stuff an in
> the end it misses some important lib. Does anyone have an idea about the
> problem ? It seems to be related to the host-installation: I use an ubuntu
> 12.10 system, fully uptodate; ia32 package is installed.
> 

Look at the g++ call the "-m32" argument:

Ouoting g++ manual:

"-m32
-m64
-mx32
   Generate code for a 32-bit or 64-bit environment.  The -m32 option
   sets "int", "long", and pointer types to 32 bits, and generates
   code that runs on any i386 system.

   The -m64 option sets "int" to 32 bits and "long" and pointer types
   to 64 bits, and generates code for the x86-64 architecture.  For
   Darwin only the -m64 option also turns off the -fno-pic and
   -mdynamic-no-pic options.

   The -mx32 option sets "int", "long", and pointer types to 32 bits,
   and generates code for the x86-64 architecture."

So you using a x86_64 system and try to build qmake with a -m32 argument
linked to a libstdc++ which are build for 64 bit system. This can't be
work. Check why there is a -m32.

- Alex

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2014-04-11  6:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10 13:18 Marc Michalewicz, Railtec Systems GmbH
2014-04-11  6:23 ` Alexander Aring [this message]
2014-04-23  7:20   ` 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=20140411062343.GB5058@omega \
    --to=alex.aring@gmail.com \
    --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