Hello.
So, I love OpenBSD, and I love icarus verilog.
Here are my Two Cents:
Within the sources, the file driver/main.c, I found this:
-x-x-x-x-x-x-x-x-x-
#ifndef __MINGW32__
/* First try the location specified in the build process. */
if (access(IVL_ROOT, F_OK) != -1) {
Stuart Henderson wrote:
> On 2021/02/02 21:18, Greg Steuck wrote:
> > Added a patch from upstream to work around a case of
> > "all-world-is-Linux"ism.
>
> That's not really true; pretty much every OS other than OpenBSD has a
> way to determine the path that the current executable was started f
On 2021/02/02 21:18, Greg Steuck wrote:
> Added a patch from upstream to work around a case of "all-world-is-Linux"ism.
That's not really true; pretty much every OS other than OpenBSD has a
way to determine the path that the current executable was started from.
There are various different ways of
On Tue, Feb 02, 2021 at 09:18:53PM -0800, Greg Steuck wrote:
> Christian Weisgerber writes:
>
> > Greg Steuck:
> >
> >> iverilog still starts.
> >
> > But the regression tests fail:
> >
> > driver/iverilog -B. -BMvpi -BPivlpp -tcheck -ocheck.vvp ./examples/hello.vl
> > Cannot locate IVL modules :
Christian Weisgerber writes:
> Greg Steuck:
>
>> iverilog still starts.
>
> But the regression tests fail:
>
> driver/iverilog -B. -BMvpi -BPivlpp -tcheck -ocheck.vvp ./examples/hello.vl
> Cannot locate IVL modules : couldn't get command path from OS.
> gmake: *** [Makefile:141: check] Error 1
I
Greg Steuck:
> iverilog still starts.
But the regression tests fail:
driver/iverilog -B. -BMvpi -BPivlpp -tcheck -ocheck.vvp ./examples/hello.vl
Cannot locate IVL modules : couldn't get command path from OS.
gmake: *** [Makefile:141: check] Error 1
--
Christian "naddy" Weisgerber
iverilog still starts.
OK?
Subject: [PATCH] Update lang/iverilog to 11.0
This allows it to build with CXXFLAGS=-fno-common
---
lang/iverilog/Makefile | 4 ++--
lang/iverilog/distinfo | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git lang/iverilog/Makefile lang/iverilog/Make
