New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Latest update through PAMAC on Stable Manjaro fails #1366
Comments
Also affects the 2.4.0 tarball on openSUSE Tumbleweed, I created a pull request based on the compiler suggestion that seems to fix the issue. |
Not sure if things turn around this fast, but I just tried again and I got this:
|
You can check the GIt history/PR status to check if things have been fixed. This is a volunteer project... so I wouldn't expect it to be an instant fix.
…On Wed, Nov 3, 2021, at 7:57 AM, Zeddock wrote:
Not sure if things turn around this fast, but I just tried again and I got this:
`Preparing...
Cloning barrier-git build files...
Generating barrier-git information...
Checking barrier-git dependencies...
Synchronizing package databases...
Resolving dependencies...
Checking inter-conflicts...
Building barrier-git...
==> Making package: barrier-git v2.4.0+4+gac5a1bfd-1 (Wed 03 Nov 2021
03:55:38 AM EDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Updating barrier-git git repo...
Fetching origin
==> Validating source files with sha512sums...
barrier-git ... Skipped
==> Removing existing $srcdir/ directory...
==> Extracting sources...
-> Creating working copy of barrier-git git repo...
Cloning into 'barrier-git'...
done.
==> Starting prepare()...
==> Starting pkgver()...
==> Removing existing $pkgdir/ directory...
==> Starting build()...
/var/tmp/pamac-build-jim/barrier-git/PKGBUILD: line 58: float*: command
not found
==> ERROR: A failure occurred in build().
Aborting...
`
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1366 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKF2QBI7LTGF62HCKB7M4TUKD2Q3ANCNFSM5HG3XKTQ>.
--
Kind regards,
--
Dom Rodriguez (also known as shymega)
|
I am not expecting an instant fix at all. I just thought it was fixed because it acted differently when I tried it again. Here is why. I now get this error, which is much different!
|
Since the previous was closed, I opened this new one to cover the new
missing reference.
#1406
Jim
* Jim*Garner *304-933-9858*
* www.Ground*Scouts.com
…On Wed, Nov 3, 2021 at 4:58 PM Povilas Kanapickas ***@***.***> wrote:
Closed #1366 <#1366> via
4b12265
<4b12265>
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1366 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGKYJWP6ZPBZXSOOKTIF5BLUKGO6LANCNFSM5HG3XKTQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
What happened?
upon building I get this:
I truly hope this is helpful as I fully support and encourage this application. If you need more info I will be happy to help with details, but I am limited in understanding.
Version
v2.3.3
Git commit hash (if applicable)
'7d33fee11ec480beae4c28ad09ca56d974140a72' and '800f5422ac9d9e0ad59cd860a2ef3a679588acb4' and '614bbe87b80435d87ab8791564370e0c1d13627d'
If applicable, where did you install Barrier from?
Pamac Gui
What OSes are you seeing the problem on? (Check all that apply)
Linux
What OS versions are you using?
Operating System: Manjaro Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.14.10-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-6700 CPU @ 3.40GHz
Memory: 15.6 GiB of RAM
Graphics Processor: AMD Radeon ™ RX 480 Graphics
Relevant log output
Any other information
No response
The text was updated successfully, but these errors were encountered: