Martin, you wrote: | [nothing new] | | You sent this yesterday already. With the aim of | helping you (and out of | curiosity), I am trying to find out which of your | tools produces this | strange error. | | But we can only find this out if cooperate, | because the problem is on | *your* computer. Let me try again: | | The configure script uses a relatively | complicated piece of code to | determine the version of fontforge that is | installed. Normally this code | does what it is supposed to do, that is, it | produces something like | | checking /sw/bin/fontforge version... 20080927 | | In your case, it produces some strange output | instead. The piece of code | in question runs first "fontforge --version" and | then filters the output | through "head" and "sed". Therefore I asked first | what you get from the | command | | fontforge --version | | If the output of this was OK, the next step would | have been to see if | the "head" command is working correctly, for | example by looking at the | output of | | echo foo | head -n 1 | | If this gives anything other than "foo", the | culprit would be clear. | | -- | Martin | [nothing new] | | You sent this yesterday already. With the aim of | helping you (and out of | curiosity), I am trying to find out which of your | tools produces this | strange error. | | But we can only find this out if cooperate, | because the problem is on | *your* computer. Let me try again: | | The configure script uses a relatively | complicated piece of code to | determine the version of fontforge that is | installed. Normally this code | does what it is supposed to do, that is, it | produces something like | | checking /sw/bin/fontforge version... 20080927 | | In your case, it produces some strange output | instead. The piece of code | in question runs first "fontforge --version" and | then filters the output | through "head" and "sed". Therefore I asked first | what you get from the | command | | fontforge --version | | If the output of this was OK, the next step would | have been to see if | the "head" command is working correctly, for | example by looking at the | output of | | echo foo | head -n 1 | | If this gives anything other than "foo", the | culprit would be clear. | | -- | Martin
This gives "foo". -- Jonathan ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Fink-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
