This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc 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] |
the main configure script sets up a $dest variable before executing configure scripts in subdirs. this path ends up being relative to the top builddir. this ends up bubbling into the ldd_rewrite_script variable that some machines need to override: sysdeps/unix/sysv/linux/ia64/configure.in:ldd_rewrite_script=ports/sysdeps/unix/sysv/linux/ia64/ldd-rewrite.sed sysdeps/unix/sysv/linux/mips/mips64/configure.in:ldd_rewrite_script=$dest/ldd-rewrite.sed sysdeps/unix/sysv/linux/m68k/configure.in:ldd_rewrite_script=sysdeps/unix/sysv/linux/ldd-rewrite.sed and then the ldd_rewrite_script file is used relative to the top srcdir that means each of these are easy to break: - ia64 can be broken by not naming the top dir "ports" (which happens when you unpack the released glibc-ports-xxx tarball). - mips can be broken by building in a dir two deep: mkdir build/mips; cd build/mips; ../../configure ... - m68k looks pointless considering that's what common code sets up seems like the easy fix would be to have the top level configure script setup a variable that specifies the specific subdir relative to the top srcdir, and then these sub-configure scripts can use those instead ? i'm not sure if the $dest convention was on purpose, but seems more like an accident that port maintainers noticed & needed & abused rather than writing a specific API between the configure scripts. -mike
Attachment:
signature.asc
Description: This is a digitally signed message part.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |