Skip to content
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

Paladin cannot compile projects on latest Haiku release, gives gcc errors. #382

Open
Dio9sys opened this issue Jul 6, 2022 · 2 comments
Labels
bug investigate Diagnose whether its a bug prior to classification

Comments

@Dio9sys
Copy link

Dio9sys commented Jul 6, 2022

Paladin cannot compile the example projects, even when the files have not been edited at all.

affected version: 2.5 d0, both the packaged version from pkgman and a compiled version utilizing the GNU DEBUG fix.

Steps to recreate:

  1. Install Paladin or compile from source.
  2. Create a new project. For the sake of simplicty, you can test with "GUI with main window" from the Project Type dropdown
    2a. Be aware, if you installed paladin with pkgman you may need to run chmod +700 on your Projects folder, as the packaged version sets your project folder to read only by default.
  3. build the project, either through the GUI or through alt+r

Observe the following errors:

g++: error trying to exec 'cc1plus': execvp: No such file or directory
g++: error trying to exec 'cc1plus': execvp: No such file or directory
g++: error trying to exec 'cc1plus': execvp: No such file or directory
g++: error trying to exec 'cc1plus': execvp: No such file or directory
g++: error: /boot/home/Projects/app/(Objects.app)/App.o: No such file or directory
g++: error: /boot/home/Projects/app/(Objects.app)/MainWindow.o: No such file or directory

@mbrumbelow
Copy link
Collaborator

Is this still valid?

@mbrumbelow mbrumbelow added bug investigate Diagnose whether its a bug prior to classification labels Mar 6, 2024
@Dio9sys
Copy link
Author

Dio9sys commented Apr 29, 2024

I haven't checked on the latest dev build yet. I later found that I could fix the problem if I chmod'd the project files to have full read/write permission. Something was changing in the file permissions when I would edit through paladin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug investigate Diagnose whether its a bug prior to classification
Development

No branches or pull requests

2 participants