[Bug build/19207] New: Build failed with option that impact on binary format in CFLAGS

["zizztux at gmail dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=19207

            Bug ID: 19207
           Summary: Build failed with option that impact on binary format
                    in CFLAGS
           Product: glibc
           Version: 2.22
            Status: NEW
          Severity: minor
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: zizztux at gmail dot com
                CC: carlos at redhat dot com
  Target Milestone: ---

there are some CFLAGS options that impact on binary architecture.
for example, -m32 on 64bit compiler with multilib support.

$ CFLAGS="-m32" ./configure

configure script checks linker output format by calling gcc with
--print-output-format.
but, in configure script, CFLAGS value doesn't passed to gcc.

see below code.

-----

{ $as_echo "$as_me:${as_lineno-$LINENO}: checking linker output format" >&5
$as_echo_n "checking linker output format... " >&6; }
if ${libc_cv_output_format+:} false; then :
  $as_echo_n "(cached) " >&6
else
  if libc_cv_output_format=`
${CC-cc} -nostartfiles -nostdlib -Wl,--print-output-format 2>&5`
then
  :
else
  libc_cv_output_format=
fi
test -n "$libc_cv_output_format" || libc_cv_output_format=unknown
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $libc_cv_output_format" >&5
$as_echo "$libc_cv_output_format" >&6; }

-----

Incorrectly detected output format is used to generate ld script (ex. libc.so,
...). This output format string is written to OUTPUT_FORMAT directive. So, in
remain build process, this raise linking failure.

Therefore, I think that configure script is fixed to pass CFLAGS value to gcc.

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