-
```
What steps will reproduce the problem?
1. extract expat-2.0.1 into third_party directory
2. execute ./configure
3. execute hammer.sh
What is the expected output? What do you see instead?
_______…
-
```
What steps will reproduce the problem?
1. extract expat-2.0.1 into third_party directory
2. execute ./configure
3. execute hammer.sh
What is the expected output? What do you see instead?
_______…
-
```
What steps will reproduce the problem?
1. extract expat-2.0.1 into third_party directory
2. execute ./configure
3. execute hammer.sh
What is the expected output? What do you see instead?
_______…
-
```
What steps will reproduce the problem?
1. extract expat-2.0.1 into third_party directory
2. execute ./configure
3. execute hammer.sh
What is the expected output? What do you see instead?
_______…
-
```
What steps will reproduce the problem?
1. extract expat-2.0.1 into third_party directory
2. execute ./configure
3. execute hammer.sh
What is the expected output? What do you see instead?
_______…
-
due to the platform non dependecy of emscripten the dbus or sdcpp-dbus shoudl be a better way to communicate with other linux or windows processes without include problems.
-
On `mark-testing` or `mark-unstable` could be good to upgrade `expat` and check what happens.
There are tons of CVE to fix:
* CVE-2024-45490
* CVE-2024-45491
* CVE-2024-45492
* CVE-2024-28757
…
-
```
What steps will reproduce the problem?
1. extract expat-2.0.1 into third_party directory
2. execute ./configure
3. execute hammer.sh
What is the expected output? What do you see instead?
_______…
-
```
What steps will reproduce the problem?
1. extract expat-2.0.1 into third_party directory
2. execute ./configure
3. execute hammer.sh
What is the expected output? What do you see instead?
_______…
-
```
What steps will reproduce the problem?
1. extract expat-2.0.1 into third_party directory
2. execute ./configure
3. execute hammer.sh
What is the expected output? What do you see instead?
_______…