Comments (11)
It appears I've temporarily solved this by adding....
#define _GNU_SOURCE
to the top of the file fwup_apply.c
Does this seem like a safe/proper fix in general?
from fwup.
The man pages for pread(2) and open(2) (for O_CLOEXEC) weren't clear on which versions of glibc included them, but it sounds like that's the issue. The man page for open_memstream(2) says that before glibc 2.10, you need _GNU_SOURCE so that definitely sounds like the right fix for your system. There should be some fancy autoconf way of addressing this. If I don't find it, I'll rewrite the code to avoid the issues, since I used pread, O_CLOEXEC, and open_memstream for convenience rather than necessity.
from fwup.
I tried to reproduce on Debian 7.6, but couldn't. What version are you using again? If you update, do the errors go away?
from fwup.
Ha, good question. I’m running 7.4, I’ll update and try again.
On Sep 1, 2014, at 7:32 PM, Frank Hunleth [email protected] wrote:
I tried to reproduce on Debian 7.6, but couldn't. What version are you using again? If you update, do the errors go away?
—
Reply to this email directly or view it on GitHub.
from fwup.
Sorry, under 7.6, I have the same error. Ii’m not sure why.
fwup_apply.c: In function ‘fwup_apply’:
fwup_apply.c:226:56: error: ‘O_CLOEXEC’ undeclared (first use in this function)
fwup_apply.c:226:56: note: each undeclared identifier is reported only once for each function it appears in
make[5]: *** [fwup-fwup_apply.o] Error 1
garth@debian:~/hello_alix$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 7.6 (wheezy)
Release: 7.6
Codename: wheezy
garth@debian:~/hello_alix$ uname -a
Linux debian 3.2.0-4-686-pae #1 SMP Debian 3.2.60-1+deb7u3 i686 GNU/Linux
Just checking if you building the sample alix defconfig, because that one doesnt include fwup on the target, just the host.
On Sep 1, 2014, at 7:32 PM, Frank Hunleth [email protected] wrote:
I tried to reproduce on Debian 7.6, but couldn't. What version are you using again? If you update, do the errors go away?
—
Reply to this email directly or view it on GitHub.
from fwup.
Wierd. I installed the 64 bit version when I tried it out, but it's hard to
believe that's the difference. I definitely tried host fwup. Anyway, could
you send a pull request with _GNU_SOURCE in the place that makes things
work for you? I'll merge it in and propagate the change through nerves so
that you can get working again. I'm pretty sure that adding _GNU_SOURCE
won't break anything. When I have more time later this week, I'll look into
it some more, but there's no reason to hold things up. Thanks for taking
the time to look into the issue as much as you did.
On Tue, Sep 2, 2014 at 11:19 PM, Garth Hitchens [email protected]
wrote:
Sorry, under 7.6, I have the same error. Ii’m not sure why.
fwup_apply.c: In function ‘fwup_apply’:
fwup_apply.c:226:56: error: ‘O_CLOEXEC’ undeclared (first use in this
function)
fwup_apply.c:226:56: note: each undeclared identifier is reported only
once for each function it appears in
make[5]: *** [fwup-fwup_apply.o] Error 1garth@debian:~/hello_alix$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 7.6 (wheezy)
Release: 7.6
Codename: wheezygarth@debian:~/hello_alix$ uname -a
Linux debian 3.2.0-4-686-pae #1 SMP Debian 3.2.60-1+deb7u3 i686 GNU/LinuxJust checking if you building the sample alix defconfig, because that one
doesnt include fwup on the target, just the host.On Sep 1, 2014, at 7:32 PM, Frank Hunleth [email protected]
wrote:I tried to reproduce on Debian 7.6, but couldn't. What version are you
using again? If you update, do the errors go away?—
Reply to this email directly or view it on GitHub.—
Reply to this email directly or view it on GitHub
#1 (comment).
Frank Hunleth
Troodon Software LLC
Embedded Software Development
http://troodon-software.com/
from fwup.
Wierd. I installed the 64 bit version when I tried it out, but it's hard to
believe that's the difference. I definitely tried host fwup. Anyway, could
you send a pull request with _GNU_SOURCE in the place that makes things
work for you? I'll merge it in and propagate the change through nerves so
that you can get working again. I'm pretty sure that adding _GNU_SOURCE
won't break anything. When I have more time later this week, I'll look into
it some more, but there's no reason to hold things up. Thanks for taking
the time to look into the issue as much as you did. I wonder if you misspoke above or if we’re still not clear on the problem. The issue isn’t host fwup, it’s target fwup. I’m building both in my config. I can add a pull request for this, but won’t be able to get to that until tomorrow likely. Thanks for your help in trying to track this down.
Here is my nerves config:
BR2_x86_geode=y
BR2_CCACHE=y
BR2_TOOLCHAIN_BUILDROOT_LARGEFILE=y
BR2_TOOLCHAIN_BUILDROOT_WCHAR=y
BR2_ENABLE_LOCALE_PURGE=y
BR2_ENABLE_LOCALE_WHITELIST="C"
BR2_TARGET_GENERIC_HOSTNAME="cr"
BR2_TARGET_GENERIC_ISSUE="linux"
BR2_TARGET_GENERIC_REMOUNT_ROOTFS_RW is not set
BR2_ROOTFS_OVERLAY="../config/rootfs-additions"
BR2_ROOTFS_POST_BUILD_SCRIPT="../config/post-build.sh"
BR2_ROOTFS_POST_IMAGE_SCRIPT="../config/post-createfs.sh"
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="3.13.5"
BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="../config/linux-3.13.config"
BR2_PACKAGE_BUSYBOX_CONFIG="../config/busybox-1.22.config"
BR2_PACKAGE_OPENSSL=y
BR2_PACKAGE_NCURSES=y
BR2_TARGET_SYSLINUX=y
BR2_TARGET_SYSLINUX_MBR=y
BR2_PACKAGE_HOST_DOSFSTOOLS=y
BR2_PACKAGE_HOST_E2FSPROGS=y
BR2_PACKAGE_HOST_GENEXT2FS=y
BR2_PACKAGE_HOST_MTOOLS=y
BR2_PACKAGE_ERLINIT=y
BR2_PACKAGE_MMCCOPY=y
BR2_PACKAGE_FWUP=y
BR2_PACKAGE_NERVES_MINIMAL=y
BR2_PACKAGE_HOST_ELIXIR=y
BR2_PACKAGE_HOST_ERLANG_RELSYNC=y
BR2_PACKAGE_HOST_FWUP=y
BR2_PACKAGE_HOST_MMCCOPY=y
On Sep 3, 2014, at 6:18 AM, Frank Hunleth [email protected] wrote:
On Tue, Sep 2, 2014 at 11:19 PM, Garth Hitchens [email protected]
wrote:Sorry, under 7.6, I have the same error. Ii’m not sure why.
fwup_apply.c: In function ‘fwup_apply’:
fwup_apply.c:226:56: error: ‘O_CLOEXEC’ undeclared (first use in this
function)
fwup_apply.c:226:56: note: each undeclared identifier is reported only
once for each function it appears in
make[5]: *** [fwup-fwup_apply.o] Error 1garth@debian:~/hello_alix$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 7.6 (wheezy)
Release: 7.6
Codename: wheezygarth@debian:~/hello_alix$ uname -a
Linux debian 3.2.0-4-686-pae #1 SMP Debian 3.2.60-1+deb7u3 i686 GNU/LinuxJust checking if you building the sample alix defconfig, because that one
doesnt include fwup on the target, just the host.On Sep 1, 2014, at 7:32 PM, Frank Hunleth [email protected]
wrote:I tried to reproduce on Debian 7.6, but couldn't. What version are you
using again? If you update, do the errors go away?—
Reply to this email directly or view it on GitHub.—
Reply to this email directly or view it on GitHub
#1 (comment).Frank Hunleth
Troodon Software LLC
Embedded Software Development
http://troodon-software.com/
—
Reply to this email directly or view it on GitHub.
from fwup.
Ohhh. I completely misunderstood and thought you were having a problem with
host-fwup, not target-fwup. That makes so much more sense since it's highly
likely that uclibc is behind glibc. I still want to fix the problem, but
since you're using your own firmware update, you don't even need
target-fwup at all! Just turn it off in your nerves configuration. I'm
confident that I can reproduce the issue now.
On Wed, Sep 3, 2014 at 9:23 AM, Garth Hitchens [email protected]
wrote:
Wierd. I installed the 64 bit version when I tried it out, but it's hard
to
believe that's the difference. I definitely tried host fwup. Anyway,
could
you send a pull request with _GNU_SOURCE in the place that makes things
work for you? I'll merge it in and propagate the change through nerves
so
that you can get working again. I'm pretty sure that adding _GNU_SOURCE
won't break anything. When I have more time later this week, I'll look
into
it some more, but there's no reason to hold things up. Thanks for takingthe time to look into the issue as much as you did. I wonder if you
misspoke above or if we’re still not clear on the problem. The issue isn’t
host fwup, it’s target fwup. I’m building both in my config. I can add a
pull request for this, but won’t be able to get to that until tomorrow
likely. Thanks for your help in trying to track this down.Here is my nerves config:
BR2_x86_geode=y
BR2_CCACHE=y
BR2_TOOLCHAIN_BUILDROOT_LARGEFILE=y
BR2_TOOLCHAIN_BUILDROOT_WCHAR=y
BR2_ENABLE_LOCALE_PURGE=y
BR2_ENABLE_LOCALE_WHITELIST="C"
BR2_TARGET_GENERIC_HOSTNAME="cr"
BR2_TARGET_GENERIC_ISSUE="linux"BR2_TARGET_GENERIC_REMOUNT_ROOTFS_RW is not set
BR2_ROOTFS_OVERLAY="../config/rootfs-additions"
BR2_ROOTFS_POST_BUILD_SCRIPT="../config/post-build.sh"
BR2_ROOTFS_POST_IMAGE_SCRIPT="../config/post-createfs.sh"
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="3.13.5"
BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="../config/linux-3.13.config"
BR2_PACKAGE_BUSYBOX_CONFIG="../config/busybox-1.22.config"
BR2_PACKAGE_OPENSSL=y
BR2_PACKAGE_NCURSES=y
BR2_TARGET_SYSLINUX=y
BR2_TARGET_SYSLINUX_MBR=y
BR2_PACKAGE_HOST_DOSFSTOOLS=y
BR2_PACKAGE_HOST_E2FSPROGS=y
BR2_PACKAGE_HOST_GENEXT2FS=y
BR2_PACKAGE_HOST_MTOOLS=y
BR2_PACKAGE_ERLINIT=y
BR2_PACKAGE_MMCCOPY=y
BR2_PACKAGE_FWUP=y
BR2_PACKAGE_NERVES_MINIMAL=y
BR2_PACKAGE_HOST_ELIXIR=y
BR2_PACKAGE_HOST_ERLANG_RELSYNC=y
BR2_PACKAGE_HOST_FWUP=y
BR2_PACKAGE_HOST_MMCCOPY=yOn Sep 3, 2014, at 6:18 AM, Frank Hunleth [email protected]
wrote:On Tue, Sep 2, 2014 at 11:19 PM, Garth Hitchens <
[email protected]>
wrote:Sorry, under 7.6, I have the same error. Ii’m not sure why.
fwup_apply.c: In function ‘fwup_apply’:
fwup_apply.c:226:56: error: ‘O_CLOEXEC’ undeclared (first use in this
function)
fwup_apply.c:226:56: note: each undeclared identifier is reported only
once for each function it appears in
make[5]: *** [fwup-fwup_apply.o] Error 1garth@debian:~/hello_alix$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 7.6 (wheezy)
Release: 7.6
Codename: wheezygarth@debian:~/hello_alix$ uname -a
Linux debian 3.2.0-4-686-pae #1 SMP Debian 3.2.60-1+deb7u3 i686
GNU/LinuxJust checking if you building the sample alix defconfig, because that
one
doesnt include fwup on the target, just the host.On Sep 1, 2014, at 7:32 PM, Frank Hunleth [email protected]
wrote:I tried to reproduce on Debian 7.6, but couldn't. What version are
you
using again? If you update, do the errors go away?—
Reply to this email directly or view it on GitHub.—
Reply to this email directly or view it on GitHub
#1 (comment).Frank Hunleth
Troodon Software LLC
Embedded Software Development
http://troodon-software.com/
—
Reply to this email directly or view it on GitHub.—
Reply to this email directly or view it on GitHub
#1 (comment).
Frank Hunleth
Troodon Software LLC
Embedded Software Development
http://troodon-software.com/
from fwup.
I have been building with it turned off. You’re right that I’m doing my own firmware update (in elixir), but was trying to rewrite my firmware updater to use fwup and its config to be more “nerves standard”, which prompted this whole thing. I’ve postponed that work for other reasons than this (worth another discussion some other time). Sorry for the misunderstanding!
Let me know if you still want a pull request (although at this point I’m going to delay the fwup-ification of my firmware updater for a while anyway due to issues about methods of validation of firmware and fallback configs).
On Sep 3, 2014, at 6:35 AM, Frank Hunleth [email protected] wrote:
Ohhh. I completely misunderstood and thought you were having a problem with
host-fwup, not target-fwup. That makes so much more sense since it's highly
likely that uclibc is behind glibc. I still want to fix the problem, but
since you're using your own firmware update, you don't even need
target-fwup at all! Just turn it off in your nerves configuration. I'm
confident that I can reproduce the issue now.On Wed, Sep 3, 2014 at 9:23 AM, Garth Hitchens [email protected]
wrote:Wierd. I installed the 64 bit version when I tried it out, but it's hard
to
believe that's the difference. I definitely tried host fwup. Anyway,
could
you send a pull request with _GNU_SOURCE in the place that makes things
work for you? I'll merge it in and propagate the change through nerves
so
that you can get working again. I'm pretty sure that adding _GNU_SOURCE
won't break anything. When I have more time later this week, I'll look
into
it some more, but there's no reason to hold things up. Thanks for takingthe time to look into the issue as much as you did. I wonder if you
misspoke above or if we’re still not clear on the problem. The issue isn’t
host fwup, it’s target fwup. I’m building both in my config. I can add a
pull request for this, but won’t be able to get to that until tomorrow
likely. Thanks for your help in trying to track this down.Here is my nerves config:
BR2_x86_geode=y
BR2_CCACHE=y
BR2_TOOLCHAIN_BUILDROOT_LARGEFILE=y
BR2_TOOLCHAIN_BUILDROOT_WCHAR=y
BR2_ENABLE_LOCALE_PURGE=y
BR2_ENABLE_LOCALE_WHITELIST="C"
BR2_TARGET_GENERIC_HOSTNAME="cr"
BR2_TARGET_GENERIC_ISSUE="linux"BR2_TARGET_GENERIC_REMOUNT_ROOTFS_RW is not set
BR2_ROOTFS_OVERLAY="../config/rootfs-additions"
BR2_ROOTFS_POST_BUILD_SCRIPT="../config/post-build.sh"
BR2_ROOTFS_POST_IMAGE_SCRIPT="../config/post-createfs.sh"
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="3.13.5"
BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="../config/linux-3.13.config"
BR2_PACKAGE_BUSYBOX_CONFIG="../config/busybox-1.22.config"
BR2_PACKAGE_OPENSSL=y
BR2_PACKAGE_NCURSES=y
BR2_TARGET_SYSLINUX=y
BR2_TARGET_SYSLINUX_MBR=y
BR2_PACKAGE_HOST_DOSFSTOOLS=y
BR2_PACKAGE_HOST_E2FSPROGS=y
BR2_PACKAGE_HOST_GENEXT2FS=y
BR2_PACKAGE_HOST_MTOOLS=y
BR2_PACKAGE_ERLINIT=y
BR2_PACKAGE_MMCCOPY=y
BR2_PACKAGE_FWUP=y
BR2_PACKAGE_NERVES_MINIMAL=y
BR2_PACKAGE_HOST_ELIXIR=y
BR2_PACKAGE_HOST_ERLANG_RELSYNC=y
BR2_PACKAGE_HOST_FWUP=y
BR2_PACKAGE_HOST_MMCCOPY=yOn Sep 3, 2014, at 6:18 AM, Frank Hunleth [email protected]
wrote:On Tue, Sep 2, 2014 at 11:19 PM, Garth Hitchens <
[email protected]>
wrote:Sorry, under 7.6, I have the same error. Ii’m not sure why.
fwup_apply.c: In function ‘fwup_apply’:
fwup_apply.c:226:56: error: ‘O_CLOEXEC’ undeclared (first use in this
function)
fwup_apply.c:226:56: note: each undeclared identifier is reported only
once for each function it appears in
make[5]: *** [fwup-fwup_apply.o] Error 1garth@debian:~/hello_alix$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 7.6 (wheezy)
Release: 7.6
Codename: wheezygarth@debian:~/hello_alix$ uname -a
Linux debian 3.2.0-4-686-pae #1 SMP Debian 3.2.60-1+deb7u3 i686
GNU/LinuxJust checking if you building the sample alix defconfig, because that
one
doesnt include fwup on the target, just the host.On Sep 1, 2014, at 7:32 PM, Frank Hunleth [email protected]
wrote:I tried to reproduce on Debian 7.6, but couldn't. What version are
you
using again? If you update, do the errors go away?—
Reply to this email directly or view it on GitHub.—
Reply to this email directly or view it on GitHub
#1 (comment).Frank Hunleth
Troodon Software LLC
Embedded Software Development
http://troodon-software.com/
—
Reply to this email directly or view it on GitHub.—
Reply to this email directly or view it on GitHub
#1 (comment).Frank Hunleth
Troodon Software LLC
Embedded Software Development
http://troodon-software.com/
—
Reply to this email directly or view it on GitHub.
from fwup.
No need to send a pull request. I totally understand the issue now and just
had completely misunderstood what you were trying to do.
If you have feature requests for fwup that you want in there, feel free to
add them. At some point, I'll get to digital signature checks. I think that
I have hooks in both erlinit and fwup to do fallback, but I doubt that it's
obvious and I could easily have something missing since I haven't needed to
implement it in the systems that I'm building.
On Wed, Sep 3, 2014 at 9:41 AM, Garth Hitchens [email protected]
wrote:
I have been building with it turned off. You’re right that I’m doing my
own firmware update (in elixir), but was trying to rewrite my firmware
updater to use fwup and its config to be more “nerves standard”, which
prompted this whole thing. I’ve postponed that work for other reasons than
this (worth another discussion some other time). Sorry for the
misunderstanding!Let me know if you still want a pull request (although at this point I’m
going to delay the fwup-ification of my firmware updater for a while anyway
due to issues about methods of validation of firmware and fallback
configs).On Sep 3, 2014, at 6:35 AM, Frank Hunleth [email protected]
wrote:Ohhh. I completely misunderstood and thought you were having a problem
with
host-fwup, not target-fwup. That makes so much more sense since it's
highly
likely that uclibc is behind glibc. I still want to fix the problem, but
since you're using your own firmware update, you don't even need
target-fwup at all! Just turn it off in your nerves configuration. I'm
confident that I can reproduce the issue now.On Wed, Sep 3, 2014 at 9:23 AM, Garth Hitchens [email protected]
wrote:
Wierd. I installed the 64 bit version when I tried it out, but it's
hard
to
believe that's the difference. I definitely tried host fwup. Anyway,
could
you send a pull request with _GNU_SOURCE in the place that makes
things
work for you? I'll merge it in and propagate the change through
nerves
so
that you can get working again. I'm pretty sure that adding
_GNU_SOURCE
won't break anything. When I have more time later this week, I'll
look
into
it some more, but there's no reason to hold things up. Thanks for
takingthe time to look into the issue as much as you did. I wonder if you
misspoke above or if we’re still not clear on the problem. The issue
isn’t
host fwup, it’s target fwup. I’m building both in my config. I can add
a
pull request for this, but won’t be able to get to that until tomorrow
likely. Thanks for your help in trying to track this down.Here is my nerves config:
BR2_x86_geode=y
BR2_CCACHE=y
BR2_TOOLCHAIN_BUILDROOT_LARGEFILE=y
BR2_TOOLCHAIN_BUILDROOT_WCHAR=y
BR2_ENABLE_LOCALE_PURGE=y
BR2_ENABLE_LOCALE_WHITELIST="C"
BR2_TARGET_GENERIC_HOSTNAME="cr"
BR2_TARGET_GENERIC_ISSUE="linux"BR2_TARGET_GENERIC_REMOUNT_ROOTFS_RW is not set
BR2_ROOTFS_OVERLAY="../config/rootfs-additions"
BR2_ROOTFS_POST_BUILD_SCRIPT="../config/post-build.sh"
BR2_ROOTFS_POST_IMAGE_SCRIPT="../config/post-createfs.sh"
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="3.13.5"
BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="../config/linux-3.13.config"
BR2_PACKAGE_BUSYBOX_CONFIG="../config/busybox-1.22.config"
BR2_PACKAGE_OPENSSL=y
BR2_PACKAGE_NCURSES=y
BR2_TARGET_SYSLINUX=y
BR2_TARGET_SYSLINUX_MBR=y
BR2_PACKAGE_HOST_DOSFSTOOLS=y
BR2_PACKAGE_HOST_E2FSPROGS=y
BR2_PACKAGE_HOST_GENEXT2FS=y
BR2_PACKAGE_HOST_MTOOLS=y
BR2_PACKAGE_ERLINIT=y
BR2_PACKAGE_MMCCOPY=y
BR2_PACKAGE_FWUP=y
BR2_PACKAGE_NERVES_MINIMAL=y
BR2_PACKAGE_HOST_ELIXIR=y
BR2_PACKAGE_HOST_ERLANG_RELSYNC=y
BR2_PACKAGE_HOST_FWUP=y
BR2_PACKAGE_HOST_MMCCOPY=yOn Sep 3, 2014, at 6:18 AM, Frank Hunleth [email protected]
wrote:On Tue, Sep 2, 2014 at 11:19 PM, Garth Hitchens <
[email protected]>
wrote:Sorry, under 7.6, I have the same error. Ii’m not sure why.
fwup_apply.c: In function ‘fwup_apply’:
fwup_apply.c:226:56: error: ‘O_CLOEXEC’ undeclared (first use in
this
function)
fwup_apply.c:226:56: note: each undeclared identifier is reported
only
once for each function it appears in
make[5]: *** [fwup-fwup_apply.o] Error 1garth@debian:~/hello_alix$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 7.6 (wheezy)
Release: 7.6
Codename: wheezygarth@debian:~/hello_alix$ uname -a
Linux debian 3.2.0-4-686-pae #1 SMP Debian 3.2.60-1+deb7u3 i686
GNU/LinuxJust checking if you building the sample alix defconfig, because
that
one
doesnt include fwup on the target, just the host.On Sep 1, 2014, at 7:32 PM, Frank Hunleth <
[email protected]>
wrote:I tried to reproduce on Debian 7.6, but couldn't. What version
are
you
using again? If you update, do the errors go away?—
Reply to this email directly or view it on GitHub.—
Reply to this email directly or view it on GitHub
#1 (comment).Frank Hunleth
Troodon Software LLC
Embedded Software Development
http://troodon-software.com/
—
Reply to this email directly or view it on GitHub.—
Reply to this email directly or view it on GitHub
#1 (comment).Frank Hunleth
Troodon Software LLC
Embedded Software Development
http://troodon-software.com/
—
Reply to this email directly or view it on GitHub.—
Reply to this email directly or view it on GitHub
#1 (comment).
Frank Hunleth
Troodon Software LLC
Embedded Software Development
http://troodon-software.com/
from fwup.
I just committed a simple fix to the issue. It only appeared to be broken under uclibc. After the fix, testing with uclibc, MUSL, and glibc works for me.
from fwup.
Related Issues (20)
- fsck.fat v4.2 failure HOT 4
- question: sometimes, for ext4 partition, no sparse compression is done HOT 4
- Failed to start File System Check on Root Device HOT 6
- fwup:amd64 : Depends: libc6:amd64 (>= 2.4) but it is not installable HOT 8
- Add `.deb` for `aarch64` to the releases
- zlib-1.2.11 is no longer available from zlib.net HOT 3
- Add lock file support
- Support usb drive or card reader HOT 4
- Compiling with glibc 2.36 fails due to conflicting headers HOT 1
- xdelta tries to read too much data HOT 5
- Handle /dev/null as a special case output device HOT 4
- Support delta-source-fat-offset and delta-source-fat-path HOT 4
- Arm build is missing from releases. HOT 1
- u-boot redundant environment support issue HOT 5
- UMS is not detected by fwup on Windows 11 HOT 5
- fwupd defeated by secure boot kernel lockdown? HOT 1
- Test failure installing 1.10.1 HOT 3
- Suggestion: Ignore tiny discovered drives/devices HOT 4
- Signing firmware files post-delta creation fails
- Red Hat support HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from fwup.