From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] libmusl woes
Date: Tue, 16 Jun 2015 23:05:58 -0700 [thread overview]
Message-ID: <CAA93jw4T=xjkAW225++A5KJrn1gNcV2tePzRysnk8qjwXxx1Tw@mail.gmail.com> (raw)
so I was very happy babel-1.6.1 and dnsmasq-2.73 landed, and wanted to
try the latest cake code, and maybe, finally deploy a couple routers
this week. I'd mostly just been working on debian/ubuntu x86 when I
had time to do anything technical...
...sometime in the past month openwrt switched to libmusl, a new
"cleaner" libc replacing uclibc. I am not sure how (or even if I
should) to switch back to uclibc, but it broke a half dozen+ apps I
used to build regularly: tcsh, libposix for lua, pimd, etherwake,
netperf, strongswan, xinetd, tinc, and I forget what else.
Of these I managed to build netperf, and just went down the list
disabling everything else. I happen to use tinc on the vpn, but I
don't need it right now...
And just as I finally got a new build, jonathon dropped a new version
of cake on me. I mean, not less than 5 seconds, after I got a build to
complete.
Attempting to build (for the first time) the mve stuff (linksys 1900,
1200ac) failed completely with a:
checking for arm-openwrt-linux-muslgnueabi-gcc...
/build/cero3/src/ac1900/build_dir/toolchain-arm_cortex-a9+vfpv3_gcc-4.8-linaro_musl-1.1.10_eabi/gcc-linaro-4.8-2014.04-minimal/./gcc/xgcc
-B/build/cero3/src/ac1900/build_dir/toolchain-arm_cortex-a9+vfpv3_gcc-4.8-linaro_musl-1.1.10_eabi/gcc-linaro-4.8-2014.04-minimal/./gcc/
-B/build/cero3/src/ac1900/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-4.8-linaro_musl-1.1.10_eabi/arm-openwrt-linux-muslgnueabi/bin/
-B/build/cero3/src/ac1900/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-4.8-linaro_musl-1.1.10_eabi/arm-openwrt-linux-muslgnueabi/lib/
-isystem /build/cero3/src/ac1900/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-4.8-linaro_musl-1.1.10_eabi/arm-openwrt-linux-muslgnueabi/include
-isystem /build/cero3/src/ac1900/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-4.8-linaro_musl-1.1.10_eabi/arm-openwrt-linux-muslgnueabi/sys-include
checking for suffix of object files... configure: error: in
`/build/cero3/src/ac1900/build_dir/toolchain-arm_cortex-a9+vfpv3_gcc-4.8-linaro_musl-1.1.10_eabi/gcc-linaro-4.8-2014.04-minimal/arm-openwrt-linux-muslgnueabi/libgcc':
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.
make[4]: *** [configure-target-libgcc] Error 1
make[4]: Leaving directory
`/build/cero3/src/ac1900/build_dir/toolchain-arm_cortex-a9+vfpv3_gcc-4.8-linaro_musl-1.1.10_eabi/gcc-linaro-4.8-2014.04-minimal'
--
Dave Täht
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast
next reply other threads:[~2015-06-17 6:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 6:05 Dave Taht [this message]
2015-06-17 11:47 ` Toke Høiland-Jørgensen
2015-06-17 16:59 ` Dave Taht
2015-06-19 19:13 ` Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw4T=xjkAW225++A5KJrn1gNcV2tePzRysnk8qjwXxx1Tw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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