GNU bug report logs -
#17501
ARM cast-align Error
Previous Next
Reported by: Nathan Royce <naroyce <at> hotmail.com>
Date: Thu, 15 May 2014 19:37:01 UTC
Severity: minor
Tags: moreinfo
Done: Paul Eggert <eggert <at> cs.ucla.edu>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 17501 in the body.
You can then email your comments to 17501 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-grep <at> gnu.org
:
bug#17501
; Package
grep
.
(Thu, 15 May 2014 19:37:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Nathan Royce <naroyce <at> hotmail.com>
:
New bug report received and forwarded. Copy sent to
bug-grep <at> gnu.org
.
(Thu, 15 May 2014 19:37:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Similar to: http://lists.gnu.org/archive/html/bug-grep/2010-10/msg00020.html" CC memchr.omemchr.c: In function 'rpl_memchr':memchr.c:84:18: error: cast increases required alignment of target type [-Werror=cast-align] longword_ptr = (const longword *) char_ptr; ^cc1: all warnings being treated as errorsmake[3]: *** [memchr.o] Error 1"commit 3b301a71d94eec362f00905be9d2fa2b044f6f83
It was working with previous commits such as commit a46b95cb3f5a1b6e399a48cc0f554c1df1371b21
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-grep <at> gnu.org
:
bug#17501
; Package
grep
.
(Fri, 16 May 2014 02:20:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 17501 <at> debbugs.gnu.org (full text, mbox):
Nathan Royce wrote:
> Similar to: http://lists.gnu.org/archive/html/bug-grep/2010-10/msg00020.html"
> CC memchr.o
> memchr.c: In function 'rpl_memchr':memchr.c:84:18: error: cast increases required alignment of target type [-Werror=cast-align]
Unless you're on a weird machine (e.g., not byte addressible), I
wouldn't worry about that. I'd worry more about why 'configure' decided
that memchr doesn't work on your machine. What's up with that? What
does config.log say?
I suggest running 'configure' without using the '--enable-gcc-warnings'
option, and/or building without -Werror. --enable-gcc-warnings and/or
-Werror work only on reasonably-recent-and-reliable platforms.
Information forwarded
to
bug-grep <at> gnu.org
:
bug#17501
; Package
grep
.
(Fri, 16 May 2014 02:26:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 17501 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Oh bugger, I should have added that I'm cross-compiling from amd64 to ARM.
I think that is important and probably would help clear things up.
And so for more completeness:
Build machine:
config.log
$ ./configure --prefix=/arm-linux-gnueabihf
--build=x86_64-cross-linux-gnu --host=arm-linux-gnueabihf
--without-included-regex --quiet CFLAGS=-O3 -pipe -mfpu=neon
-mtune=cortex-a9 -march=armv7-a -mfloat-abi=hard CXXFLAGS=-O3 -pipe
-mfpu=neon -mtune=cortex-a9 -march=armv7-a -mfloat-abi=hard
LDFLAGS=-L/arm-linux-gnueabihf/lib -Wl,-rpath -Wl,/arm-linux-gnueabihf/lib
CPPFLAGS=-I/arm-linux-gnueabihf/include
What I ended up doing was just sed-ing configure to wipe out Wcast-align.
On Thu, May 15, 2014 at 9:19 PM, Paul Eggert <eggert <at> cs.ucla.edu> wrote:
> Unless you're on a weird machine (e.g., not byte addressible), I wouldn't
> worry about that. I'd worry more about why 'configure' decided that memchr
> doesn't work on your machine. What's up with that? What does config.log
> say?
>
> I suggest running 'configure' without using the '--enable-gcc-warnings'
> option, and/or building without -Werror. --enable-gcc-warnings and/or
> -Werror work only on reasonably-recent-and-reliable platforms.
>
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-grep <at> gnu.org
:
bug#17501
; Package
grep
.
(Fri, 16 May 2014 02:33:01 GMT)
Full text and
rfc822 format available.
Message #14 received at 17501 <at> debbugs.gnu.org (full text, mbox):
Nathan wrote:
> What I ended up doing was just sed-ing configure to wipe out Wcast-align.
Quite possibly you have another configuration problem lurking in there
somewhere, I'm afraid. 'configure' is supposed to put -Wcast-align into
CFLAGS only if you specify the --enable-gcc-warnings option, and you
didn't do that, so I suggest getting to the bottom of why -Wcast-align
was used. My guess is that you have some global options set somewhere
with --enable-gcc-warnings, and they may be messing up other things.
But it's just a guess.
Information forwarded
to
bug-grep <at> gnu.org
:
bug#17501
; Package
grep
.
(Fri, 16 May 2014 03:00:04 GMT)
Full text and
rfc822 format available.
Message #17 received at 17501 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hmmm, ok starting from scratch with this grep:
>git log
commit 3b301a71d94eec362f00905be9d2fa2b044f6f83
>arm-linux-gnueabihf-gcc -v
Reading specs from
/home/vboxadmin/Desktop/CLFS/cross-tools/bin/../lib/gcc/arm-linux-gnueabihf/4.10.0/specs
COLLECT_GCC=arm-linux-gnueabihf-gcc
COLLECT_LTO_WRAPPER=/home/vboxadmin/Desktop/CLFS/cross-tools/bin/../libexec/gcc/arm-linux-gnueabihf/4.10.0/lto-wrapper
Target: arm-linux-gnueabihf
Configured with: ../gcc/configure --prefix=/cross-tools
--build=x86_64-cross-linux-gnu --host=x86_64-cross-linux-gnu
--target=arm-linux-gnueabihf --with-sysroot=/home/vboxadmin/Desktop/CLFS
--with-local-prefix=/arm-linux-gnueabihf
--with-native-system-header-dir=/arm-linux-gnueabihf/include --disable-nls
--enable-shared --disable-static --enable-languages=c,c++
--enable-__cxa_atexit --enable-c99 --enable-long-long
--enable-threads=posix --disable-multilib --with-mpfr=/cross-tools
--with-gmp=/cross-tools --with-isl=/cross-tools --with-cloog=/cross-tools
--with-mpc=/cross-tools --with-arch=armv7-a --with-float=hard
--with-fpu=neon --disable-isl-version-check --with-system-zlib
--enable-checking=release --enable-libstdcxx-time AR=ar
'CFLAGS_FOR_BUILD=-O3 -pipe -march=corei7 -mtune=corei7 -D__ARM_PCS_VFP'
'CXXFLAGS_FOR_BUILD=-O3 -pipe -march=corei7 -mtune=corei7 -D__ARM_PCS_VFP'
'CFLAGS_FOR_TARGET=-O3 -pipe' 'CXXFLAGS_FOR_TARGET=-O3 -pipe'
LDFLAGS='-L/cross-tools/lib -Wl,-rpath -Wl,/cross-tools/lib'
Thread model: posix
gcc version 4.10.0 20140513 (experimental) (GCC)
>git clean -xdf
>git reset --hard
>./bootstrap --no-git --skip-po //skipping git and po only for this example
>./configure --prefix=/${CLFS_TARGET} --build=${CLFS_HOST}
--host=${CLFS_TARGET} --without-included-regex --quiet
CFLAGS="${targetCFLAGS}" CXXFLAGS="${targetCXXFLAGS}"
LDFLAGS="${targetLDFLAGS}" CPPFLAGS="${targetCPPFLAGS}"
>make 2>&1 | tee make.log
I've attached the configure, config.log, Makefile and make.log
Looking at "configure", I was looking for an if-fi in that area, especially
thinking it would be easier to figure out considering it was indented. Then
I saw gl_manywarn_set led to ws and it was starting to look like it would
just get harder for me to find, rather than the one who surrounds himself
with these types of files.
On Thu, May 15, 2014 at 9:32 PM, Paul Eggert <eggert <at> cs.ucla.edu> wrote:
> Quite possibly you have another configuration problem lurking in there
> somewhere, I'm afraid. 'configure' is supposed to put -Wcast-align into
> CFLAGS only if you specify the --enable-gcc-warnings option, and you didn't
> do that, so I suggest getting to the bottom of why -Wcast-align was used.
> My guess is that you have some global options set somewhere with
> --enable-gcc-warnings, and they may be messing up other things. But it's
> just a guess.
>
[Message part 2 (text/html, inline)]
[grepLogs.tar.xz (application/octet-stream, attachment)]
Information forwarded
to
bug-grep <at> gnu.org
:
bug#17501
; Package
grep
.
(Fri, 16 May 2014 04:37:01 GMT)
Full text and
rfc822 format available.
Message #20 received at 17501 <at> debbugs.gnu.org (full text, mbox):
What can I say? You've got a big hairy cross-build that isn't working
right. For example, it claims memchr doesn't work, when I'm pretty sure
it does. Cross-builds tend to be not well debugged, and if you really
want to do one you're going to have to bird-dog it yourself. For
example, you can set gl_cv_func_memchr_works=yes in your environment
before running 'configure', so that 'configure' doesn't mistakenly think
that memchr is broken.
You should also figure out on your own why 'configure' is deciding to
use -Werror -- normally it doesn't -- and fix that too.
There are probably a dozen other things that need to be fixed.
Added tag(s) moreinfo.
Request was from
Paul Eggert <eggert <at> cs.ucla.edu>
to
control <at> debbugs.gnu.org
.
(Fri, 16 May 2014 04:39:02 GMT)
Full text and
rfc822 format available.
Severity set to 'minor' from 'normal'
Request was from
Paul Eggert <eggert <at> cs.ucla.edu>
to
control <at> debbugs.gnu.org
.
(Fri, 16 May 2014 04:39:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-grep <at> gnu.org
:
bug#17501
; Package
grep
.
(Fri, 16 May 2014 04:44:01 GMT)
Full text and
rfc822 format available.
Message #27 received at 17501 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Too funny. Good input too, especially with that gl_cv_func_memchr_wrks as
I've had to do that with a few other packages and I had forgotten about
that option.
It probably won't be worth debugging since I'm just trying to cross-build
the minimum amount, enough to get it up and then rebuild all of it from the
ARM device itself.
It also probably doesn't help that I'm trying to use the latest (and
greatest?) of every package I come across.
Thanks for that heads-up.
On Thu, May 15, 2014 at 11:36 PM, Paul Eggert <eggert <at> cs.ucla.edu> wrote:
> What can I say? You've got a big hairy cross-build that isn't working
> right. For example, it claims memchr doesn't work, when I'm pretty sure it
> does. Cross-builds tend to be not well debugged, and if you really want to
> do one you're going to have to bird-dog it yourself. For example, you can
> set gl_cv_func_memchr_works=yes in your environment before running
> 'configure', so that 'configure' doesn't mistakenly think that memchr is
> broken.
>
> You should also figure out on your own why 'configure' is deciding to use
> -Werror -- normally it doesn't -- and fix that too.
>
> There are probably a dozen other things that need to be fixed.
>
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-grep <at> gnu.org
:
bug#17501
; Package
grep
.
(Fri, 16 May 2014 17:03:02 GMT)
Full text and
rfc822 format available.
Message #30 received at 17501 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Just putting it out there that appending "-w" to CFLAGS will suppress
werror (warnings) and "make" will finish.
[Message part 2 (text/html, inline)]
Reply sent
to
Paul Eggert <eggert <at> cs.ucla.edu>
:
You have taken responsibility.
(Sat, 17 May 2014 00:39:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Nathan Royce <naroyce <at> hotmail.com>
:
bug acknowledged by developer.
(Sat, 17 May 2014 00:39:03 GMT)
Full text and
rfc822 format available.
Message #35 received at 17501-done <at> debbugs.gnu.org (full text, mbox):
Nathan wrote:
> Just putting it out there that appending "-w" to CFLAGS will suppress
> werror (warnings) and "make" will finish.
Glad you found a workaround; closing the bug report.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sat, 14 Jun 2014 11:24:03 GMT)
Full text and
rfc822 format available.
This bug report was last modified 11 years and 12 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.