Package Details: rstudio-desktop 2025.05.0.496-1

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.57
First Submitted: 2011-03-04 15:02 (UTC)
Last Updated: 2025-05-12 06:23 (UTC)

Dependencies (36)

Required by (0)

Sources (4)

Pinned Comments

xiota commented on 2025-03-01 05:16 (UTC) (edited on 2025-05-01 20:46 (UTC) by xiota)

Packaging notes:

  • Given the inconvenience of having this package become unusable for an indefinite amount time, sodeps are used to prevent boost upgrades from breaking this package. Others may be added. Updates may need to be forced with pacman -Syudd prior to rebuilding. This is unnecessary when building in a clean chroot.
  • Any variable declared : ${var:=value} can be set in the environment prior to build.
    • For example: var=value makepkg -rsC; Method for AUR helpers may vary.
    • For clean chroot, try something like: extra-x86_64-build -- var=value

Problems?

  • Try building in a clean chroot.
  • If your distro has delayed updates, you may need to wait a few weeks.
  • Avoid commenting and flagging for the same issue at the same time.
    • Flag for routine and mechanical issues (depends, typos, mistakes, etc)
    • Comment for issues requiring discussion.
    • Please use a pastebin for blocks of text more than a few lines.

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 31 Next › Last »

trap000d commented on 2024-05-28 10:25 (UTC)

@xiota, Unfortunately, your trick with LDFLAGS didn't work for me. After few more build iterations with various combinations of flags and options, I suppose the only working option is to disable LTO for soci.

You can find updated PKGBUILD here: https://github.com/trap000d/aur/tree/master/soci

as well as new RStudio pkgrel: https://github.com/trap000d/aur/tree/master/rstudio-desktop

So I'm going to write to soci AUR maintainer and ask to add '!lto' option.

Could you please test my variants of these packages before? There is a probability I've missed something, or changed some new default makepkg settings accidentally.

Possible alternatives are:

trap000d commented on 2024-05-28 08:44 (UTC)

@xiota, On my side I've just managed to build the package by disabling lto in both rstudio-desktop and soci PKGBUILDs. It looks like when link time optimization is on, some information about exports/locations is missed. On the other hand, your proposed workaround looks good too (at least it should work in any environment and would not require to make changes in multiple packages).

P.S. I have some ideas to optimize the build process. I planned to postpone them until the next rstudio release. Now I think it might be a good idea to roll them out, as I'll have to push a new pkgrel anyway. Just let me test if your ld flags work as expected.

trap000d commented on 2024-05-28 04:41 (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.

trap000d commented on 2024-05-28 03:47 (UTC) (edited on 2024-05-28 04:19 (UTC) by trap000d)

@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)

trap000d commented on 2024-05-28 03:17 (UTC)

@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.

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 31 Next › Last »