Bug 161087
| Summary: | Problem with configure probing for serial ports during build. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Andreas Thienemann <andreas> |
| Component: | minicom | Assignee: | Martin Stransky <stransky> |
| Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-07-15 12:48:19 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
fixed in rawhide - minicom-2.1 |
During a testbuild of minicom-2.00.0-19 in mock, the rebuild process stops with the following error: checking for default serial port device... configure: error: No suitable default serial port error: Bad exit status from /var/tmp/rpm-tmp.68348 (%build) This bug is present in rawhide as well. The problem stems from the fact that the configure script probes different serial ports to see which one should be used by default. This is problematic at best as it makes the build process unreproducible, depending on the devices present on the buildhost. A short discussion on #fedora-devel suggests the best way to deal with this issue would be to pass /dev/modem or /dev/ttySx directly to the configure-script: --enable-dfl-port=DEVFILE Set default /dev/.. modem device (def: try common locations)