Package Details: openafs 1.8.7-1

Git Clone URL: (read-only, click to copy)
Package Base: openafs
Description: Open source implementation of the AFS distributed file system
Upstream URL:
Licenses: custom:"IBM Public License Version 1.0"
Conflicts: openafs-features
Submitter: None
Maintainer: Bevan
Last Packager: Bevan
Votes: 61
Popularity: 0.007974
First Submitted: 2006-02-01 17:18
Last Updated: 2021-01-15 08:34

Latest Comments

1 2 3 4 5 6 ... Next › Last »

gay commented on 2020-10-20 00:57

@Bevan: Thanks again for your help. Trying again a week later, the package compiled cleanly. Since the source has evidently not changed, the problem must have been something with my system last week. Perhaps something did not update correctly without me noticing.

Bevan commented on 2020-10-13 19:06

@gay: That's weird. I cannot reproduce this issue. Did you clean the build directory between the builds? Maybe there is a partial build still lying around from your earlier attempts?

gay commented on 2020-10-13 16:52

@Bevan: Thanks for the very quick reply and for pointing out that I am missing bison.

However, it seems that I receive the exact same error as reported below (even the addresses) with /usr/bin/yacc from bison 3.7.2-1 (the most recent version of bison), all of base-devel installed and all packages up to date.

It is, of course, possible that I am somehow missing something again.

A quick search reveals that similar errors have popped up periodically with openafs. (Apparently that was occasionally related to both byacc and bison being installed, but it's not that in my case.)

Bevan commented on 2020-10-13 14:21

@gay: the packages in the AUR assume that all packages from the base-devel group are installed: pacman -S base-devel

This also includes the bison package which contains yacc. byacc-bison in the AUR is an alternative implementation which seems to be missing some symbols required by openafs.

gay commented on 2020-10-13 14:04

I am having difficulty compiling this. Are there maybe missing dependencies? The make process complains about missing yacc. I tried installing byacc-bison from AUR that provides /usr/bin/yacc, but make is still not happy:

/usr/bin/ld: compile_et.o: in function `main':
compile_et.c:(.text+0x7f5): undefined reference to `yyin'
/usr/bin/ld: compile_et.c:(.text+0x813): undefined reference to `yyout'
/usr/bin/ld: compile_et.c:(.text+0x9d0): undefined reference to `yyout'
/usr/bin/ld: compile_et.c:(.text+0xc74): undefined reference to `yyin'
/usr/bin/ld: compile_et.o: in function `yyerror':
compile_et.c:(.text+0xf2e): undefined reference to `yylineno'
/usr/bin/ld: error_table.o: in function `yyparse':
error_table.c:(.text+0x9ab): undefined reference to `yylex'
/usr/bin/ld: error_table.c:(.text+0xefe): undefined reference to `yylex'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:39: compile_et] Error 1

nickoe commented on 2020-07-08 22:55

@Bevan, ok, thank you for looking into this and maintaining the package :)

Bevan commented on 2020-07-08 21:38

@nickoe: I had another look and I think there is not much we can do about that. The source code contains the __FILE__ macro in many places and the build system is written in a way that the source code location is given as absolute path to the compiler. It's mostly a cosmetic warning. A possible consequence is that certain error messages contain the path where the openafs package was built.

nickoe commented on 2020-07-07 11:52

@Bevan, ok no worries. I noticed this in a couple of packages by now. Maybe it is a new check that has been added to makepkg.

Bevan commented on 2020-07-07 11:38

@nickoe: Yes, for some reason the paths to some of the source files are included in those binaries / libraries. So far I just ignored this phenomenon - it does not really hurt. But I will see if I can find the root cause for this and if it is easily avoidable.

nickoe commented on 2020-07-07 11:30

I got this warning when building:

==> WARNING: Package contains reference to $srcdir