Opened 19 years ago
Closed 19 years ago
#1667 closed defect (fixed)
Mktemp installation instructions
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | lowest | Milestone: | |
| Component: | Book | Version: | SVN |
| Severity: | normal | Keywords: | |
| Cc: |
Description
Why does the mktemp configure command use the "--with-libc" switch? I know the book says that the switch causes mktemp to use functions from the system libc, but why exactly? The reason should be explained in the book.
Change History (5)
comment:1 by , 19 years ago
| bug_file_loc: | → http://linuxfromscratch.org/pipermail/lfs-dev/2005-December/054577.html |
|---|
comment:2 by , 19 years ago
comment:3 by , 19 years ago
| Version: | TESTING → SVN |
|---|
comment:5 by , 19 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I think we really need to reverse that question. i.e. why should we use mktemp's own versions of these functions instead of the one's we've already been given by glibc? I can't think of any good reasons, therefore we may as well use glibc's versions, right? Proposed wording:
"This causes the mktemp program to use the mkstemp and mkdtemp functions from the system C library instead of its own implementation of them."
I think using common functions rather than custom versions is reason enough to use that switch. Therefore making it explicit that that's what we achieve by using the switch is enough to close this bug. Thoughts?