Re: SPIRO_SELECT etc

Matijs van Zuijlen <[email protected]> Sat, 31 Mar 2018 07:45:57 +0200

Newsgroups	gmane.comp.fonts.fontforge.devel
Message-ID	<[email protected]>

On 30/03/18 15:48, Apostolos Syropoulos wrote:
> 2018-03-30 7:20 GMT+03:00 Jose Da Silva <[email protected]>:
>> 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
>>
> 
> I can have the Makefile only if I have a template which was clearly missing.
> Since there is no template, configure cannot create a Makefile, I have
> compiled zillions of things and I think I know a thing or two.

So, for some reason running ./bootstrap didn't result in Makefile.in
being created from Makefile.am. Is there anything in the output that
would shed a light on why that is?

Regards,
Matijs

------------------------------------------------------------------------------
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

signature.asc (application/pgp-signature, 512 B)