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

Compiling under openSUSE 12.2 #32

Closed
gskillas opened this issue Oct 31, 2012 · 4 comments
Closed

Compiling under openSUSE 12.2 #32

gskillas opened this issue Oct 31, 2012 · 4 comments
Assignees
Milestone

Comments

@gskillas
Copy link

I am trying to compile the latest release-1.4 branch and I am getting the following errors:

guieditboundaryconditions.cpp: In member function ‘void GuiEditBoundaryConditions::setupSolvers()’:
guieditboundaryconditions.cpp:332:26: error: redeclaration of ‘MultiPageWidgetPage* page’
guieditboundaryconditions.cpp:312:3: error: ‘QString page’ previously declared here
make[2]: *** [release/guieditboundaryconditions.o] Error 1
make[2]: Leaving directory `/home/cfd/engrid/src/libengrid'
make[1]: *** [release] Error 2
make[1]: Leaving directory `/home/cfd/engrid/src/libengrid'
make: *** [sub-libengrid-libengrid-pro-make_default-ordered] Error 2

which branch should I use to compile under Linux?

Best regards,

George

@ghost ghost assigned ogloth Oct 31, 2012
@ogloth
Copy link
Contributor

ogloth commented Nov 2, 2012

Hello,

you must have used a fairly old source code, because the problem appears to have been fixed already. The variable "page", for example, is now called "page2".

I checked the current "release-1.4" branch on a fresh installation of openSUSE 12.2 and it compiled without any compiler errors. There have been a few problems related to the VTK paths, but no compiler errors.

Best regards,
Oliver

@ogloth ogloth closed this as completed Nov 2, 2012
@gskillas
Copy link
Author

gskillas commented Nov 3, 2012

This is strange. I used the update.bash script, which does a 'git pull'. Which did not work I found out. So yes the code was old. I recloned the repository and it worked.

kind Regards,

George

1 similar comment
@gskillas
Copy link
Author

gskillas commented Nov 3, 2012

This is strange. I used the update.bash script, which does a 'git pull'. Which did not work I found out. So yes the code was old. I recloned the repository and it worked.

kind Regards,

George

@wyldckat
Copy link
Collaborator

wyldckat commented Nov 3, 2012

Allow me to shine some light into this:
The compiler issue initially reported here, was already fixed in Issue #21, but it was only applied in the windows-1.4 branch back then ;)

As for the installation scripts, they were also up-to-date, but also only in the windows-1.4 branch. This is/was being tracked in Issue #29.

As soon as @ogloth merged windows-1.4 into release-1.4, (almost) all of these issues became instantaneously fixed :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants