This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Why do we create a broken symlink for include/bits/stamp-bits ?
- From: Jonathan Wakely <jwakely at redhat dot com>
- To: libstdc++ at gcc dot gnu dot org
- Date: Wed, 25 Oct 2017 13:18:50 +0100
- Subject: Why do we create a broken symlink for include/bits/stamp-bits ?
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx02.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx02.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=jwakely at redhat dot com
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com F1FAF82100
In include/Makefile the stamp-bits-sup target creates a symlink called
stamp-bits:
stamp-bits-sup: stamp-bits ${bits_sup_headers}
@-cd ${bits_builddir} && $(LN_S) $? . 2>/dev/null
# ^^^^^^^^^^^^
@$(STAMP) stamp-bits-sup
Should this use "$(LN_S) ${bits_sup_headers} ." instead, so it only
creates symlinks for the headers, not "stamp-bits" as well?
The broken symlink isn't a big deal but causes errors like:
libstdc++-v3$ grep -R foobar include/
grep: include/bits/stamp-bits: Too many levels of symbolic links