From: Luis Felipe <sirgazil@zoho.com>
To: "Simen Endsjø" <contact@simendsjo.me>, help-guix@gnu.org
Subject: Re: Building mysql-workbench-community cannot find cairo.h
Date: Mon, 21 Oct 2024 18:36:43 +0000 [thread overview]
Message-ID: <908ed5dc-5441-45e8-a5e9-188257ceb072@zoho.com> (raw)
In-Reply-To: <87784640-6cd3-459e-a5cf-5d706f6d304f@app.fastmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 2926 bytes --]
Hi Simen,
On 20/10/24 16:41, Simen Endsjø wrote:
> Hi, I need some help packaging mysql-workbench.
>
> I'm using
> https://git.sr.ht/~yewscion/yewscion-guix-channel/tree/trunk/item/cdr255/utils.scm#L985
> as a base. That channel doesn't work, but it seems pretty complete although
> maybe not 100% up to date.
>
> I pushed my changes to a branch in case someone want to give it a go:
> https://codeberg.org/simendsjo/dotfiles/src/branch/wip-mysql-package/sijo/packages/mysql.scm#L117
>
> When trying to build this, I get an error:
> /tmp/guix-build-mysql-workbench-community-8.0.40-1.a7478f6.drv-0/source/library/forms/swig/cairo.i:180: Error: Unable to find 'cairo/cairo.h'
I'm not familiar with building MySQL Workbench, but I get a different
error while trying to build it from your branch:
#+begin_example
$ guix build -L . --cores=1 mysql-workbench-community
...
[ 47%] [mysql] Generating parser files...
cd
/tmp/guix-build-mysql-workbench-community-8.0.40-1.a7478f6.drv-0/source/library/parsers/grammars
&& /gnu/store/71aka05f0ldz2x3wf3491iz488qxgqk3-icedtea-2.6.13/bin/java
-Xmx1024m -jar
/gnu/store/zbzixk2v8vnc0i4xzg73q8f3lfm0ybw3-antlr4-4.10.1/share/java/antlr4.jar/antlr-4.13.2-complete.jar
-Dlanguage=Cpp -listener -visitor -o ../mysql -package parsers
/tmp/guix-build-mysql-workbench-community-8.0.40-1.a7478f6.drv-0/source/library/parsers/grammars/MySQLLexer.g4
/tmp/guix-build-mysql-workbench-community-8.0.40-1.a7478f6.drv-0/source/library/parsers/grammars/MySQLParser.g4
Error: Unable to access jarfile
/gnu/store/zbzixk2v8vnc0i4xzg73q8f3lfm0ybw3-antlr4-4.10.1/share/java/antlr4.jar/antlr-4.13.2-complete.jar
make[2]: ***
[library/parsers/CMakeFiles/generate_parser_mysql.dir/build.make:90:
/tmp/guix-build-mysql-workbench-community-8.0.40-1.a7478f6.drv-0/source/library/parsers/mysql/MySQLLexer.h]
Error 1
make[2]: Leaving directory
'/tmp/guix-build-mysql-workbench-community-8.0.40-1.a7478f6.drv-0/build'
make[1]: *** [CMakeFiles/Makefile2:1986:
library/parsers/CMakeFiles/generate_parser_mysql.dir/all] Error 2
make[1]: Leaving directory
'/tmp/guix-build-mysql-workbench-community-8.0.40-1.a7478f6.drv-0/build'
make: *** [Makefile:139: all] Error 2
error: in phase 'build': uncaught exception:
%exception #<&invoke-error program: "make" arguments: ("-j" "1")
exit-status: 2 term-signal: #f stop-signal: #f>
phase `build' failed after 980.0 seconds
command "make" "-j" "1" failed with status 2
build process 6 exited with status 256
#+end_example
I'm not using the channel you pointed to, though, only the mysql.scm
module from your repository and the rest of the packages from the Guix
channel.
Also, even though MySQL Workbench fails to build, the other packages in
the module build correctly, look like free software and useful in their
own, so maybe those can be contributed already to Guix?
Cheers,
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2881 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
prev parent reply other threads:[~2024-10-21 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-20 16:41 Building mysql-workbench-community cannot find cairo.h Simen Endsjø
2024-10-21 18:36 ` Luis Felipe [this message]
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=908ed5dc-5441-45e8-a5e9-188257ceb072@zoho.com \
--to=sirgazil@zoho.com \
--cc=contact@simendsjo.me \
--cc=help-guix@gnu.org \
/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.
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).