-
-
Notifications
You must be signed in to change notification settings - Fork 76
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.
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
remake -xn isn't the same as remake -nx #40
Comments
Make it easy for me to help you. Come up with a specific Makefile, and show the results of one over the other. Then do the same with GNU make. Give the GNU remake and GNU make versions that you used as well as the OS versions. |
All right, sorry for that oversight, I was quite tired at the time. I expanded a bit with some system information and more examples on how to reproduce this. This isn't reproducible with
part out. Off-topic, but might be worthy to discuss: I also reported a French translation bug to https://translationproject.org/team/index.html since that's what was indicated on that page; but I had to read this repository's makefiles to find that page, so I guess it could be a bit more documented as well. The bug was:
is translated to
litterally meaning:
which is completely backwards, and hard to understand. "nécessaire pour" should be something along the lines of "à cause de" (~"because of") or "causée par" (~"caused by"). I'm only writing this here to get confirmation that this was the right channel to report the translation issue; if not, I can open a ticket in the right place. |
Will have to look at what's up with As for the translations, that discussion isn't going to do anything here. |
I did have a look at this issue and I can't decide if it's a bug or expected behaviour. The trace (-x | --trace) parameter accepts an argument and therefore the character(s) that follow '-x' are assumed to be that argument. No argument is necessary since it sets a default, hence '-nx' works. The same erroneous behaviour can be seen if running For debugging this issue I used the source of hashdeep since it got no dependencies expect autoconf/automake build tools. But every project will do. I would expect
It doesn't do that yet, see main.c, line 563-584 function decode_trace_flags(). Personally I would let remake exit with a meaningful error text. |
Feel free to fix and put in a PR! If you are feeling more ambitious there is a new vesion of GNU make, version 4.3 out. So there eventually will be a 4.3 branch with an entires set of patches to add the features here that aren't in GNU make. |
I'll create a PR probably sometimes next week. And for the being more ambitious, I'll have a look at the code to see if I can wrap my head around that topic. |
- This fix came to light through issue Trepan-Debuggers#40 'remake -xn isn't the same as remake -nx' - Added a check for invalid tracing option (-x|--trace)
Is fixed with remake@e141b6a |
@rocky, regarding make 4.3: I did a diff and I'm up for the task - not like from 3.8 to 4 :) ... it may take a week or two. If you're ok with that timeline I would take on the task. |
remake -nx
does perform a dry run;remake -xn
does not.The problem might seat between the keyboard and the chair, as I didn't extensively read the documentation (thus it could be intended behaviour, just unexpected for me); but I would expect them to perform the same.
System configuration
Steps to reproduce
Example Makefile:
Correct output
Unexpected output
The text was updated successfully, but these errors were encountered: