-
Notifications
You must be signed in to change notification settings - Fork 15
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
unexpected symbol near '#' #1
Comments
Have you installed Qt 5 and run qmake as described in the build instructions? Looks rather that arch linux is interpreting the pro file like a normal script file which fails on line 2. |
When I run qmake from /usr/bin/qmake I get this error: /usr/bin/qmake LjBcViewer.pro |
Make clean, delete the Makefile and run "qmake LjBcViewer.pro" again; if it still has this issue (which is surprising since the include directive in the pro file has an alternative for this case which works on my machine) then delete the "include( /home/me/Desktop/LuaJIT-2.0.5/src/LuaJit.pri ) {...} part and replace it by "LIBS += -lluajit" only. EDIT: EDIT2: |
Thnaks for your help so far. I tried to run both of your files provided but both throw the following error: /LjBcViewer: error while loading shared libraries: libQt5PrintSupport.so.5: cannot open shared object file: No such file or directory |
Have you looked with ldd what else is missing? What Qt version is installed on your system? You need at least version 5, better even 5.4. On my Ubuntu version the QtPrintSupport is a separate installer package. And the 32 bit version is required. |
Qt 5.13.2 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC
9.2.0) on "xcb"
OS: Arch Linux [linux version 4.18.11-MagpieOS]
I will check on the print support.
…On Sun, Nov 10, 2019 at 9:21 AM Rochus Keller ***@***.***> wrote:
Have you looked with ldd what else is missing? What Qt version is
installed on your system? You need at least version 5, better even 5.4. On
my Ubuntu version the QtPrintSupport is a separate installer package. And
the 32 bit version is required.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1?email_source=notifications&email_token=AE3VKHCBKPY6MRBULCI6M3LQTARHRA5CNFSM4JLKXR52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDU7OTI#issuecomment-552204109>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE3VKHHQHVXE4PRM62LUO6DQTARHRANCNFSM4JLKXR5Q>
.
--
Joe Bill Schirtzinger
Beit Eshel Elder/Director
http://www.beitesheldonate.org | (270) 681-5728
http://www.theroyalrainbow.com
|
Ok, you have an x86-64 system. To run 32 bit binaries you also have to install the i386 versions of the binaries. Maybe it's easier if you continue to try to compile it yourself. I didn't compile it for 64 bits yet, but there is a good chance that it works ;-) |
Yeah I didn't notice the 32 although you clearly put it on there. I will try to wrangle with QT. It's pretty messy on my distro of arch at the moment. |
Did it work? Can I close the issue? |
No. It didn't work. You can go ahead and close the issue though because I
suspect QT is doing all manner of odd things and I don't have the time to
troubleshoot it the way I would need to to get the program to run.
…On Tue, Nov 12, 2019 at 4:00 AM Rochus Keller ***@***.***> wrote:
Did it work? Can I close the issue?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1?email_source=notifications&email_token=AE3VKHDTPRXQUXD7GR75PMTQTJ5EXA5CNFSM4JLKXR52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDZWKAY#issuecomment-552822019>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE3VKHDUW4PGS7CPZH4DQVDQTJ5EXANCNFSM4JLKXR5Q>
.
--
Joe Bill Schirtzinger
Beit Eshel Elder/Director
http://www.beitesheldonate.org | (270) 681-5728
http://www.theroyalrainbow.com
|
On arch linux derivative, get the following error via build instructions: /usr/local/bin/luajit LjBcViewer.pro /usr/local/bin/luajit: LjBcViewer.pro:2: unexpected symbol near '#'
The text was updated successfully, but these errors were encountered: