element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      • Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Autodesk EAGLE
  • Products
  • More
Autodesk EAGLE
EAGLE User Support (English) symbol lookup error
  • Blog
  • Forum
  • Documents
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Autodesk EAGLE to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Not Answered
  • Replies 4 replies
  • Subscribers 178 subscribers
  • Views 364 views
  • Users 0 members are here
Related

symbol lookup error

jkuzmack
jkuzmack over 10 years ago

Hi,

 

I recently upgraded from Eagle 7.1 to 7.5.  After the upgrade, I was able to load multiple prior designs successfully.

 

After restarting my Linux machine over the weekend, I got an error when attempting to open either a prior design or a new design (no content):

 

eagle: symbol lookup error: eagle: undefined symbol: EC_get_builtin_curves

 

If I attempted to open the same file a second time I got a "file locking" window indicating that the file is locked by owner (me).   I was reluctant to choose "save as" at this point as the "hour glass" was still rotating, implying that the state of the software was not happy.

 

In the design directory, files were created after attempting to open with 7.5 as follows:

.filenam.brd.lck

.filename.sch.lck

 

After .alias was changed to revert back to 7.1  and the .lck files were removed, I could successfully open prior designs.  Additionally, changing .alias to 7.5 again (for the second time) successfully opens existing files.  I also disabled file locking.  Subsequent reboot allows multiple files to open successfully.  At the moment, it seems all is well as far as opening new/prior designs but the unexplained behavior is concerning.


Can you provide any insight into the original "symbol lookup error " and whether this is a real error going forward with 7.5?  Thanks.


John

  • Sign in to reply
  • Cancel
  • jkuzmack
    0 jkuzmack over 10 years ago

    Hi,

     

    Some additional information.

     

    After another weekend reboot, some of the previously mentioned behavior returned (with the exception that the .lck files were not created).  When attempting to open a design file with 7.5, the same symbol lookup error occurred.  Reverting back to 7.1 by changing the .alias did not clear the error.  Rebooting with .alias pointing to 7.5 allowed the files to open successfully (error does not occur).

     

    It appears that the symbol lookup error is somehow related to whether and how the .alias update is invoked; through reboot or source .alias command.  Subsequent reboots may or may not create the situation in which the error occurs.

     

    Any insight would be greatly appreciated.  Thanks.

     

    John

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • autodeskguest
    0 autodeskguest over 10 years ago

    On 11/23/2015 3:10 PM, John Kuzmack wrote:

    Hi,

     

    I recently upgraded from Eagle 7.1 to 7.5.  After the upgrade, I was

    able to load multiple prior designs successfully.

     

    After restarting my Linux machine over the weekend, I got an error when

    attempting to open either a prior design or a new design (no content):

     

    eagle: symbol lookup error: eagle: undefined symbol:

    EC_get_builtin_curves

     

    If I attempted to open the same file a second time I got a "file

    locking" window indicating that the file is locked by owner (me).   I

    was reluctant to choose "save as" at this point as the "hour glass" was

    still rotating, implying that the state of the software was not happy.

     

    In the design directory, files were created after attempting to open

    with 7.5 as follows:

    filenam.brd.lck

    filename.sch.lck

     

    After .alias was changed to revert back to 7.1  and the .lck files were

    removed, I could successfully open prior designs.  Additionally,

    changing .alias to 7.5 again (for the second time) successfully opens

    existing files.  I also disabled file locking.  Subsequent reboot allows

    multiple files to open successfully.  At the moment, it seems all is

    well as far as opening new/prior designs but the unexplained behavior is

    concerning.

     

     

    Can you provide any insight into the original "symbol lookup error " and

    whether this is a real error going forward with 7.5?  Thanks.

     

     

     

    Hi John,

     

    I hope you're doing well. This is an odd error, that I've never seen

    before.

     

    What is this .alias that you are referring to? Is this a hidden file on

    your system?

     

    Best Regards,

    Jorge Garcia

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • jkuzmack
    0 jkuzmack over 10 years ago in reply to autodeskguest

    Hi Jorge,

     

    Yes, .alias is a hidden file on my system.  It contains the additions for all the various engineering tools used by the team such as PYTHON, MATLAB, FPGA tools, and EAGLE.

     

    For EAGLE, the latest using 7.5 reads as follows:

     

    #Additions for Eagle

    #export EAGLE_PATH=/home/tools/eagle/eagle-lin-eng-5.11.0

    #export EAGLE_PATH=/home/tools/eagle/eagle-lin-eng-6.4.0

    #export EAGLE_PATH=/home/tools/eagle/eagle-lin-eng-6.5.0

    #export EAGLE_PATH=/home/tools/eagle/eagle-lin-eng-7.1.0

    export EAGLE_PATH=/home/tools/eagle/eagle-lin-eng-7.5.0

    export EAGLE_PATH_BIN=$EAGLE_PATH/bin

    export EAGLE_PATH_LIB=$EAGLE_PATH/eagle_libs


    In order to upgrade from 7.1 to 7.5, I only add the latest 7.5 export line and comment out (#) previous 7.1 line.  After saving the change, then use the command "source .alias" to invoke the changes.  Hope this is clear.


    Also fyi, a coworker has the same error when using 7.5.


    John


    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • autodeskguest
    0 autodeskguest over 10 years ago in reply to jkuzmack

    Taking this issue up with the devs.

     

    I'll post once I have a response.

     

    Best Regards,

    Jorge Garcia

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube