From: Alexander Stadler <sa.musl@univie.ac.at>
To: musl@lists.openwall.com
Subject: unknown type name 'loff_t'
Date: Wed, 23 Jan 2013 18:33:42 +0100 [thread overview]
Message-ID: <51001EF6.8040502@univie.ac.at> (raw)
Thanks for your fast responses.
The other error I'm currently running into is
make[4]: Entering directory `/space/build-trunk/trunk/build_dir/target-mips_r2_musl-0.9.8/uboot-envtools-2012.04.01'
mips-openwrt-linux-musl-gcc -Wall -Os -pipe -mips32r2 -mtune=mips32r2 -fno-caller-saves -mno-branch-likely -fhonour-copts -Wno-error=unused-but-set-variable -msoft-float -I/space/build-trunk/trunk/staging_dir/target-mips_r2_musl-0.9.8/usr/include -I/space/build-trunk/trunk/staging_dir/target-mips_r2_musl-0.9.8/include -I/space/build-trunk/trunk/staging_dir/toolchain-mips_r2_gcc-4.6-linaro_musl-0.9.8/usr/include -I/space/build-trunk/trunk/staging_dir/toolchain-mips_r2_gcc-4.6-linaro_musl-0.9.8/include crc32.c fw_env.c fw_env_main.c -o fw_printenv
fw_env.c:643:55: error: unknown type name 'loff_t'
fw_env.c: In function 'flash_read_buf':
fw_env.c:680:2: error: unknown type name 'loff_t'
fw_env.c:713:3: warning: implicit declaration of function 'flash_bad_block' [-Wimplicit-function-declaration]
fw_env.c: In function 'flash_write_buf':
fw_env.c:777:2: error: unknown type name 'loff_t'
make[4]: *** [fw_printenv] Error 1
make[4]: Leaving directory `/space/build-trunk/trunk/build_dir/target-mips_r2_musl-0.9.8/uboot-envtools-2012.04.01'
I've found
linux/include/linux/types.h:
#if defined(__GNUC__)
typedef __kernel_loff_t loff_t;
#endif
and
linux/include/asm-generic/posix_types.h:
typedef long long __kernel_loff_t;
but
arch/arm/include/asm/posix_types.h:
arch/x86/include/asm/posix_types_32.h:
arch/x86/include/asm/posix_types_64.h:
#ifdef __GNUC__
typedef long long __kernel_loff_t;
#endif
So is this something which should be changed at openwrt, upstream, or your library?
My research was limited on that because I'm currently not experienced enough to understand why long long got typedefed. And works in uClibc (does this really go true for #if defined(__GNUC__) in opposite to yours?).
Alex
next reply other threads:[~2013-01-23 17:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 17:33 Alexander Stadler [this message]
2013-01-23 17:37 ` Rich Felker
2013-01-24 18:55 ` Alexander Stadler
2013-01-24 19:47 ` Szabolcs Nagy
2013-01-25 10:10 ` MAP_LOCKED already added to mmap on current git version (was a sidenote on unknown type name 'loff_t' , which is an other "problem") Alexander Stadler
2013-01-24 18:57 ` unknown type name 'loff_t' Alexander Stadler
2013-01-24 19:19 ` Rich Felker
2013-01-24 19:28 ` Alexander Stadler
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=51001EF6.8040502@univie.ac.at \
--to=sa.musl@univie.ac.at \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).