On a freshly-installed FreeBSD 14.1 amd64 system, I'm hitting errors
in the system C++ standard include files.
For example, trying to build editors/le produces:
c++ -DHAVE_CONFIG_H -I. -I../lib -I../lib -I../lib -isystem
/usr/local/include -D_THREAD_SAFE -O2 -pipe -fstack-protector-strong
-is
On 30 Aug 2024, at 17:48, J David wrote:
>
> On a freshly-installed FreeBSD 14.1 amd64 system, I'm hitting errors
> in the system C++ standard include files.
...
> /usr/include/c++/v1/ios:260:25: error: expected ')'
> 260 | static const fmtflags hex = 0x0008;
> |
On Fri, Aug 30, 2024 at 1:54 PM Dimitry Andric wrote:
> This is the problem: do not redefine identifiers like this, as it leads
> to problems. Try renaming this macro to "my_hex", "le_hex" or anything
> but "hex". :)
/usr/include/c++/v1/ios is the system C++ standard library include
file for stre
On 30 Aug 2024, at 20:19, J David wrote:
>
> On Fri, Aug 30, 2024 at 1:54 PM Dimitry Andric wrote:
>> This is the problem: do not redefine identifiers like this, as it leads
>> to problems. Try renaming this macro to "my_hex", "le_hex" or anything
>> but "hex". :)
>
> /usr/include/c++/v1/ios is
On Fri, Aug 30, 2024 at 2:19 PM Dimitry Andric wrote:
> As to your question about why it builds for the package builders, my
> guess is that these use the oldest supported releases, so 13.3 and 14.0,
> which have older versions of the libc++ headers.
That could be true for 14.0; I haven't tried t
On Fri, Aug 30, 2024 at 2:36 PM Dimitry Andric wrote:
> Try using the attached patch.
Wow. That's... nasty... but effective. Haven't tested (I'm not the end
user) but it does build that way. I guess it's probably safe because
it's not like the code could have also been using std::hex somewhere.
On 30 Aug 2024, at 20:45, J David wrote:
>
> On Fri, Aug 30, 2024 at 2:36 PM Dimitry Andric wrote:
>> Try using the attached patch.
>
> Wow. That's... nasty... but effective. Haven't tested (I'm not the end
> user) but it does build that way. I guess it's probably safe because
> it's not like t
On Fri, Aug 30, 2024 at 3:03 PM Dimitry Andric wrote:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281141
Thanks. The project looks moribund but not dead, so I've opened a
report with the upstream and I'll try to do a pull request for them.
Really appreciate the help!
On 8/28/24 9:20 PM, Moin Rahman wrote:
On Aug 28, 2024, at 12:54 PM, Kaya Saman
wrote:
Hi,
I'm trying to upgrade my ports collection but running into this error. I
performed the necessary upgrade steps:
uname -a
FreeBSD 13.3-RELEASE-p5 FreeBSD 13.3-RELEASE-p5 GENERIC amd64
and have
On Aug 30, 2024, at 22:05, Mark Millard wrote:
> On Aug 30, 2024, at 21:26, Mark Millard wrote:
>
>> On Aug 30, 2024, at 20:33, Mark Millard wrote:
>>
>>> [Subject was retitled.]
>>>
>>> On Aug 30, 2024, at 16:24, Mark Millard wrote:
>>>
What my test-of-building got was: No include f
What my test-of-building got was: No include file found and
no OFlags::TMPFILE found (OFlags:: was found, TMPFILE in OFlags:: was not):
In file included from
/wrkdirs/usr/ports/www/firefox/work/firefox-129.0.2/mfbt/lz4/xxhash.c:43:
In file included from
/wrkdirs/usr/ports/www/firefox/work/firef
On Aug 30, 2024, at 20:33, Mark Millard wrote:
> [Subject was retitled.]
>
> On Aug 30, 2024, at 16:24, Mark Millard wrote:
>
>> What my test-of-building got was: No include file found and
>> no OFlags::TMPFILE found (OFlags:: was found, TMPFILE in OFlags:: was not):
>>
>> In file included f
On Aug 30, 2024, at 21:26, Mark Millard wrote:
> On Aug 30, 2024, at 20:33, Mark Millard wrote:
>
>> [Subject was retitled.]
>>
>> On Aug 30, 2024, at 16:24, Mark Millard wrote:
>>
>>> What my test-of-building got was: No include file found and
>>> no OFlags::TMPFILE found (OFlags:: was fou
[Subject was retitled.]
On Aug 30, 2024, at 16:24, Mark Millard wrote:
> What my test-of-building got was: No include file found and
> no OFlags::TMPFILE found (OFlags:: was found, TMPFILE in OFlags:: was not):
>
> In file included from
> /wrkdirs/usr/ports/www/firefox/work/firefox-129.0.2/mf
14 matches
Mail list logo
