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

Qucs Build Fails creating modelist.lo #570

Closed
AndyKirby opened this issue Oct 19, 2016 · 4 comments
Closed

Qucs Build Fails creating modelist.lo #570

AndyKirby opened this issue Oct 19, 2016 · 4 comments

Comments

@AndyKirby
Copy link

Guys

The build is currently failing to compile on Debian unstable:-

4.7.0-1-amd64 #1 SMP Debian 4.7.6-1 (2016-10-07) x86_64 GNU/Linux

ADMS built and installed OK, but I had to run ldconfig manualy as root before qucs configure would complete sucessfuly.

Thereafter the qucs -core build using make fails on nodelist.cpp

/bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -I../src/math -I../src/components -I../src/components -I../src/interface -I. -O2 -pipe -fno-exceptions -fno-check-new -ldl -rdynamic -MT nodelist.lo -MD -MP -MF .deps/nodelist.Tpo -c -o nodelist.lo nodelist.cpp
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I../src/math -I../src/components -I../src/components -I../src/interface -I. -O2 -pipe -fno-exceptions -fno-check-new -ldl -rdynamic -MT nodelist.lo -MD -MP -MF .deps/nodelist.Tpo -c nodelist.cpp -fPIC -DPIC -o .libs/nodelist.o
In file included from nodelist.cpp:32:0:
logging.h:37:8: error: ‘FILE’ does not name a type
extern FILE * file_status;
^~~~
logging.h:38:8: error: ‘FILE’ does not name a type
extern FILE * file_error;
^~~~
Makefile:860: recipe for target 'nodelist.lo' failed
make[5]: *** [nodelist.lo] Error 1
make[5]: Leaving directory '/home/andy/Apps/qucs/qucs/qucs-core/src'
Makefile:906: recipe for target 'all-recursive' failed
make[4]: *** [all-recursive] Error 1

@in3otd
Copy link
Contributor

in3otd commented Oct 22, 2016

this sounds like the issue fixed in #536 ; did you pull the release-0.0.19 branch? The master branch is not up to date at present, it will contain the release 0.0.19 code once this is released

@AndyKirby
Copy link
Author

Thanks in3otd.

That worked fine.I can confirm that the qucs 0.0.19 branch compiled,
installed and looks to be working fine on Debian unstable.

I did have a good google around and a skim through the issues before
pestering you guys, but obviously missed that one.

Might be worth putting a note to this effect on the readme for qucs in
github at least in the interim. Just to save folk like me that arrive to
install qucs and don't have the context.

Are there any plans to update the versions etc in the debian repo's ??
These do feed into a lot of other distributions, so are likely to be
worth the effort.

Cheers

Kirbs

On 22/10/16 19:21, in3otd wrote:

this sounds like the issue fixed in #536
#536 ; did you pull the
|release-0.0.19| branch? The |master| branch is not up to date at
present, it will contain the release 0.0.19 code once this is released


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#570 (comment), or
mute the thread
https://github.com/notifications/unsubscribe-auth/AARf9qx9LY_w_vYbFDGsSCkfSp6Anhhtks5q2lQngaJpZM4Ka0yY.

www.kirbyand.co.uk
andy@kirbyand.co.uk

@ra3xdh
Copy link
Contributor

ra3xdh commented Oct 30, 2016

@AndyKirby , You can read about plans for Qucs inclusion in Debian repos here #454

@ra3xdh ra3xdh closed this as completed Oct 30, 2016
@AndyKirby
Copy link
Author

Thanks Vadim

On 30/10/16 08:00, Vadim Kusnetsov wrote:

@AndyKirby https://github.com/AndyKirby , You can read about plans
for Qucs inclusion in Debian repos here #454
#454


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#570 (comment), or
mute the thread
https://github.com/notifications/unsubscribe-auth/AARf9nnP0MgtRAEgU1qDcodbaV9sdAT2ks5q5E6YgaJpZM4Ka0yY.

andy@kirbyand.co.uk
www.kirbyand.co.uk

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