Merry Christmas all,
I have been looking for a general PKGBUILD forum to get some help with some build problems.
I have been trying to build the mingw packages using makechrootpkg -c
I have built 436 out of 497 packages.
There are a few corrections I have to submit.
BUT
There are a few issues that are quite simply driving me nuts.
These PKGBUILD'S are supposed to have built at some point :}
I have come across an interesting error with mingw-w64-python-setuptools
Quite simply the package() function needs access to /tmp/
It uses wine to install the package. But the fakeroot wont allow wine access to /tmp/ ie -
wine: chdir to /tmp/.wine-0/server-841-4e2c3c : Permission denied
I have tried a few tricks - even invoking wineserver as a daemon at prepare()
this either freezes the build process - or cant access /build/.wine
Any clues or hints would be appreciated.
Thanks
Macca
On December 25, 2018 7:37:32 AM EST, hagar hagar@iinet.net.au wrote:
Merry Christmas all,
I have been looking for a general PKGBUILD forum to get some help with some build problems.
There's #archlinux-aur on irc.freenode.net and an Arch forum: https://bbs.archlinux.org/viewforum.php?id=38
I have been trying to build the mingw packages using makechrootpkg -c
I have built 436 out of 497 packages.
There are a few corrections I have to submit.
If you didn't know, you could do this through comments on the AUR packages.
-- Best, polyzen
On 26/12/18 3:19 am, Daniel M. Capella via aur-general wrote:
On December 25, 2018 7:37:32 AM EST, hagar hagar@iinet.net.au wrote:
Merry Christmas all,
I have been looking for a general PKGBUILD forum to get some help with some build problems.
There's #archlinux-aur on irc.freenode.net and an Arch forum: https://bbs.archlinux.org/viewforum.php?id=38
I have been trying to build the mingw packages using makechrootpkg -c
I have built 436 out of 497 packages.
There are a few corrections I have to submit.
If you didn't know, you could do this through comments on the AUR packages.
-- Best, polyzen
That part I knew.
I am even considering adopting a package or two.
But I was looking for some general PKGBUILD syntax and usage help.
Thanks
Macca
On 12/25/18 5:23 PM, hagar wrote:
That part I knew.
I am even considering adopting a package or two.
But I was looking for some general PKGBUILD syntax and usage help.
This list is one of the several places to get exactly such help. But "general syntax and usage help" is a suitably vague question such that no one can possibly help you, since no one knows what the issue is.
If you just want generic tutorials, the wiki has documentation on how PKGBUILDs work, and there have been Arch Classroom sessions on the topic as well.
Not sure what else you're looking for. :)
On 26/12/18 6:39 am, Eli Schwartz via aur-general wrote:
On 12/25/18 5:23 PM, hagar wrote:
That part I knew.
I am even considering adopting a package or two.
But I was looking for some general PKGBUILD syntax and usage help.
This list is one of the several places to get exactly such help. But "general syntax and usage help" is a suitably vague question such that no one can possibly help you, since no one knows what the issue is.
If you just want generic tutorials, the wiki has documentation on how PKGBUILDs work, and there have been Arch Classroom sessions on the topic as well.
Not sure what else you're looking for. :)
The original question was-
How do you access /tmp/ during the package() phase while in fakeroot?
Some programs require this access.(hardcoded)
Thanks
Macca
On 12/25/18 6:05 PM, hagar wrote:
On 26/12/18 6:39 am, Eli Schwartz via aur-general wrote:
On 12/25/18 5:23 PM, hagar wrote:
That part I knew.
I am even considering adopting a package or two.
But I was looking for some general PKGBUILD syntax and usage help.
This list is one of the several places to get exactly such help. But "general syntax and usage help" is a suitably vague question such that no one can possibly help you, since no one knows what the issue is.
If you just want generic tutorials, the wiki has documentation on how PKGBUILDs work, and there have been Arch Classroom sessions on the topic as well.
Not sure what else you're looking for. :)
The original question was-
How do you access /tmp/ during the package() phase while in fakeroot?
Some programs require this access.(hardcoded)
And there is nothing about fakeroot which prevents this.
In fact, I have just successfully run a package that executes `wine cmd dir` and it has successfully created both /tmp/.wine-0 and ~/.wine inside of a chroot.
...
Now, is your question about PKGBUILDs in general, or is it about wine in particular? Because if you want help about wine in particular, then it would be helpful to clearly distinguish this as the question.
On 26/12/18 7:24 am, Eli Schwartz via aur-general wrote:
On 12/25/18 6:05 PM, hagar wrote:
On 26/12/18 6:39 am, Eli Schwartz via aur-general wrote:
On 12/25/18 5:23 PM, hagar wrote:
That part I knew.
I am even considering adopting a package or two.
But I was looking for some general PKGBUILD syntax and usage help.
This list is one of the several places to get exactly such help. But "general syntax and usage help" is a suitably vague question such that no one can possibly help you, since no one knows what the issue is.
If you just want generic tutorials, the wiki has documentation on how PKGBUILDs work, and there have been Arch Classroom sessions on the topic as well.
Not sure what else you're looking for. :)
The original question was-
How do you access /tmp/ during the package() phase while in fakeroot?
Some programs require this access.(hardcoded)
And there is nothing about fakeroot which prevents this.
In fact, I have just successfully run a package that executes `wine cmd dir` and it has successfully created both /tmp/.wine-0 and ~/.wine inside of a chroot.
...
Now, is your question about PKGBUILDs in general, or is it about wine in particular? Because if you want help about wine in particular, then it would be helpful to clearly distinguish this as the question.
It is about the combination of both
I am only building using makechrootpkg -c
I have built other packages which use wine - no problem
But this package is using wine in the package() phase while the others did not, and falling over.
I was wondering if I had missed something?
thanks
Macca
Em dezembro 25, 2018 21:52 hagar escreveu:
It is about the combination of both
Whatever that means.
I am only building using makechrootpkg -c
That's fine, if your package is well defined
I have built other packages which use wine - no problem
Use wine where?
But this package is using wine in the package() phase while the others did not, and falling over.
If wine is in your depends=() array, it shouldn't be a problem.
I was wondering if I had missed something?
Without a log, it's hard to know. Try building with multilib-build instead of plain mkchrootpkg. I'm assuming this is a multilib package. If not, you can build with extra-x86_64-build.
Both these commands run namcap for each stage. You can send those plus your PKGBUILD and then we can start helping you. Without those, we're just guessing now.
Regards, Giancarlo Razzolini
aur-general@lists.archlinux.org