Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 398420 Details for
Bug 542606
dev-lang/pcc-1.1.0 - ./cc.c:212:47: error: expected '}' before 'MULTIARCH_PATH'
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
build.log
build.log (text/x-log), 7.44 KB, created by
Bertrand Jacquin
on 2015-03-08 23:38:30 UTC
(
hide
)
Description:
build.log
Filename:
MIME Type:
Creator:
Bertrand Jacquin
Created:
2015-03-08 23:38:30 UTC
Size:
7.44 KB
patch
obsolete
>[32;01m * [39;49;00mPackage: dev-lang/pcc-1.1.0 >[32;01m * [39;49;00mRepository: gentoo >[32;01m * [39;49;00mMaintainer: patrick@gentoo.org >[32;01m * [39;49;00mUSE: abi_x86_32 elibc_glibc kernel_linux userland_GNU x86 >[32;01m * [39;49;00mFEATURES: preserve-libs sandbox userpriv usersandbox >>>> Unpacking source... >>>> Unpacking pcc-1.1.0.tgz to /var/tmp/portage/dev-lang/pcc-1.1.0/work >>>> Source unpacked in /var/tmp/portage/dev-lang/pcc-1.1.0/work >>>> Preparing source in /var/tmp/portage/dev-lang/pcc-1.1.0/work/pcc-1.1.0 ... > [32;01m*[0m Running eautoreconf in '/var/tmp/portage/dev-lang/pcc-1.1.0/work/pcc-1.1.0' ... > [32;01m*[0m Running aclocal ... >[A[72C [34;01m[ [32;01mok[34;01m ][0m > [32;01m*[0m Running autoconf --force ... >[A[72C [34;01m[ [32;01mok[34;01m ][0m > [32;01m*[0m Running autoheader ... >[A[72C [34;01m[ [32;01mok[34;01m ][0m > [32;01m*[0m Running elibtoolize in: pcc-1.1.0/ >>>> Source prepared. >>>> Configuring source in /var/tmp/portage/dev-lang/pcc-1.1.0/work/pcc-1.1.0 ... > * econf: updating pcc-1.1.0/config.sub with /usr/share/gnuconfig/config.sub > * econf: updating pcc-1.1.0/config.guess with /usr/share/gnuconfig/config.guess >./configure --prefix=/usr --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib --disable-stripping >configure: loading site script /usr/share/config.site >checking build system type... i686-pc-linux-gnu >checking host system type... i686-pc-linux-gnu >checking target system type... i686-pc-linux-gnu >checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc >checking whether the C compiler works... yes >checking for C compiler default output file name... a.out >checking for suffix of executables... >checking whether we are cross compiling... no >checking for suffix of object files... o >checking whether we are using the GNU C compiler... yes >checking whether i686-pc-linux-gnu-gcc accepts -g... yes >checking for i686-pc-linux-gnu-gcc option to accept ISO C89... none needed >checking whether i686-pc-linux-gnu-gcc accepts -Wall... yes >checking whether i686-pc-linux-gnu-gcc accepts -Wmissing-prototypes... yes >checking whether i686-pc-linux-gnu-gcc accepts -Wstrict-prototypes... no >checking whether i686-pc-linux-gnu-gcc accepts -Wshadow... yes >checking whether i686-pc-linux-gnu-gcc accepts -Wsign-compare... yes >checking whether i686-pc-linux-gnu-gcc accepts -Wtruncate... no >checking for a C compiler for mkext... not cross compiling >checking how to run the C preprocessor... i686-pc-linux-gnu-gcc -E >checking for grep that handles long lines and -e... /bin/grep >checking for egrep... /bin/grep -E >checking for ANSI C header files... yes >checking for sys/types.h... yes >checking for sys/stat.h... yes >checking for stdlib.h... yes >checking for string.h... yes >checking for memory.h... yes >checking for strings.h... yes >checking for inttypes.h... yes >checking for stdint.h... yes >checking for unistd.h... yes >checking for C99 printf size specifiers... yes >checking whether byte ordering is bigendian... no >checking whether make sets $(MAKE)... yes >checking for a BSD-compatible install... /usr/lib/portage/python3.3/ebuild-helpers/xattr/install -c >checking for bison... bison -y >checking for flex... flex >checking lex output file root... lex.yy >checking lex library... -lfl >checking whether yytext is a pointer... yes >checking for string.h... (cached) yes >checking malloc.h usability... yes >checking malloc.h presence... yes >checking for malloc.h... yes >checking libgen.h usability... yes >checking libgen.h presence... yes >checking for libgen.h... yes >checking for sys/wait.h that is POSIX.1 compatible... yes >checking for strtold... yes >checking for vsnprintf... yes >checking for snprintf... yes >checking for mkstemp... yes >checking for strlcat... no >checking for strlcpy... no >checking for basename... yes >checking for getopt... yes >checking for ffs... yes >checking for vfork... yes >configure: creating ./config.status >config.status: creating Makefile >config.status: creating cc/Makefile >config.status: creating cc/cc/Makefile >config.status: creating cc/cpp/Makefile >config.status: creating cc/ccom/Makefile >config.status: creating cc/cxxcom/Makefile >config.status: creating cc/driver/Makefile >config.status: creating f77/Makefile >config.status: creating f77/f77/Makefile >config.status: creating f77/fcom/Makefile >config.status: creating config.h > >Target CPU is .................... i386 >Target ABI is .................... elf >Target OS is ..................... linux >Compiler is called ............... pcc >Installing compiler into ......... /usr/bin >Installing pre-processor into .... /usr/libexec >Using assembler .................. <default> >Using linker ..................... <default> >Using Multi-Arch path ............ (no) >Using include path ............... <default> >Using library path ............... <default> >Has TLS support .................. no >Has GCC compatibility ............ yes >Has PCC debugging ................ yes >Type of wchar_t is ............... INT (4 chars) > >Configure finished. Do 'make && make install' to compile and install. > >>>> Source configured. >>>> Compiling source in /var/tmp/portage/dev-lang/pcc-1.1.0/work/pcc-1.1.0 ... >make -j1 >===> cc >make[1]: Entering directory '/var/tmp/portage/dev-lang/pcc-1.1.0/work/pcc-1.1.0/cc' >===> cc/cc >make[2]: Entering directory '/var/tmp/portage/dev-lang/pcc-1.1.0/work/pcc-1.1.0/cc/cc' >i686-pc-linux-gnu-gcc -march=native -O2 -pipe -fomit-frame-pointer -Wall -Wmissing-prototypes -Wshadow -Wsign-compare -DLIBEXECDIR=\"/usr/libexec/\" -DGCC_COMPAT -DPCC_DEBUG -DINCLUDEDIR=\"/usr/include/\" -DPCCINCDIR=\"/usr/lib/pcc/i686-pc-linux-gnu/1.1.0/include/\" -DPCCLIBDIR=\"/usr/lib/pcc/i686-pc-linux-gnu/1.1.0/lib/\" -Dos_linux -Dmach_i386 -DTARGOSVER=0 -DCPPROGNAME=\"pcpp\" -I../../cc/driver -I../.. -I../../os/linux -I../../mip -I../../arch/i386 -c -o cc.o ./cc.c >[01m[K./cc.c:212:47:[m[K [01;31m[Kerror: [m[Kexpected '[01m[K}[m[K' before '[01m[KMULTIARCH_PATH[m[K' > #define DEFLIBDIRS { "/usr/lib/", "/usr/lib/" MULTIARCH_PATH "/", 0 } >[01;32m[K ^[m[K >[01m[K./cc.c:230:22:[m[K [01;36m[Knote: [m[Kin expansion of macro '[01m[KDEFLIBDIRS[m[K' > char *deflibdirs[] = DEFLIBDIRS; >[01;32m[K ^[m[K >Makefile:50: recipe for target 'cc.o' failed >make[2]: *** [cc.o] Error 1 >make[2]: Leaving directory '/var/tmp/portage/dev-lang/pcc-1.1.0/work/pcc-1.1.0/cc/cc' >Makefile:12: recipe for target 'all' failed >make[1]: *** [all] Error 2 >make[1]: Leaving directory '/var/tmp/portage/dev-lang/pcc-1.1.0/work/pcc-1.1.0/cc' >Makefile:12: recipe for target 'all' failed >make: *** [all] Error 2 > [31;01m*[0m ERROR: dev-lang/pcc-1.1.0::gentoo failed (compile phase): > [31;01m*[0m emake failed > [31;01m*[0m > [31;01m*[0m If you need support, post the output of `emerge --info '=dev-lang/pcc-1.1.0::gentoo'`, > [31;01m*[0m the complete build log and the output of `emerge -pqv '=dev-lang/pcc-1.1.0::gentoo'`. > [31;01m*[0m The complete build log is located at '/var/log/portage/dev-lang:pcc-1.1.0:20150308-233247.log'. > [31;01m*[0m For convenience, a symlink to the build log is located at '/var/tmp/portage/dev-lang/pcc-1.1.0/temp/build.log'. > [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/dev-lang/pcc-1.1.0/temp/environment'. > [31;01m*[0m Working directory: '/var/tmp/portage/dev-lang/pcc-1.1.0/work/pcc-1.1.0' > [31;01m*[0m S: '/var/tmp/portage/dev-lang/pcc-1.1.0/work/pcc-1.1.0/'
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 542606
: 398420 |
398422