Re: Toolchain alpha release
John Lee wrote: Yes, I met this one before and I solved it by 1). Okay, that's good enough for me. Just wanted to know where you're heading. BTW, what I need this for are the u-boot and kernel build scripts, trunk/src/target/*/scripts/ This environment setting is dumped and modified from OE Oh, I see. That's why it's so intrusive. For a only cross-build environment type of setting, as in OE, this makes sense. I think if one wants to use toolchain this kind of problems will always happen. Hmm, not sure. The previous (oabi) toolchain served us well for this kind of things for more than a whole year, without acting up. Thanks, - Werner ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Toolchain alpha release
On Sat, Jan 05, 2008 at 10:59:39PM -0300, Werner Almesberger wrote:
I found one little problem with setup-env: when I try to build u-boot
or the kernel with it, ld fails due to the LDFLAGS, which are defined
as follows:
export LDFLAGS=-L${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib
-Wl,-rpath-link,${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -Wl,-O1
Now, both u-boot and kernel invoke ld directly and not through cc
or gcc. Unfortunately, ld doesn't understand the option -Wl, so
it fails.
We couldn't just omit the -Wl, since gcc doesn't understand -rpath-link,
and we wouldn't want to unconditionally compile with -O1 anyway. But in
what scenario do we actually need to set these flags ? As far as I can
tell, just plain use of arm-angstrom-linux-gnueabi-gcc or
arm-angstrom-linux-gnueabi-ld gets all the search paths right.
If we do have to set LDFLAGS, I can think of the following ways to work
around breaking u-boot and kernel builds:
1) don't use setup-env but define only PATH (which is all kernel and
u-boot really need anyway)
2) make LDFLAGS= ...
3) LDFLAGS= make ...
What I don't like about 2) and 3) is that they make an already too long
command even longer, and that this may let more environment variables
slip through and cause subtle breakage. 1) looks much safer.
Would you agree that, if we have to keep LDFLAGS in setup-env, 1) best
reflects proper use of the toolchain in these cases ? If not, how would
you propose to solve this problem ?
Yes, I met this one before and I solved it by 1). This environment
setting is dumped and modified from OE but the way it uses LDFLAGS is
strange. However, if this got fixed, something other then kernel or
uboot might break, so I just leave it as it is.
I think if one wants to use toolchain this kind of problems will
always happen. To fully avoid it we have to use OE. For now the
users of toolchain will just have to customize it to fit their own
usage. I am thinking about dumping the run.* scripts OE generated
along with the source package to solve this but haven't got time to
really look at it.
- John
___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: Toolchain alpha release
John Lee wrote:
http://downloads.openmoko.org/toolchains/openmoko-x86_64-arm-linux-gnueabi-toolchain.tar.bz2
I found one little problem with setup-env: when I try to build u-boot
or the kernel with it, ld fails due to the LDFLAGS, which are defined
as follows:
export LDFLAGS=-L${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib
-Wl,-rpath-link,${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -Wl,-O1
Now, both u-boot and kernel invoke ld directly and not through cc
or gcc. Unfortunately, ld doesn't understand the option -Wl, so
it fails.
We couldn't just omit the -Wl, since gcc doesn't understand -rpath-link,
and we wouldn't want to unconditionally compile with -O1 anyway. But in
what scenario do we actually need to set these flags ? As far as I can
tell, just plain use of arm-angstrom-linux-gnueabi-gcc or
arm-angstrom-linux-gnueabi-ld gets all the search paths right.
If we do have to set LDFLAGS, I can think of the following ways to work
around breaking u-boot and kernel builds:
1) don't use setup-env but define only PATH (which is all kernel and
u-boot really need anyway)
2) make LDFLAGS= ...
3) LDFLAGS= make ...
What I don't like about 2) and 3) is that they make an already too long
command even longer, and that this may let more environment variables
slip through and cause subtle breakage. 1) looks much safer.
Would you agree that, if we have to keep LDFLAGS in setup-env, 1) best
reflects proper use of the toolchain in these cases ? If not, how would
you propose to solve this problem ?
- Werner
___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: Toolchain alpha release
I tried this out. I can build the sample, but then what do I do? The instructions talk about making an ipkg and scp-ing it to my Neo. But I don't have a Neo yet... Can I test an app without the hardware? -Steven On Dec 4, 2007 12:07 PM, John Lee [EMAIL PROTECTED] wrote: Hi, Please check http://downloads.openmoko.org/toolchains/openmoko-x86_64-arm-linux-gnueabi-toolchain.tar.bz2 It's the alpha release of a lean toolchain built on debian lenny, x86_64. The source of openmoko-sample2 is included so you could compile and install it on your neo. The tarball must be extracted to '/' , and please read /usr/local/openmoko/arm/README . As the name suggests, it's really in alpha stage, so please give your feedback/ flame. Thanks! The wiki page http://wiki.openmoko.org/wiki/Toolchain is not updated yet since we got (temporary ?) connection problems here in Taipei. Regards, John ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Toolchain alpha release
Hi, i686 version is released as well. http://downloads.openmoko.org/toolchains/ On Wed, Dec 05, 2007 at 02:07:59AM +0800, John Lee wrote: Hi, Please check http://downloads.openmoko.org/toolchains/openmoko-x86_64-arm-linux-gnueabi-toolchain.tar.bz2 It's the alpha release of a lean toolchain built on debian lenny, x86_64. The source of openmoko-sample2 is included so you could compile and install it on your neo. The tarball must be extracted to '/' , and please read /usr/local/openmoko/arm/README . As the name suggests, it's really in alpha stage, so please give your feedback/ flame. Thanks! The wiki page http://wiki.openmoko.org/wiki/Toolchain is not updated yet since we got (temporary ?) connection problems here in Taipei. Regards, John ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Toolchain alpha release
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 John Lee schreef: Hi, i686 version is released as well. http://downloads.openmoko.org/toolchains/ As I pointed out to Mickey last week, you can't legally distribute that toolchain for a number of reasons: * You use autotools.bbclass almost verbatin, but don't include OE's COPYING.MIT * ipkg-utils is GPL, but there's no trace of that fact in the toolchain, even if you include files from it. Most toolchains I encounter come with a document detailing the include items and their licenses, dunno if that's mandatory, but it certainly would be nice to have. regards, Koen On Wed, Dec 05, 2007 at 02:07:59AM +0800, John Lee wrote: Hi, Please check http://downloads.openmoko.org/toolchains/openmoko-x86_64-arm-linux-gnueabi-toolchain.tar.bz2 It's the alpha release of a lean toolchain built on debian lenny, x86_64. The source of openmoko-sample2 is included so you could compile and install it on your neo. The tarball must be extracted to '/' , and please read /usr/local/openmoko/arm/README . As the name suggests, it's really in alpha stage, so please give your feedback/ flame. Thanks! The wiki page http://wiki.openmoko.org/wiki/Toolchain is not updated yet since we got (temporary ?) connection problems here in Taipei. Regards, John - -- [EMAIL PROTECTED] will go go away in december 2007, please use [EMAIL PROTECTED] instead. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHXP7kMkyGM64RGpERAvhqAJwJuoE2vQAZTSENYjjJBVxOWByAiQCeKEVu JKa/DdaW+pp1nApqQY3c+K0= =HlNn -END PGP SIGNATURE- ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Toolchain alpha release
On Mon, Dec 10, 2007 at 09:55:00AM +0100, Koen Kooi wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 John Lee schreef: Hi, i686 version is released as well. http://downloads.openmoko.org/toolchains/ As I pointed out to Mickey last week, you can't legally distribute that toolchain for a number of reasons: * You use autotools.bbclass almost verbatin, but don't include OE's COPYING.MIT * ipkg-utils is GPL, but there's no trace of that fact in the toolchain, even if you include files from it. Most toolchains I encounter come with a document detailing the include items and their licenses, dunno if that's mandatory, but it certainly would be nice to have. regards, Koen Hi Koen, Thanks for pointing out that. I have updated the tarballs in question and will consult someone appropriate to know if further modificaions are required. Cheers, John ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Toolchain alpha release
Hi, Please check http://downloads.openmoko.org/toolchains/openmoko-x86_64-arm-linux-gnueabi-toolchain.tar.bz2 It's the alpha release of a lean toolchain built on debian lenny, x86_64. The source of openmoko-sample2 is included so you could compile and install it on your neo. The tarball must be extracted to '/' , and please read /usr/local/openmoko/arm/README . As the name suggests, it's really in alpha stage, so please give your feedback/ flame. Thanks! The wiki page http://wiki.openmoko.org/wiki/Toolchain is not updated yet since we got (temporary ?) connection problems here in Taipei. Regards, John ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
