From: Julien Lepiller <julien@lepiller.eu>
To: 32947@debbugs.gnu.org, maximedevos@telenet.be, frank.pursel@gmail.com
Subject: [bug#32947] Add java-xalan.
Date: Tue, 22 Mar 2022 19:18:11 +0100 [thread overview]
Message-ID: <748F479C-EE10-4720-BF39-525589A2AD50@lepiller.eu> (raw)
In-Reply-To: <fd01542ad871b18187a61763d06916d1f2ceda16.camel@telenet.be>
On March 22, 2022 6:45:15 PM GMT+01:00, Maxime Devos <maximedevos@telenet.be> wrote:
>Maxime Devos schreef op vr 18-03-2022 om 21:07 [+0100]:
>> I've been reading the source code, not seeing anything
>> ‘suspicous’ (malware etc.) so far (I'm currently at
>> xalan-j_2_7_2/src/org/apache/xalan/templates/FuncKey.java, 25%).
>
>Now I'm at 42% (src/org/apache/xalan/xsltc/compiler/XPathLexer.java).
>I've found two binaries (*):
>
> * src/org/apache/xalan/xsltc/compiler/XPathLexer.java
> * src/org/apache/xalan/xsltc/compiler/XPathParser.java
>
>They appear to be generated by a lexer and parser generator --
>apparently it's named ‘java_cup’? Given that they are in the 'xsltc'
>part, which is currently unused in the java-xalan package IIUC, I
>believe it would be sufficient to just delete these two files.
To add to your comment. I've encountered java_cup in tge past. It's not bootstrappable as far as I can see. It has a dependency on jflex and itself, and jflex requires itself and java_cup. I looked at the first commit of jflex, and it already depends on itself (but not cup). According to the devs, chey used a hand-written lexer that was too aweful to commit, and so we can't rebuild jflex.
If someone is interested, they would have to write a lexer for an early version of jflex :)
>
>(*) Here I mean 'binaries'='generated, not source code' -- it's still
>.java and not .class.
>
>Greetings,
>Maxime.
next prev parent reply other threads:[~2022-03-22 18:20 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 15:18 [bug#32947] [PATCH 0/3] Add java-xalan Danny Milosavljevic
2018-10-05 15:20 ` [bug#32947] [PATCH 1/3] gnu: Add java-cup Danny Milosavljevic
2018-10-05 15:20 ` [bug#32947] [PATCH 2/3] gnu: Add java-jakarta-regexp Danny Milosavljevic
2018-10-05 15:20 ` [bug#32947] [PATCH 3/3] gnu: Add java-xalan Danny Milosavljevic
2018-10-05 15:46 ` Julien Lepiller
2018-10-05 15:28 ` [bug#32947] [PATCH 1/3] gnu: Add java-cup Julien Lepiller
2018-10-05 16:00 ` Danny Milosavljevic
2018-10-05 16:13 ` Julien Lepiller
2018-10-05 15:52 ` Julien Lepiller
2018-12-19 14:05 ` [bug#32947] Add java-xalan Julien Lepiller
2022-03-17 21:08 ` Frank Pursel
2022-03-17 21:50 ` Maxime Devos
2022-03-17 21:53 ` Maxime Devos
2022-03-17 21:57 ` Maxime Devos
2022-03-18 17:40 ` Maxime Devos
2022-03-18 18:15 ` Frank Pursel
2022-03-18 18:22 ` Frank Pursel
2022-03-18 19:19 ` Maxime Devos
2022-03-18 17:29 ` Frank Pursel
2022-03-18 17:59 ` Maxime Devos
2022-03-18 19:16 ` Frank Pursel
2022-03-18 20:07 ` Maxime Devos
2022-03-18 20:42 ` Frank Pursel
2022-03-19 15:58 ` Maxime Devos
2022-03-22 17:45 ` Maxime Devos
2022-03-22 18:18 ` Julien Lepiller [this message]
2022-03-30 17:43 ` Maxime Devos
2022-03-30 18:41 ` Maxime Devos
2022-03-30 20:23 ` Frank Pursel
2022-04-03 8:32 ` Maxime Devos
2022-04-05 13:12 ` Maxime Devos
2022-04-05 21:09 ` Frank Pursel
2022-04-09 13:40 ` Maxime Devos
2022-04-11 16:36 ` Frank Pursel
2022-04-12 9:32 ` Maxime Devos
2022-04-13 23:43 ` Frank Pursel
2022-04-14 8:30 ` Maxime Devos
2022-04-14 16:07 ` Frank Pursel
2022-04-14 20:33 ` Maxime Devos
2022-04-14 20:49 ` Frank Pursel
2022-04-16 21:02 ` Maxime Devos
2022-04-19 17:13 ` Frank Pursel
2022-04-19 18:44 ` Maxime Devos
2022-04-19 18:55 ` Frank Pursel
2022-03-19 15:41 ` Frank Pursel
2022-03-19 16:38 ` Frank Pursel
2022-03-23 1:32 ` Frank Pursel
2022-03-23 14:14 ` Frank Pursel
2022-08-19 22:05 ` Vagrant Cascadian
2022-06-24 15:23 ` [bug#32947] [PATCH 0/3] Add java-xalan: reverse ping Maxime Devos
2022-07-14 23:46 ` [bug#32947] [PATCH 0/3] Add java-xalan Frank Pursel
2022-08-20 0:57 ` [bug#32947] Add java-xalan-interp Frank Pursel
2022-09-20 21:25 ` [bug#32947] Add java-xalan-interp CVE Frank Pursel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=748F479C-EE10-4720-BF39-525589A2AD50@lepiller.eu \
--to=julien@lepiller.eu \
--cc=32947@debbugs.gnu.org \
--cc=frank.pursel@gmail.com \
--cc=maximedevos@telenet.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).