It's absolutely OK to continue because this is leading towards helping ... you.

As far as the overall practices (1) the thread title does not indicate any particular technical topic and (2) not sure but I think that threads in this forum cannot be marked as Solved.

Therefore the technical discussion will not be readily search-able by future seekers of a similar problem.

This is sort of why it is not encouraged.

However, in spite of my title, I'm not the moderator for this sub-forum and merely take the time to say hello to new members.

Likely the moderator for this sub-forum "may" choose to split this thread and create a new thread from some or all of the posts in this forum. A problem there is we are not encouraged to edit your content, and as a result they should try to work with you to change the thread title if they choose to do this. I've sent a note (by way of using the Report button - the correct way to get the attention of a moderator) for them to review and consider this. However it is their decision.

I'm fine either way and please do not consider us forum police, we're just trying to steer things in the more common way and above I'm explaining why that way would add to the forums.

Short answer is that you are fine to continue to solve your problem and others are fine offering their advice.

My points are that ultimately this may help you, but leave a thread which may not be helpful to others with the same problem, and also if there are other members who may have a solution, some of them may not see this because they may not browse the introductions forum, nor will they see any problem description matching what you're working on.

This lib must have already been installed on my system: https://packages.debian.org/sid/liblo-dev

R: It's absolutely OK to continue because this is leading towards helping ... you.
T: Fine. If it was not, people in the know should go back through the process that got me here ... and see if I read instructions wrong or if instructions were ambiguous and clearly led me here.
R: As far as the overall practices (1) the thread title does not indicate any particular technical topic and (2) not sure but I think that threads in this forum cannot be marked as Solved.
T: Fine. I'm just wandering in the dark right now. It all started with my registering; being advised to introduce myself and my interests; and bring up any questions I have. I did that ... and then followed the bouncing ball.
R: Therefore the technical discussion will not be readily search-able by future seekers of a similar problem.

This is sort of why it is not encouraged.

However, in spite of my title, I'm not the moderator for this sub-forum and merely take the time to say hello to new members.

Likely the moderator for this sub-forum "may" choose to split this thread and create a new thread from some or all of the posts in this forum.
T: Or when I climb the learning curve sufficiently, I'll do that myself.
R: A problem there is we are not encouraged to edit your content, and as a result they should try to work with you to change the thread title if they choose to do this.
T: Works for me. Right now I'm just groping.
R: I've sent a note (by way of using the Report button - the correct way to get the attention of a moderator) for them to review and consider this. However it is their decision.
T: A message is addressed to me. I reply. I just follow the bouncing ball at this point.
R: I'm fine either way and please do not consider us forum police, we're just trying to steer things in the more common way and above I'm explaining why that way would add to the forums.
T: Things that might be controversial should have never been steered here in the first place. I can't get back to the new registration instructions. Can you? That's where we need to see what I did wrong and what may have caused it.
R: Short answer is that you are fine to continue to solve your problem and others are fine offering their advice.
T: Hmmm
R: My points are that ultimately this may help you, but leave a thread which may not be helpful to others with the same problem, and also if there are other members who may have a solution, some of them may not see this because they may not browse the introductions forum, nor will they see any problem description matching what you're working on.
T: I totally understand. Before I bother people with my problems I try to exhaust my efforts to solve them myself. Just being given a solution is of no use to me. I need to "know" how things work. For now, it's been expedient for me to take the advice as it's given. So far, I've learned as I've gone along (i.e. I understand what I was told to try). Climbing a new learning curve is painful. Especially when, as an old person, you've reached innumerable similar pinnacles ... only to have to go back to the bottom and be treated as a bottom feeder. Such is life.

If I continue to get guidance in this thread, I'll continue to follow that guidance and report my experience. If that guidance takes me to another thread, so be it. I'm not the leader here. I'm being led. If I've wandered into a "no trespassing zone", I'm sorry. If there was no sign? ... well, then it couldn't be helped.

Thanks for your comments and interest in keeping the process clean. I like clean processes.
/T

Not that we loose out as such but as noted above, you are loosing access to the ones that lurk in technical areas. You do have good assistants I think on this but confusing thread.

N: This lib must have already been installed on my system: https://packages.debian.org/sid/liblo-dev

T:

Taking your clues, getting the gist, and moving right along:

Next choked on the following:
==============================
Liblrdf0-dev
fftw3{f}
samplerate{0}
{lib}jack{-dev} ==> had to use apt-get

USING apt-get the process removed Ardour
I tried Qt Build and failed with the same "jack" error.

I continued to grope along.

The play-by-play to my last error is below. I groped a little past this and finally seem to have compiled. It now appears to be building ... very slowly. Looks like some kind of framework should have been setup before I started all this. Any idea what it would be?

It's currently building ... very slowly. It has produced 169 warnings so far. Clearly something is wrong. That's just not acceptable. For all I know, it's still building. Progress line is almost full ... but how could it know. I've gotten no obvious clue it's done

If you think we should move this conversation elsewhere, it's your call. I appreciate the clues.
/Todd

PLAY-BY-PLAY at current impass
==============================

From MINT Application fetcher:
------------------------------
-- Autodetecting Qt version to use
-- Checking for module 'sndfile>=1.0.16'
--
-- Checking for module 'jack'
-- No package 'jack' found
CMake Warning at CMakeLists.txt:179 (message):
Failed to find LIRC header lirc/lirc_client.h


CMake Warning at CMakeLists.txt:183 (message):
Failed to find LIRC library lirc_client


--
-- The following features have been enabled:

* ALSA , Alsa library (Advanced Linux Sound Architecture), used for MIDI support

-- The following REQUIRED packages have been found:

* Qt4
* PkgConfig
* ZLIB
* X11

-- The following features have been disabled:

* SNDFILE , Better support for WAV files
* JACK , WARNING: the library for accessing the JACK server (http://jackaudio.org) was not found. Audio will be unavailable!
* LIRCCLIENT , The LIRC client library, for remote control support

-- Not building unit tests, using a static library for rosegarden
-- Configuring done
-- Generating done
-- Build files have been written to: /home/user/Desktop/rosegarden-build
============================
USING COMMAND LINE:
---------------------
Unable to correct problems, you have held broken packages.
user@user-Latitude-E6410 ~ $ sudo apt-get install libjack0
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
ardour-data libaubio4 libcwiid1 libftgl2 liblilv-0-0 libltc11
libprojectm-qt1v5 libprojectm2v5 librubberband2v5 libserd-0-0 libsord-0-0
libsratom-0-0 libsuil-0-0 libvamp-hostsdk3v5 libvamp-sdk2v5 projectm-data
ttf-dejavu-core
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
jackd1 libzita-alsa-pcmi0 libzita-resampler1
Suggested packages:
jack-tools meterbridge
Recommended packages:
jackd1-firewire qjackctl
The following packages will be REMOVED:
ardour gstreamer0.10-plugins-good:i386 ia32-libs jackd jackd2
libasound2-plugins:i386 libfluidsynth1:i386 libjack-jackd2-0
libjack-jackd2-0:i386 libsdl-mixer1.2:i386 qmidinet
The following NEW packages will be installed:
jackd1 libjack0 libzita-alsa-pcmi0 libzita-resampler1
0 upgraded, 4 newly installed, 11 to remove and 88 not upgraded.
Need to get 312 kB of archives.
After this operation, 34.5 MB disk space will be freed.
Do you want to continue? [Y/n] y
Get:1 http://archive.ubuntu.com/ubuntu xenial/universe amd64 libjack0 amd64 1:0.124.1+20140122git5013bed0-3build2 [43.1 kB]
Get:2 http://archive.ubuntu.com/ubuntu xenial/universe amd64 libzita-alsa-pcmi0 amd64 0.2.0-2 [13.8 kB]
Get:3 http://archive.ubuntu.com/ubuntu xenial/universe amd64 libzita-resampler1 amd64 1.3.0-2 [10.3 kB]
Get:4 http://archive.ubuntu.com/ubuntu xenial/universe amd64 jackd1 amd64 1:0.124.1+20140122git5013bed0-3build2 [245 kB]
Fetched 312 kB in 0s (336 kB/s)
Preconfiguring packages ...
(Reading database ... 295061 files and directories currently installed.)
Removing ardour (1:4.6~dfsg-1) ...
Removing ia32-libs (2016.02.18) ...
Removing gstreamer0.10-plugins-good:i386 (0.10.31-3+nmu4ubuntu2.16.04.3) ...
Removing qmidinet (0.3.0-1) ...
Removing jackd (5) ...
Removing jackd2 (1.9.10+20150825git1ed50c92~dfsg-1ubuntu1) ...
Removing libasound2-plugins:i386 (1.1.0-0ubuntu1) ...
Removing libsdl-mixer1.2:i386 (1.2.12-11build1) ...
Removing libfluidsynth1:i386 (1.1.6-3) ...
Removing libjack-jackd2-0:i386 (1.9.10+20150825git1ed50c92~dfsg-1ubuntu1) ...
dpkg: libjack-jackd2-0:amd64: dependency problems, but removing anyway as you requested:
libfluidsynth1:amd64 depends on libjack-jackd2-0 (>= 1.9.5~dfsg-14) | libjack-0.116; however:
Package libjack-jackd2-0:amd64 is to be removed.
Package libjack-0.116 is not installed.
Package libjack-jackd2-0:amd64 which provides libjack-0.116 is to be removed.
timidity depends on libjack-jackd2-0 (>= 1.9.5~dfsg-14) | libjack-0.116; however:
Package libjack-jackd2-0:amd64 is to be removed.
Package libjack-0.116 is not installed.
Package libjack-jackd2-0:amd64 which provides libjack-0.116 is to be removed.
gstreamer1.0-plugins-good:amd64 depends on libjack-jackd2-0 (>= 1.9.5~dfsg-14) | libjack-0.116; however:
Package libjack-jackd2-0:amd64 is to be removed.
Package libjack-0.116 is not installed.
Package libjack-jackd2-0:amd64 which provides libjack-0.116 is to be removed.
seq24 depends on libjack-jackd2-0 (>= 1.9.5~dfsg-14) | libjack-0.116; however:
Package libjack-jackd2-0:amd64 is to be removed.
Pack
Removing libjack-jackd2-0:amd64 (1.9.10+20150825git1ed50c92~dfsg-1ubuntu1) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) ...
Processing triggers for mime-support (3.59ubuntu1) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for shared-mime-info (1.5-2ubuntu0.1) ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Processing triggers for libc-bin (2.23-0ubuntu9) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
Selecting previously unselected package libjack0:amd64.
(Reading database ... 294768 files and directories currently installed.)
Preparing to unpack .../libjack0_1%3a0.124.1+20140122git5013bed0-3build2_amd64.deb ...
Unpacking libjack0:amd64 (1:0.124.1+20140122git5013bed0-3build2) ...
Selecting previously unselected package libzita-alsa-pcmi0:amd64.
Preparing to unpack .../libzita-alsa-pcmi0_0.2.0-2_amd64.deb ...
Unpacking libzita-alsa-pcmi0:amd64 (0.2.0-2) ...
Selecting previously unselected package libzita-resampler1:amd64.
Preparing to unpack .../libzita-resampler1_1.3.0-2_amd64.deb ...
Unpacking libzita-resampler1:amd64 (1.3.0-2) ...
Selecting previously unselected package jackd1.
Preparing to unpack .../jackd1_1%3a0.124.1+20140122git5013bed0-3build2_amd64.deb ...
Unpacking jackd1 (1:0.124.1+20140122git5013bed0-3build2) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up libjack0:amd64 (1:0.124.1+20140122git5013bed0-3build2) ...
Setting up libzita-alsa-pcmi0:amd64 (0.2.0-2) ...
Setting up libzita-resampler1:amd64 (1.3.0-2) ...
Setting up jackd1 (1:0.124.1+20140122git5013bed0-3build2) ...
Processing triggers for libc-bin (2.23-0ubuntu9) ...
user@user-Latitude-E6410 ~ $

Update: It has finished building and began executing in "debug" mode (I presume). Found the executable in rosegarden-build named "rosegarden" of type "application/x-executable". Version is 17.12. I'm able to start multiple instances simultaneously.

Now I guess the fun really begins.

Thanks again for all the help. Hope I didn't rile people here too much. Now (for sure) is (beyond) the time to find another home in the forum to proceed. Recommendations welcomed.

/Todd

You're welcome! Glad that you got it running.

I'll suggest to the admins to stage a new user account and see where it commonly brings people.

It's great feedback you're citing about the new experience.