SH scanning #67
Merged
SH scanning #67
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
i merged, but each check now say something like: 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
<#67 (comment)>, 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
> <#67 (comment)>, 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
>> <#67 (comment)>, 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
<#67 (comment)>, 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
> >> <#67 (comment)>, 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
> <#67 (comment)>, 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
<#67 (comment)>, 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
> > >> <#67 (comment)>, 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
> > <#67 (comment)>, 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
> <#67 (comment)>, 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
>> > >> <#67 (comment)>,
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
>> > <#67 (comment)>, 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
>> <#67 (comment)>, 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
<#67 (comment)>, 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 :-) A makefile can be surprisingly powerful, but has simple rules. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Also changed all the " to ' so that everything is uniform.