date: support gcc14 on test_package

[toge]

Specify library name and version: date/*

In gcc14 and msvc, there are compilation errors on building test_package.

---

• I've read the contributing guidelines.
• I've used a recent Conan client version close to the currently deployed.
• I've tried at least one configuration locally with the conan-center hook activated.

[conan-center-bot]

Conan v1 pipeline ✔️

All green in build 1 (50b3550f1035121b00e943c9d4cbd0751d1615b9):

• date/2.4.1:
  All packages built successfully! (All logs)

• date/3.0.1:
  All packages built successfully! (All logs)

• date/3.0.0:
  All packages built successfully! (All logs)

---

Conan v2 pipeline ✔️

Note: Conan v2 builds are now mandatory. Please read our discussion about it.

All green in build 1 (50b3550f1035121b00e943c9d4cbd0751d1615b9):

• date/2.4.1:
  All packages built successfully! (All logs)

• date/3.0.1:
  All packages built successfully! (All logs)

• date/3.0.0:
  All packages built successfully! (All logs)

[AbrilRBS]

Hi @toge thanks a lot! Posting the before and after logs for gcc would be great, as we're not yet building that configuration to test it ourselves, so it would help a ton for future traceability, thanks!

[AbrilRBS]

@toge note that the new CI system requires the recipe folder to be up-to-date, so you'll need to rebase in cases like this. For now, I've merged from master as I want to try these kinds of changes in the new CI, thanks!

[AbrilRBS]

Thanks!

[jcar87]

it shouldn't be necessary to publish a new recipe revision for this!

note to team: the pipeline should be able to handle fixing a test package without requiring to publish recipe revisions (or rebuilding packages from new revisions)

[jcar87]

note to team: the pipeline should be able to handle fixing a test package without requiring to publish recipe revisions (or rebuilding packages from new revisions)

note to self - fixing this asap ;)

[AbrilRBS]

The fix to support test_package only changes is now live, thanks!

[jcar87]

Thanks!
I've modified the test package to minimise it as much as possible - ensuring that when there is a library to test, we check a symbol from that library, and nothing else.
This helps with ongoing maintenance and hopefully will be more robust to compiler updates...
(I did test it with gcc-14 on Linux)