headers
Gour | 1 Jul 2005 09:44

Re: [xindy] no result

Jörg Sommer (joerg <at> alea.gnuu.de) wrote:

> $ xindy -V
> xindy release: unknown
> xindy script version: 1.06

Did you build your xindy from the source distribution which I prepare?

It looks that the bug was sneaked in causing the xindy.mem and
xindy.run missing '+x' attribute.

Check it and just do chmod +x on them.

Yesterday, while working on alpha4 I noticed this behaviour and
wondered hod did it happen all of sudden :-o

Sincerely,
Gour

--

-- 
Registered Linux User	| #278493
GPG Public Key		| 8C44EDCD

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
________________________________________________________________________
xindy-discuss mailing list -- general xindy announcements and discussions
(Continue reading)

Permalink | Reply | 4 comments |
headers
Gour | 1 Jul 2005 09:51

Re: [xindy] xindy-2.3-alpha4 tarball available

Maarten Sneep (maarten.sneep <at> xs4all.nl) wrote:

> I'm sad to tell that on Mac OS X it still doesn't work: the readline
> issue again. I tried the main configure with the --without-readline
> option, but it seems this isn't passed on to the rte configure call.
> I'll try later on to see 

Nothing has changed in rte/configure script, but you have to modify
rte/configure not the main one 'cause the main configure just calls
rte/configure and, at the moment, rte/configure does not check
parameters from main configure - clisp is really a different beast and
it is just a sub-package of the xindy distribution, i.e. it has
separate build process not a part of the main one.

So, modify rte/configure, line 26: clisp_modules='...'

> if other patches I needed before are there,  and whether the iconv issue has 
> been resolved. So far alpha 2 was  more successful for me - I only needed 2 
> patches there.

Well, the alpha2 did not include complete make-rules package :-)

> * Apply the patch Joachim posted to the list on the 27th to fix the  
> ordrules.[ch] files.

Somehow I missed that patch. Is it relevant only for Mac OS?

Sincerely,
Gour
(Continue reading)

Permalink | Reply | 5 comments |
headers
Joachim Schrod | 1 Jul 2005 10:01
Picon
Favicon

Re: [xindy] source distribution & make-rules

>>>>> Gour  <list <at> atmarama.org> writes:

Sorry for the late answer, I'm deeply buried in work.

> Now I've finished make-rules/styles & make-rules/inputenc and few
> things remains:

> a) what about modules/tex/isolatin*.xdy files

Please include them as is. They were created by Roger, and are not
part of make-rules. They provide handling of traditional (manual
input) TeX macros for many west-european characters. They will be
replaced somewhere in the future.

> b) file ../inputenc/latin.xdy is not generated via make-inp-rules
> script. What is its origin?

Created by me; sorry, I did not mention that.
Use the commands:

    echo ';; Generated at' `date` 'from latin?.xdy' >latin.xdy
    echo >>latin.xdy
    sort -u latin?.xdy | grep -v '^;' >>latin.xdy

> c) what about documentation in ../alphabets, i.e. targets like
> alphabets-doc.* ? Shall we build those and distribute in doc folder or
> not?

Very good idea. Create alphabets-doc.pdf and install it in the doc
folder.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Joachim Schrod | 1 Jul 2005 10:04
Picon
Favicon

Re: [xindy] no result

>>>>> "G" == Gour  <list <at> atmarama.org> writes:

> Jörg Sommer (joerg <at> alea.gnuu.de) wrote:
>> $ xindy -V
>> xindy release: unknown
>> xindy script version: 1.06

> Did you build your xindy from the source distribution which I prepare?

> It looks that the bug was sneaked in causing the xindy.mem and
> xindy.run missing '+x' attribute.

A small clarification: just xindy.run needs +x, xindy.mem doesn't.

	Joachim

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Joachim		     The most exciting phrase to hear in science, the
Rödermark, Germany   one that heralds new discoveries, is not "Eureka!"
<jschrod <at> acm.org>    (I found it!) but "That's funny..." [Isaac Asimov]

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
________________________________________________________________________
xindy-discuss mailing list -- general xindy announcements and discussions
Unsubscribe via https://lists.sourceforge.net/lists/listinfo/xindy-discuss
(Continue reading)

Permalink | Reply | 3 comments |
headers
Joachim Schrod | 1 Jul 2005 10:11
Picon
Favicon

Re: [xindy] no result

>>>>> "JS" == Jörg Sommer <joerg <at> alea.gnuu.de> writes:
JS> Joachim Schrod schrieb am Wed 29. Jun, 17:36 (+0200):

>> Does "xindy -V" produce any output?

JS> $ xindy -V
JS> xindy release: unknown
JS> xindy script version: 1.06

OK, then xindy isn't called at all.

As Gour wrote, it might simply be that xindy.run is not executable,
please check that first. I just checked that the xindy wrapper script
does not properly output error messages when calling xindy.run.

If if is executable, go into that lib directory and call:

    ./xindy.run -M xindy.mem

There should be the prompt "[1]> ". Type "(exit)" to exit.

Successful? Call it again. Type

    (xindy:startup :show-version t)

at the "[1]> " prompt. Output must look similar to

    xindy core version: 2.2-rc2-pre2
    xindy run time engine: ix86-linux-glibc22, version 2.2-rc2
    CLISP version 2.33.2 (2004-06-02) (built 3323871360) (memory 3324049660)
(Continue reading)

Permalink | Reply | 17 comments |
headers
Gour | 1 Jul 2005 10:09

Re: [xindy] no result

Joachim Schrod (jschrod <at> acm.org) wrote:

> A small clarification: just xindy.run needs +x, xindy.mem doesn't.

Nice to know. Binary distribution has flag on both.

Fixed (in my repo).

Sincerely,
Gour

--

-- 
Registered Linux User	| #278493
GPG Public Key		| 8C44EDCD

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
________________________________________________________________________
xindy-discuss mailing list -- general xindy announcements and discussions
Unsubscribe via https://lists.sourceforge.net/lists/listinfo/xindy-discuss
Permalink | Reply | 2 comments |
headers
Joachim Schrod | 1 Jul 2005 10:19
Picon
Favicon

Re: [xindy] no result

>>>>> "G" == Gour  <list <at> atmarama.org> writes:

G> Joachim Schrod (jschrod <at> acm.org) wrote:
>> A small clarification: just xindy.run needs +x, xindy.mem doesn't.

G> Nice to know. Binary distribution has flag on both.

Yes, I noticed this as well and saw that you took it from there.
Completely my fault.

But since I want to create my next binary distribution from your
source package, I thought it's best to change it at your side. :-)

	Joachim

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Joachim Schrod					Email: jschrod <at> acm.org
Roedermark, Germany

	``How do we persuade new users that spreading fonts across the page
	like peanut butter across hot toast is not necessarily the route to
	typographic excellence?''			-- Peter Flynn

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
________________________________________________________________________
(Continue reading)

Permalink | Reply | 1 comment |
headers
Joachim Schrod | 1 Jul 2005 10:43
Picon
Favicon

Re: [xindy] xindy-2.3-alpha4 tarball available

>>>>> "G" == Gour  <list <at> atmarama.org> writes:

> The remaining issues:

> - I have problems in making 'clisp' module dist-ready, so if someone
>   can write some rule for making clisp package dist-ready,

What is `dist-ready'? What is `make dist' supposed do?

>   I'll gladly include it in the distribution 'cause it will enable
>   us to have the present source distribution in the same structure
>   under e.g CVS.

Please note that I don't plan to put the whole CLISP in xindy's CVS. I
want to add make rules to create a source distribution from the CVS
tree, though. That would be the place for patches, changed Makefiles,
changed configures, etc.

The CVS tree has a completely different structure that is optimized
for development and work on single modules, and not for distribution
and generation. In particular, the Lisp sources are _not_ in one
directory, as they are in the distribution; each module has its own
directory. Besides, Imake and noweb is used in the development
enviroment, the sources have been striped of that demand for the
distribution.

> - unanswered questions regarding the rules for building
>   documentation in make-rules/alphabets

done in a previous email.
(Continue reading)

Permalink | Reply | 4 comments |
headers
Joachim Schrod | 1 Jul 2005 10:53
Picon
Favicon

Re: [xindy] xindy-2.3-alpha4 tarball available

>>>>> "G" == Gour  <list <at> atmarama.org> writes:

> Nothing has changed in rte/configure script, but you have to modify
> rte/configure not the main one 'cause the main configure just calls
> rte/configure and, at the moment, rte/configure does not check
> parameters from main configure - clisp is really a different beast and
> it is just a sub-package of the xindy distribution, i.e. it has
> separate build process not a part of the main one.

> So, modify rte/configure, line 26: clisp_modules='...'

If you apply the following patch to rte/configure, it will pass
arguments to CLISP:

--- ../xindy-rte-2.2.1/configure	2005-05-25 16:22:04.000000000 +0200
+++ configure	2005-07-01 10:49:48.858881573 +0200
 <at>  <at>  -9,9 +9,8  <at>  <at> 

 # Check that we're called without argument.

-if [ $# -gt 0 ]
-   then	echo 'usage: ./configure' >&2
-	echo '       No configuration options currently.' >&2
+if [ "$1" = '-?' ]
+   then	echo 'usage: ./configure [options-for-clisp]' >&2
 	exit 1
 fi

 <at>  <at>  -41,9 +40,9  <at>  <at> 
 cd ..
(Continue reading)

Permalink | Reply | 4 comments |
headers
Gour | 1 Jul 2005 11:26

Re: [xindy] source distribution & make-rules

Joachim Schrod (jschrod <at> acm.org) wrote:

> Sorry for the late answer, I'm deeply buried in work.

Well, I had some free slot (some serious work is awaiting me) so I took 
advantage :-)

> > a) what about modules/tex/isolatin*.xdy files
> 
> Please include them as is. They were created by Roger, and are not
> part of make-rules. They provide handling of traditional (manual
> input) TeX macros for many west-european characters. They will be
> replaced somewhere in the future.

OK. I included them in ..modules/tex folder.

Now, I've 'discovered'  few more, i.e.:

gour <at> gaura-nitai ~/prj/gnu/xindy-2.2/modules/rules $ ls -l
total 16
-rw-rw-r--  1 gour users 1618 May 21  2004 isolatin1-exchange.xdy
-rw-rw-r--  1 gour users 1223 May 21  2004 isolatin1-tolower.xdy
-rw-rw-r--  1 gour users 1318 May 21  2004 latin-exchange.xdy
-rw-rw-r--  1 gour users  966 May 21  2004 latin-tolower.xdy

Should they be put in ../modules/rules ?

And there is ../modules/letorder.xdy. What about that?

> > b) file ../inputenc/latin.xdy is not generated via make-inp-rules
(Continue reading)

Permalink | Reply | 1 comment |

Gmane