pkgsrc-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: pkg/43263: Dragonfly and Darwin default configuration can be improved
The following reply was made to PR pkg/43263; it has been noted by GNATS.
From: Francisco Garcia <frankalahan%gmail.com@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc:
Subject: Re: pkg/43263: Dragonfly and Darwin default configuration can be
improved
Date: Thu, 13 May 2010 08:29:05 +0200
--Apple-Mail-1--927798115
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
That is exactly the reason I had problems. I've been looking at =
mk/compiler/gcc.mk
> # _CC is the full path to the compiler named by ${CC} if it can be =
found.
> .if !defined(_CC)
> _CC:=3D ${CC:C/^/_asdf_/1:M_asdf_*:S/^_asdf_//}
I think it would be useful to make some checks. At least checking that =
either $CC or the output of $CC --version has the "gcc" string
I tried to add the check, but now I don't know how to report the error =
or stop the process.
Am 06.05.2010 um 01:40 schrieb Joerg Sonnenberger:
> The following reply was made to PR pkg/43263; it has been noted by =
GNATS.
>=20
> From: Joerg Sonnenberger <joerg%britannica.bec.de@localhost>
> To: gnats-bugs%NetBSD.org@localhost
> Cc:=20
> Subject: Re: pkg/43263: Dragonfly and Darwin default configuration can =
be
> improved
> Date: Thu, 6 May 2010 01:36:53 +0200
>=20
> On Wed, May 05, 2010 at 08:50:00PM +0000, frankalahan%gmail.com@localhost
> wrote:
>>> Description:
>> I have noticed that PKGSRC default installation does not enforce the
>> use of the native GCC.
>=20
> Yes and no. mk/compiler/gcc.mk tries to figure out what version of GCC
> is present, but that fails in various situations, e.g. if CC is
> specified manually to the wrong command etc. As usual, the correct =
trick
> is to figure out why it failed. USE_NATIVE_GCC is just a crude
> hackaround.
>=20
> Joerg
>=20
--Apple-Mail-1--927798115
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=us-ascii
<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">That =
is exactly the reason I had problems. I've been looking at =
mk/compiler/gcc.mk<div><br></div><div><blockquote =
type=3D"cite"><div><font class=3D"Apple-style-span" color=3D"#000000"># =
_CC is the full path to the compiler named by ${CC} if it can be =
found.</font></div><div><font class=3D"Apple-style-span" =
color=3D"#000000">.if !defined(_CC)</font></div></blockquote><blockquote =
type=3D"cite"><div><font class=3D"Apple-style-span" =
color=3D"#000000">_CC:=3D =
${CC:C/^/_asdf_/1:M_asdf_*:S/^_asdf_//}</font></div></blockquote><div><br>=
</div><div>I think it would be useful to make some checks. At least =
checking that either $CC or the output of $CC --version has the "gcc" =
string</div><div><br></div><div>I tried to add the check, but now I =
don't know how to report the error or stop the =
process.</div><div><br></div><div><div><br></div><div>Am 06.05.2010 um =
01:40 schrieb Joerg Sonnenberger:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>The =
following reply was made to PR pkg/43263; it has been noted by =
GNATS.<br><br>From: Joerg Sonnenberger <<a =
href=3D"mailto:joerg%britannica.bec.de@localhost">joerg%britannica.bec.de@localhost</a>><br=
>To: <a =
href=3D"mailto:gnats-bugs%NetBSD.org@localhost">gnats-bugs%NetBSD.org@localhost</a><br>Cc:
=
<br>Subject: Re: pkg/43263: Dragonfly and Darwin default configuration =
can be<br> improved<br>Date: Thu, 6 May 2010 01:36:53 +0200<br><br> On =
Wed, May 05, 2010 at 08:50:00PM +0000, <a =
href=3D"mailto:frankalahan%gmail.com@localhost">frankalahan%gmail.com@localhost</a>
=
wrote:<br><blockquote type=3D"cite"><blockquote =
type=3D"cite">Description:<br></blockquote></blockquote><blockquote =
type=3D"cite">I have noticed that PKGSRC default installation does not =
enforce the<br></blockquote><blockquote type=3D"cite">use of the native =
GCC.<br></blockquote><br> Yes and no. mk/compiler/gcc.mk tries to figure =
out what version of GCC<br> is present, but that fails in various =
situations, e.g. if CC is<br> specified manually to the wrong command =
etc. As usual, the correct trick<br> is to figure out why it failed. =
USE_NATIVE_GCC is just a crude<br> hackaround.<br><br> =
Joerg<br><br></div></blockquote></div><br></div></body></html>=
--Apple-Mail-1--927798115--
Home |
Main Index |
Thread Index |
Old Index