Skip to content

Conversation

dhuseby
Copy link

@dhuseby dhuseby commented Feb 3, 2016

@alexcrichton this fixes the current build breakage for the bitrig build:

./src/libstd/sys/unix/fs.rs:221:37: 221:56 error: attempted access of field `d_namlen` on type `libc::unix::bsd::openbsdlike::bitrig::dirent`, but no field with that name was found
../src/libstd/sys/unix/fs.rs:221                                     self.entry.d_namlen as usize)
                                                                     ^~~~~~~~~~~~~~~~~~~
../src/libstd/sys/unix/fs.rs:221:48: 221:56 help: did you mean `d_namelen`?
../src/libstd/sys/unix/fs.rs:221                                     self.entry.d_namlen as usize)
                                                                                ^~~~~~~~

alexcrichton added a commit that referenced this pull request Feb 4, 2016
fixes the bitrig d_namlen compile error
@alexcrichton alexcrichton merged commit 579f2c9 into rust-lang:master Feb 4, 2016
@dhuseby dhuseby deleted the fixing_bitrig_d_namlen branch February 19, 2016 03:08
Susurrus pushed a commit to Susurrus/libc that referenced this pull request Mar 26, 2017
The returned length of AF_UNIX sockaddrs is significant, and generally
does not match the length of the entire structure. For filesystem
sockets, this is ignorable because the path is also NUL-terminated, but
for unbound sockets (e.g., a socketpair) or abstract-namespace
sockets (a Linux extension where the address is an arbitrary
bytestring), we need to keep track of the length.

Fixes rust-lang#177. Also add a UnixAddr::new_abstract function and some better
handling of abstract-namespace socket addresses to fix rust-lang#169.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants