[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/17169] New: argument list too long error

From: parkch98 at gmail dot com
Subject: [Bug binutils/17169] New: argument list too long error
Date: Thu, 17 Jul 2014 07:02:11 +0000


            Bug ID: 17169
           Summary: argument list too long error
           Product: binutils
           Version: 2.24
            Status: NEW
          Severity: normal
          Priority: P2
         Component: binutils
          Assignee: unassigned at sourceware dot org
          Reporter: parkch98 at gmail dot com

When I tried to build binutils 2.24 using our build system.
Actually, it occurred only arm(armv7l) build system.
Like openSUSE, we use obs build system for arm build.
It's compiled in the qemu environment.

We found below error during generating a many_sections_define.h.
It obviously occurred since 2.23.2.

[  942s] make[3]: Entering directory
[  942s] make[3]: Nothing to be done for `info-am'.
[  942s] make[3]: Leaving directory
[  942s] gcc -DHAVE_CONFIG_H -I. -I../../gprof  -DDEBUG -I../bfd
-I../../gprof/../include -I../../gprof/../bfd  -I.
-DLOCALEDIR="\"/usr/share/locale\""  -W -Wall -Wstrict-prototypes
-Wmissing-prototypes -Wshadow -Werror -O2 -g2 -feliminate-unused-debug-types
-pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=32 -Wformat -Wformat-security -fmessage-length=0
-march=armv7-a -mtune=cortex-a8 -mlittle-endian -mfpu=neon -mfloat-abi=softfp
-D__SOFTFP__ -g -Wno-error -MT symtab.o -MD -MP -MF .deps/symtab.Tpo -c -o
symtab.o ../../gprof/symtab.c
[  943s] make[4]: Entering directory
[  943s] (for i in `seq 1 70000`; do \
[  943s]    echo "int var_$i __attribute__((section(\"section_$i\"))) = $i;"; \
[  943s]  done) > many_sections_define.h.tmp
[  943s] make[4]: execvp: /bin/sh: Argument list too long
[  943s] make[4]: *** [many_sections_define.h] Error 127
[  943s] make[4]: Leaving directory
[  943s] make[4]: Entering directory

You are receiving this mail because:
You are on the CC list for the bug.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]