This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug other/42280] libiberty configure script fails checking pid_t when without-headers



------- Comment #6 from viriketo at gmail dot com  2009-12-05 14:03 -------
Ok, I traced the problem down. The main change between 4.3.4 and 4.4.1 that
triggered the problem was the addition of 'zlib' in the core package (what I am
trying to build).

The configure script has the following logic around line 5370:
# Sometimes the tools are distributed with libiberty but with no other
# libraries.  In that case, we don't want to build target-libiberty.
# Don't let libgcc imply libiberty either.
if test -n "${target_configdirs}" ; then
  libgcc=
  others=
  for i in `echo ${target_configdirs} | sed -e s/target-//g` ; do
    if test "$i" = "libgcc"; then
      libgcc=target-libgcc
    elif test "$i" != "libiberty" ; then     # OFFENDING CHECK
      if test -r $srcdir/$i/configure ; then
    others=yes;
    break;
      fi
    fi
  done
  if test -z "${others}" ; then
    target_configdirs=$libgcc  # This happens only if 'zlib' is not there - and
this line should be run in my use case.
  fi
fi

So, I can't really propose a patch. What I did to get gcc 4.4.2 building is
remove the zlib directory after unpacking the core package.

I don't know the packaging procedure of gcc, but this concerns this procedure.
I don't know what status apply to the bug.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42280


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]