LinuxQuestions.org - . /Configure not workin and Synaptic not working

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - . /Configure not workin and Synaptic not working (https://www.linuxquestions.org/questions/linux-newbie-8/configure-not-workin-and-synaptic-not-working-696872/)

. /Configure not workin and Synaptic not working

I tried installing flashplayer with ./configure but as I typed it in Terminal it shows "no such directory exists" while I 'm in right directory (I have un tar ed the flashplayer), I tried it with Synaptic Pkg Manager but when I go to add downladed pkges the pkg (flashplayer) appeared un highlighted and can not select it ? My Synaptic doesn't ask for root password when opened please I need to install some CAD software urgentlly so How can I make thiss all install ? (I'm trying to learn installation with flashplayer as it is known and simple)

Quote:

I tried installing flashplayer with ./configure but as I typed it in Terminal it shows "no such directory exists"

for that to run you first need to 'cd" to the folder that the file"configure" is in
http://www.linuxcommand.org/index.php
http://tldp.org/LDP/Bash-Beginners-G...tml/index.html

i am ASSUMING you are running Debian or Ubuntu ????
What is your operating System and version ?
is it 32 bit or 64 bit
What is your hardware specs ?
Did YOU install the os or was it preinstalled when you bought the computer?
some more info is needed for us to help.

in order to build the source code
-------------
./configure -- prefix=/use - - more options
make
su
make install
----------
you need to have the " Development Tools " and " Development Library's" installed for YOUR operating System and ALL of the prerequisites installed for that program .

I'm on Debian AMD64 (I installed it by mistake from directly net, it was supposed to be i386 for my processor is Intel dual core, mercury main board, BUT IT IS RUNNING WELL, I think 64 bit is supported on my PC), I done all that "cd" thing and reached exactly to un tar ed folder of flashplayer which has one *.so and one flashplayer installer file, after "cd //home/christian/c/falsh_player"in which above mentioned two files are present I typed "./configure" but it returned with "no such directory exixsts" in Synaptic the flash player (those two files) just doesn't open:mad::cry:

Check if you are running configure in the right directory.

Always try downloading .deb file for your machine.That will easily do the needful.
Also see http://www.psychocats.net/ubuntu/flash for further help

As flash player is not supported for 64 bit I'll try it later, as of learning installation is concerned I'm trying my PICKIT2 but, see what happens

Code:

PC NAME://home/christian/d$ cd //home/christian/d

PC NAME://home/christian/d$ ls

pk2cmdv1-12Linux2-4  pk2cmdv1-12Linux2-4.tar.gz

PC NAME://home/christian/d$ cd //home/christian/d/pk2cmdv1-12Linux2-4

PC NAME://home/christian/d/pk2cmdv1-12Linux2-4$ ./configure

bash: ./configure: No such file or directory

PC NAME://home/christian/d/pk2cmdv1-12Linux2-4$ ./Configure

bash: ./Configure: No such file or directory

PC NAME://home/christian/d/pk2cmdv1-12Linux2-4$ ls

pk2cmd            PK2V023200.hex              usbhotplug.txt

PK2DeviceFile.dat  ReadmeForPK2CMDLinux2-4.txt

PC NAME://home/christian/d/pk2cmdv1-12Linux2-4$

cd into flashplayer directory.if you type ls you should see libflashplayer-installer and libflash.so
you can run installer with ./flashplayer-installer as root.or you can just copy the libflash.so to your browser plugins folder...
/usr/lib/mozilla/plugins
/usr/lib/firefox/plugins
/home/urname/.mozilla/plugins

you dont use ./configure to install flash player..thats a command you use for building packages from source code

just read you have 64 bit...
i do believe there is a 64 bit flash player
http://labs.adobe.com/technologies/f...tes_64bit.html

also for that program your trying to compile..did you read the read me's??when you build from sources read the read me's

A Makefile is provided for compiling on several versions of Linux and Mac OS X.
Select the system either by uncommenting one of the TARGET options in the
Makefile or by specifying the target on the command line.

make linux Build for Linux kernel 2.6
make linux-old Build for Linux kernel 2.4
make freebsd Build for FreeBSD (See FREEBSD NOTE below)
make mac104 Build for OS X version 10.4
make mac105 Build for OS X version 10.5

After successfully compiling pk2cmd, use su or sudo to run 'make install' as
root. The pk2cmd binary will be copied to /usr/local/bin with the 's'
permission bit set (necessary for running pk2cmd as a non-root user). The
device data file, PK2DeviceFile.dat, will be copied to /usr/share/pk2. If
/usr/share/pk2 doesn't already exist, it will be created by running
make install.

I did this .....

Code:

PC NAME:~$ su

Password:

PC NAME:/home/christian# cp -i //home/christian/c/libflashplayer.so ~/.mozilla/plugins

PC NAME:/home/christian#

But still on youtube it shows I don't have flashplayer:(

And yes hat is what I want to learn "How to install files (or build or whatever you may called) from *.tar.gz fromat" and that is WHY I AM TRYING ./configure and still have the same problem,
In short I want to and really need to learn how to install applications from *.tar.gz format and why ./configure return with "no such directory exists"PLEASE IT IS VERY URGENT I NEED TO DO A PROJECT WITH PIC KIT 2, don't bother much about flash player tell me first how to overcome this ./configure stuff :confused:

Just read Replay from STARTOTAK, I'm a hardware guy (progarmming microcontrller), I don't understand what the readme says I'm attaching it here, as for the download the readme mentions in "installation" section from microchip.com I allready have it. PLEASE GUIDE ME

Quote:

. Operating System Support List (Tested)

----------------------------------------------------------------------------

The pk2cmd binary for kernel 2.4 was built on, and only tested on, Red Hat

Linux 7.2 but should work for other distributions using the 2.4 kernel.

It is recommended that you build a binary from the source code. The source

code is downloadable from the Microchip PICkit 2 webpage, and includes build

and installation instructions:

www.microchip.com/pickit2

----------------------------------------------------------------------------

4. What's New or Updated

----------------------------------------------------------------------------

>>> Version 1.12 <<<<

Bug fix for "-s" option allows simultaneous operation of multiple instances

of PK2CMD and multiple PICkit 2 units.

Changes to "-s" option:

See online help "pk2cmd -s?"

Bug fix for PIC32 programming with blank boot flash.

Requires OS firmware v2.32.00 or later

>>> Version 1.10 <<<<

-N option for assigning a Unit ID string to a PICkit 2 unit.

Support for multiple PICkit 2 units with 1 PC:

-S option to list all connected PICkit 2 units, or to select a particular

unit for use by the Unit ID.

-M or -MP commands will only verify the programmed portions of Program

Memory to reduce total programming time. (This does not apply to

verification with -Y or -YP)

PIC18 J-Series and PIC24FJ devices have updated handling of Configuration

words to match MPLAB IDE and PICkit 2 Programmer v2.5x

New support for PIC32, 11LCxxx, and MCP250xx devices.

Now allows spacing between command options and parameters.

Ex: -pPIC16F887 and -p PIC16F887 are both valid.

For -GP and -GE option types, spaces are not allowed in the address ranges.

EX:

Supported: -G P 0-F, -GP0-F, -G P0-F, -GP 0-F

Not Supported: -G P 0 - F, -GP0 -F, -GP0- F, or other combinations with

spaces in the range

----------------------------------------------------------------------

5. Known Problems

----------------------------------------------------------------------

When using option "-s" to list PICkit 2 units, it will display units

with firmware older than v2.30.00 as being in the bootloader with

a Unit ID of <bootloader>.

Use "-s#" to accurately list units with older firmware distinctly from

units in the bootloader.

----------------------------------------------------------------------------

6. Important Notes

----------------------------------------------------------------------------

-------------------------

Note on -R and -T options

-------------------------

4 different cases requiring different uses of -R and -T to run after

programming:

1) MCU is externally powered, and MCLR pin is configured as IO.

Switches needed to run after programming: NONE

2) MCU is externally powered, and MCLR pin is configured as MCLR

Switches needed to run after programming: -R

3) MCU needs to be powered from PICkit 2, MCLR configured as IO.

Switches needed to run after programming : -T

4) MCU needs to be powered from PICkit 2, MCLR configured as MCLR.

Switches needed to run after programming: -R -T

----------------------------------------------------------------------------

7. Installation

----------------------------------------------------------------------------

It is recommended that you build a binary from the source code. The source

code is downloadable from the Microchip PICkit 2 webpage, and includes build

and installation instructions:

www.microchip.com/pickit2

The method to run pk2cmd as a normal user (not root) depends on your

particular Linux distribution. Please consult your Linux distribution

documentation or use the support option as detailed in Section 12 of this

documentation if you can not get it to work.

Please read the file 'usbhotplug.txt' before installing pk2cmd. It explains

how to set up USB udev or hotplug rules so pk2cmd can be run in user mode.

You will need libusb runtime to run pk2cmd. Typical linux distros will have

libusb-0.1 package installed already, so no additonal installation is

needed. If not, use your linux distro's package management software to

install it (typically named libusb).

If you are running a very old Linux version which only includes an older

version of libusb (older than 0.1.10), then it is better you install

libusb-0.1 from the website below. In this case, you will have both the

runtime library and the development package installed in the same time.

You can download libusb-0.1 from http://libusb.sourceforge.net. See the

README and INSTALL files for instructions on how to install libusb on your

system.

As root (using 'su' or 'sudo'), copy the file pk2cmd to /usr/local/bin and

the file PK2DeviceFile.dat to /usr/share/pk2. Make sure that pk2cmd has the

s permission bit set:

chmod u+s pk2cmd

Your user PATH environment variable should include /usr/share/pk2. If using

bash, edit the file .bashrc to include:

PATH=$PATH:/usr/share/pk2

export PATH

Other command line interfaces should have a similar mechanism for setting

your PATH variable.

If you continue to have problems with pk2cmd not finding PK2DeviceFile.dat,

try copying the dat file to /usr/local/bin manually as a last resort.

----------------------------------------------------------------------------

8. Upgrading the PICkit 2 Operating System

----------------------------------------------------------------------------

If the executable detects an incompatible OS, an updated operating system

may be downloaded using the -D command line option. The latest OS firmware

can be downloaded from the PICkit 2 webpage at www.microchip.com/pickit2

----------------------------------------------------------------------------

9. Command Line Options

----------------------------------------------------------------------------

The following commands are available in the command line interface.

PICkit 2 COMMAND LINE HELP

Options Description Default

----------------------------------------------------------------------------

A<value> Set Vdd voltage Device Specific

C Blank Check Device No Blank Check

D<file> OS Download None

E Erase Flash Device Do Not Erase

F<file> Hex File Selection None

G<Type><range/path> Read functions None

Type F: = read into hex file,

path = full file path,

range is not used

Types P,E,I,C: = ouput read of Program,

EEPROM, ID and/or Configuration

Memory to the screen. P and E

must be followed by an address

range in the form of x-y where

x is the start address and y is

the end address both in hex,

path is not used

(Serial EEPROM memory is 'P')

H<value> Delay before Exit Exit immediately

K = Wait on keypress before exit

1 to 9 = Wait <value> seconds

before exit

I Display Device ID Do Not Display

K Display Hex File Checksum Do Not Display

M<memory region> Program Device Do Not Program

memory regions:

P = Program memory

E = EEPROM

I = ID memory

C = Configuration memory

If no region is entered, the entire

device will be erased & programmed.

If a region is entered, no erase

is performed and only the given

region is programmed.

All programmed regions are verified.

(serial EEPROM memory is 'P')

N<string> Assign Unit ID string to first found None

PICkit 2 unit. String is limited to 15

characters maximum. May not be used

with other options.

Example: -NLab1B

P<part> Part Selection. Example: -PPIC16f887 (Required)

R Release /MCLR after operations Assert /MCLR

S<string/#> Use the PICkit 2 with the given Unit ID First found unit

string. Useful when multiple PICkit 2

units are connected.

Example: -SLab1B

If no <string> is entered, then the

Unit IDs of all connected units will be

displayed. In this case, all other

options are ignored. -S# will list units

with their firmware versions.

See help -s? for more info.

T Power Target after operations Vdd off

U<value> Program OSCCAL memory, where: Do Not Program

<value> is a hexidecimal number

representing the OSCCAL value to be

programmed. This may only be used in

conjunction with a programming

operation.

V<value> Vpp override Device Specific

W Externally power target Power from Pk2

X Use VPP first Program Entry Method VDD first

Y<memory region> Verify Device Do Not Verify

P = Program memory

E = EEPROM

I = ID memory

C = Configuration memory

If no region is entered, the entire

device will be verified.

(Serial EEPROM memory is 'P')

Z Preserve EEData on Program Do Not Preserve

? Help Screen Not Shown

Each option must be immediately preceeded by a switch, Which can

be either a dash <-> or a slash </> and options must be separated

by a single space.

Example: PK2CMD /PPIC16F887 /Fc:\mycode /M

or

PK2CMD -PPIC16F887 -Fc:\mycode -M

Any option immediately followed by a question mark will invoke

a more detailed description of how to use that option.

Commands and their parameters are not case sensitive. Commands will

be processed according to command order of precedence, not the order

in which they appear on the command line.

Precedence:

-? (first)

-S

-D

-N

-P

-A -F -V -W -X -Z

-C

-U

-E

-M

-Y

-G

-I -K

-R -T

-H (last)

The program will return an exit code upon completion which will

indicate either successful completion, or describe the reason for

failure. To view the list of exit codes and their descriptions,

type -?E on the command line.

type -?V on the command line for version information.

type -?L on the command line for license information.

your on a 64 bit system?you download adobes 64bit ?I believe its /usr/lib64...
As far as that program you dont use ./configure on it..its "make linux" "make install"
Majority of times it will be
./configure
make
make install
but not always..you need to read the readme files in source code folder..it will tell you what you need to know to build .
If your going to build from source do you have build-essential installed??that will install basics you need build and compile..

i downloades source code and built it..you will need libusb-dev..look for it in synaptic..I built it but didnt install it..I have no use for the program..just make sure you have build-essential installed and libusb-dev..heres the make output..

strat@razor:~/pk2cmdv1.20LinuxMacSource$ make linux
make TARGET=linux
make[1]: Entering directory `/home/strat/pk2cmdv1.20LinuxMacSource'
g++ -Wall -D_GNU_SOURCE -O2 -I/usr/local/include -DLINUX -DUSE_DETACH -DCLAIM_USB -o cmd_app.o -c cmd_app.cpp
g++ -Wall -D_GNU_SOURCE -O2 -I/usr/local/include -DLINUX -DUSE_DETACH -DCLAIM_USB -o DeviceData.o -c DeviceData
.cpp
g++ -Wall -D_GNU_SOURCE -O2 -I/usr/local/include -DLINUX -DUSE_DETACH -DCLAIM_USB -o DeviceFile.o -c DeviceFile .cpp
g++ -Wall -D_GNU_SOURCE -O2 -I/usr/local/include -DLINUX -DUSE_DETACH -DCLAIM_USB -o ImportExportHex.o -c Impor tExportHex.cpp
g++ -Wall -D_GNU_SOURCE -O2 -I/usr/local/include -DLINUX -DUSE_DETACH -DCLAIM_USB -o PICkitFunctions.o -c PICki tFunctions.cpp
g++ -Wall -D_GNU_SOURCE -O2 -I/usr/local/include -DLINUX -DUSE_DETACH -DCLAIM_USB -o PIC32PE.o -c PIC32PE.cpp
g++ -Wall -D_GNU_SOURCE -O2 -I/usr/local/include -DLINUX -DUSE_DETACH -DCLAIM_USB -o Pk2BootLoader.o -c Pk2Boot Loader.cpp
g++ -Wall -D_GNU_SOURCE -O2 -I/usr/local/include -DLINUX -DUSE_DETACH -DCLAIM_USB -o pk2cmd.o -c pk2cmd.cpp
g++ -Wall -D_GNU_SOURCE -O2 -I/usr/local/include -DLINUX -DUSE_DETACH -DCLAIM_USB -o stdafx.o -c stdafx.cpp
g++ -Wall -D_GNU_SOURCE -O2 -I/usr/local/include -DLINUX -DUSE_DETACH -DCLAIM_USB -o pk2usbcommon.o -c pk2usbco mmon.cpp
g++ -Wall -D_GNU_SOURCE -O2 -I/usr/local/include -DLINUX -DUSE_DETACH -DCLAIM_USB -o pk2usb.o -c pk2usb.cpp
g++ -Wall -D_GNU_SOURCE -O2 -I/usr/local/include -DLINUX -DUSE_DETACH -DCLAIM_USB -o P24F_PE.o -c P24F_PE.cpp
g++ -Wall -D_GNU_SOURCE -O2 -I/usr/local/include -DLINUX -DUSE_DETACH -DCLAIM_USB -o dsP33_PE.o -c dsP33_PE.cpp
g++ -Wall -D_GNU_SOURCE -O2 -I/usr/local/include -DLINUX -DUSE_DETACH -DCLAIM_USB -x c -o strnatcmp.o -c strnat cmp.c
g++ -Wall -D_GNU_SOURCE -O2 -I/usr/local/include -DLINUX -DUSE_DETACH -DCLAIM_USB -o pk2cmd cmd_app.o DeviceData .o DeviceFile.o ImportExportHex.o PICkitFunctions.o PIC32PE.o Pk2BootLoader.o pk2cmd.o stdafx.o pk2usbcommon.o p k2usb.o P24F_PE.o dsP33_PE.o strnatcmp.o -L/usr/local/lib -lusb
make[1]: Leaving directory `/home/strat/pk2cmdv1.20LinuxMacSource'
strat@razor:~/pk2cmdv1.20LinuxMacSource$

Im assuming this the right packages you are trying to build..here link to where i got source code
http://www.microchip.com/stellent/id...irects=pickit2

O.K. first PICkit2 is a USB microcontroller programmer which I NEED to and HAVE TO install on my Debian, I have the following files from the microchip (menufacturer of PICkit2),.....
pk2cmd , pk2Devicefile.dat , pk2v023200.hex , ReadmeforPK2cmdLinux.txt , usbhotplug.txt, which file I should use to build and compile and how would I do that ?

Just read the reply what Build essentials and how would I verify I have it ?

ok..from the top..download the source code..extract it..cd into the directory..from reading the readmes you should read the usbhotplug.txt
"Please read the file 'usbhotplug.txt' before compiling and installing pk2cmd.
It explains how to set up USB udev or hotplug rules so pk2cmd can be run in
user mode. You must also have libusb (http://libusb.sourceforge.net) installed"
then after you do whatever usbhotplug.text tells you to do.
Then in source code directory you
make linux then when its done you..
make install
and then quoting from make readme..
"After successfully compiling pk2cmd, use su or sudo to run 'make install' as
root. The pk2cmd binary will be copied to /usr/local/bin with the 's'
permission bit set (necessary for running pk2cmd as a non-root user). The
device data file, PK2DeviceFile.dat, will be copied to /usr/share/pk2. If
/usr/share/pk2 doesn't already exist, it will be created by running
make install.

Both of these directories must be in your PATH variable. /usr/local/bin should
normally be in your PATH by default. If you're using bash as your command line
interface, edit the file .bashrc in your home directory to include:
PATH=$PATH:/usr/share/pk2
export PATH
Some similar procedure should exist for other command line shells; consult your
system's documentation. You'll need to restart your window manager for these
changes to take effect."

and build-essential can be installed with apt-get
apt-get install build-essential
and like i said you will need libusb and libusb-dev..libusb should already be installed

How to do this ????????:confused:

Quote:

In order for libusb to find the device node, it needs to locate it

in the /dev filesystem. The recommended way to let udev create nodes

in the /dev filesystem is to add a udev rule like the following into

some foo.rules file inside the /etc/udev/rules.d/ directory:

# usbfs-like devices

SUBSYSTEM=="usb_device", PROGRAM="/bin/sh -c 'K=%k; K=$${K#usbdev}; \

printf bus/usb/%%03i/%%03i $${K%%%%.*} $${K#*.}'", \

NAME="%c"

This layout is used by for example the Debian distribution and Fedora

Core. This rule creates a device tree identical to the earlier

/proc/bus/usb/ tree, but under /dev/bus/usb/ instead. If this device

tree exists, libusb will default to use it.

I tried typing "usbfs-like devices" in Terminal window but doesn't work, btw I installed essentials and libusb successfuly.