| Git Clone URL: | https://aur.archlinux.org/rstudio-desktop.git (read-only, click to copy) |
|---|---|
| Package Base: | rstudio-desktop |
| Description: | A powerful and productive integrated development environment (IDE) for R programming language |
| Upstream URL: | https://github.com/rstudio/rstudio |
| Licenses: | AGPL-3.0-only |
| Conflicts: | rstudio-desktop |
| Provides: | rstudio-desktop |
| Submitter: | None |
| Maintainer: | xiota |
| Last Packager: | xiota |
| Votes: | 73 |
| Popularity: | 0.052003 |
| First Submitted: | 2011-03-04 15:02 (UTC) |
| Last Updated: | 2024-11-11 05:37 (UTC) |
Gotcha!!!
Yes, it sounds as problem with soci-debug. I've built soci-debug and then fed rstudio-desktop chroot with it, then it showed pretty the same error @xiota and @mrhooman reported.
I would suggest to override it either by disabling of debug option in your /etc/makepkg.conf
or remove soci-debug package before building of rstudio-desktop.
@xiota,
makechrootpkg -c -u -r $CHROOT -I soci-4.0.3-1-x86_64.pkg.tar.zst -I quarto-cli-1.4.554-1-x86_64.pkg.tar.zst
..........
==> Creating package "rstudio-desktop"...
-> Generating .PKGINFO file...
-> Generating .BUILDINFO file...
-> Generating .MTREE file...
-> Compressing package...
==> Creating package "rstudio-desktop-debug"...
-> Generating .PKGINFO file...
-> Generating .BUILDINFO file...
-> Generating .MTREE file...
-> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: rstudio-desktop 2024.04.1.748-3 (Tue May 28 15:31:21 2024)
Several notes.
Indeed, I've got 2 packages now: release and debug. I could spot /usr/src/debug lines during the build process. Anyway I didn't have any build issues. Here I assume there is something in either repository or your chroot environment (see below).
Sorry, @mrhooman, looks like you've got something somewhere else. Something wrong with soci. Hmm, try to rebuild then reinstall soci?
For thousands warnings about _FORTIFY_SOURCE I suppose there is a definition mismatch between root and user chroot environment. My own arch chroot has been set up a year ago (Jun 2023) and has -D_FORTIFY_SOURCE=2 in /etc/makepkg.conf, whereas fresh build environment has -D_FORTIFY_SOURCE=3
I'm just wondering if total chroot directory removal and re-creation could magically fix this? I'll try (anyway it makes sense to renew the build environment at least once a year).
UPD: rstudio-2024.04.1-748/src/cpp/CMakeLists.txt
OK. They have forced it to 2, which causes a clash with new /etc/makepkg.conf
if(NOT APPLE)
add_definitions(-Wformat -Wformat-security)
add_definitions(-D_FORTIFY_SOURCE=2)
@xiota,
options=(debug) doesn't explain how files appeared in the system directory before installation of package. Something must run sudo blahblah after makepkg successfully finishes the job.
@xiota,
Yep, there is always a chance some dependencies are missed. I still think this is something related to unofficial repository. Hope I'm wrong.
For soci, I've looked inside CMakeFiles. The message SOCI libraries found under is correct and means 'soci is found and is in the right place' - Rstudio developers simply forgot to format it properly.
I'll give build a try in clean chroot a bit later then let you know of results.
@mrhooman,
https://paste.ee/p/b0dQi#s=1&l=1620
/usr/src/debug/rstudio-desktop/rstudio-2024.04.1-748/src/cpp/shared_core/include/shared_core/Logger.hpp:89: warning: type ‘rstudio::core::log::LogLevel’ violates the C++ One Definition Rule [-Wodr]
Please try to find out how you've managed to place rstudio source files into /usr/src/debug directory? And why? Do you have any custom PATH or LD_LIBRARY_PATH definitions? Do you have anything manually installed into e.g. /usr/local/{bin,lib,share} ?
P.S. Here I assume your Arch installation is somehow broken (fatally?) I could only recommend to make your experiments either with fresh installation or in clean chroot.
Pinned Comments
trap000d commented on 2024-05-16 21:42 (UTC) (edited on 2024-05-28 20:09 (UTC) by trap000d)
A note for users.
This package is quite complex. It MAY not be built because of OTHER issues. I always build, install and test it on at least two different machines. Only after that I would push a new version to AUR.
Please try some generic solutions before reporting of build problems:
1) Update all other packages (sudo pacman -Syu),
2) Clean up yay and/or makepkg caches ('yay -Sc', 'rm -rf /var/tmp/makepkg'),
3) Be sure you've got enough RAM (8 GB or more is highly recommended) and space on disk (at least 3 GB).
4) Is your Internet connection is stable, fast and not blocked somewhere?
trap000d commented on 2022-07-05 20:32 (UTC) (edited on 2022-10-03 06:28 (UTC) by trap000d)
PLEASE READ THIS MESSAGE BEFORE COMPLAINING FOR LIBBOOST
When boost is updated to a new version and you see an error message about missing libboost*.so, you will need to rebuild and reinstall the rstudio-desktop package.
trap000d commented on 2022-02-19 06:20 (UTC) (edited on 2022-02-19 06:21 (UTC) by trap000d)
Build logic is slightly changed due to changes in upstream. As they've introduced new project format (quarto), it contradicted with standard Arch package base. In brief, quarto contains pandoc as part of itself, so it's pretty hard to keep together system pandoc and embedded quarto.
So I've "resolved" it such way: if there is "quarto*" package installed, then rstudio-desktop will pick it up and use. Otherwise (not installed), quarto support in rstudio will be disabled.
'quarto' is added as optional dependency.