[Buildroot] Qt tribulations take 2

[Buildroot] Qt tribulations take 2

[Charles Krinke]

Let me start over with my Qt question.

I downloaded buildroot-2011.05 and ran several tests, each with "make
clean && make" and each with C++ support checked, both with powerpc
and arm and the results are the same, so either my understanding of
what to click in xconfig is faulty (probable) or there is an issue in
the Qt package scripts. In both cases, I can compile successfully
without Qt checked and in both cases, I get into problems with Qt
checked. I would have expected one of powerpc or arm to successfully
compile and wonder if a suggestion could be made.

You have asked to use pkg-config and are cross-compiling.
Please make sure you have a correctly set-up pkg-config
environment!


This is the Qt for Embedded Linux Open Source Edition.

You are licensed to use this software under the terms of
the Lesser GNU General Public License (LGPL) versions 2.1.
You are also licensed to use this software under the terms of
the GNU General Public License (GPL) versions 3.

Type '3' to view the GNU General Public License version 3.
Type 'L' to view the Lesser GNU General Public License version 2.1.
Type 'yes' to accept this license offer.
Type 'no' to decline this license offer.

Do you accept the terms of either license? yes

Creating qmake. Please wait...
make[1]: Entering directory
`/home/ckrinke/buildroot-2012.05/output/build/qt-4.8.1/qmake'
make[1]: c: Command not found
make[1]: [project.o] Error 127 (ignored)
make[1]: c: Command not found
make[1]: [property.o] Error 127 (ignored)



-- 
Charles Krinke

[Buildroot] Qt tribulations take 2

[Thomas Petazzoni]

Le Fri, 13 Jul 2012 06:51:34 -0700,
Charles Krinke <charles.krinke@gmail.com> a ?crit :

> Let me start over with my Qt question.
> 
> I downloaded buildroot-2011.05 and ran several tests, each with "make

I presume you wanted to say 2012.05, right?

> clean && make" and each with C++ support checked, both with powerpc
> and arm and the results are the same, so either my understanding of
> what to click in xconfig is faulty (probable) or there is an issue in
> the Qt package scripts. In both cases, I can compile successfully
> without Qt checked and in both cases, I get into problems with Qt
> checked. I would have expected one of powerpc or arm to successfully
> compile and wonder if a suggestion could be made.
> Creating qmake. Please wait...
> make[1]: Entering directory
> `/home/ckrinke/buildroot-2012.05/output/build/qt-4.8.1/qmake'
> make[1]: c: Command not found
> make[1]: [project.o] Error 127 (ignored)
> make[1]: c: Command not found
> make[1]: [property.o] Error 127 (ignored)

Please send your Buildroot .config file.

Thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] Qt tribulations take 2

[Charles Krinke]

My apologies, Thomas, I did mean buildroot-2012.05 and here is its
.config renamed as dotconfig. In the mean time, I am frustrating
myself with !#$%* openembedded in an attempt to glean some knowledge
about how Qt fits together in an embedded environment as I slide into
this new project.

Charles

On Fri, Jul 13, 2012 at 7:55 AM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Le Fri, 13 Jul 2012 06:51:34 -0700,
> Charles Krinke <charles.krinke@gmail.com> a ?crit :
>
>> Let me start over with my Qt question.
>>
>> I downloaded buildroot-2011.05 and ran several tests, each with "make
>
> I presume you wanted to say 2012.05, right?
>
>> clean && make" and each with C++ support checked, both with powerpc
>> and arm and the results are the same, so either my understanding of
>> what to click in xconfig is faulty (probable) or there is an issue in
>> the Qt package scripts. In both cases, I can compile successfully
>> without Qt checked and in both cases, I get into problems with Qt
>> checked. I would have expected one of powerpc or arm to successfully
>> compile and wonder if a suggestion could be made.
>> Creating qmake. Please wait...
>> make[1]: Entering directory
>> `/home/ckrinke/buildroot-2012.05/output/build/qt-4.8.1/qmake'
>> make[1]: c: Command not found
>> make[1]: [project.o] Error 127 (ignored)
>> make[1]: c: Command not found
>> make[1]: [property.o] Error 127 (ignored)
>
> Please send your Buildroot .config file.
>
> Thanks!
>
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers, real-time and embedded Linux
> development, consulting, training and support.
> http://free-electrons.com
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot



-- 
Charles Krinke
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dotconfig
Type: application/octet-stream
Size: 29673 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120713/ab4eeb89/attachment-0001.obj>

[Buildroot] Qt tribulations take 2

[Julian Lunz]

Took your provided config and gave it a try on my machine (32bit-Ubuntu
10.04). 
Went through without any hassles :/
What's your environment?


 On Fri, 13 Jul 2012 08:41:37 -0700
Charles Krinke <charles.krinke@gmail.com> wrote:

> My apologies, Thomas, I did mean buildroot-2012.05 and here is its
> .config renamed as dotconfig. In the mean time, I am frustrating
> myself with !#$%* openembedded in an attempt to glean some knowledge
> about how Qt fits together in an embedded environment as I slide into
> this new project.
> 
> Charles
> 
> On Fri, Jul 13, 2012 at 7:55 AM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
> > Le Fri, 13 Jul 2012 06:51:34 -0700,
> > Charles Krinke <charles.krinke@gmail.com> a ?crit :
> >
> >> Let me start over with my Qt question.
> >>
> >> I downloaded buildroot-2011.05 and ran several tests, each with
> >> "make
> >
> > I presume you wanted to say 2012.05, right?
> >
> >> clean && make" and each with C++ support checked, both with powerpc
> >> and arm and the results are the same, so either my understanding of
> >> what to click in xconfig is faulty (probable) or there is an issue
> >> in the Qt package scripts. In both cases, I can compile
> >> successfully without Qt checked and in both cases, I get into
> >> problems with Qt checked. I would have expected one of powerpc or
> >> arm to successfully compile and wonder if a suggestion could be
> >> made. Creating qmake. Please wait...
> >> make[1]: Entering directory
> >> `/home/ckrinke/buildroot-2012.05/output/build/qt-4.8.1/qmake'
> >> make[1]: c: Command not found
> >> make[1]: [project.o] Error 127 (ignored)
> >> make[1]: c: Command not found
> >> make[1]: [property.o] Error 127 (ignored)
> >
> > Please send your Buildroot .config file.
> >
> > Thanks!
> >
> > Thomas
> > --
> > Thomas Petazzoni, Free Electrons
> > Kernel, drivers, real-time and embedded Linux
> > development, consulting, training and support.
> > http://free-electrons.com
> > _______________________________________________
> > buildroot mailing list
> > buildroot at busybox.net
> > http://lists.busybox.net/mailman/listinfo/buildroot
> 
> 
> 

[Buildroot] Qt tribulations take 2

[Arnout Vandecappelle]

On 07/13/12 15:51, Charles Krinke wrote:
> I downloaded buildroot-2011.05 and ran several tests, each with "make
> clean&&  make" and each with C++ support checked, both with powerpc
> and arm and the results are the same, so either my understanding of
> what to click in xconfig is faulty (probable) or there is an issue in
> the Qt package scripts. In both cases, I can compile successfully
> without Qt checked and in both cases, I get into problems with Qt
> checked. I would have expected one of powerpc or arm to successfully
> compile and wonder if a suggestion could be made.
>
> You have asked to use pkg-config and are cross-compiling.
> Please make sure you have a correctly set-up pkg-config
> environment!

  Take a look at output/build/qt-4.8.2/qmake/Makefile.  Near the top you
should find
CXX = @g++
but you probably have 'CXX = @' instead.

  The question is where this comes from.  Can you check your environment if
CXX is defined?  'env | grep CXX'

  Regards,
  Arnout
-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

[Buildroot] Qt tribulations take 2

[Charles Krinke]

Dear Julian:

You were right as usual. It was an environment variable. It was
QMAKESPEC which was set by my installation of the TI SDK a week ago. I
should have checked my  .bashrc after installing the SDK, but I did
not expect any environment changes as a result of installing a
toolchain and u-boot source.

I can compile successfully Qt with the buildroot generated toolchain
now. However, that gets me to the next step. When I try to go back to
using TI's external toolchain, I get this error with libtool. I get no
corresponding libtool error with the buildroot compiled toolchain.
Would you be willing to comment on what might be going on here?

Charles

libtool: Version mismatch error.  This is libtool 2.2.10, but the
libtool: definition of this LT_INIT comes from libtool 2.2.6b.
libtool: You should recreate aclocal.m4 with macros from libtool 2.2.10
libtool: and run autoconf again.
make[5]: *** [gcache.lo] Error 63
make[5]: *** Waiting for unfinished jobs....
libtool: Version mismatch error.  This is libtool 2.2.10, but the
libtool: definition of this LT_INIT comes from libtool 2.2.6b.
libtool: You should recreate aclocal.m4 with macros from libtool 2.2.10
libtool: and run autoconf again.
m

On Sat, Jul 14, 2012 at 9:25 AM, Julian Lunz <git@jlunz.de> wrote:
> Took your provided config and gave it a try on my machine (32bit-Ubuntu
> 10.04).
> Went through without any hassles :/
> What's your environment?
>
>
>  On Fri, 13 Jul 2012 08:41:37 -0700
> Charles Krinke <charles.krinke@gmail.com> wrote:
>
>> My apologies, Thomas, I did mean buildroot-2012.05 and here is its
>> .config renamed as dotconfig. In the mean time, I am frustrating
>> myself with !#$%* openembedded in an attempt to glean some knowledge
>> about how Qt fits together in an embedded environment as I slide into
>> this new project.
>>
>> Charles
>>
>> On Fri, Jul 13, 2012 at 7:55 AM, Thomas Petazzoni
>> <thomas.petazzoni@free-electrons.com> wrote:
>> > Le Fri, 13 Jul 2012 06:51:34 -0700,
>> > Charles Krinke <charles.krinke@gmail.com> a ?crit :
>> >
>> >> Let me start over with my Qt question.
>> >>
>> >> I downloaded buildroot-2011.05 and ran several tests, each with
>> >> "make
>> >
>> > I presume you wanted to say 2012.05, right?
>> >
>> >> clean && make" and each with C++ support checked, both with powerpc
>> >> and arm and the results are the same, so either my understanding of
>> >> what to click in xconfig is faulty (probable) or there is an issue
>> >> in the Qt package scripts. In both cases, I can compile
>> >> successfully without Qt checked and in both cases, I get into
>> >> problems with Qt checked. I would have expected one of powerpc or
>> >> arm to successfully compile and wonder if a suggestion could be
>> >> made. Creating qmake. Please wait...
>> >> make[1]: Entering directory
>> >> `/home/ckrinke/buildroot-2012.05/output/build/qt-4.8.1/qmake'
>> >> make[1]: c: Command not found
>> >> make[1]: [project.o] Error 127 (ignored)
>> >> make[1]: c: Command not found
>> >> make[1]: [property.o] Error 127 (ignored)
>> >
>> > Please send your Buildroot .config file.
>> >
>> > Thanks!
>> >
>> > Thomas
>> > --
>> > Thomas Petazzoni, Free Electrons
>> > Kernel, drivers, real-time and embedded Linux
>> > development, consulting, training and support.
>> > http://free-electrons.com
>> > _______________________________________________
>> > buildroot mailing list
>> > buildroot at busybox.net
>> > http://lists.busybox.net/mailman/listinfo/buildroot
>>
>>
>>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot



-- 
Charles Krinke

[Buildroot] Qt tribulations take 2

[Thomas Petazzoni]

Le Sat, 14 Jul 2012 15:00:18 -0700,
Charles Krinke <charles.krinke@gmail.com> a ?crit :

> You were right as usual. It was an environment variable. It was
> QMAKESPEC which was set by my installation of the TI SDK a week ago. I
> should have checked my  .bashrc after installing the SDK, but I did
> not expect any environment changes as a result of installing a
> toolchain and u-boot source.

Then we should probably unset this environment variable in the main
Makefile. It seems like a lot of environment variables are causing
various issues in the build. Is there any way to simply unset all
environments variables, except the few we are actually interested in?

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] Qt tribulations take 2

[Arnout Vandecappelle]

On 07/15/12 00:00, Charles Krinke wrote:
> I can compile successfully Qt with the buildroot generated toolchain
> now. However, that gets me to the next step. When I try to go back to
> using TI's external toolchain, I get this error with libtool. I get no
> corresponding libtool error with the buildroot compiled toolchain.
> Would you be willing to comment on what might be going on here?

  When you "go back to using TI's external toolchain", that should include
the following steps:

- set BR2_TOOLCHAIN_EXTERNAL_CUSTOM and set BR2_TOOLCHAIN_EXTERNAL_PATH to
the location of the TI toolchain;

- set the other toolchain options to whatever is provided by the TI toolchain
(probably glibc and C++)

- run make clean

- run make.


  By the way, when you post some error output, it's better if you can also
include the call from buildroot to the package's build system so we can
spot discrepancies there.  And also include the final lines about which
package failed...

  Regards,
  Arnout
-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

[Buildroot] Qt tribulations take 2

[Arnout Vandecappelle]

On 07/15/12 01:05, Thomas Petazzoni wrote:
> Le Sat, 14 Jul 2012 15:00:18 -0700,
> Charles Krinke<charles.krinke@gmail.com>  a ?crit :
>
>> You were right as usual. It was an environment variable. It was
>> QMAKESPEC which was set by my installation of the TI SDK a week ago. I
>> should have checked my  .bashrc after installing the SDK, but I did
>> not expect any environment changes as a result of installing a
>> toolchain and u-boot source.
>
> Then we should probably unset this environment variable in the main
> Makefile. It seems like a lot of environment variables are causing
> various issues in the build. Is there any way to simply unset all
> environments variables, except the few we are actually interested in?

  Not really I'm afraid...

  We could define MAKE as env -i $(MAKE), but there are some environment
variables that are passed to sub-makes that you loose this way.  Maybe
better is to define SHELL as env -i sh, but that could have huge side
effects...


  But maybe we shouldn't exaggerate here.  Putting a QMAKESPEC in your
environment would make any qt build fail, so it's not really a
buildroot problem.  Maybe a better idea is to put in the documentation
that the safe way is to use 'env -i make' to start a build...


  Regards,
  Arnout
-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

[Buildroot] Qt tribulations take 2

[Thomas Petazzoni]

Le Sun, 15 Jul 2012 12:33:09 +0200,
Arnout Vandecappelle <arnout@mind.be> a ?crit :

>   We could define MAKE as env -i $(MAKE), but there are some environment
> variables that are passed to sub-makes that you loose this way.  Maybe
> better is to define SHELL as env -i sh, but that could have huge side
> effects...

Hm, ok.

>   But maybe we shouldn't exaggerate here.  Putting a QMAKESPEC in your
> environment would make any qt build fail, so it's not really a
> buildroot problem.  Maybe a better idea is to put in the documentation
> that the safe way is to use 'env -i make' to start a build...

Well, there are already many other environment variables that may break
the build and that we are either checking in
support/dependencies/dependencies.sh, or unsetting in main Makefile.
Shouldn't we do the same for QMAKESPEC?

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] Qt tribulations take 2

[Stephan Hoffmann]

Am 15.07.2012 12:38, schrieb Thomas Petazzoni:
> Well, there are already many other environment variables that may break
> the build and that we are either checking in
> support/dependencies/dependencies.sh, or unsetting in main Makefile.
> Shouldn't we do the same for QMAKESPEC?
>
After spending several hours in this trap this sounds like a real good
Idea to me.

Kind regards

Stephan

-- 
reLinux     -    Stephan Hoffmann
Am Schmidtgrund 124    50765 K?ln
Tel. +49.221.95595-19    Fax: -64
www.reLinux.de     sho at reLinux.de

[Buildroot] Qt tribulations take 2

[Thomas Petazzoni]

Le Thu, 16 Aug 2012 19:28:49 +0200,
Stephan Hoffmann <sho@relinux.de> a ?crit :

> After spending several hours in this trap this sounds like a real good
> Idea to me.

Then please send a patch adding an unexport QMAKESPEC to the main
Buildroot Makefile, with a short comment on the top that explains why
it is needed. You will find other variables already being unexported,
such as PKG_CONFIG_PATH.

Thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com