explain why location of compiled software is unknown?

If none of the more specific forums is the right place to ask

explain why location of compiled software is unknown?

Postby hthi » 2017-09-20 19:16

Can you tell, why if you install software on debian by compiling software, the software makers may not be
able to say, where the installed software is located on the computer?
And you cannot find the location?
That is unfortunate, if you want to uninstall the software. Maybe the software does not work.

Is it difficult for those who make the software to investigate, where the software will be installed?
Does it require more work for those who make the software, to make software which you in advance
will know the location of, when it has been installed?
If those who make the software cannot tell the location of the installed software, they cannot tell the
names of the installed files either? Making a computer search easier. Thank you.
hthi
 
Posts: 132
Joined: 2015-05-09 15:43

Re: explain why location of compiled software is unknown?

Postby peter_irich » 2017-09-20 19:30

If you want know where are the compiled software it must be build and installed as a package.

Peter.
peter_irich
 
Posts: 1189
Joined: 2009-09-10 20:15
Location: Saint-Petersburg, Russian Federation

Re: explain why location of compiled software is unknown?

Postby Danielsan » 2017-09-20 19:34

If you install the software through "make install" you can easily uninstall it with "make uninstall" in the same folder where you launch the installation command, it couldn't be so easier. But when you use "make install" dpkg and apt, the default tool to handle the packages, are unable to track your manual installation so it would be a wise idea using checkinstall to install compiled software, software installed through "checkinstall" can be handle with dpkg/apt and relatives front-end.
Last edited by Danielsan on 2017-09-20 21:31, edited 1 time in total.
If you can't fork then hold you in silence.
User avatar
Danielsan
 
Posts: 462
Joined: 2010-10-10 22:36

Re: explain why location of compiled software is unknown?

Postby stevepusser » 2017-09-20 19:54

If compiled manually, the software goes wherever the install directions tell it to go, so it's not unknowable. If you typed "make install" to install the software, read the Makefile and see where the "install" target put it. This may take some expertise in reading Makefiles and decoding the variables in the target, though.

That's another reason that building proper Debian packages is the One True Way™.
The MX Linux repositories: Backports galore! If we don't have something, just ask and we'll try--we like challenges. New packages: AzPainter 2.1.0, Pale Moon 27.5.0, Liquorix kernel 4.12-10, mpv 0.27.0, Kodi 17.3, 0ad 0.0.22, Mesa 13.0.6
User avatar
stevepusser
 
Posts: 8817
Joined: 2009-10-06 05:53

Re: explain why location of compiled software is unknown?

Postby milomak » 2017-09-20 22:02

iMac - MacOS and Windows 10 (Bootcamp)/ Debian Sid (External SSD)
Laptop (64-bit) - Debian Sid, Win10,
Kodi Box - Debian Sid
milomak
 
Posts: 1678
Joined: 2009-06-09 22:20

Re: explain why location of compiled software is unknown?

Postby debiman » 2017-09-21 18:20

hthi wrote:software makers may not be
able to say, where the installed software is located on the computer?

not true.
assuming the makefile is part of the software.

Danielsan wrote:If you install the software through "make install" you can easily uninstall it with "make uninstall" in the same folder where you launch the installation command, it couldn't be so easier.

only if the makefile provide an "uninstall" target.
not all of them do.
User avatar
debiman
 
Posts: 1341
Joined: 2013-03-12 07:18

Re: explain why location of compiled software is unknown?

Postby hthi » 2017-09-23 15:25

Thanks.
same folder where you launch the installation command

If the name of the source software folder is flashrom-0.9.9, I can cd
to flashrom-0.9.9 and compile in that folder?
hthi
 
Posts: 132
Joined: 2015-05-09 15:43

Re: explain why location of compiled software is unknown?

Postby stevepusser » 2017-09-23 20:39

I must ask why you are trying to compile 0.9.9 when Debian stretch has a newer 0.9.9+r1954 in the main repository. If you're running an older Debian, you can very probably backport the package and save yourself a lot of hassle.
The MX Linux repositories: Backports galore! If we don't have something, just ask and we'll try--we like challenges. New packages: AzPainter 2.1.0, Pale Moon 27.5.0, Liquorix kernel 4.12-10, mpv 0.27.0, Kodi 17.3, 0ad 0.0.22, Mesa 13.0.6
User avatar
stevepusser
 
Posts: 8817
Joined: 2009-10-06 05:53

Re: explain why location of compiled software is unknown?

Postby debiman » 2017-09-23 22:21

if you downloaded a source code archive to compile manually, the first thing is always to look for a file named README or INSTALL or similar and read it to get instructions on how to proceed.
User avatar
debiman
 
Posts: 1341
Joined: 2013-03-12 07:18

Re: explain why location of compiled software is unknown?

Postby Head_on_a_Stick » 2017-09-23 22:26

"Are you quite sure that all those bells and whistles, all those wonderful facilities of your so called powerful programming languages, belong to the solution set rather than the problem set?" — Edsger W. Dijkstra
User avatar
Head_on_a_Stick
 
Posts: 6606
Joined: 2014-06-01 17:46
Location: /dev/chair


Return to General Questions

Who is online

Users browsing this forum: No registered users and 7 guests

fashionable