Re: gEDA-user: iverilog main.cc undefined reference using --host=mingw32

["Shing-Fat (Fred) Ma" <fma@doe.carleton.ca>]

OK, thanks, Steve.  Actually, if I don't use --host=mingw32, I don't
get those compilation errors, so I probably don't need to worry about
the -liberty in that case.  The build happens uneventfully.  My
small toy example runs perfectly with both vvm and vvp as the compilation
target.  It's only when I get to my bigger design, with layers of module wrapping
and lots of overridden parameters that it croaks with the assertion error.
I haven't been able to create a smaller (and less proprietary) case which
duplicates this error.

Regarding why I'm following such a complicated procedure,
I was only able to get my installation working on the
smaller example using the modified installation procedure of
http://www.seul.org/archives/geda/user/Nov-2001/msg00017.html after
experiencing problems with the mingw.txt procedure and spawning the
thread in http://www.seul.org/archives/geda/user/Nov-2001/msg00012.html .

Thanks for the quick look.  I'll be on the lookout for further suggestions,
though I probably won't be able to pursue any in the short term.

Fred
--
--------------------------------------------------------------------------
Fred Ma
Department of Electronics
Carleton University, Mackenzie Building
1125 Colonel By Drive
Ottawa, Ontario
Canada     K1S 5B6
fma@doe.carleton.ca
==========================================================================
Stephen Williams wrote:

> fma@doe.carleton.ca said:
> > I hadn't quite thrown in the towel....here's the "last gasp" in trying
> > to solve the error messages associated with "configure --host=mingw32"
>
> Why the "--host-mingw32" bit? The configure script will detect the
> compiler and tools, so this is unnecessary, maybe a hazard.
>
> fma@doe.carleton.ca said:
> > All those names that are undefined, they appear in ...../mingw/include/
> > getopt.h .
>
> The -liberty flag is probably not being passed to the linker. There
> were a few snapshots where this was broken, but the latest snapshots
> should be fine.
>
> fma@doe.carleton.ca said:
> > Who knows, maybe using "config --host=mingw32" isn't even the right
> > way to go about this
>
> It is not. Follow the mingw.txt instructions, there is no need for
> the --host=anything flag. Also, try the latest snapshot, or at least
> hand edit the generated Makefile to pass -liberty to the linker.
>
> --
> Steve Williams                "The woods are lovely, dark and deep.
> steve at icarus.com           But I have promises to keep,
> steve at picturel.com         and lines to code before I sleep,
> http://www.picturel.com       And lines to code before I sleep."