On 8/10/2018 8:11 AM, Stuart Henderson wrote:
> On 2018/08/10 11:45, Stuart Henderson wrote:
>> Save trouble, it's not needed. These config options don't do anything useful.
>> Still building but here's a diff on top of your last tar which fixes a few
>> little issues (one of which was failure
On 2018/08/10 11:45, Stuart Henderson wrote:
> Save trouble, it's not needed. These config options don't do anything useful.
> Still building but here's a diff on top of your last tar which fixes a few
> little issues (one of which was failure to fetch the tarball from
> MASTER_SITES :)
Oops,
On 2018/08/10 08:41, Alessandro DE LAURENZIS wrote:
> Hi Brian,
>
> On 08/10/18 06:20, Brian Callahan wrote:
> >
> >
> > On 8/10/2018 12:05 AM, Alessandro DE LAURENZIS wrote:
> > > Hi Brian,
> > >
> > > [...]
> > > > Could you explain why ports-gcc is needed? Is there a reason that
> > > >
Hi Brian,
On 08/10/18 06:20, Brian Callahan wrote:
On 8/10/2018 12:05 AM, Alessandro DE LAURENZIS wrote:
Hi Brian,
[...]
Could you explain why ports-gcc is needed? Is there a reason that
gcc-4.9.4 would be preferred over clang-6.0.0?
Usually, if you have a COMPILER line, you have a comment
On 8/10/2018 12:05 AM, Alessandro DE LAURENZIS wrote:
> Hi Brian,
>
> [...]
>> Could you explain why ports-gcc is needed? Is there a reason that
>> gcc-4.9.4 would be preferred over clang-6.0.0?
>> Usually, if you have a COMPILER line, you have a comment above it
>> with a reason why. I don't
Hi Brian,
[...]
Could you explain why ports-gcc is needed? Is there a reason that
gcc-4.9.4 would be preferred over clang-6.0.0?
Usually, if you have a COMPILER line, you have a comment above it with a
reason why. I don't know if it's true for this port, but something like:
# C++11
COMPILER =
Hi Alessandro --
On 8/4/18 3:04 AM, Alessandro DE LAURENZIS wrote:
Hi Stuart,
On 08/03/18 17:56, Alessandro DE LAURENZIS wrote:
Hi Stuart,
On 08/03/18 13:21, Stuart Henderson wrote:
On 2018/08/03 12:23, Alessandro DE LAURENZIS wrote:
I think we need the line:
FAKE_FLAGS =
Hi Stuart,
On 08/03/18 17:56, Alessandro DE LAURENZIS wrote:
Hi Stuart,
On 08/03/18 13:21, Stuart Henderson wrote:
On 2018/08/03 12:23, Alessandro DE LAURENZIS wrote:
I think we need the line:
FAKE_FLAGS = PREFIX="${LOCALBASE}"
since PREFIX is explicitly set to /usr/local in upstream
Hi Stuart,
On 08/03/18 13:21, Stuart Henderson wrote:
On 2018/08/03 12:23, Alessandro DE LAURENZIS wrote:
I think we need the line:
FAKE_FLAGS =PREFIX="${LOCALBASE}"
since PREFIX is explicitly set to /usr/local in upstream Makefile when
undefined.
That should probably be
On 2018/08/03 13:57, Alessandro DE LAURENZIS wrote:
> Hi Stuart,
>
> On 08/03/18 13:21, Stuart Henderson wrote:
> > > std::string proc_self_dirname()
> > > {
> > > // No direct way to get the process executable base path
> > > char path[PATH_MAX];
> > > ssize_t buflen = sizeof(path);
Hi Stuart,
On 08/03/18 13:21, Stuart Henderson wrote:
std::string proc_self_dirname()
{
// No direct way to get the process executable base path
char path[PATH_MAX];
ssize_t buflen = sizeof(path);
char *res = realpath(getenv("_"), path);
if (!res) {
On 2018/08/03 12:23, Alessandro DE LAURENZIS wrote:
> I think we need the line:
>
> FAKE_FLAGS = PREFIX="${LOCALBASE}"
>
> since PREFIX is explicitly set to /usr/local in upstream Makefile when
> undefined.
That should probably be PREFIX="${TRUEPREFIX}"
> Also, in order to avoid python3 setup
Dear ports@ readers,
Yosys [1] is the second port required by Qflow [2]:
From DESCR:
[... snip ...]
Yosys Open SYnthesis Suite
Yosys is a framework for Verilog RTL synthesis. It currently has
extensive Verilog-2005 support and provides a basic set of synthesis
algorithms for various
13 matches
Mail list logo
