"Dr.-Ing. Dieter Jurzitza" <[email protected]> writes:

> I would like to start with a "happy New Year" to each of the
> listmembers.

Thanks, same to you as well.

> Let me describe the issue I am facing right now: I am attempting to
> build auctex 13.3 within the framework of the rpm - package build of
> openSUSE.

Sorry if my question is off, but is this for personal use or for the
opensuse distro?  Besides, why AUCTeX 13.3?  Current version is 14.1.0.

> this results in tons of error - messages like the following:
>
> ************************************************************
> *
> *
> Parsing hebrew_oldcode.sty...done
> Applying style hooks...
> Applying style hooks...done
> Parsing hebrew_p.sty...
> Parsing hebrew_p.sty...done
> Applying style hooks...
> Applying style hooks...done
> Parsing romanidx.sty...
> Parsing romanidx.sty...done
> Applying style hooks...
> Applying style hooks...done
> Parsing bibnames.sty...
> Font-lock trying to use keywords before setting them up
> error: Bad exit status from /var/tmp/rpm-tmp.kjLkIx (%install)
>
>
> RPM build errors:
>     Bad exit status from /var/tmp/rpm-tmp.kjLkIx (%install)
> ************************************************************

That rings a bell: I remember this report[1] which was in another setup,
and the solution was to put (font-lock-update) somewhere in the code.
Maybe you can apply that to your setup.

> It moans about the usage of keywords before they have been set up. If I 
> temporarily rename "bibnames.sty" it proceeds until it stumbles across the 
> next style - file causing issues. I guess this is not an auctex issue but an 
> emacs issue. 

As a sidenote, I really discourage letting AUCTeX parse all the .sty
files in your TeX distro.  The results will be more than questionable.

> However, can someone probably shed some light on this and (maybe) help
> me with a solution so I can build the new package?

I'm adding Werner Fink to this message, maybe he has some insight.

Best, Arash

Footnotes:
[1]  https://lists.gnu.org/archive/html/auctex/2023-03/msg00022.html

Reply via email to