• Website
  • Search
  • Member List
  • Help
  • Old Forum
  • Social Media
    •   @Wings3dOfficial
    •   @Wings3dOfficial
    •   Wings3dOfficial
    •   Wings3dOfficial
  • Register
  • Login
  • Website
  • Search
  • Member List
  • Help
  • Old Forum
  • Register
  • Login
Wings 3D Development Forum Wings 3D Bug Reports v
« Previous 1 … 20 21 22 23 24 … 35 Next »
[Linux][2.0.3] wings.erl compile error

 
  • 0 Vote(s) - 0 Average
[Linux][2.0.3] wings.erl compile error

Pages (2): 1 2 Next »
LousyLynx
Offline

Junior Member

Posts: 7
Threads: 2
Joined: Apr 2016
#1
04-16-2016, 12:27 AM (This post was last modified: 04-16-2016, 02:17 PM by LousyLynx.)
Hello. I have spoken to Dan G. about getting 2.0.3, and he said that I need to build it myself, due to a wxWidgets error. So I have been trying to build it, but I have run into this error:

Code:
(cd intl_tools; make)
make[1]: Entering directory `/home/<user>/wings-2.0.3-Src/intl_tools'
make TYPE=opt common
make[2]: Entering directory `/home/<user>/wings-2.0.3-Src/intl_tools'
make[2]: Nothing to be done for `common'.
make[2]: Leaving directory `/home/<user>/wings-2.0.3-Src/intl_tools'
make[1]: Leaving directory `/home/<user>/wings-2.0.3-Src/intl_tools'
(cd src; make)
make[1]: Entering directory `/home/<user>/wings-2.0.3-Src/src'
make TYPE=opt common
make[2]: Entering directory `/home/<user>/wings-2.0.3-Src/src'
erlc -Werror -I ../e3d +debug_info '-Dwings_version="1.2.x.y.WINGS"' -pa ../intl_tools  -o../ebin wings.erl
wings.hrl:161: referring to built-in type queue as a remote type; please take out the module name
wings.hrl:178: referring to built-in type array as a remote type; please take out the module name
wings.hrl:179: referring to built-in type array as a remote type; please take out the module name
wings.hrl:180: referring to built-in type array as a remote type; please take out the module name
wings.hrl:182: referring to built-in type set as a remote type; please take out the module name
wings.hrl:183: referring to built-in type array as a remote type; please take out the module name
wings.hrl:185: referring to built-in type array as a remote type; please take out the module name
make[2]: *** [../ebin/wings.beam] Error 1
make[2]: Leaving directory `/home/<user>/wings-2.0.3-Src/src'
make[1]: *** [opt] Error 2
make[1]: Leaving directory `/home/<user>/wings-2.0.3-Src/src'
make: *** [all] Error 2

After running `erl -make` in the `src` directory, this is the output:

Code:
Recompile: wings
wings.erl: undefined parse transform 'tools'
I have no clue what line that is, but I know its an error with `wings.erl`.
micheus
Offline

Forum's Admin and Support | Bug fixer
Posts: 3,676
Threads: 183
Joined: Jun 2012
#2
04-16-2016, 03:30 AM
Which version of Erlang are you using? You must install the latest one.
I got this kind of message when I was trying to use an old one.
[Image: tw.png] @MicheusVieira [Image: yt.png] @MicheusVieira [Image: da.png] Micheuss [Image: ig.png] micheus4wings3d
* Wings3D Team stands for: Björn and Dan
LousyLynx
Offline

Junior Member

Posts: 7
Threads: 2
Joined: Apr 2016
#3
04-16-2016, 11:38 AM (This post was last modified: 04-16-2016, 11:54 AM by LousyLynx.)
When I did `erl -version` this was the output:

Code:
Erlang (SMP,ASYNC_THREADS) (BEAM) emulator version 5.10.4

UPDATE

I updated my erlang, now I have this error while building:

Code:
wings_dialog.erl:15: can't find include lib "wings/e3d/e3d_image.hrl"
wings_dialog.erl:1523: record e3d_image undefined
make[2]: *** [../ebin/wings_dialog.beam] Error 1
make[2]: Leaving directory `/home/<user>/wings-2.0.3-Src/src'
make[1]: *** [opt] Error 2
make[1]: Leaving directory `/home/<user>/wings-2.0.3-Src/src'
make: *** [all] Error 2
ggaliens
Offline

Erlang Hacker
Posts: 954
Threads: 143
Joined: Nov 2012
#4
04-16-2016, 12:50 PM
I got that error the other day ...

If you wings folder is here

/home/bob/wings

then do

ERL_LIBS="/home/bob"
export ERL_LIBS
LousyLynx
Offline

Junior Member

Posts: 7
Threads: 2
Joined: Apr 2016
#5
04-16-2016, 02:12 PM (This post was last modified: 04-16-2016, 02:18 PM by LousyLynx.)
(04-16-2016, 12:50 PM)ggaliens Wrote: I got that error the other day ...

If you wings folder is here

/home/bob/wings

then do

ERL_LIBS="/home/bob"
export ERL_LIBS

Thank you! This made my build work past that error. Now I have come across this error:

Code:
escript tools/verify_language_files .
escript tools/release
error:{badmatch,{error,badarg}} in [{release__escript__1460__816114__899206__2,
                                     copy_app,2,
                                     [{file,"tools/release"},{line,178}]},
                                    {release__escript__1460__816114__899206__2,
                                     '-release_otp/1-lc$^0/1-0-',2,
                                     [{file,"tools/release"},{line,141}]},
                                    {release__escript__1460__816114__899206__2,
                                     release_otp,1,
                                     [{file,"tools/release"},{line,141}]},
                                    {release__escript__1460__816114__899206__2,
                                     unix_release,2,
                                     [{file,"tools/release"},{line,82}]},
                                    {release__escript__1460__816114__899206__2,
                                     main,1,
                                     [{file,"tools/release"},{line,22}]},
                                    {escript,run,2,
                                     [{file,"escript.erl"},{line,757}]},
                                    {escript,start,1,
                                     [{file,"escript.erl"},{line,277}]},
                                    {init,start_it,1,[]}]
ggaliens
Offline

Erlang Hacker
Posts: 954
Threads: 143
Joined: Nov 2012
#6
04-16-2016, 02:40 PM
Make sure that ERL_LIBS and export have the proper level of visibility throughout your shells and build session.

I had min in my .profile

so that when I started a new shell. It would get defined. Then I tried putting it in my launch script and somehow that was not as good as doing it in the console windows, or in the .profile
LousyLynx
Offline

Junior Member

Posts: 7
Threads: 2
Joined: Apr 2016
#7
04-16-2016, 03:12 PM
(04-16-2016, 02:40 PM)ggaliens Wrote: Make sure that ERL_LIBS and export have the proper level of visibility throughout your shells and build session.

I had min in my .profile

so that when I started a new shell. It would get defined. Then I tried putting it in my launch script and somehow that was not as good as doing it in the console windows, or in the .profile

Even with my .profile looking like this:
Code:
# ~/.profile: executed by the command interpreter for login shells.
# This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login
# exists.
# see /usr/share/doc/bash/examples/startup-files for examples.
# the files are located in the bash-doc package.

# the default umask is set in /etc/profile; for setting the umask
# for ssh logins, install and configure the libpam-umask package.
#umask 022

# if running bash
if [ -n "$BASH_VERSION" ]; then
    # include .bashrc if it exists
    if [ -f "$HOME/.bashrc" ]; then
    . "$HOME/.bashrc"
    fi
fi

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
    PATH="$HOME/bin:$PATH"
fi

ERL_LIBS="/home/<user>"
export ERL_LIBS
I am still getting this error:
Code:
escript tools/verify_language_files .
escript tools/release
error:{badmatch,{error,badarg}} in [{release__escript__1460__819428__583980__2,
                                     copy_app,2,
                                     [{file,"tools/release"},{line,178}]},
                                    {release__escript__1460__819428__583980__2,
                                     '-release_otp/1-lc$^0/1-0-',2,
                                     [{file,"tools/release"},{line,141}]},
                                    {release__escript__1460__819428__583980__2,
                                     release_otp,1,
                                     [{file,"tools/release"},{line,141}]},
                                    {release__escript__1460__819428__583980__2,
                                     unix_release,2,
                                     [{file,"tools/release"},{line,82}]},
                                    {release__escript__1460__819428__583980__2,
                                     main,1,
                                     [{file,"tools/release"},{line,22}]},
                                    {escript,run,2,
                                     [{file,"escript.erl"},{line,757}]},
                                    {escript,start,1,
                                     [{file,"escript.erl"},{line,277}]},
                                    {init,start_it,1,[]}]
micheus
Offline

Forum's Admin and Support | Bug fixer
Posts: 3,676
Threads: 183
Joined: Jun 2012
#8
04-16-2016, 03:41 PM
The erlang version is old. You neede to update it. Probably rebuild it using the latest sources.
[Image: tw.png] @MicheusVieira [Image: yt.png] @MicheusVieira [Image: da.png] Micheuss [Image: ig.png] micheus4wings3d
* Wings3D Team stands for: Björn and Dan
micheus
Offline

Forum's Admin and Support | Bug fixer
Posts: 3,676
Threads: 183
Joined: Jun 2012
#9
04-16-2016, 07:05 PM
Just to confirm the latest version is 7.3. You need to use it in order to be able to build the wings3d code using the new features that were added to it.

It seems you had an old dev environment set - maybe for 1.4* or 1.5*, so it's time to update it.
I started to update the informations to build a new dev environment - maybe it could help you. Check the Programming session.
[Image: tw.png] @MicheusVieira [Image: yt.png] @MicheusVieira [Image: da.png] Micheuss [Image: ig.png] micheus4wings3d
* Wings3D Team stands for: Björn and Dan
LousyLynx
Offline

Junior Member

Posts: 7
Threads: 2
Joined: Apr 2016
#10
04-17-2016, 02:07 AM
It turns out that using kerl, or an apt-get package does not work. I did not know I had to build erlang from the source to get wxWidgets. I am trying to build it now. I will check back later to tell you if I got it working.
« Next Oldest | Next Newest »

Users browsing this thread: 1 Guest(s)

Pages (2): 1 2 Next »


  • View a Printable Version
  • Subscribe to this thread
Forum Jump:

© Designed by D&D - Powered by MyBB

Linear Mode
Threaded Mode