Re: SPIRO_SELECT etc

On March 28, 2018 07:48:40 AM Apostolos Syropoulos wrote:
> Hello,
> 
> I downloaded the latest source (not the git source) and I tried to
> compile it. Somewhere compilation stops with the following errors:
> 
>  CCLD     libfontforge.la
> Undefined                       first referenced
>  symbol                             in file
> SPIRO_SELECT                        .libs/libfontforge_la-python.o
> SPIRO_SPL_OPEN                      .libs/libfontforge_la-spiro.o
> SPIRO_SELECTED                      .libs/libfontforge_la-spiro.o
> 
> 
> All these symbols are defined nowhere! I have installed Libspiro,
> version 0.5.20150702

Some linux distributions have two types of files to download,
 - a binary file (uses less disk space on the computer)
 - a developer version (has extra files needed to build something).

Since you are not installing a prebuilt binary, but have decided to build 
your own, you will also need developer versions of libraries used.

The developer version includes header *.h files expected to be used during 
the building steps of fontforge.

Reading the messages above, you need to install the developer version of 
libspiro first.

Some linux distros are smart enough to allow you to install libraries, then 
build the main program. Other distros require you to run an intermediate 
program to "update" a library list (or you simply reboot your PC before 
building the next-higher-level piece).

Some linux distros will also search /usr/local, while others are not as 
smart, and will need extra information to check there too.
/usr/local will usually be where you find the stuff you built yourself


> but this version does not define these symbols. So is there any way to
> solve this problem?
> 
> BTW, when I tried to bootstrap the git tree, for some reason it failed
> to create file
> Makefile.in and of course configure fails at the end because of this.

When you bootstrap, you need to pay attention to the text output.
Some of the messages are warnings, others are errors, but still allow you 
to keep going. If there are error or warning messages mentioned during 
bootstrap, you will probably want to answer those first.
When all errors and warnings are answered in ./bootstrap, then the should 
see a ./configure that needs to be run. After running ./configure you will 
then have Makefile.in and also (more importantly) a Makefile

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
fontforge-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html