@nesk_aur base-devel, which includes bison
and patch
, is assumed to be installed when building packages. As per the wiki, this should not be in the makedepends
array.
Thanks for the information on aarch64. I've added it to the PKGBUILD.
Git Clone URL: | https://aur.archlinux.org/sc-im.git (read-only, click to copy) |
---|---|
Package Base: | sc-im |
Description: | A spreadsheet program based on SC |
Upstream URL: | https://github.com/andmarti1424/sc-im |
Licenses: | BSD |
Conflicts: | sc-im-git, scim-spreadsheet |
Submitter: | Rhinoceros |
Maintainer: | Rhinoceros (andmarti1424) |
Last Packager: | Rhinoceros |
Votes: | 54 |
Popularity: | 1.42 |
First Submitted: | 2015-09-05 01:44 (UTC) |
Last Updated: | 2021-11-05 00:36 (UTC) |
@nesk_aur base-devel, which includes bison
and patch
, is assumed to be installed when building packages. As per the wiki, this should not be in the makedepends
array.
Thanks for the information on aarch64. I've added it to the PKGBUILD.
Additional build-time deps: bison, patch. This pkg builds fine on aarch64.
@Rhinoceros Thanks!
@Strider85 You probably need to look upstream. It's likely not a packaging error. I just searched and found this.
Hi. I was getting the faulty segmentation error for many random cases (for external functions, mainly), even with the "external_functions" option set. Worked fine after downgrade to 0.8.1.0.
@GregTheMadMonk No worries at all. Easy error to make, and you aren't the first person to get confused by this. And I appreciate you posting here and attempting to improve the package too!
@Rhinoceros, oh, I see... My bad, sorry...
@GregTheMadMonk base-devel, which includes bison
, is assumed to be installed when building packages. As per the wiki, this should not be in the makedepends
array.
You should probably add bison
to make dependencies. yacc
(which is provided by bison
package) seems to be required during build (or, at least, it didn't build for me unless I've installed bison
)
Right you are, my bad.
@luukvbaal Works for me in a clean directory. Upstream changed their versioning, but I reflected the change in the new checksum. You probably have the old one cached by your AUR helper.
Getting
sc-im-0.8.0.tar.gz ... FAILED
arch.0.8.0.patch ... Passed
==> ERROR: One or more files did not pass the validity check!
please check.
@crossgear Sorry, I didn't mean the Markdown, but thanks for fixing up the formatting anyway. I actually meant the Warning: sc-im is only available from AUR
parts, etc., which I didn't recognise. The "basic" way to install is manually doing makepkg -s
, which excludes all the additional things that can go wrong when using an AUR helper to install packages. It's a good fallback test when things go wrong.
Having said that, I don't know anything about Manjaro really, so the issues might be related to different version or defaults of patch? Or more likely the paths where it builds packages? If you can't get it to build, it might be more helpful to ask at a Manjaro forum.
@Rhinoceros No, I've just never used Markdown before. I was redirected from Github to comment here. Never tried makepkg -s
, but I can try. Maybe worth noting that I'm running Manjaro.
@crossgear I just tried again and it works for me. What is all that extra text you posted? Are you using some AUR helper? Can you test with just a manual makepkg -s
?
When attempting to install, I get this error output:
Warning: sc-im is only available from AUR
Preparing...
Cloning sc-im build files...
Checking sc-im dependencies...
Resolving dependencies...
Checking inter-conflicts...
To build (1):
sc-im 0.7.0-2 AUR
Edit build files : [e]
Apply transaction ? [e/y/N] y
Building sc-im...
==> Making package: sc-im 0.7.0-2 (Wed 24 Feb 2021 07:25:11 PM CST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found sc-im-0.7.0.tar.gz
-> Found arch.patch
-> Found 258.patch
==> Validating source files with sha256sums...
sc-im-0.7.0.tar.gz ... Passed
arch.patch ... Passed
258.patch ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
-> Extracting sc-im-0.7.0.tar.gz with bsdtar
==> Starting prepare()...
can't find file to patch at input line 3
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
--------------------------
|--- Makefile.orig 2017-12-14 04:48:59.000000000 +1100
|+++ Makefile 2017-12-15 09:23:07.776195283 +1100
--------------------------
File to patch:
Skip this patch? [y] y
Skipping patch.
2 out of 2 hunks ignored
==> ERROR: A failure occurred in prepare().
Aborting...
Thank you @cloudhead. That works perfectly. Package updated.
gcc-8
is not needed if the -fcommon
flag is passed to gcc. Editing the PKGBUILD build()
phase to have:
build() {
cd "$pkgname-$pkgver/src"
make CC='gcc -fcommon'
}
Solves the problem for me.
Thanks @teleportex for all that information! I've updated the PKGBUILD. A few notes:
-C
flag with a clean directory.gcc8
was added to makedependsgnuplot
was added to optdepends, because the main functionality of sc-im
works without itThanks again.
I have ecnountered 2 problems when building:
Changes to the PKGBUILD:
build(){
cd "$pkgname-$pkgver"
make -C src CC=gcc-8
}
@Tymekm: That's true. yacc is provided by bison, which is part of base-devel. base-devel is assumed as an implicit dependency for building any package (see <https://wiki.archlinux.org/index.php/PKGBUILD#makedepends>). This is why bison is not included in the makedepends array. Seeing that you don't seem to have bison installed on your system, you might want to run pacman -S base-devel
.
[Sorry for cross-posting from sc-im-git, but this may be useful to know here as well.]
The build will fail without yacc.
yacc -d gram.y
make: yacc: Command not found
make: *** [Makefile:167: gram.c] Error 127
@Rhinoceros It does indeed look like it. Last comment suggests that trouble comes from "shared formulas", but these are so common in speadsheets!
@snake Looks like this? https://github.com/andmarti1424/sc-im/issues/218
Did anyone manage to make the --xlsx_readformulas option work? On my system it fails with a segmentation fault.
@terinjokes That's pretty straightforward for me to do, but I'm surprised that github.com would be reachable and githubusercontent.com wouldn't be?
Do you mind including the patch in the Git repo, rather than fetching it from GitHub? I was having issues fetching it this morning.
Thanks @tealeaf. Good call. I've patched with the pull request, changing the executable name. Please let me know if it works (I don't use the scim
package).
Ah, looks like an upstream change: https://github.com/andmarti1424/sc-im/pull/258
I notice that installing sc-im-git
creates a binary at /usr/bin/sc-im
, whilst this PKGBUILD produces /usr/bin/scim
. Is that a naming change upstream, or has the scim
name been implemented here?
The reason I ask is that /usr/bin/scim
is a file conflict with the scim
input method, which prevented me from installing both.
Looking at github, it does seem that the binary should be sc-im
.
@armanleftarm Thanks for the feedback. Done.
Add armv7h to the arch, builds proper on Samsung XE303C12
Good catch @aplund. Thank you and fixed.
Needs the following patch if BUILDDIR is set:
diff --git a/PKGBUILD b/PKGBUILD
index 800dc83
..3a25dda 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -20,7 +20,7 @@ MAKEFLAGS='-j1'
prepare() {
cd "$pkgname-$pkgver/src"
# install things in the correct place for package managers
- patch <../../../arch.patch
+ patch < "$srcdir/arch.patch"
}
build() {
Pinned Comments