8000 Cat Windows 10 does not work · Issue #2601 · uutils/coreutils · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Cat Windows 10 does not work #2601

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
Quackdoc opened this issue Aug 25, 2021 · 9 comments · Fixed by #2610
Closed

Cat Windows 10 does not work #2601

Quackdoc opened this issue Aug 25, 2021 · 9 comments · Fixed by #2610

Comments

@Quackdoc
Copy link

when building on windows 10 trying to run cat gives this error


thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 1, kind: Uncategorized, message: "Incorrect function." }', src\uu\cat\src/cat.rs:375:71
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
@miDeb miDeb mentioned this issue Aug 25, 2021
Closed
@miDeb
Copy link
Contributor
miDeb commented Aug 25, 2021

Whoops, that was my fault. Could you check if the PR I linked fixes the issue? I don't have access to a windows machine right now, so I can't check it myself, but I think I found what caused this.

@Qu 8000 ackdoc
Copy link
Author

Whoops, that was my fault. Could you check if the PR I linked fixes the issue? I don't have access to a windows machine right now, so I can't check it myself, but I think I found what caused this.

Sorry for the late reply the fix works fine.

@miDeb miDeb mentioned this issue Aug 28, 2021
Merged
@Lertsenem
Copy link

Hello, when is this fix planned for release? I'm using version 0.0.8 and the error is still occuring.

@sylvestre
Copy link
Contributor

We are all volunteers. Nothing planed AFAIK.

Don't hesitate to give it a try to fix it!

@Lertsenem
Copy link

I realize that, sorry I was not trying to sound harsh. I just read in the thread that the patch was ready and the line

[...] linked a pull request that will close this issue on 28 Aug

made me wonder if I had missed a release or if the bug had been fixed but then reappeared somehow. :)

@tertsdiepraam
Copy link
Member

That PR has indeed been open for a long time, but it looks good. @Lertsenem, could you maybe check whether that PR fixes the issue for you? I think most maintainers are on Linux so it's hard to validate.

@Lertsenem
Copy link

I'd like too, but this is unfortunately a work PC and I don't have the opportunity to build anything on it. Hence my wait for the release. :/

@tertsdiepraam
Copy link
Member

Alright, I might be able to test it this weekend then.

@tertsdiepraam
Copy link
Member

I've tested the PR and it does indeed fix this issue. I think it can be merged!
80B8

@tertsdiepraam tertsdiepraam mentioned this issue Jan 10, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
5 participants
@sylvestre @Lertsenem @tertsdiepraam @miDeb @Quackdoc
0