Bug 1339192
| Summary: | Missing autotools helper config.* files | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Niels de Vos <ndevos> |
| Component: | build | Assignee: | Niels de Vos <ndevos> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.8.0 | CC: | bugs |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.8rc2 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1223937 | Environment: | |
| Last Closed: | 2016-06-16 14:07:54 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1223937 | ||
| Bug Blocks: | |||
|
Description
Niels de Vos
2016-05-24 11:13:03 UTC
REVIEW: http://review.gluster.org/14517 (build: include a dummy config.sub and config.guess in releases) posted (#1) for review on release-3.8 by Niels de Vos (ndevos) COMMIT: http://review.gluster.org/14517 committed in release-3.8 by Kaleb KEITHLEY (kkeithle) ------ commit b00eb38bff09b3fec6a273b7cb84cee3fa581a0d Author: Niels de Vos <ndevos> Date: Mon May 23 11:06:38 2016 +0200 build: include a dummy config.sub and config.guess in releases There is no hard requirement for a config.guess and config.sub script in the release tarball. By passing --build=... and --host=... to ./configure, the scripts are not executed. When doing local builds, the ./autogen.sh script (by running automake) will place a config.guess and config.sub script in the root of the source tree. Upon creation of the release ('make dist') tarball, the scripts are replaced by dummy copies from the build-aux/ directory. The main advantage to not include these scripts in the repository, is that there is no need to track upstream updates for them either. Cherry picked from commit bfd43dc894fcf2cc64ec73e8ea0a779064c47dd4: > Change-Id: I5e930988a9e849ec5d0c84d2e30e61f2a9685f45 > BUG: 1223937 > Reported-by: Emmanuel Dreyfus <manu> > Signed-off-by: Niels de Vos <ndevos> > Reviewed-on: http://review.gluster.org/14503 > Smoke: Gluster Build System <jenkins.com> > NetBSD-regression: NetBSD Build System <jenkins.org> > CentOS-regression: Gluster Build System <jenkins.com> > Reviewed-by: Kaleb KEITHLEY <kkeithle> Change-Id: I5e930988a9e849ec5d0c84d2e30e61f2a9685f45 BUG: 1339192 Reported-by: Emmanuel Dreyfus <manu> Signed-off-by: Niels de Vos <ndevos> Reviewed-on: http://review.gluster.org/14517 Reviewed-by: Kaleb KEITHLEY <kkeithle> Smoke: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report. glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |