Closed ParkerTewell closed 3 years ago
i merged, but each check now say something like:
ccdflip
man: ['\\fBin', '\\fBout', '\\fBflip']
bin: ['in', 'out', 'flip']
an easy check is to run "make checkpars" from the $NEMO directory.
That's what I get for not testing. I'm on it now.
On Fri, Jun 25, 2021 at 7:52 AM Peter Teuben @.***> wrote:
i merged, but each check now say something like:
ccdflip man: ['\fBin', '\fBout', '\fBflip'] bin: ['in', 'out', 'flip']
an easy check is to run "make checkpars" from the $NEMO directory.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/teuben/nemo/pull/67#issuecomment-868444650, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH7PRPOWAIPOBERZ6BKSGNLTURUXVANCNFSM47IYH6DA .
-- Parker Tewell B.S. Computer Science - UMD
When I run make checkpars in $NEMO I get the following error message:
make: *** No rule to make target `checkpars'. Stop.
Any ideas what causes this?
On Sun, Jun 27, 2021 at 8:57 PM Parker Tewell @.***> wrote:
That's what I get for not testing. I'm on it now.
On Fri, Jun 25, 2021 at 7:52 AM Peter Teuben @.***> wrote:
i merged, but each check now say something like:
ccdflip man: ['\fBin', '\fBout', '\fBflip'] bin: ['in', 'out', 'flip']
an easy check is to run "make checkpars" from the $NEMO directory.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/teuben/nemo/pull/67#issuecomment-868444650, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH7PRPOWAIPOBERZ6BKSGNLTURUXVANCNFSM47IYH6DA .
-- Parker Tewell B.S. Computer Science - UMD
-- Parker Tewell B.S. Computer Science - UMD
yes, this is when the Makefile.in (which was updated) wasn't updated to Makefile. to fix that, assuming you have myh master merged, do this:
./config.status
which probably has some kind of make target too. Perhaps "make config" or so????
On Sun, Jun 27, 2021 at 9:22 PM Parker @.***> wrote:
When I run make checkpars in $NEMO I get the following error message:
make: *** No rule to make target `checkpars'. Stop.
Any ideas what causes this?
On Sun, Jun 27, 2021 at 8:57 PM Parker Tewell @.***> wrote:
That's what I get for not testing. I'm on it now.
On Fri, Jun 25, 2021 at 7:52 AM Peter Teuben @.***> wrote:
i merged, but each check now say something like:
ccdflip man: ['\fBin', '\fBout', '\fBflip'] bin: ['in', 'out', 'flip']
an easy check is to run "make checkpars" from the $NEMO directory.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/teuben/nemo/pull/67#issuecomment-868444650, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AH7PRPOWAIPOBERZ6BKSGNLTURUXVANCNFSM47IYH6DA
.
-- Parker Tewell B.S. Computer Science - UMD
-- Parker Tewell B.S. Computer Science - UMD
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/teuben/nemo/pull/67#issuecomment-869268071, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZ4MGMWEWEVOGNSPKGCUEDTU7FGPANCNFSM47IYH6DA .
That worked! Thanks.
On Sun, Jun 27, 2021 at 9:25 PM Peter Teuben @.***> wrote:
yes, this is when the Makefile.in (which was updated) wasn't updated to Makefile. to fix that, assuming you have myh master merged, do this:
./config.status
which probably has some kind of make target too. Perhaps "make config" or so????
On Sun, Jun 27, 2021 at 9:22 PM Parker @.***> wrote:
When I run make checkpars in $NEMO I get the following error message:
make: *** No rule to make target `checkpars'. Stop.
Any ideas what causes this?
On Sun, Jun 27, 2021 at 8:57 PM Parker Tewell @.***> wrote:
That's what I get for not testing. I'm on it now.
On Fri, Jun 25, 2021 at 7:52 AM Peter Teuben @.***> wrote:
i merged, but each check now say something like:
ccdflip man: ['\fBin', '\fBout', '\fBflip'] bin: ['in', 'out', 'flip']
an easy check is to run "make checkpars" from the $NEMO directory.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/teuben/nemo/pull/67#issuecomment-868444650, or unsubscribe <
https://github.com/notifications/unsubscribe-auth/AH7PRPOWAIPOBERZ6BKSGNLTURUXVANCNFSM47IYH6DA
.
-- Parker Tewell B.S. Computer Science - UMD
-- Parker Tewell B.S. Computer Science - UMD
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/teuben/nemo/pull/67#issuecomment-869268071, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AAZ4MGMWEWEVOGNSPKGCUEDTU7FGPANCNFSM47IYH6DA
.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/teuben/nemo/pull/67#issuecomment-869268862, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH7PRPI6ZEUD7OJQ2ASBDV3TU7FO3ANCNFSM47IYH6DA .
-- Parker Tewell B.S. Computer Science - UMD
Is there anything special I need to do to use flags? Running make checkpars -v results in
GNU Make 3.81
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
On Sun, Jun 27, 2021 at 9:28 PM Parker Tewell @.***> wrote:
That worked! Thanks.
On Sun, Jun 27, 2021 at 9:25 PM Peter Teuben @.***> wrote:
yes, this is when the Makefile.in (which was updated) wasn't updated to Makefile. to fix that, assuming you have myh master merged, do this:
./config.status
which probably has some kind of make target too. Perhaps "make config" or so????
On Sun, Jun 27, 2021 at 9:22 PM Parker @.***> wrote:
When I run make checkpars in $NEMO I get the following error message:
make: *** No rule to make target `checkpars'. Stop.
Any ideas what causes this?
On Sun, Jun 27, 2021 at 8:57 PM Parker Tewell @.***> wrote:
That's what I get for not testing. I'm on it now.
On Fri, Jun 25, 2021 at 7:52 AM Peter Teuben @.***> wrote:
i merged, but each check now say something like:
ccdflip man: ['\fBin', '\fBout', '\fBflip'] bin: ['in', 'out', 'flip']
an easy check is to run "make checkpars" from the $NEMO directory.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/teuben/nemo/pull/67#issuecomment-868444650, or unsubscribe <
https://github.com/notifications/unsubscribe-auth/AH7PRPOWAIPOBERZ6BKSGNLTURUXVANCNFSM47IYH6DA
.
-- Parker Tewell B.S. Computer Science - UMD
-- Parker Tewell B.S. Computer Science - UMD
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/teuben/nemo/pull/67#issuecomment-869268071, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AAZ4MGMWEWEVOGNSPKGCUEDTU7FGPANCNFSM47IYH6DA
.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/teuben/nemo/pull/67#issuecomment-869268862, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH7PRPI6ZEUD7OJQ2ASBDV3TU7FO3ANCNFSM47IYH6DA .
-- Parker Tewell B.S. Computer Science - UMD
-- Parker Tewell B.S. Computer Science - UMD
Just make checkpars
On Sun, Jun 27, 2021, 22:00 Parker @.***> wrote:
Is there anything special I need to do to use flags? Running make checkpars -v results in
GNU Make 3.81
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
On Sun, Jun 27, 2021 at 9:28 PM Parker Tewell @.***> wrote:
That worked! Thanks.
On Sun, Jun 27, 2021 at 9:25 PM Peter Teuben @.***> wrote:
yes, this is when the Makefile.in (which was updated) wasn't updated to Makefile. to fix that, assuming you have myh master merged, do this:
./config.status
which probably has some kind of make target too. Perhaps "make config" or so????
On Sun, Jun 27, 2021 at 9:22 PM Parker @.***> wrote:
When I run make checkpars in $NEMO I get the following error message:
make: *** No rule to make target `checkpars'. Stop.
Any ideas what causes this?
On Sun, Jun 27, 2021 at 8:57 PM Parker Tewell @.***> wrote:
That's what I get for not testing. I'm on it now.
On Fri, Jun 25, 2021 at 7:52 AM Peter Teuben @.***> wrote:
i merged, but each check now say something like:
ccdflip man: ['\fBin', '\fBout', '\fBflip'] bin: ['in', 'out', 'flip']
an easy check is to run "make checkpars" from the $NEMO directory.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/teuben/nemo/pull/67#issuecomment-868444650, or unsubscribe <
https://github.com/notifications/unsubscribe-auth/AH7PRPOWAIPOBERZ6BKSGNLTURUXVANCNFSM47IYH6DA
.
-- Parker Tewell B.S. Computer Science - UMD
-- Parker Tewell B.S. Computer Science - UMD
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/teuben/nemo/pull/67#issuecomment-869268071, or unsubscribe <
https://github.com/notifications/unsubscribe-auth/AAZ4MGMWEWEVOGNSPKGCUEDTU7FGPANCNFSM47IYH6DA
.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/teuben/nemo/pull/67#issuecomment-869268862, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AH7PRPI6ZEUD7OJQ2ASBDV3TU7FO3ANCNFSM47IYH6DA
.
-- Parker Tewell B.S. Computer Science - UMD
-- Parker Tewell B.S. Computer Science - UMD
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/teuben/nemo/pull/67#issuecomment-869278707, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZ4MGOMAU4F3F7J7GJOBXDTU7JVXANCNFSM47IYH6DA .
I realize with your example of where you added the -v that make will see it as a flag for make, not for checkpars. The make program can only pass parameters to the targets via a macro assignment, and the Makefile must then actually implement it. Which in this case it didn't. A way to find out what targets there are could be unix grep :-) grep : Makefile and the -n flag would say what it would do , but not do it, e.g. grep -n checkpars now you will see what it does, there -v was pre-defined by me in the Makefile
A makefile can be surprisingly powerful, but has simple rules.
Also changed all the " to ' so that everything is uniform.