Eby and Elie:

 

Thank you for your response to my earlier questions of 11/9 and 11/17 regarding 
the "installation script" not working and the "make" command. Yes, I can be 
more specific and in the future will make it a point to cc the 
[email protected] list.

 

I am using windows with vista home premium, and am trying to install 
gregorio-1.0 on two desktop computers, a HP Pavilion Elite d5000t and a Dell 
Dimension E510.  Space and speed are most likely non-issues. Cygwin, Texlive, 
Unix-related commands and the terminology associated with these programs or 
systems are all brand new to me since becoming aware of gregorio. 

 

With that as background, listed below are eight steps taken so far in trying to 
get up and running with gregorio, following the latest instructions on the 
website...

 

1. Cygwin was installed along with "the following supplementary software 
packages: libxml2, libxml2-dev, python, libtool, gettext, and glib2". If these 
six packages are what you mean by "all development tools", then, yes, they are 
all installed. On the other hand, the additional packages required to "compile 
the development version" in the instructions were not installed. I assumed the 
current version of gregorio was all one needed to work with chant neumes and 
text, and that the development version was an option strictly for programmers 
and technical specialists.

 

2. Texlive 2009 was installed with the Omega scheme selected and two other 
changes made as called for in the instructions. The tetex-related files were 
not installed.

 

3. The gregorio "tarball" - another new term apparently representing another 
kind of  .zip file --was downloaded from HTTP://download.gna.org/gregorio/ 
release/current, and saved in the Cygwin home directory C:\\Cygwin\home\MKC. I 
made a note of where it was downloaded from, since this apparently affects what 
commands should be used later in the compiling process. 

 

4. Here is where some difficulty emerged. Cygwin was launched and an attempt    
          was made to "uncompress gregorio archives" using 
"tar.xzf.gregorio-1.0.tar.gz". This   did not work. I then tried to uncompress 
gregorio using "tar.xzf.gregorio-1.0.tar.tar.gz". That, too, didn't work. The 
screen said, among other things, ".cannot open: No such file or directory." In 
other words, I was unable to create a subdirectory for gregorio-1.0.

 

Eventually, as best I can recall, the subdirectory was created by saving the 
tarball as "gregorio-1.0.tar.gz" in the home directory, and not as 
"gregorio-1.0.tar.tar" which is what the computer wanted to save. I was puzzled 
by the double use of the .tar extension. It seemed that only by getting rid of 
one of the "tar"s was I able to create a gregorio subdirectory.

 

Of the eight steps outlined in this email, this is the one that has taken the 
most time, and the one that I feel the least certain of having done correctly.

 

5. I switched into the new gregorio subdirectory and ran the "ls" command to be 
sure the files were there. They were. But what directory the gregorio 
subdirectory should be under is not clear. It happens to be under the directory 
entitled "m...@mkcjic2 -PC, which, unless mistaken, is the main or home 
directory when operating in Cygwin. Is this the correct location for the 
gregorio-1.0 subdirectory, and, also, is there a Cygwin command one could use 
to produce a listing of all directories and subdirectories being used in the 
compilation process? 

 

6. I omitted the "autoreconf -f -i" command, based on where the gregorio 
tarball file was downloaded from in Step three above.  "./configure" was run. 
This produced, among other comments, "error: No acceptable C compiler found in 
$PATH", and later on "error: C++ processor lib/cpp fails sanity check". I 
googled the error and found out that the gcc packages or at least some of them 
needed to be added to Cygwin. Therefore I did a "run setup 1.7.exe" and added 
four of the 32 available gcc packages. The four added were: "gcc-core.lst.gz", 
"gcc-g++.lst.gz", "gcc-mingw-core.lst.gz", and "gcc-mingw-g++.lst.gz". Was this 
the correct thing to do? And was it correct to ignore the "autoreconf -f -i " 
command?

 

7. "./configure -prefix=/usr -enable-glib-utf8" was run, while still in the 
gregorio-1.0 subdirectory. There were almost two full pages of output. At the 
end it said "*** a new enough version of pkg.config was not found". That was 
followed by "*** see http://www.freedesktop.org/software/pkgconfig/";, and by 
"configure. Error: glib not found."  This was puzzling because "glib2.lst.gz" 
is shown as one of the packages that was downloaded from the Cygwin master list 
of packages after running the "/etc/setup" command. A look at the 47-page 
master list of Cygwin packages revealed that there were six glib-related 
packages (glib, glib-devel, glib2, glib2-devel, glib2-doc, and glib2-runtime). 
But as mentioned in Step one, the gregorio instructions only call for "glib2". 
Is there something more to be done here? Also, should I look for a new version 
of "pkg.config"?

 

Finally, it said "See config.log for more details".

 

8. Ignoring for the moment the questions raised in Step seven, I ran "make" at 
the $ prompt. The computer wrote: "bash: make: Command not found".

 

Hopefully, the above will give you enough information to help determine how I 
might proceed next in order to overcome these snags. Any further tips and 
advice you may have would be greatly appreciated. And I apologize for the 
length of this email. 

 

Mike Cronin

Ormond Beach, FL
_______________________________________________
Gregorio-users mailing list
[email protected]
https://mail.gna.org/listinfo/gregorio-users

Reply via email to