make hostpath Don't give expected output

[Kartik494]

When i run command "make hostpath" from my root directory i got the error as "make: *** No rule to make target 'hostpath'. Stop."
and in make file the argument is used for build is: all
CMDS=hostpathplugin
all: build

include release-tools/build.make

However when i changes the argument all to hostpath then the command "make hostpath" is executed

CMDS=hostpathplugin
hostpath: build

include release-tools/build.make

So in Docs should we update make hostpath command to make all ?

[Kartik494]

/assign

[pohly]

Works for me. I'm using:

• GNU Make 4.2.1
• Debian GNU/Linux 10 (buster)
• csi-driver-host-path master (= 123fa4e).

all depends on build, which depends on $(CMDS:%=build-%).

I've not checked whether the latter is part of POSIX make or specific to GNU Make.

[Kartik494]

Hi @pohly Thanks for input , could you please suggest is there any pre-requisite i have to follow for running the command make hostpath in my envoirment. Is the GNU Make is specific to be at 4.2.1 version? Because i am still facing issue in that , only command is working for me is when i change this to make all or make. Please Suggest

[pohly]

Now I get it. It's failing for your because you literally are running make hostpath.

That simply isn't a valid invocation because there is no such build target, as make is pointing out.

If you want to build the binary, use make without a build target. That works in any of the Kubernetes-CSI repos, so you don't have to figure out what the binary is called.

[Kartik494]

If you want to build the binary, use make without a build target. That works in any of the Kubernetes-CSI repos, so you don't have to figure out what the binary is called.

@pohly Yes when i use without build target then it works fine for me i.e by simply running make command , i will be closing this issue.
Thanks

[Kartik494]

/close

[k8s-ci-robot]

@Kartik494: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.