On a roll now!

[coreplayer2]

Now that many of my system issues have been resolved I've been making extensions left and right, thanks guys

like a wireless extension (with latest usb adapter driver) so can connect at every boot without issue, libdvdcss so can now watch dvd's  YAY  am almost ready to make an extension of all backed up settings.

The wiki is great for those who know how already, some examples of each of how to apply each process would really help, like
Am curious how to apply these flags?  at the terminal with compiletc loaded perhaps?

export CFLAGS="-march=i486 -mtune=i686 -Os -pipe"
export CXXFLAGS="-march=i486 -mtune=i686 -Os -pipe"
export LDFLAGS="-Wl,-O1"


And why "touch" exactly?  what is it's purpose?    is it a time stamp utility?


I can't help but wonder why the process is left for users to complete the process,  A utility to automate the entire process surely would make the OS more appealing to the masses.    Open the app, point to the downloaded tar file and lastly a on click install install,   right?   does it really need to be more complex  than this?

[hiro]

Huh, are you trying to compile something there?

[Rich]

Hi coreplayer2

The command   touch filename   will update the time stamp of the file   filename.
If the file   filename   does not exist, it will create an empty file called   filename.

[coreplayer2]

Hi coreplayer2

The command   touch filename   will update the time stamp of the file   filename.
If the file   filename   does not exist, it will create an empty file called   filename.

cool, so the reason for updating the time stamp is ?  possibly to ensure this file is used over an older file? ie one which is included in an extension over one present prior to extension loading??

[maro]

The touch /tmp/mark needs to be seen in conjunction with the find /usr/local -newer /tmp/mark -not -type d command (for the "When DESTDIR Fails" case).

For those cases the installation attempt via make DESTDIR=/tmp/package install does not result in an installation in '/tmp/package'. The idea is that even though the "final" installation is to '/usr/local' (due to ./configure --prefix=/usr/local) a "mock" installtion into DESTDIR (e.g. '/tmp/package') is attempted. If that works (i.e. no files are written to ''/usr/local' but rather to '/tmp/package/usr/local') one can easily use '/tmp/package' as the root of the squashFS.

In case DESTDIR has been "ignored" the timestamped file allows 'find' to figure out which files have been written to '/usr/local'. This file list is then used via two 'tar' executions to copy all those files to '/tmp/pkg' and this then becomes the root of the squashFS.

So creating a timestamped file immediately prior to the installation attempt should limit said file list to only those files that were part of the installation process.

[coreplayer2]

I was wondering how you tar up the files associated with the recent compilation.  thanks  great description..
 

[bmarkus]

So creating a timestamped file immediately prior to the installation attempt should limit said file list to only those files that were part of the installation process.

In most cases. However installer may copy some data, configuration or other files with original date which is not found by this method.

[maro]

In most cases. However installer may copy some data, configuration or other files with original date which is not found by this method.

Very true, in which case one could try a "brute force" approach along the lines of
    find / -xdev | sort > ~/before
    sudo make install
    find / -xdev | sort > ~/after
    diff -U 0 ~/before ~/after
plus some appropriate post-processing of the 'diff' result to get to the list of added entries accross the whole file system (minus '/proc'  and '/sys' which the '-xdev' option helps to suppress).

[coreplayer2]

A quick question, while this seems obvious, what is the difference between "make" and "make install" ?

[gerald_clark]

You have to read the makefile to see what each target does.

man make

[maro]

A quick question, while this seems obvious, what is the difference between "make" and "make install" ?

I also strongly believe that reading relevant man-pages is an excercise anyone asking questions should have done prior to posting. This case might be a bit different, as I could not find 'man.1' (i.e. provides.sh man.1 && cat info.lst only delivers false positives).

So I went over to my usual first stop for online man-pages (i.e. this page), pretending that I don't know the answer. But this one is a bit too terse to help answer the original question. So I take the clue and head over to the GNU make manual. But a 800k+ document might be a bit intimidating initially. Nevertheless as a consequence of skimming over it I'd consider sections 1 (Overview) and 2 (Introduction) probably worth reading for a start. Another source of information might be the relevant Wikipedia page.

If after some reading the question is still open one could always come back here (or contact me by PM).

[coreplayer2]

yes I read the die.net explanation thanks, I also find it a great resource.   I was asking here directly because usually when you ask folks with experience using the specific program in question, one will often get more meaningful  explanations which no book or manual will ever be capable of explaining.