<div dir="ltr"><div class="gmail_default" style="font-size:small">Hi Harald,<br><br></div><div class="gmail_default" style="font-size:small">This was a rather old post, ~3 days ago. All these issues have been resolved <br></div><div class="gmail_default" style="font-size:small">in subsequent mails. Thx for your thoughtful and lengthy response.<br></div><div class="gmail_default" style="font-size:small">The configure I was referring to is the libosmocore/configure. Back then, I didn't know that there were 7! <br>Have already a patch for it, waiting for access by Neel.<br></div><div class="gmail_default" style="font-size:small">I'm using a clean libosmocore. Outdated version was due to nginx caching the https request.<br></div><div class="gmail_default" style="font-size:small">Resolved by using the git request.<br></div><div class="gmail_default" style="font-size:small">When I was writing this, I assumed that all ARM toolchains produce correct ARM code. Didn't<br></div><div class="gmail_default" style="font-size:small">know about the extensive code written to support it and produce correct Calypso code:(<br></div><div class="gmail_default" style="font-size:small">At that point I couldn't find the <a href="http://gnuarm.org">gnuarm.org</a> toolchain, and tried to use the Linaro,<br></div><div class="gmail_default" style="font-size:small">until I was told that you maintain your own, and switched to that.<br></div><div class="gmail_default" style="font-size:small">You already support 2 toolchains, no need for more:)<br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">BR<br></div><div class="gmail_default" style="font-size:small">Nikos<br></div><div class="gmail_default" style="font-size:small"><br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 14, 2018 at 10:43 PM, Harald Welte <span dir="ltr"><<a href="mailto:laforge@gnumonks.org" target="_blank">laforge@gnumonks.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Nikos,<br>
<span class=""><br>
On Sat, May 12, 2018 at 04:09:47AM +0300, Nikos Balkanas wrote:<br>
> According to the src/README.building file, I should get the arm toolchain<br>
> from <a href="http://gnuarm.com" rel="noreferrer" target="_blank">gnuarm.com</a><br>
> This should be updated, <a href="http://gnuarm.com" rel="noreferrer" target="_blank">gnuarm.com</a> doesn't have any downloads any more.<br>
> Instead I installed gcc-arm-linux-gnueabi from ubuntu reps<br>
<br>
</span>Won't work, sorry. You need the specific toolchain, see<br>
<br>
<a href="https://osmocom.org/projects/baseband/wiki/GnuArmToolchain" rel="noreferrer" target="_blank">https://osmocom.org/projects/<wbr>baseband/wiki/GnuArmToolchain</a><br>
also note<br>
<a href="https://osmocom.org/issues/1916" rel="noreferrer" target="_blank">https://osmocom.org/issues/<wbr>1916</a><br>
<span class=""><br>
> 1) normal gcc seems to support x-compiling for arm CPUs. Why not use that?<br>
<br>
</span>if it was that simple, we wouldn't have to rely on one specific old toolchain.<br>
<br>
The OsmocomBB code was simply developed 8 years ago, and while lots of<br>
people ar very enthusiastic about using it, not one such user has been<br>
bothering over the coures of 8 years to invest the time to port the code<br>
to more modern toolchains :/<br>
<br>
The biggest knwon problem is about the fact that GNU binutils changed<br>
their features/syntax for the linkerscripts, see<br>
<a href="https://osmocom.org/issues/1917" rel="noreferrer" target="_blank">https://osmocom.org/issues/<wbr>1917</a><br>
<span class=""><br>
> 2) Your stock Makefile tests for CROSS_HOST against arm-elf-gcc. This<br>
> should be updated to test also against arm-linux-gnueabi-gcc from<br>
> gcc-arm-linux-gnueabi package<br>
<br>
</span>No, it should not be updated, as it won't match a toolchain/compiler that will<br>
produce a working binary.<br>
<span class=""><br>
> 3) configure warnings:<br>
> configure: WARNING: unrecognized options: --disable-tests, --disable-tests.<br>
> Should be disabled if not supported any more<br>
> checking for arm-linux-gnueabi-mt... no<br>
> checking for mt... mt<br>
> configure: WARNING: using cross tools not prefixed with host triplet<br>
> Is there a problem to use the OS mt?<br>
<br>
</span>It would be helpful if you could explain which "configure" are you<br>
talking about? There are a total of _7_ configure scripts in the<br>
osmocom-bb source tree.<br>
<span class=""><br>
> 4) configure asks for libosmovty >= 0.10.0. libosmovty is part of<br>
> libosmocore. Latest libosmocore master provides libosmovty 0.9.0.16-abc4:(<br>
<br>
</span>Again, *which* configure? Also, are you talking about a requirement for<br>
libosmcoore on the host or on the target?<br>
<br>
The libosmocore included in the osmocom-bb.git repository is *ONLY FOR<br>
CROSS-COMPILATION TO THE TARGET* as is stated very clearly in<br>
README.building. Also, the master makefile will not do that.<br>
<br>
As written already earlier, libosmocore.git contains a version >= 0.10.0<br>
for more than six months. Please make sure you understand your build<br>
process and ensure you are not using outdated source code to build, or<br>
building against outdated installs of libosmocore that may still be<br>
somewhere installed in your search paths.<br>
<br>
btw: the OpenSUSE package feeds by Martin Hauke contain builds of a suitable<br>
cross-compiler as well as pre-compiled omsocom-bb firmware:<br>
<a href="https://build.opensuse.org/project/show/home:mnhauke:osmocom:nightly" rel="noreferrer" target="_blank">https://build.opensuse.org/<wbr>project/show/home:mnhauke:<wbr>osmocom:nightly</a><br>
<br>
This is not available in the official osmocom Debian builds. We're<br>
always happy to merge related contributions, though.<br>
<br>
Regards,<br>
Harald<br>
<span class="HOEnZb"><font color="#888888">-- <br>
- Harald Welte <<a href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>> <a href="http://laforge.gnumonks.org/" rel="noreferrer" target="_blank">http://laforge.gnumonks.org/</a><br>
==============================<wbr>==============================<wbr>================<br>
"Privacy in residential applications is a desirable marketing option."<br>
(ETSI EN 300 175-7 Ch. A6)<br>
</font></span></blockquote></div><br></div>