From: Juergen Beisert <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: oselas@community.pengutronix.de, muntaqa <muntaqa@juno.com>
Subject: Re: [ptxdist] Using external toolchain with penguitronix BSP distribution
Date: Sat, 5 Nov 2011 15:54:43 +0100 [thread overview]
Message-ID: <201111051554.43244.jbe@pengutronix.de> (raw)
In-Reply-To: <loom.20111105T141110-613@post.gmane.org>
muntaqa wrote:
> Juergen Beisert <jbe@...> writes:
> > Out of curiosity: what advantage has your toolchain compared to our
> > OSELAS ARMv4 toolchain?
>
> This is CodeSourcery open source toolchain. I had chosen it a while ago
> when building the project with buildroot. I have been using it for a while
> and have built and debugged all of my applications with it on mini2440. At
> this point, I did not want to discover or spend time on any other problems
> since I have a working system except that I am trying to add QT
> applications to my mini2440 platform.
Okay.
> Reason I switched to Pengutronix is that buildroot gave me some trouble
> when building QT thru it plus it had always given me kernel panic errors
> when installing the jffs2 root image (so I had been simply using tar balls
> on top of the stock kernel/rootfs that mini2440 is shipped with). I
> thought switching to Pengutronix would finally let me burn a true image and
> I can organize my project much better.
>
> Currently, I still have kernel panic messages when building the rootfs
> using Pengutronix and CodeSourcery. It seems perhaps that it is because of
> gcc 4.5.1 that is being used in my version of CodeSourcery. When I use
> your toolchain, I can burn an image properly and do not receive kernel panic
> messages. Your toolchain uses gcc 4.5.2.
Do all supported kernels show the same panic? Sometimes one kernel has trouble
with a specific gcc version, and other kernels not. Did you try all kernels
from the BSP with your CodeSourcery toolchain?
> One issue that I see though with Pengutronix is that any time I change a
> selection or add anything to QT configuration in Penguitronix ptxdist
> menuconfig, it rebuilds the whole QT (ends up costing me couple of hours
> plus I am not able to try anything quickly.)
On our new 24 core/96 GiB RAM machine Qt4 builds really quick in a few
minutes. ;-)
Maybe you should start with a full blown Qt4, do your development with it, and
when it is finished, you can try to shrink the library by disabling some of
its options.
> I would like to start using pengutronix as long as it would be less
> frustrating than buildroot.
I don't know buildroot. I work with PTXdist since years.
> BTW, my best wishes to you on this project, you guys have done alot of
> good work and looking at your documentation the working environment, it
> seems very promising.
Thanks.
Regards,
Juergen
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2011-11-05 14:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-30 23:57 muntaqa
2011-11-01 10:13 ` Michael Olbrich
2011-11-02 1:39 ` muntaqa
2011-11-02 8:35 ` Juergen Beisert
2011-11-05 13:31 ` muntaqa
2011-11-05 14:54 ` Juergen Beisert [this message]
2011-11-15 14:32 ` muntaqa
2011-11-15 14:57 ` Juergen Beisert
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=201111051554.43244.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=muntaqa@juno.com \
--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