On 10/2/10 8:28 AM, David wrote:
> Just a suggestion, but why not provide pre-compiled install packages
> for Linux so users wouldn't have to compile it themselves?
I'm not very knowledgeable about Linux software distribution. One
problem is that Linux has many variants and the differences really
matter, so I believe that a pre-compiled package will only be good for a
particular installation. There are some pre-compiled versions of Nyquist
for Linux, but I assume not for EasyPeasy or Ubuntu. A common approach
in these cases is to provide source and use configuration tools to
explore the local environment, figure out the proper options, and build
a working version of the program for that local environment. This has
not been done for Nyquist. Instead, I've tried to make Nyquist as
self-contained as possible, and to avoid system-dependent code as much
as possible. Most of this work predated the widespread use of Linux,
auto configure tools, and Linux distributions, so I'll readily admit
that Nyquist is not using popular distribution methods and it could use
an upgrade by someone that really understands this. Maybe it would be
possible to take an existing distribution (I think Debian has a packaged
version of Nyquist) and make it more universal.
> Maybe you
> don't have enough users on Linux to justify the work, I don't know.
> But it might save everybody time in the long run. And some users who
> don't have a programming background may not have the expertise to
> compile it themselves.
> At the very least, I'd update the install instructions in the Nyquist
> manual. For example, the 'setenv' command is only available in some
> Unix/Linux shells. On others, you have to use the 'export' command.
> It's not a big deal if you know Unix or Linux well enough, but it
> might be a problem for inexperienced users. And I'd also add a list of
> the tools needed to compile Nyquist; you can't assume that they will
> be automatically included in all Linux distributions, as Raymond seems
> to think.
In the words of Perlis, "One man's constant is another man's variable."
Seriously, this is good information; I *do* update installation
instructions based on problems and feedback, so thanks for the input.
> I'm using EasyPeasy, a trimmed-down version of Ubuntu for
> small netbooks, which doesn't include a lot of the development tools
> needed to compile Nyquist (although I can download and install them,
> of course).
I think you'll find it necessary to add lots of dev tools as you move
away from "standard" apps like open office toward more experimental
> As for the header file, it may be that newer compilers have the
> contents of stdio.h "hard-wired" into them, but in the old days, you
> had to include the header file or take the chance that the compiler
> would make some invalid assumptions about the functions declared in
> it. Personally, I think it's still better to include the header
> explicitly, even if it does compile without it on some systems. Maybe
> you could suggest this to the STK folk.
Probably this problem is solved in current STK, but I haven't upgraded.
> As for myself, I've downloaded the missing development tools, but I'm
> still getting a compile error about a missing library ('asound'). I'll
> try to figure it out, but if I can't, I'll post details later.
asound is ALSA. This is fundamental to any sound-related linux program
(although you could have ALSA without the ALSA development tools needed
to compile a program that uses ALSA)
> Thanks for your help.
> On Sat, Oct 2, 2010 at 1:33 AM, Roger Dannenberg<rbd@...> wrote:
>> There was a discussion here about some undeclared functions such as
>> "fopen" in Nyquist. My local copy of nyqstk/src/FileRead.cpp has been
>> modified by adding
>> I think the change was put in by some Audacity folks to reduce some
>> warning messages, but apparently with some compilers (or some
>> configurations) a missing declaration is an error. This file comes from
>> STK, and I try to avoid changing STK code so that it will be easier to
>> upgrade, but in this case it really needs the include.
>> I was signed up to get digests, and I guess it took almost a year to
>> make a digest's worth of stuff. If you're reading this in 2011, maybe
>> you should ask me to change your settings. (I just changed mine -- sorry
>> I wasn't getting messages more promptly.)
>> Finally, Edgar, I manually put you on the list. I hope that works for
>> you. I have no idea why you weren't able to sign up yourself.
>> While I'm writing, I'll mention that I'm going to do some work on
>> Nyquist between now and January to get ready for my class. Among other
>> things, Nyquist doesn't work on some systems without an upgrade of
>> PortAudio, and Nyquist Makefiles are not set up for 64-bit machines.
>> (Nyquist will not run on 64-bit instruction sets without a lot of work,
>> but I can at least provide Makefiles that generate 32-bit code even when
>> the native architecture is 64-bit.) I've done this and it seems to work
>> fine, but the changes are not in the release. There are a few other
>> things that are broken. Let me know (or remind me) if there are other
>> fixes I should look into.
>> Start uncovering the many advantages of virtual appliances
>> and start using them to simplify application deployment and
>> accelerate your shift to cloud computing.
>> Nyquist-users mailing list