One can get the same error by running `makepkg --nobuild && makepkg --noextract`. So it is not an error of pacaur.
The error is in the PKGBUILD not in pacaur or makepkg. The line
unset CPPFLAGS CFLAGS
has to be moved to the build() function to be used even if prepare() is not called.
Search Criteria
Package Details: hfsutils 3.2.6-11
| Git Clone URL: | https://aur.archlinux.org/hfsutils.git (read-only) |
|---|---|
| Package Base: | hfsutils |
| Description: | A comprehensive software to permit manipulation of HFS volumes |
| Upstream URL: | http://www.mars.org/home/rob/proj/hfs/ |
| Keywords: | hfs hfs+ mac OSX |
| Licenses: | |
| Submitter: | frony0 |
| Maintainer: | Jristz |
| Last Packager: | Jristz |
| Votes: | 42 |
| Popularity: | 0.945179 |
| First Submitted: | 2013-03-27 13:16 |
| Last Updated: | 2017-05-29 05:40 |
Dependencies (3)
Required by (0)
Sources (5)
Latest Comments
kolewu commented on 2017-05-28 20:25
severach commented on 2017-03-28 17:49
Pacaur is not running prepare. The patches are skipped and CFLAGS are left original. You can get the same errors from makepkg by disabling prepare.
jarerod commented on 2017-03-28 17:01
So how exactly so I get this to install? I keep getting this. https://paste.opensuse.org/view/raw/74041580
And I'm not sure how to go about tweaking this...
jamesan commented on 2017-03-17 18:59
I was getting the same build error as ashaman-crypto and s0nspark:
In file included from hfsutil.c:23:0:
config.h:35:16: error: duplicate ‘unsigned’
and started looking into the most recent PKGBUILD change (commit e627ddc) when the error spontaneously stopped occurring. Now, the package builds both with and without the CFLAGS being unset in the prepare() function and it builds whether I initiate it using yaourt or manually using makepkg. I don't know how this happened...
s0nspark commented on 2017-03-16 12:52
I am on x86_64...
Jristz commented on 2017-03-14 06:45
@s0nspark and that why I hate this package sometimes, it build fine here now that I unset the flags... do you run this on a i686 or an x86_64?
s0nspark commented on 2017-03-13 17:42
I'm getting the same build error as ashaman-crypto with build 9 of this package. It looks to me as if the only change between build versions is that CFLAGS is now being unset in addition to CPPFLAGS... The previous version builds without issue for me.
Jristz commented on 2017-03-13 01:10
thanks @ashaman-crypto
this package is really annoyingly trickly tricky to build since it can build ok and then not rebuild for no aparent reason and sometimes build with all the flags and then not or just woth some flags.
It will take sometime to try find anew fix or patch, so anythink is welcome (maybe even fork it).
ashaman-crypto commented on 2017-03-13 01:04
Getting a build error. http://pastebin.com/pAx2Bn9r
mir91 commented on 2016-12-08 14:44
makepkg will fail if the path of the file path you're currently residing in when invoking makepkg contains spaces.