Skip to content
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

How do I use??? #10

Open
dylanjewel opened this issue Apr 17, 2017 · 8 comments
Open

How do I use??? #10

dylanjewel opened this issue Apr 17, 2017 · 8 comments

Comments

@dylanjewel
Copy link

I'm a total noob to linux still learning I read the usage document but I don't understand how to actually install ratslap?? I downloaded files then what

@dylanjewel
Copy link
Author

dylanjewel commented Apr 17, 2017

~/ratslap $ make
Generating tags file...
RatSlap
Pulling from origin...
Already up-to-date.
Generating Changelog...
Generating git header file...
Package libusb-1.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libusb-1.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libusb-1.0' found
gcc -march=native -O2 -pipe -Wall -Werror -ggdb -DDEBUG -DINFO -c main.c -o main.o
main.c:30:31: fatal error: libusb-1.0/libusb.h: No such file or directory
compilation terminated.
Makefile:195: recipe for target 'main.o' failed
make: *** [main.o] Error 1

@dylanjewel
Copy link
Author

~/ratslap $ make
Generating tags file...
RatSlap
Pulling from origin...
Already up-to-date.
Generating Changelog...
Generating git header file...
Linking ratslap...
gcc -o "ratslap" -march=native -O2 -pipe -Wall -Werror -ggdb -I/usr/include/libusb-1.0 -DDEBUG -DINFO log.o main.o -lusb-1.0
BUILD COMPLETE: RatSlap (ratslap) v0.2.1-1-gd6b9714

@dylanjewel
Copy link
Author

ratslap command still doesn't work

@dylanjewel
Copy link
Author

no help? i'm noob i know but i need this thing

@opensiriusfox
Copy link

opensiriusfox commented May 6, 2017

To execute a command post build you need to either (1) add the directory path to your environment PATH variable or (2) execute the command directly from an out-of-path location by running ./ratslap from within the project directory, or using the absolute path of the binary.

Your problems are fundamentally basic Linux/Unix problems. Please attempt to be more considerate of developers who often don't have time to hand hold new users through introductory concepts in Linux. Beginner's frustration is understandable, but your problems are thus far not related to ratslap. Information on the PATH variable is widespread, but a basic overview is available here.

The step-by-step to use solution (2) as described above is the following:

$ git clone https://github.com/krayon/ratslap
$ cd ratslap
$ make
$ ./ratslap <flags as you want>

@tillcash
Copy link

To execute a command post build you need to either (1) add the directory path to your environment PATH variable or (2) execute the command directly from an out-of-path location by running ./ratslap from within the project directory, or using the absolute path of the binary.

Your problems are fundamentally basic Linux/Unix problems. Please attempt to be more considerate of developers who often don't have time to hand hold new users through introductory concepts in Linux. Beginner's frustration is understandable, but your problems are thus far not related to ratslap. Information on the PATH variable is widespread, but a basic overview is available here.

The step-by-step to use solution (2) as described above is the following:

$ git clone https://github.com/krayon/ratslap
$ cd ratslap
$ make
$ ./ratslap <flags as you want>

Getting below result while executing the command directly from the directory. Any suggestion to fix the this?

$ ./ratslap -h
./ratslap: symbol lookup error: ./ratslap: undefined symbol: libusb_set_option

@opensiriusfox
Copy link

Sounds like a missing library, which is really strange if you managed to build it. I really can't say much more without context.

@silkentrance
Copy link

silkentrance commented Jun 8, 2020

@dylanjewel I ran these apt-get commands and then make and everything worked except for the interface number, which defaults to 1 but had to be 0 on my system and which resulted in the fact that the kernel driver could not be detached.

sudo apt-get install build-essential pkg-config linux-headers-amd64 libusb-1.0-0-dev

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants