Problem reports for chrom...@freebsd.org that need special attention

2024-09-22 Thread bugzilla-noreply
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
Open|233095 | www/firefox geolocation no longer working 

1 problems total for which you should take action.


[Bug 259811] www/chromium: No sound on skype for web calls

2024-09-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259811

Alexander Vereeken  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |Overcome By Events

--- Comment #3 from Alexander Vereeken  ---
Alright, thank you for your feeedback.

Closing this accordingly.

-- 
You are receiving this mail because:
You are the assignee for the bug.


Problem reports for chrom...@freebsd.org that need special attention

2024-09-15 Thread bugzilla-noreply
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
Open|233095 | www/firefox geolocation no longer working 

1 problems total for which you should take action.


[Bug 259811] www/chromium: No sound on skype for web calls

2024-09-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259811

--- Comment #2 from Geezer  ---
With Version 127.0.6533.88 and the latest web.skype.com it seems to run well.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 259811] www/chromium: No sound on skype for web calls

2024-09-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259811

Alexander Vereeken  changed:

   What|Removed |Added

 CC||Alexander88207@protonmail.c
   ||om

--- Comment #1 from Alexander Vereeken  ---
Hello,

can you give a feedback if this still happens?

-- 
You are receiving this mail because:
You are the assignee for the bug.


Problem reports for chrom...@freebsd.org that need special attention

2024-09-08 Thread bugzilla-noreply
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
Open|233095 | www/firefox geolocation no longer working 

1 problems total for which you should take action.


[Bug 281196] www/chromium: 127.0.6533.119 poudriere build fails

2024-09-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281196

Alexander Vereeken  changed:

   What|Removed |Added

 CC||Alexander88207@protonmail.c
   ||om

--- Comment #3 from Alexander Vereeken  ---
Hello,

in case of general building, can you update your portstree and try again?
(There have been some updates and it builds at least on the cluster fine)

I think an extra rebuild of chromium is not needed for widevine support.

The option only adds foreign-cdm as run-depend so you should only need to build
foreign-cdm and linux-widevine-cdm.

-- 
You are receiving this mail because:
You are the assignee for the bug.


Problem reports for chrom...@freebsd.org that need special attention

2024-09-01 Thread bugzilla-noreply
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
Open|233095 | www/firefox geolocation no longer working 

1 problems total for which you should take action.


[Bug 281196] www/chromium: 127.0.6533.119 poudriere build fails

2024-09-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281196

--- Comment #2 from Dwayne MacKinnon  ---
Created attachment 253257
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=253257&action=edit
My poudriere.conf

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 281196] www/chromium: 127.0.6533.119 poudriere build fails

2024-09-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281196

Dwayne MacKinnon  changed:

   What|Removed |Added

 Attachment #253256|text/x-log  |text/plain
  mime type||

--- Comment #1 from Dwayne MacKinnon  ---
Created attachment 253256
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=253256&action=edit
Build log with extract error

-- 
You are receiving this mail because:
You are the assignee for the bug.


maintainer-feedback requested: [Bug 281196] www/chromium: 127.0.6533.119 poudriere build fails

2024-09-01 Thread bugzilla-noreply
Bugzilla Automation  has asked freebsd-chromium (Nobody)
 for maintainer-feedback:
Bug 281196: www/chromium: 127.0.6533.119 poudriere build fails
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281196



--- Description ---
I've been attempting to update chromium, which I compile with poudriere to add
in the widevine support. First few times the process died, so I cut the jobs
down to one. Still died... determined it was running out of swap. So I stopped
using the memory file system. So, with one job and everything on hard disk it
still failed.

This time, the error was this:

../../base/gtest_prod_util.h:9:10: fatal error:
'testing/gtest/include/gtest/gtest_prod.h' file not found

I don't know a lot about the build process, so I thought I'd try enabling the
tests to see if this file would then be available.

Failed again, this time on extract:

mv: rename /wrkdirs/usr/ports/www/chromium/work/test_fonts to
/wrkdirs/usr/ports/www/chromium/work/chromium-127.0.6533.119/third_party/test_f
onts/test_fonts:
Directory not empty

Any advice on what I can do to get this to work would be greatly appreciated.



[Bug 281196] www/chromium: 127.0.6533.119 poudriere build fails

2024-09-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281196

Bug ID: 281196
   Summary: www/chromium: 127.0.6533.119 poudriere build fails
   Product: Ports & Packages
   Version: Latest
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: Individual Port(s)
  Assignee: chrom...@freebsd.org
  Reporter: d...@ncf.ca
 Flags: maintainer-feedback?(chrom...@freebsd.org)
  Assignee: chrom...@freebsd.org
 Attachment #253255 text/plain
 mime type:

Created attachment 253255
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=253255&action=edit
Build log with missing file

I've been attempting to update chromium, which I compile with poudriere to add
in the widevine support. First few times the process died, so I cut the jobs
down to one. Still died... determined it was running out of swap. So I stopped
using the memory file system. So, with one job and everything on hard disk it
still failed.

This time, the error was this:

../../base/gtest_prod_util.h:9:10: fatal error:
'testing/gtest/include/gtest/gtest_prod.h' file not found

I don't know a lot about the build process, so I thought I'd try enabling the
tests to see if this file would then be available.

Failed again, this time on extract:

mv: rename /wrkdirs/usr/ports/www/chromium/work/test_fonts to
/wrkdirs/usr/ports/www/chromium/work/chromium-127.0.6533.119/third_party/test_fonts/test_fonts:
Directory not empty

Any advice on what I can do to get this to work would be greatly appreciated.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279998] www/chromium: Skype does not work after implement selectable audio backend support

2024-08-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279998

--- Comment #6 from Aman  ---
I liked your article very much, I will definitely forward it so that more
people can read this article.

https://www.mictesters.com/

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 281104] www/chromium: build fails by patch-build_rust_rust__bindgen.gni

2024-08-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281104

Robert Nagy  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |FIXED
 CC||rn...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 281104] www/chromium: build fails by patch-build_rust_rust__bindgen.gni

2024-08-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281104

--- Comment #2 from commit-h...@freebsd.org ---
A commit in branch 2024Q3 references this bug:

URL:
https://cgit.FreeBSD.org/ports/commit/?id=3b8a0e985946a867277298c4fd7d5363f56bdfae

commit 3b8a0e985946a867277298c4fd7d5363f56bdfae
Author: Robert Nagy 
AuthorDate: 2024-08-28 10:30:18 +
Commit: Robert Nagy 
CommitDate: 2024-08-28 10:32:09 +

www/{*chromium,iridium}: revert hardcoded paths that sneaked in

PR: 281104
(cherry picked from commit d0c3a2d4b6bfcdd482143cde1f7e459461482e40)

 www/chromium/files/patch-build_rust_rust__bindgen.gni   | 6 +++---
 www/iridium/files/patch-build_rust_rust__bindgen.gni| 6 +++---
 www/ungoogled-chromium/files/patch-build_rust_rust__bindgen.gni | 6 +++---
 3 files changed, 9 insertions(+), 9 deletions(-)

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 281104] www/chromium: build fails by patch-build_rust_rust__bindgen.gni

2024-08-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281104

--- Comment #1 from commit-h...@freebsd.org ---
A commit in branch main references this bug:

URL:
https://cgit.FreeBSD.org/ports/commit/?id=d0c3a2d4b6bfcdd482143cde1f7e459461482e40

commit d0c3a2d4b6bfcdd482143cde1f7e459461482e40
Author: Robert Nagy 
AuthorDate: 2024-08-28 10:30:18 +
Commit: Robert Nagy 
CommitDate: 2024-08-28 10:31:10 +

www/{*chromium,iridium}: revert hardcoded paths that sneaked in

PR: 281104

 www/chromium/files/patch-build_rust_rust__bindgen.gni   | 6 +++---
 www/iridium/files/patch-build_rust_rust__bindgen.gni| 6 +++---
 www/ungoogled-chromium/files/patch-build_rust_rust__bindgen.gni | 6 +++---
 3 files changed, 9 insertions(+), 9 deletions(-)

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 281104] www/chromium: build fails by patch-build_rust_rust__bindgen.gni

2024-08-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281104

Bug ID: 281104
   Summary: www/chromium: build fails by
patch-build_rust_rust__bindgen.gni
   Product: Ports & Packages
   Version: Latest
  Hardware: Any
   URL: https://cgit.freebsd.org/ports/commit/?id=43ddb9a8a4b2
2a4b81ca32698948e5832a6d93c6
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: Individual Port(s)
  Assignee: chrom...@freebsd.org
  Reporter: kdegu...@sz.tokoha-u.ac.jp
  Assignee: chrom...@freebsd.org
 Flags: maintainer-feedback?(chrom...@freebsd.org)

www/chromium fails build in
https://cgit.freebsd.org/ports/commit/?id=43ddb9a8a4b22a4b81ca32698948e5832a6d93c6.

I think we need to revert on the fixes to
www/chromium/files/patch-build_rust_rust__bindgen.gni.

-- 
You are receiving this mail because:
You are the assignee for the bug.


maintainer-feedback requested: [Bug 281104] www/chromium: build fails by patch-build_rust_rust__bindgen.gni

2024-08-27 Thread bugzilla-noreply
Bugzilla Automation  has asked freebsd-chromium (Nobody)
 for maintainer-feedback:
Bug 281104: www/chromium: build fails by patch-build_rust_rust__bindgen.gni
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281104



--- Description ---
www/chromium fails build in
https://cgit.freebsd.org/ports/commit/?id=43ddb9a8a4b22a4b81ca32698948e5832a6d9
3c6.

I think we need to revert on the fixes to
www/chromium/files/patch-build_rust_rust__bindgen.gni.



Problem reports for chrom...@freebsd.org that need special attention

2024-08-25 Thread bugzilla-noreply
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
Open|233095 | www/firefox geolocation no longer working 

1 problems total for which you should take action.


Problem reports for chrom...@freebsd.org that need special attention

2024-08-18 Thread bugzilla-noreply
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
Open|233095 | www/firefox geolocation no longer working 

1 problems total for which you should take action.


Problem reports for chrom...@freebsd.org that need special attention

2024-08-11 Thread bugzilla-noreply
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
Open|233095 | www/firefox geolocation no longer working 

1 problems total for which you should take action.


[Bug 280733] www/chromium: web serial api access is disabled

2024-08-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280733

Bug ID: 280733
   Summary: www/chromium: web serial api access is disabled
   Product: Ports & Packages
   Version: Latest
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: Individual Port(s)
  Assignee: chrom...@freebsd.org
  Reporter: grae...@gmail.com
  Assignee: chrom...@freebsd.org
 Flags: maintainer-feedback?(chrom...@freebsd.org)

I don't know why, but the web serial api is disabled in FreeBSD chromium
builds. This means I can't manage serial devices via my web browser (a common
thing these days). eg: I have multi programable keyboards, and they use a
website and serial communications to maintain the device.

This was raised in the FreeBSD Forum, where I discovered that it wasn't user
permission issues, but rather that chromium is not built with Serial API
enabled.

https://forums.FreeBSD.org/threads/manage-usb-devices-via-chromium-serial-api.92255/post-652150

Examples of website with serial web api functionality

1. https://manager.charachorder.com/config/layout/
2. https://www.serialterminal.com

-- 
You are receiving this mail because:
You are the assignee for the bug.


maintainer-feedback requested: [Bug 280733] www/chromium: web serial api access is disabled

2024-08-10 Thread bugzilla-noreply
Bugzilla Automation  has asked freebsd-chromium (Nobody)
 for maintainer-feedback:
Bug 280733: www/chromium: web serial api access is disabled
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280733



--- Description ---
I don't know why, but the web serial api is disabled in FreeBSD chromium
builds. This means I can't manage serial devices via my web browser (a common
thing these days). eg: I have multi programable keyboards, and they use a
website and serial communications to maintain the device.

This was raised in the FreeBSD Forum, where I discovered that it wasn't user
permission issues, but rather that chromium is not built with Serial API
enabled.

https://forums.FreeBSD.org/threads/manage-usb-devices-via-chromium-serial-api.9
2255/post-652150

Examples of website with serial web api functionality

1. https://manager.charachorder.com/config/layout/
2. https://www.serialterminal.com



[Bug 280268] www/ungoogled-chromium: add the ability to build with any set of audio backends, including without sound for headless usage

2024-08-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280268

--- Comment #12 from Robert Nagy  ---
(In reply to Jonathan Chen from comment #11)

That did not change. You will get all backends enabled by default with
a user setting available in chrome://flags.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 280268] www/ungoogled-chromium: add the ability to build with any set of audio backends, including without sound for headless usage

2024-08-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280268

Jonathan Chen  changed:

   What|Removed |Added

 CC||j...@chen.org.nz

--- Comment #11 from Jonathan Chen  ---
Why have we put audio knobs back into the port? I actually preferred the
dynamic selection, which picked up whichever sound-backend that the user had
actually installed on their system.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 280268] www/ungoogled-chromium: add the ability to build with any set of audio backends, including without sound for headless usage

2024-08-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280268

--- Comment #10 from Vladimir Druzenko  ---
(In reply to Mathieu Bâl from comment #9)
Thanks, made me laugh! :-D

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 280268] www/ungoogled-chromium: add the ability to build with any set of audio backends, including without sound for headless usage

2024-08-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280268

Mathieu Bâl  changed:

   What|Removed |Added

 CC||nenet54...@mvpalace.com

--- Comment #9 from Mathieu Bâl  ---
(In reply to Robert Nagy from comment #3)

I don't use Chromium, but the lack of options was never among the reasons why.
Now it is.

Allow me to introduce myself: I am the Priest of the Church of Minimalism. Our
Church is relatively new, so it's likely you haven’t heard of us. Like any
religion, we have our dogmas—though we prefer to call them "Truths." And being
a new faith, we also have Truths about software development.

Our central Truth states, "Everything that can be configurable must be
configurable." This is not merely about the size of libraries but, rather,
about freedom. And freedom, in turn, leads to prosperity.

Naturally, we have rituals. One of these involves manually counting packages
before and after each execution of 'pkg install/delete/upgrade/autoremove.'
After counting, the results are recorded in the Grand Book of Sinister
Imperfections, which is my solemn duty to maintain.

It may be hard to believe, but this is how our Prophet taught us.

May the light of wisdom be with you!

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 280268] www/ungoogled-chromium: add the ability to build with any set of audio backends, including without sound for headless usage

2024-08-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280268

--- Comment #8 from Vladimir Druzenko  ---
(In reply to commit-hook from comment #4)
This is not what I suggested to do - see my patch, which is attached to this
PR.
My patch did not assume any changes for current users of binary packages. Only
the ability to disable unnecessary sound backends during manual build.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 280268] www/ungoogled-chromium: add the ability to build with any set of audio backends, including without sound for headless usage

2024-08-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280268

--- Comment #7 from Oleh Hushchenkov  ---
(In reply to Robert Nagy from comment #6)

This port affects a lot of people, that have different priorities.
One wants minimal dependency, another wants best supported but huge pulseaudio,
one builds it locally, another can't do it due to highend pc required for
builds.
Very hard to satisfy everyones need.

I think that following previous approach, to not make pulse as a dependency,
and enabling all three audio backends by default(preserving port options to
disable undesired backends) will satisfy everyone.

However I don't know how it affects maintainability of the port.

Probably, it's better to wait for other people who will come here after last
commit to say that it breaks their use case. To see if there will be some
consensus among them.

And thanks again.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 280268] www/ungoogled-chromium: add the ability to build with any set of audio backends, including without sound for headless usage

2024-08-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280268

--- Comment #6 from Robert Nagy  ---
(In reply to Oleh Hushchenkov from comment #5)

Yes the logic is still there, so all three can be enabled by default.
That's fine by me.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 280268] www/ungoogled-chromium: add the ability to build with any set of audio backends, including without sound for headless usage

2024-08-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280268

Oleh Hushchenkov  changed:

   What|Removed |Added

 CC||o.hushchen...@gmail.com

--- Comment #5 from Oleh Hushchenkov  ---
(In reply to Robert Nagy from comment #3)

Thank you for working on chromium port.

After this change, people who can't build chromium locally have no possibility
to use other audio backends but sndio.

If internal audio backend selection logic is still there, it would be better to
enable all 3 backends by default as it was before this PR.

The reporter still be able to disable undesired backends by added port options.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 280268] www/ungoogled-chromium: add the ability to build with any set of audio backends, including without sound for headless usage

2024-08-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280268

Robert Nagy  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|New |Closed

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 280268] www/ungoogled-chromium: add the ability to build with any set of audio backends, including without sound for headless usage

2024-08-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280268

--- Comment #4 from commit-h...@freebsd.org ---
A commit in branch main references this bug:

URL:
https://cgit.FreeBSD.org/ports/commit/?id=18a8d77e0e182d2188cc6b8dbb9ebac63d71d16d

commit 18a8d77e0e182d2188cc6b8dbb9ebac63d71d16d
Author: Robert Nagy 
AuthorDate: 2024-08-05 15:00:16 +
Commit: Robert Nagy 
CommitDate: 2024-08-05 15:16:14 +

www/{*chromium,iridium}: bring back audio knobs

It seems that 683K worth of libs are too much dependencies.

PR: 280268

 www/chromium/Makefile  | 37 --
 www/chromium/distinfo  |  4 +--
 www/chromium/files/patch-media_audio_BUILD.gn  | 11 ---
 www/iridium/Makefile   | 35 +++-
 www/iridium/distinfo   |  4 +--
 www/iridium/files/patch-media_audio_BUILD.gn   | 11 ---
 www/ungoogled-chromium/Makefile| 37 --
 www/ungoogled-chromium/distinfo|  4 +--
 .../files/patch-media_audio_BUILD.gn   | 11 ---
 9 files changed, 86 insertions(+), 68 deletions(-)

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 280268] www/ungoogled-chromium: add the ability to build with any set of audio backends, including without sound for headless usage

2024-08-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280268

--- Comment #3 from Robert Nagy  ---
I give up. Let's add more knobs back, even though I did not hear a proper
argument of why so far. I will make a diff for all of the chromium based ports.

-- 
You are receiving this mail because:
You are the assignee for the bug.


Problem reports for chrom...@freebsd.org that need special attention

2024-08-04 Thread bugzilla-noreply
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
Open|233095 | www/firefox geolocation no longer working 

1 problems total for which you should take action.


[Bug 280268] www/ungoogled-chromium: add the ability to build with any set of audio backends, including without sound for headless usage

2024-08-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280268

--- Comment #2 from Vladimir Druzenko  ---
I don't need sndio and pulse in any form. What's the problem with keeping these
options? I need to apply my patches every time the port is updated - it takes
much longer than just keeping them in the port (they don't require any
maintenance).

-- 
You are receiving this mail because:
You are the assignee for the bug.


Problem reports for chrom...@freebsd.org that need special attention

2024-07-28 Thread bugzilla-noreply
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
Open|233095 | www/firefox geolocation no longer working 

1 problems total for which you should take action.


[Bug 254564] www/chromium: wrong dependency to libkrb5

2024-07-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254564

--- Comment #8 from Dave Hayes  ---
As of 2024Q3 this is still required for me to build chromium:

--- www/chromium/Makefile.orig  2024-07-28 09:22:15.319382000 -0700
+++ www/chromium/Makefile   2024-07-28 09:22:59.747868000 -0700
@@ -188,7 +188,7 @@

 DRIVER_MAKE_ARGS=  chromedriver

-HEIMDAL_LIB_DEPENDS=   libkrb.so.26:security/heimdal
+HEIMDAL_LIB_DEPENDS=   libkrb5.so.26:security/heimdal
 KERBEROS_VARS= GN_ARGS+=use_kerberos=true
 KERBEROS_VARS_OFF= GN_ARGS+=use_kerberos=false

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


[Bug 280376] www/qt6-webengine: Fix build on head after string.h changes

2024-07-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280376

--- Comment #7 from Hiroki Tagato  ---
(In reply to Guido Falsi from comment #3)

I have confirmed the same patch can be applied to devel/electron* as well. They
build fine on recent 15-CURRENT with the changes.

Thanks for the heads up and the patch!

-- 
You are receiving this mail because:
You are on the CC list for the bug.


Problem reports for chrom...@freebsd.org that need special attention

2024-07-21 Thread bugzilla-noreply
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
Open|233095 | www/firefox geolocation no longer working 

1 problems total for which you should take action.


[Bug 280376] www/qt6-webengine: Fix build on head after string.h changes

2024-07-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280376

--- Comment #6 from Guido Falsi  ---
(In reply to Jason E. Hale from comment #5)

Thanks to you!

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug 280376] www/qt6-webengine: Fix build on head after string.h changes

2024-07-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280376

Jason E. Hale  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|Open|Closed

--- Comment #5 from Jason E. Hale  ---
(In reply to Guido Falsi from comment #3)
Thanks, Guido! I just committed your changes.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug 280376] www/qt6-webengine: Fix build on head after string.h changes

2024-07-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280376

--- Comment #4 from commit-h...@freebsd.org ---
A commit in branch main references this bug:

URL:
https://cgit.FreeBSD.org/ports/commit/?id=9fd42baef1d67ba2b5be74ec5ca634a044b13cb8

commit 9fd42baef1d67ba2b5be74ec5ca634a044b13cb8
Author: Guido Falsi 
AuthorDate: 2024-07-21 14:27:05 +
Commit: Jason E. Hale 
CommitDate: 2024-07-21 14:50:37 +

www/qt6-webengine: Fix build on recent -CURRENT

Due to recent changes in string.h, the regex in our local patch for the
bundled nasm to check whether mempcpy(3) was available no longer worked.
This caused it to use its own implementation which caused an error due
to a declaration conflict.

Since all currently supported versions of FreeBSD have mempcpy(3), this
patch is no longer needed.

PR: 280376

 ...c_3rdparty_chromium_third__party_nasm_BUILD.gn (gone) | 16 
 ...arty_chromium_third__party_nasm_config_config-linux.h | 11 ++-
 2 files changed, 2 insertions(+), 25 deletions(-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug 280376] www/qt6-webengine: Fix build on head after string.h changes

2024-07-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280376

Guido Falsi  changed:

   What|Removed |Added

 Attachment #252179|0   |1
is obsolete||

--- Comment #3 from Guido Falsi  ---
Created attachment 252193
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=252193&action=edit
patch v2

I implemented the patch as suggested by jhale.

I'm attaching it, it works fine here!

Thanks!

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug 280376] www/qt6-webengine: Fix build on head after string.h changes

2024-07-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280376

--- Comment #2 from Guido Falsi  ---
(In reply to Jason E. Hale from comment #1)

Thanks for explaining this to me. I was not aware of such details. I was simply
in an hurry to fix the ports build on my machine and thought I could report the
issue, a patch also helps defining the issue.

Thanks for the fast feedback!

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug 280376] www/qt6-webengine: Fix build on head after string.h changes

2024-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280376

Jason E. Hale  changed:

   What|Removed |Added

 Status|New |Open
  Flags|maintainer-feedback?(kde@Fr |maintainer-feedback+
   |eeBSD.org)  |
 CC||chrom...@freebsd.org,
   ||jh...@freebsd.org,
   ||tagat...@freebsd.org

--- Comment #1 from Jason E. Hale  ---
Thanks for the report and patch, but I think the underlying issue is that the
regex in [1] no longer matches after [2], so HAVE_MEMPCPY=1 no longer gets
defined and nasm uses it's own implementation instead. The pattern
"*\*mempcpy*" will match "*mempcpy", but not "*(mempcpy)".

Since all supported versions of FreeBSD have mempcpy(3), we can probably just
remove [1] entirely and that part of the patch in [3], but I haven't tested
that theory yet.

These patches were taken from www/chromium, so it and other chromium-based
ports like www/electron*, will also need reworked. CC'ing maintainers of those
ports.

[1]
https://cgit.freebsd.org/ports/tree/www/qt6-webengine/files/patch-src_3rdparty_chromium_third__party_nasm_BUILD.gn#n9
[2]
https://github.com/freebsd/freebsd-src/commit/0c47b9c211ede221629914ae0c5553586e772109
[3]
https://cgit.freebsd.org/ports/tree/www/qt6-webengine/files/patch-src_3rdparty_chromium_third__party_nasm_config_config-linux.h#n36

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug 280268] www/ungoogled-chromium: add the ability to build with any set of audio backends, including without sound for headless usage

2024-07-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280268

Robert Nagy  changed:

   What|Removed |Added

 CC||rn...@freebsd.org

--- Comment #1 from Robert Nagy  ---
Hi

I will not take this. If you want to disable Audio completely,
then you can have one option to disable audio from the build completely,
but I do not want to re-add options for all the backends.

-- 
You are receiving this mail because:
You are the assignee for the bug.


Problem reports for chrom...@freebsd.org that need special attention

2024-07-14 Thread bugzilla-noreply
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
Open|233095 | www/firefox geolocation no longer working 

1 problems total for which you should take action.


maintainer-feedback requested: [Bug 280268] www/ungoogled-chromium: add the ability to build with any set of audio backends, including without sound for headless usage

2024-07-13 Thread bugzilla-noreply
Bugzilla Automation  has asked freebsd-chromium (Nobody)
 for maintainer-feedback:
Bug 280268: www/ungoogled-chromium: add the ability to build with any set of
audio backends, including without sound for headless usage
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280268



--- Description ---
Tested build in poudriere 14.1 amd64 with ALSA only and without sounds + run
both versions.



[Bug 280268] www/ungoogled-chromium: add the ability to build with any set of audio backends, including without sound for headless usage

2024-07-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280268

Bug ID: 280268
   Summary: www/ungoogled-chromium: add the ability to build with
any set of audio backends, including without sound for
headless usage
   Product: Ports & Packages
   Version: Latest
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: Individual Port(s)
  Assignee: chrom...@freebsd.org
  Reporter: v...@freebsd.org
 Flags: maintainer-feedback?(chrom...@freebsd.org)
  Assignee: chrom...@freebsd.org
 Attachment #252029 maintainer-approval?
 Flags:

Created attachment 252029
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=252029&action=edit
v1

Tested build in poudriere 14.1 amd64 with ALSA only and without sounds + run
both versions.

-- 
You are receiving this mail because:
You are the assignee for the bug.


Problem reports for chrom...@freebsd.org that need special attention

2024-07-07 Thread bugzilla-noreply
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
Open|233095 | www/firefox geolocation no longer working 

1 problems total for which you should take action.


[Bug 279998] www/chromium: Skype does not work after implement selectable audio backend support

2024-07-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279998

Oleh Hushchenkov  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|Open|Closed

--- Comment #5 from Oleh Hushchenkov  ---
I have tested Skype + ALSA with the latest package. It works as before
selectable audio backend support was added.

So, I'm closing the bug.

Thanks again.

-- 
You are receiving this mail because:
You are the assignee for the bug.


Problem reports for chrom...@freebsd.org that need special attention

2024-06-30 Thread bugzilla-noreply
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
Open|233095 | www/firefox geolocation no longer working 

1 problems total for which you should take action.


[Bug 278413] www/chromium: --headless seems to be broken

2024-06-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278413

end...@gmail.com changed:

   What|Removed |Added

 CC||end...@gmail.com

--- Comment #1 from end...@gmail.com ---
I can confirm the same issue with Chromium 126.0.6478.126
on
FreeBSD 14.0-RELEASE-p6 #0: Tue Mar 26 20:26:20 UTC 2024
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/amd64.amd64/sys/GENERIC
amd64

I'm currently trying to build Chrome 117.0.5938.132 this way :

cloned branch 2203Q3 from github

replacing www/chromium into my port tree

building in process... take long...

=> I'm interesting if there's a faster way to downgrade to some chrome
118.0.5993.88 or older as this may help with further investigations here

thx

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279998] www/chromium: Skype does not work after implement selectable audio backend support

2024-06-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279998

--- Comment #4 from Oleh Hushchenkov  ---
(In reply to Robert Nagy from comment #2)
Hi Robert,

MicTest and Google Meet work fine with sndio.

It's solely Skype issue, people describe it as audio stuttering and metallic
echoes. This happens only with sndio.

Thanks for the fix. I rarely use Skype, so didn't report it earlier.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279998] www/chromium: Skype does not work after implement selectable audio backend support

2024-06-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279998

--- Comment #3 from commit-h...@freebsd.org ---
A commit in branch main references this bug:

URL:
https://cgit.FreeBSD.org/ports/commit/?id=0792294cb90ce950b6a0d58ddc2f3cd95111b0d6

commit 0792294cb90ce950b6a0d58ddc2f3cd95111b0d6
Author: Robert Nagy 
AuthorDate: 2024-06-26 15:46:42 +
Commit: Robert Nagy 
CommitDate: 2024-06-26 15:47:51 +

www/{*chromium,iridium}: fix audio backend selection logic

PR: 279998

 www/chromium/Makefile| 1 +
 .../files/patch-media_audio_sndio_audio__manager__sndio.cc   | 9 +
 www/iridium/Makefile | 1 +
 .../files/patch-media_audio_sndio_audio__manager__sndio.cc   | 9 +
 www/ungoogled-chromium/Makefile  | 1 +
 .../files/patch-media_audio_sndio_audio__manager__sndio.cc   | 9 +
 6 files changed, 18 insertions(+), 12 deletions(-)

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279998] www/chromium: Skype does not work after implement selectable audio backend support

2024-06-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279998

--- Comment #2 from Robert Nagy  ---
Ehrm I actually find a logic error in the auto selection. I will commit
a fix for that soon.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279998] www/chromium: Skype does not work after implement selectable audio backend support

2024-06-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279998

Robert Nagy  changed:

   What|Removed |Added

 Status|New |Open
 CC||rn...@freebsd.org

--- Comment #1 from Robert Nagy  ---
(In reply to Oleh Hushchenkov from comment #0)

Hi

I've just tested both sndio and the alsa audio backend
and both audio input and output work fine with them,
including google meet.

Can you do a test on https://restream.io/tools/mic-test with

--audio-backend=sndio and then --audio-backend=alsa.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279998] www/chromium: Skype does not work after implement selectable audio backend support

2024-06-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279998

Bug ID: 279998
   Summary: www/chromium: Skype does not work after implement
selectable audio backend support
   Product: Ports & Packages
   Version: Latest
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: Individual Port(s)
  Assignee: chrom...@freebsd.org
  Reporter: o.hushchen...@gmail.com
 Flags: maintainer-feedback?(chrom...@freebsd.org)
  Assignee: chrom...@freebsd.org

Previously I used chromium built from ports with audio backend alsa. Skype
calls worked with it.

After #246449 was committed I use chromium package. Tried Skype call recently,
with default audio backend sndio, but people can't hear me. Then I added
--audio-backend=alsa and tried again, but the same issue.

Fortunately no .so version bump for dependencies since version 124. So I just
installed chromium 124 with alsa and tried again. It works.

Looks like alsa does not activated/used properly after implement selectable
audio backend support was committed.

-- 
You are receiving this mail because:
You are the assignee for the bug.


maintainer-feedback requested: [Bug 279998] www/chromium: Skype does not work after implement selectable audio backend support

2024-06-26 Thread bugzilla-noreply
Bugzilla Automation  has asked freebsd-chromium (Nobody)
 for maintainer-feedback:
Bug 279998: www/chromium: Skype does not work after implement selectable audio
backend support
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279998



--- Description ---
Previously I used chromium built from ports with audio backend alsa. Skype
calls worked with it.

After #246449 was committed I use chromium package. Tried Skype call recently,
with default audio backend sndio, but people can't hear me. Then I added
--audio-backend=alsa and tried again, but the same issue.

Fortunately no .so version bump for dependencies since version 124. So I just
installed chromium 124 with alsa and tried again. It works.

Looks like alsa does not activated/used properly after implement selectable
audio backend support was committed.



[Bug 205188] www/chromium: Latest version does not compile with option PULSEAUDIO set

2024-06-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205188

--- Comment #9 from swati sharma  ---
When you've chosen to have a fun time with a group of hot female escorts, you
can book them anytime. With your laptop in your hand and a comfy couch, you are
able to browse the site, go through all the details about each of the female
escorts in Jaipur and then choose the one you want to arrange an appointment
for a play date. 
https://www.jaipurescorts.org
https://www.jaipurescorts.org/call-girls-service-jaipur.html
https://www.jaipurescorts.org/raja-park-escorts.html
https://www.jaipurescorts.org/bani-park-escorts-services.html
https://www.jaipurescorts.org/tonk-road-escorts-services.html
https://www.jaipurescorts.org/durgapura-escorts-services.html
https://www.jaipurescorts.org/jagatpura-escorts-services.html
https://www.jaipurescorts.org/gopalpura-escorts-services.html
https://www.jaipurescorts.org/mansarovar-escorts-services.html
https://www.jaipurescorts.org/civil-lines-escorts-services.html
https://www.jaipurescorts.org/sangner-escorts-services.html
https://www.jaipurescorts.org/bhankrota-call-girls-escorts-services.html
https://www.jaipurescorts.org/ajmer-road-call-girls-escorts-services.html
https://www.jaipurescorts.org/chitrakoot-call-girls-escorts-services.html
https://www.jaipurescorts.org/jhotwara-call-girls-escorts-services.html
https://www.jaipurescorts.org/bajaj-nagar-call-girls-escorts-services.html
https://www.jaipurescorts.org/adarsh-nagar-call-girls-escorts-services.html
https://www.jaipurescorts.org/pratap-nagar-call-girls-escorts-services.html
https://www.jaipurescorts.org/mahesh-nagar-call-girls-escorts-services.html
https://www.jaipurescorts.org/shyam-nagar-call-girls-escorts-services.html
https://www.jaipurescorts.org/nirman-nagar-call-girls-escorts-services.html
https://www.jaipurescorts.org/malviya-nagar-escorts-services.html
https://www.jaipurescorts.org/vaishali-nagar-escorts-services.html
https://www.jaipurescorts.org/sodala-call-girls-escorts-services.html
https://www.jaipurescorts.org/sindhi-camp-call-girls-escorts-services.html
https://www.jaipurescorts.org/narayan-vihar-call-girls-escorts-services.html
https://www.jaipurescorts.org/bais-godam-call-girls-escorts-services.html
https://www.jaipurescorts.org/vivek-vihar-call-girls-escorts-services.html
https://www.jaipurescorts.org/khatipura-call-girls-escorts-services.html
https://www.jaipurescorts.org/ajmer-escort-service.html
https://www.jaipurescorts.org/jaisalmer-escort-service.html
https://www.jaipurescorts.org/udaipur-escort-service.html
https://www.jaipurescorts.org/jodhpur-escort-service.html
https://www.jaipurescorts.org/pushkar-escort-service.html
https://www.jaipurescorts.org/beawar-escort-service.html
https://www.jaipurescorts.org/kishangarh-escort-service.html

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 205188] www/chromium: Latest version does not compile with option PULSEAUDIO set

2024-06-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205188

--- Comment #8 from swati sharma  ---
You can seek Chandigarh independent escorts at any time to solve problems of a
lifestyle that is not tasteful. Girls who are a good match have an excellent
reputation and are proficient in their job, which is to be able to show
themselves as a companion in difficult times. The best ways to spend your time. 
https://www.angelsnight.in
https://www.angelsnight.in/chandigarh-escort-service.html
https://www.angelsnight.in/ahmedabad-escort-service.html
https://www.angelsnight.in/ajmer-escort-service.html
https://www.angelsnight.in/dehradun-escort-service.html
https://www.angelsnight.in/jaipur-escort-service.html
https://www.angelsnight.in/jodhpur-escort-service.html

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 205188] www/chromium: Latest version does not compile with option PULSEAUDIO set

2024-06-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205188

--- Comment #7 from swati sharma  ---
The most genuine joy and satisfaction is when you are able to engage in
intimate interactions. These females will know that you will have the right
time when you need someone close to you to melt away into darkness. All Call
Girls are sources of pleasure and are able to provide anyone with pleasure to
the amazing. 
https://www.alishaoberoi.co.in
https://www.alishaoberoi.co.in/gurgaon-escort-service.html
https://www.alishaoberoi.co.in/ajmer-escort-service.html
https://www.alishaoberoi.co.in/jodhpur-escort-service.html
https://jodhpur.alishaoberoi.com/
https://www.alishaoberoi.co.in/pushkar-escort-service.html
https://www.alishaoberoi.co.in/haldwani-escort-service.html
https://www.alishaoberoi.co.in/ramnagar-escort-service.html
https://www.alishaoberoi.co.in/rudrapur-escort-service.html
https://www.alishaoberoi.co.in/bhimtal-escort-service.html
https://www.alishaoberoi.co.in/udaipur-escort-service.html
https://www.alishaoberoi.co.in/dehradun-escort-service.html

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 205188] www/chromium: Latest version does not compile with option PULSEAUDIO set

2024-06-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205188

--- Comment #6 from swati sharma  ---
The services we provide are unique and extraordinary. There might be a lot of
young women in Ajmer, but those working with us look like magical pixies that
can turn your visions into the real world. The world is changing, and
technological advancement is changing our lives at a rapid pace. We've got top
and tasteful names of Bollywood stars on our list that are prepared to make
your evening deliciously hot and tasty. In fact, it's real and real! You can
grab access to gorgeous Bollywood ladies on our portal.
https://www.shikharoy.in
https://www.aurangabaddesires.in
https://www.vmumbaiescorts.in

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 205188] www/chromium: Latest version does not compile with option PULSEAUDIO set

2024-06-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205188

--- Comment #5 from swati sharma  ---
I have over 23 years of experience working as an Escort professional in the
field of rub. Make sure you are able to meet your needs first to make sure you
are feeling your most at your best. Spa knead spa, so call it your body.  Our
Goa escorts are highly skilled and dedicated to their job. They make you feel
comfortable with the kind of assistance we offer you. We guarantee that we will
serve you in a manner that you return to us time and time. 
https://www.juhimittal.com
https://www.juhimittal.com/location/panaji-escorts.html
https://www.juhimittal.com/location/calangute-beach-escorts.html
https://www.juhimittal.com/location/baga-beach-escorts.html
https://www.juhimittal.com/location/anjuna-beach-escorts.html
https://www.juhimittal.com/location/colva-beach-escorts.html
https://www.juhimittal.com/location/candolim-beach-escorts.html

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 205188] www/chromium: Latest version does not compile with option PULSEAUDIO set

2024-06-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205188

--- Comment #4 from swati sharma  ---
In certain cases, portfolios conceal the disintegration of them. Thus, the
physical appearance and images are both altered things. Udaipur is a city that
is famous across the globe. The escorts of Udaipur are one of the hottest and
hottest women found in and around Rajasthan. 
https://find.udaipurescortservice.com
https://find.udaipurescortservice.com/call-girls-udaipur-city.html

-- 
You are receiving this mail because:
You are the assignee for the bug.


Problem reports for chrom...@freebsd.org that need special attention

2024-06-23 Thread bugzilla-noreply
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
Open|233095 | www/firefox geolocation no longer working 

1 problems total for which you should take action.


[Bug 279880] www/iridium - History and Cache are not cleared when delete history is selected.

2024-06-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279880

Bug ID: 279880
   Summary: www/iridium - History and Cache are not cleared when
delete history is selected.
   Product: Ports & Packages
   Version: Latest
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: Individual Port(s)
  Assignee: chrom...@freebsd.org
  Reporter: byrn...@harte-lyne.ca
  Assignee: chrom...@freebsd.org
 Flags: maintainer-feedback?(chrom...@freebsd.org)

Iridium does not clear cache or history when delete action selected from
browser customization and control history pane.

The only way found to delete history is to open the browser history page and
individually select and delete each entry.

-- 
You are receiving this mail because:
You are the assignee for the bug.


maintainer-feedback requested: [Bug 279880] www/iridium - History and Cache are not cleared when delete history is selected.

2024-06-20 Thread bugzilla-noreply
Bugzilla Automation  has asked freebsd-chromium (Nobody)
 for maintainer-feedback:
Bug 279880: www/iridium - History and Cache are not cleared when delete history
is selected.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279880



--- Description ---
Iridium does not clear cache or history when delete action selected from
browser customization and control history pane.

The only way found to delete history is to open the browser history page and
individually select and delete each entry.



Problem reports for chrom...@freebsd.org that need special attention

2024-06-16 Thread bugzilla-noreply
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
Open|233095 | www/firefox geolocation no longer working 

1 problems total for which you should take action.


[Bug 263833] www/chromium: no longer packaged for FreeBSD:12:amd64 – build/timeout

2024-06-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263833

Jan Beich  changed:

   What|Removed |Added

 Resolution|--- |Overcome By Events
 Status|Open|Closed

--- Comment #5 from Jan Beich  ---
FreeBSD < 13 isn't supported since ports bbab7f59e963.

-- 
You are receiving this mail because:
You are the assignee for the bug.


Problem reports for chrom...@freebsd.org that need special attention

2024-06-09 Thread bugzilla-noreply
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
Open|233095 | www/firefox geolocation no longer working 

1 problems total for which you should take action.


maintainer-feedback requested: [Bug 279610] www/linux-chrome: wrong description

2024-06-09 Thread bugzilla-noreply
Bugzilla Automation  has asked freebsd-chromium (Nobody)
 for maintainer-feedback:
Bug 279610: www/linux-chrome: wrong description
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279610



--- Description ---
Hi,

I've noticed that the ports www/linux-chrome and www/chromium share the same
description, basically only the port name changed.
It can be confusing, people might not realize which one is the proprietary
software.
I myself wasn't sure about what the port was about until I looked into the
makefile which led me to the google site:
https://cgit.freebsd.org/ports/tree/www/linux-chrome/Makefile#n5
https://dl.google.com/linux/chrome/rpm/stable/x86_64/

This is the current description:
Chrome is an open-source browser project that aims to build a safer,
faster, and more stable way for all users to experience the web.

The Chrome website contains design documents, architecture overviews,
testing information, and more to help you learn to build and work with
the Chrome source code.

Source:
https://cgit.freebsd.org/ports/tree/www/linux-chrome/pkg-descr
https://cgit.freebsd.org/ports/tree/www/chromium/pkg-descr

https://www.freshports.org/www/linux-chrome/
https://www.freshports.org/www/chromium/

Thank you.



[Bug 279610] www/linux-chrome: wrong description

2024-06-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279610

Bug ID: 279610
   Summary: www/linux-chrome: wrong description
   Product: Ports & Packages
   Version: Latest
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: Individual Port(s)
  Assignee: chrom...@freebsd.org
  Reporter: ze...@zaclys.net
 Flags: maintainer-feedback?(chrom...@freebsd.org)
  Assignee: chrom...@freebsd.org

Hi,

I've noticed that the ports www/linux-chrome and www/chromium share the same
description, basically only the port name changed.
It can be confusing, people might not realize which one is the proprietary
software.
I myself wasn't sure about what the port was about until I looked into the
makefile which led me to the google site:
https://cgit.freebsd.org/ports/tree/www/linux-chrome/Makefile#n5
https://dl.google.com/linux/chrome/rpm/stable/x86_64/

This is the current description:
Chrome is an open-source browser project that aims to build a safer,
faster, and more stable way for all users to experience the web.

The Chrome website contains design documents, architecture overviews,
testing information, and more to help you learn to build and work with
the Chrome source code.

Source:
https://cgit.freebsd.org/ports/tree/www/linux-chrome/pkg-descr
https://cgit.freebsd.org/ports/tree/www/chromium/pkg-descr

https://www.freshports.org/www/linux-chrome/
https://www.freshports.org/www/chromium/

Thank you.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279397] www/chromium sqlite3_shim.c compilation error

2024-06-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279397

--- Comment #23 from George Mitchell  ---
(In reply to commit-hook from comment #17)
Following the commit in comment #17, I have successfully compiled sqlite3, and
I have a compile of chromium in progress which has gotten past the problematic
point.  So I'm glad this bug has been closed as fixed.  Again, thanks to all!

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279397] www/chromium sqlite3_shim.c compilation error

2024-06-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279397

--- Comment #22 from Tatsuki Makino  ---
It seems to me that any way to fix it with a patch so that it can be built is
good.

However, I think there is something strange about the fact that _XOPEN_SOURCE
was defined because there are functions that cannot be used.
If it is defined, wouldn't we have to give up on using alloca in the entire
source?
Isn't it strange that the definition is variable depending on the type of OS?

It's not something to do here, though, which is already closed :)

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279397] www/chromium sqlite3_shim.c compilation error

2024-06-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279397

--- Comment #21 from Robert Nagy  ---
(In reply to Florian Walpen from comment #19)

It is a compiler / freebsd-base change that triggered it, not a chromium
change.

Yes the patches are shared between OpenBSD and FreeBSD as I maintain the port
for both of them.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279397] www/chromium sqlite3_shim.c compilation error

2024-06-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279397

--- Comment #20 from George Mitchell  ---
Having just now recovered from the trauma--whoops, I mean exercise--of fixing
for CVE-2024-5274 (with the ad-hoc patch, which worked fine), I'll install the
new chromium on my vast local network (has four machines) before I try dealing
with the upstreamable fix.  But my sincere thanks to all who help maintain
chromium on FreeBSD!  (One thousand two hundred and ninety-two patch files?? 
Bravo!)

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279397] www/chromium sqlite3_shim.c compilation error

2024-06-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279397

--- Comment #19 from Florian Walpen  ---
(In reply to Robert Nagy from comment #15)
> I cannot reproduce this on 13.3/amd64 so I assume this happens due to some
> header poisoning from some dependencies.

I suppose you did check that all of your patches are in main now?
The trigger has to be somewhere in the changes since 125.0.6422.76, but I
didn't see anything obvious in port commits. Maybe a chromium upstream change?

BTW, we have patches in www/chromium specific to OpenBSD, are we sharing
patches with OpenBSD chromium maintainers? Does their port build?

> If that is to be upstreamed the comment needs to be fixed up as well.

Yeah, it's not meant to be upstreamed just like that, but I'd want to discuss
and test the (supposedly) proper fix here before proposing it upstream.
Regarding upstream, SQLite still has no pull requests anyway, but they got a
support forum since my last SQLite bug fix long time ago. There I found a
similar PR:

https://www.sqlite.org/forum/forumpost/6a755ae973123d61c7a22aeabbd16d1f2b5747e94fddd59207e56fa9d0b97e66

I think we could offer both the proper fix and one checking for __FreeBSD__
only. They may be hesitant to possibly break other build systems. Long standing
bugs tend to become standard ;-)

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279397] www/chromium sqlite3_shim.c compilation error

2024-06-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279397

Robert Nagy  changed:

   What|Removed |Added

 Status|In Progress |Closed
 Resolution|--- |FIXED

--- Comment #18 from Robert Nagy  ---
I've committed a similar fix, but only for FreeBSD for now as we need
to investigate further for other platforms.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279397] www/chromium sqlite3_shim.c compilation error

2024-06-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279397

--- Comment #17 from commit-h...@freebsd.org ---
A commit in branch main references this bug:

URL:
https://cgit.FreeBSD.org/ports/commit/?id=4ba66b974729b45f6c2418d87d7403ef2e7b474d

commit 4ba66b974729b45f6c2418d87d7403ef2e7b474d
Author: Robert Nagy 
AuthorDate: 2024-06-03 12:52:56 +
Commit: Robert Nagy 
CommitDate: 2024-06-03 12:54:46 +

www/*chromium: update to 125.0.6422.141

Additionally to the update, do not define _XOPEN_SOURCE on FreeBSD
either in the internal copy of sqlite3 to avoid new compiler errors
with llvm18.

Security:  
https://vuxml.freebsd.org/freebsd/b058380e-21a4-11ef-8a0f-a8a1599412c6.html
PR: 279397

 www/chromium/Makefile  |  5 +++--
 www/chromium/distinfo  | 14 +++---
 ...ty_libaom_source_libaom_aom__ports_aarch64__cpudetect.c |  4 ++--
 .../patch-third__party_sqlite_src_amalgamation_sqlite3.c   | 11 ++-
 www/chromium/files/patch-third__party_zlib_cpu__features.c |  4 ++--
 www/chromium/files/patch-v8_src_api_api.cc |  4 ++--
 www/ungoogled-chromium/Makefile|  2 +-
 www/ungoogled-chromium/distinfo| 14 +++---
 ...ty_libaom_source_libaom_aom__ports_aarch64__cpudetect.c |  4 ++--
 .../patch-third__party_sqlite_src_amalgamation_sqlite3.c   | 11 ++-
 .../files/patch-third__party_zlib_cpu__features.c  |  4 ++--
 www/ungoogled-chromium/files/patch-v8_src_api_api.cc   |  4 ++--
 12 files changed, 50 insertions(+), 31 deletions(-)

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279397] www/chromium sqlite3_shim.c compilation error

2024-06-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279397

mario felicioni  changed:

   What|Removed |Added

 CC||marietto2...@gmail.com

--- Comment #16 from mario felicioni  ---
On FreeBSD 14p6 :

[root@marietto /usr/ports/www/chromium]==> MAKE_JOBS_UNSAFE=yes make

 -m64 -msse3 -Xclang -fdebug-compilation-dir -Xclang . -no-canonical-prefixes
-ftrivial-auto-var-init=pattern -O2 -fdata-sections -ffunction-sections
-fno-unique-section-names -fno-math-errno -fno-omit-frame-pointer -g0
-fprofile-use=../../chrome/build/pgo_profiles/chrome-linux-6422-1715686914-39d3c200676449e33ad84989ea45ad3474fab6e2-013ab7d1275249b95c27d770d257ac6d2359.profdata
-Wno-profile-instr-unprofiled -Wno-profile-instr-out-of-date
-Wno-backend-plugin -mllvm -enable-ext-tsp-block-placement=1
-fvisibility=hidden -Wheader-hygiene -Wstring-conversion
-Wtautological-overlap-compare -Wall -Wno-unused-variable -Wno-c++11-narrowing
-Wno-missing-field-initializers -Wno-unused-parameter -Wno-psabi
-Wloop-analysis -Wno-unneeded-internal-declaration -Wno-cast-function-type
-Wno-ignored-pragma-optimize -Wno-deprecated-builtins
-Wno-bitfield-constant-conversion -Wno-deprecated-this-capture
-Wno-invalid-offsetof -Wno-vla-extension -Wno-shadow -Wno-unused-function
-isystem/usr/local/include -isystem/usr/local/include -std=c11 -c
./../third_party/sqlite/sqlite3_shim.c -o
obj/third_party/sqlite/chromium_sqlite3/sqlite3_shim.o
In file included from ../../third_party/sqlite/sqlite3_shim.c:16:
./../third_party/sqlite/src/amalgamation/sqlite3.c:53619:21: error: call to
undeclared function 'alloca'; ISO C99 and later do not support implicit
function declarations [-Wimplicit-function-declaration]
 53619 | u32 *aiValues = sqlite3StackAllocRaw(0, sizeof(p->u.aHash));
   | ^
./../third_party/sqlite/src/amalgamation/sqlite3.c:20536:38: note: expanded
from macro 'sqlite3StackAllocRaw'
 20536 | # define sqlite3StackAllocRaw(D,N)   alloca(N)
   |  ^
./../third_party/sqlite/src/amalgamation/sqlite3.c:53619:10: error:
incompatible integer to pointer conversion initializing 'u32 *' (aka 'unsigned
int *') with an expression of type 'int' [-Wint-conversion]
 53619 | u32 *aiValues = sqlite3StackAllocRaw(0, sizeof(p->u.aHash));
   |  ^  ~~~
./../third_party/sqlite/src/amalgamation/sqlite3.c:78371:14: error: call to
undeclared function 'alloca'; ISO C99 and later do not support implicit
function declarations [-Wimplicit-function-declaration]
 78371 |   b.apCell = sqlite3StackAllocRaw(0, szScratch );
   |  ^
./../third_party/sqlite/src/amalgamation/sqlite3.c:20536:38: note: expanded
from macro 'sqlite3StackAllocRaw'
 20536 | # define sqlite3StackAllocRaw(D,N)   alloca(N)
   |  ^
./../third_party/sqlite/src/amalgamation/sqlite3.c:78371:12: error:
incompatible integer to pointer conversion assigning to 'u8 **' (aka 'unsigned
char **') from 'int' [-Wint-conversion]
 78371 |   b.apCell = sqlite3StackAllocRaw(0, szScratch );
   |^ ~~~
./../third_party/sqlite/src/amalgamation/sqlite3.c:166054:12: error: call to
undeclared function 'alloca'; ISO C99 and later do not support implicit
function declarations [-Wimplicit-function-declaration]
 166054 |   pSpace = sqlite3StackAllocRawNN(pParse->db, nSpace);
|^
./../third_party/sqlite/src/amalgamation/sqlite3.c:20537:38: note: expanded
from macro 'sqlite3StackAllocRawNN'
 20537 | # define sqlite3StackAllocRawNN(D,N) alloca(N)
   |  ^
./../third_party/sqlite/src/amalgamation/sqlite3.c:166054:10: error:
incompatible integer to pointer conversion assigning to 'char *' from 'int'
[-Wint-conversion]
 166054 |   pSpace = sqlite3StackAllocRawNN(pParse->db, nSpace);
|  ^ ~~
6 errors generated.
ninja: build stopped: subcommand failed.
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/www/chromium
*** Error code 1

Stop.
make: stopped in /usr/ports/www/chromium

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279397] www/chromium sqlite3_shim.c compilation error

2024-06-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279397

--- Comment #15 from Robert Nagy  ---
(In reply to Florian Walpen from comment #12)

If that is to be upstreamed the comment needs to be fixed up as well.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279397] www/chromium sqlite3_shim.c compilation error

2024-06-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279397

--- Comment #14 from Konstantin Belousov  ---
(In reply to Robert Nagy from comment #13)
Removing the patch third__party_sqlite_BUILD.gn did not changed the outcome.
The build still fails with the same alloca() errors from sqlite3_shim.c.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279397] www/chromium sqlite3_shim.c compilation error

2024-06-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279397

Robert Nagy  changed:

   What|Removed |Added

 Status|New |In Progress

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279397] www/chromium sqlite3_shim.c compilation error

2024-06-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279397

Robert Nagy  changed:

   What|Removed |Added

 CC||rn...@freebsd.org

--- Comment #13 from Robert Nagy  ---
I cannot reproduce this on 13.3/amd64 so I assume this happens due to some
header poisoning from some dependencies.
Anyone who can reproduce this 100%, please try to remove
patch-third__party_sqlite_BUILD.gn first.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279397] www/chromium sqlite3_shim.c compilation error

2024-06-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279397

--- Comment #12 from Florian Walpen  ---
(In reply to George Mitchell from comment #10)
I'd like to hear from the maintainer about this. Could well be that
SQLITE_USE_ALLOCA was just disabled in databases/sqlite3 because of the issue
with _XOPEN_SOURCE outlined above. That should be fixed upstream.

In cases like SQLite with many temporary allocations alloca() is a nice
optimization, and in my experience alloca() works fine on FreeBSD.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279397] www/chromium sqlite3_shim.c compilation error

2024-06-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279397

--- Comment #11 from Florian Walpen  ---
Created attachment 251173
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=251173&action=edit
Build www/chromium with proposed upstreamable fix.

Fix the build as explained in previous comment, that may be upstreamable to
SQLite proper. Build is still running, but past the error with sqlite3_shimc.
I tested the same fix with the internal SQLite of devel/qtcreator, no
regressions found.

Will be testing chromium with this fix tomorrow.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279397] www/chromium sqlite3_shim.c compilation error

2024-06-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279397

--- Comment #10 from George Mitchell  ---
(In reply to Tatsuki Makino from comment #7)
My compile using this patch is past the point of the error, so the patch does
work.

I just recompiled databases/sqlite3 to see what I could find out about
SQLITE_USE_ALLOCA there.  It doesn't seem to use that option.  So it seems
plausible to me that it's not a good idea for www/chromium either.  How it gets
turned on for chromium is above my pay grade, but wherever that is is probably
the place to fix this bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.


Problem reports for chrom...@freebsd.org that need special attention

2024-06-02 Thread bugzilla-noreply
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
Open|233095 | www/firefox geolocation no longer working 

1 problems total for which you should take action.


[Bug 279397] www/chromium sqlite3_shim.c compilation error

2024-06-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279397

--- Comment #9 from George Mitchell  ---
Should have noted: I'm on 13.2-RELEASE-p10.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279397] www/chromium sqlite3_shim.c compilation error

2024-06-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279397

George Mitchell  changed:

   What|Removed |Added

 CC||geo...@m5p.com

--- Comment #8 from George Mitchell  ---
Trying the ad-hoc patch now; should know if it works in a few hours.  Thanks,
Tatsuki Makino!

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279397] www/chromium sqlite3_shim.c compilation error

2024-05-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279397

--- Comment #7 from Tatsuki Makino  ---
Created attachment 251127
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=251127&action=edit
ad-hoc patch for www/chromium

I don't think we should do it like this patch :), but I think it will
workaround it on operating systems where FreeBSD and __FreeBSD__ is defined.
Please note that this patch has only been written, and the actual build has not
yet been done.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279397] www/chromium sqlite3_shim.c compilation error

2024-05-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279397

--- Comment #6 from Florian Walpen  ---
I'm currently experimenting with the internal SQLite of devel/qtcreator, which
is easier to test for me. Appending " && !defined(__FreeBSD__)" to the
exceptions for APPLE and DARWIN works, but I think the correct solution for
upstream should be:

#if defined(_POSIX_C_SOURCE) && !defined(_XOPEN_SOURCE)
#  define _XOPEN_SOURCE 600
#endif

Rationale is that _XOPEN_SOURCE helps to extend an already present restriction
to _POSIX_C_SOURCE with XOPEN features. But SQLite should not impose a
restriction to XOPEN features only when there is no POSIX restriction in
effect, thereby reducing the available feature set (like alloca).

I don't have time to create a chromium patch now, it may be defined in multiple
places due to the amalgamated SQLite source.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279397] www/chromium sqlite3_shim.c compilation error

2024-05-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279397

Florian Walpen  changed:

   What|Removed |Added

 CC||pavelivol...@gmail.com

--- Comment #5 from Florian Walpen  ---
(In reply to Tatsuki Makino from comment #4)
You're right, I've read that code multiple times before I spotted the #else,
but with _XOPEN_SOURCE defined there is neither __BSD_VISIBLE nor alloca. And
this is correct I think, according to standards _POSIX_C_SOURCE and
_XOPEN_SOURCE actually *restrict* the set of available headers and
functionality. See:

https://pubs.opengroup.org/onlinepubs/007904975/functions/xsh_chap02_02.html

Which means _XOPEN_SOURCE should never be set if non-standard functionality
like alloca (or BSD, GNU extensions) is used.

Add the maintainer of databases/sqlite3 to this discussion, I think
SQLITE_USE_ALLOCA is disabled there as well?

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279397] www/chromium sqlite3_shim.c compilation error

2024-05-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279397

--- Comment #4 from Tatsuki Makino  ---
The reason why alloca is not defined is likely to be the following part.

# 14123 "../../third_party/sqlite/src/amalgamation/sqlite3.c"
#define _XOPEN_SOURCE 600

This defines _POSIX_C_SOURCE and makes __BSD_VISIBLE completely undefined.

Line 14123 of ${WRKSRC}/third_party/sqlite/src/amalgamation/sqlite3.c reads as
follows

/*
** We need to define _XOPEN_SOURCE as follows in order to enable
** recursive mutexes on most Unix systems and fchmod() on OpenBSD.
** But _XOPEN_SOURCE define causes problems for Mac OS X, so omit
** it.
*/
#if !defined(_XOPEN_SOURCE) && !defined(__DARWIN__) && !defined(__APPLE__)
#  define _XOPEN_SOURCE 600
#endif

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279397] www/chromium sqlite3_shim.c compilation error

2024-05-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279397

Tatsuki Makino  changed:

   What|Removed |Added

 CC||tatsuki_mak...@hotmail.com

--- Comment #3 from Tatsuki Makino  ---
As a preface, I am encountering this problem in 12.4-STABLE amd64 environment
:)
But I'm writing this while looking at the  for 14.1-STABLE.

It seems that if  is used with __BSD_VISIBLE defined, alloca will
become a __builtin_alloca.
If the C version is strict, sys/cdefs.h will set the __BSD_VISIBLE to 0.

First of all, this seems to be the cause of the inability to use alloca.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279397] www/chromium sqlite3_shim.c compilation error

2024-05-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279397

--- Comment #2 from Florian Walpen  ---
Mixed that up, sorry: Linux has an alloca.h header which FreeBSD has not
(defined in stdlib.h). The relevant SQLite config is SQLITE_USE_ALLOCA, and in
devel/qtcreator where I had similar problems I just disabled that.

This may not be the best solution here, since alloca has an impact on runtime
efficiency. We may have to #include "stdlib.h" somewhere.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279397] www/chromium sqlite3_shim.c compilation error

2024-05-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279397

Florian Walpen  changed:

   What|Removed |Added

 CC||d...@submerge.ch

--- Comment #1 from Florian Walpen  ---
I'm getting this error too. Not sure when it was introduced because it was
masked by other config and build errors since 125.0.6422.76.

This is on 14.0-RELEASE with a base compiler of clang 16.0.6, at least the log
says "c++" without any indication of the llvm18 in dependencies.

I've seen this error before in other ports with internal sqlite, there it
happened when the config header for sqlite wasn't adapted properly to FreeBSD.
The alloca function needs an additional header include, in contrast to Linux.
If I remember correctly there is a define for it somewhere in the config.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279397] www/chromium sqlite3_shim.c compilation error

2024-05-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279397

Bug ID: 279397
   Summary: www/chromium sqlite3_shim.c compilation error
   Product: Ports & Packages
   Version: Latest
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: Individual Port(s)
  Assignee: chrom...@freebsd.org
  Reporter: k...@freebsd.org
 Flags: maintainer-feedback?(chrom...@freebsd.org)
  Assignee: chrom...@freebsd.org

Created attachment 251083
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=251083&action=edit
poudriere build log

I started getting the error compiling chromium 125.0.6422.76_1, which is kept
persistent with update to 125.0.6422.112:
In file included from ../../third_party/sqlite/sqlite3_shim.c:16:
./../third_party/sqlite/src/amalgamation/sqlite3.c:53619:21: error: call to
undeclared function 'alloca'; ISO C99 and later do not support implicit
function declarations [-Wimplicit-function-declaration]
 53619 | u32 *aiValues = sqlite3StackAllocRaw(0, sizeof(p->u.aHash));
   | ^
./../third_party/sqlite/src/amalgamation/sqlite3.c:20536:38: note: expanded
from macro 'sqlite3StackAllocRaw'
 20536 | # define sqlite3StackAllocRaw(D,N)   alloca(N)
   |  ^
./../third_party/sqlite/src/amalgamation/sqlite3.c:53619:10: error:
incompatible integer to pointer conversion initializing 'u32 *' (aka 'unsigned
int *') with an expression of type 'int' [-Wint-conversion]
 53619 | u32 *aiValues = sqlite3StackAllocRaw(0, sizeof(p->u.aHash));
   |  ^  ~~~
all seemingly related to alloca().

I am not sure when did that started, might be with an update of llvm18.
Even more, I am not sure if this is a local issue or indeed a port's problem.

The poudriere log is attached.

-- 
You are receiving this mail because:
You are the assignee for the bug.


  1   2   3   4   5   6   7   8   9   10   >