I saw a message in the configure file that said you might be interested in
my experience building qucs
Well to sum things up, it was a nightmare: it ate up half my weekend
I only compiled the qucs-core subfolder , which allowed me to shun the Qt
libraries for now.
First, - and this it may appear trivial to the cross compiling croud - I
to find the autogen.sh* *because the windows filesystem is mounted under
/c/ in msys. (I know: "duh ! where else ? ")
Then, in order to run
I had to learn that sh is a linux command, and thus it can only be run from
the MSYS console that comes with mingw.
"Of course !" I hear you say - but I knew that once mingw is installed I
can access gcc, g++ and mingw-make from the DOS console ! Why not sh ?
Moving on to the prerequisites,
*mingw-get install autoconf automake
*This was pretty easy to figure out. But you could give the command line in
the build instructions.
*mingw-get install msys-bison msys-flex*
This was a bit harder to find. You could also give the command line and
mention that M4 is part of the bison package.
I just couldn't configure gperf3.0.4 (current version) ! It failed with the
following output in config.log:
*Thread model: win32^M
gcc version 4.6.2 (GCC) ^M
configure:2013: $? = 0
configure:2020: gcc -V >&5
gcc.exe: error: unrecognized option '-V'^M
gcc.exe: fatal error: no input files^M
configure:2023: $? = 1
configure:2046: checking for C compiler default output file name
configure:2073: gcc conftest.c >&5
configure:2076: $? = 0
configure:2114: result: a.exe
configure:2131: checking whether the C compiler works
- Cannot openconfigure:2144: $? = 1
configure:2153: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.*
So I resorted to downloading the prebuilt win32 binary installer for *
gperf3.0.1* from here:
Ran the installer, added the C:\Gperf301\bin path to windows PATH
and rejoiced to see that I could now run *gperf -v* from the MSYS console !
Google won't find that one little obscure project, so maybe you could
provide the link to
Again I could not build the current release (2.2.9)
After the *./configure *goes well, the *make* fails with these error
undefined reference to `rpl_malloc'
undefined reference to `rpl_realloc'*
At this point I had to edit the config.h file, created by the ./configure,
to comment out these 2 lines:
#define malloc rpl_malloc
#define realloc rpl_realloc
as someone suggests here
Now the compilation progresses on, but fails with a huge list of link
Creating library file: .libs/libadmsAdmstpath.dll.a
.libs/libadmsAdmstpath_la-admstpathYacc.o: In function `new_basicstring':
c:\adms-2.2.9\admsXml/admstpathYacc.y:91: undefined reference to
.libs/libadmsAdmstpath_la-admstpathYacc.o: In function `fixtext':
c:\adms-2.2.9\admsXml/admstpathYacc.y:100: undefined reference to
c:\adms-2.2.9\admsXml/admstpathYacc.y:109: undefined reference to
...( on and on forever )
I had to get the upcoming release (2.3.0) from here:
The I unzipped the stuff, then
*Then I edited config.h as mentionned above, then
*make && make install*
ended well this time. I could check that it worked by typing *admsXml* in
Phew ! All this to be able to go back to
*and see the configuration go well*
./configure --enable-maintainer-mode --prefix=/usr*
But then the build fails with all the issues described here
and I could post links to fedora and ubuntu forums too !
I am using gcc 4.6.2.
On your front page it says
"11 Dec 2011 Changes to avoid compile issues with g++ version 4.5 and
But the latest release is still 0.0.16
Could you MAKE IT MORE EXPLICIT that people need to download the *trunk *to
be able to build using any gcc4.5+ compiler ?