Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Firstly ./configure doesn't always find everything that it needs, or in other cases it finds everything it requires but not everything it could use. In that case you would want to know about it (and your ./install.sh script would fail anyway!) The classic example of non-failure with unintended consequences, from my point of view, is compiling large applications like ffmpeg or mplayer. These will use libraries if they are available but will compile anyway if they aren't, leaving some options disabled. The problem is that you then discover later that it was compiled without support for some format or another, thus requiring you to go back and redo it.</p> <p>Another thing ./configure does somewhat interactively is giving you the option to customise where on the system the application will be installed. Different distributions/environments have different conventions, and you would probably want to stick to the convention on your system. Also, you might want to install it locally (solely for yourself). Traditionally the ./configure and make steps aren't run as root, while make install (unless it is installed solely for yourself) has to be run as root. </p> <p>Specific distributions often provide scripts that perform this ./install.sh functionality in a distribution-sensitive manner - for example, <a href="http://fedoraproject.org/wiki/How_to_create_an_RPM_package" rel="nofollow">source RPMs + spec file + rpmbuild</a> or <a href="http://slackbuilds.org/howto/" rel="nofollow">slackbuilds</a>. </p> <p>(Footnote: that being said, I agree that ./configure; make; make install; can get extremely tedious.)</p>
    singulars
    1. This table or related slice is empty.
    1. POWhy always ./configure; make; make install; as 3 separate steps?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USSoz
    1. USSoz
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAll understandable, but in my eyes none of these possibilities are destroyed if you have one additional file that combines the three steps. E.g. if you want to read some of the configure stdout you can still grep for it or put the whole stdout into a file and read it afterwards.
      singulars
      1. PO
      1. USerikbwork
    2. COTrue, but then, why is a file required? Just use an alias (although you will have to think of a better/shorter name than 'confmakeins', I am uninspired today!). alias confmakeins='./configure && make && sudo make install'; cd source directory; confmakeins;
      singulars
      1. PO
      1. USSoz
    3. COSounds good. I never wrote an alias myself, so I didn't think about it!
      singulars
      1. PO
      1. USerikbwork
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload