===> Skipping vulnerability checks. WARNING: No /usr/pkg/pkgdb/pkg-vulnerabilities file found. WARNING: To fix run: `/usr/sbin/pkg_admin -K /usr/pkg/pkgdb fetch-pkg-vulnerabilities'. ===> Building for diesel-cli-2.2.8 Locking 204 packages to latest compatible versions warning: output filename collision. The bin target `show_posts` in package `diesel_demo_step_1_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_1)` has the same output filename as the bin target `show_posts` in package `diesel_demo_step_1_mysql v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_1)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/show_posts The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `show_posts` in package `diesel_demo_step_1_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_1)` has the same output filename as the bin target `show_posts` in package `diesel_demo_step_1_mysql v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_1)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/show_posts.dwp The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `show_posts` in package `diesel_demo_step_1_sqlite v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_1)` has the same output filename as the bin target `show_posts` in package `diesel_demo_step_1_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_1)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/show_posts The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `show_posts` in package `diesel_demo_step_1_sqlite v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_1)` has the same output filename as the bin target `show_posts` in package `diesel_demo_step_1_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_1)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/show_posts.dwp The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `show_posts` in package `diesel_demo_step_2_mysql v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_2)` has the same output filename as the bin target `show_posts` in package `diesel_demo_step_1_sqlite v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_1)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/show_posts The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `show_posts` in package `diesel_demo_step_2_mysql v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_2)` has the same output filename as the bin target `show_posts` in package `diesel_demo_step_1_sqlite v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_1)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/show_posts.dwp The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `show_posts` in package `diesel_demo_step_2_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_2)` has the same output filename as the bin target `show_posts` in package `diesel_demo_step_2_mysql v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_2)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/show_posts The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `show_posts` in package `diesel_demo_step_2_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_2)` has the same output filename as the bin target `show_posts` in package `diesel_demo_step_2_mysql v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_2)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/show_posts.dwp The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `write_post` in package `diesel_demo_step_2_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_2)` has the same output filename as the bin target `write_post` in package `diesel_demo_step_2_mysql v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_2)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/write_post The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `write_post` in package `diesel_demo_step_2_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_2)` has the same output filename as the bin target `write_post` in package `diesel_demo_step_2_mysql v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_2)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/write_post.dwp The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `show_posts` in package `diesel_demo_step_2_sqlite v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_2)` has the same output filename as the bin target `show_posts` in package `diesel_demo_step_2_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_2)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/show_posts The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `show_posts` in package `diesel_demo_step_2_sqlite v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_2)` has the same output filename as the bin target `show_posts` in package `diesel_demo_step_2_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_2)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/show_posts.dwp The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `write_post` in package `diesel_demo_step_2_sqlite v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_2)` has the same output filename as the bin target `write_post` in package `diesel_demo_step_2_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_2)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/write_post The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `write_post` in package `diesel_demo_step_2_sqlite v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_2)` has the same output filename as the bin target `write_post` in package `diesel_demo_step_2_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_2)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/write_post.dwp The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `show_posts` in package `diesel_demo_step_3_mysql v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_3)` has the same output filename as the bin target `show_posts` in package `diesel_demo_step_2_sqlite v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_2)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/show_posts The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `show_posts` in package `diesel_demo_step_3_mysql v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_3)` has the same output filename as the bin target `show_posts` in package `diesel_demo_step_2_sqlite v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_2)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/show_posts.dwp The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `write_post` in package `diesel_demo_step_3_mysql v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_3)` has the same output filename as the bin target `write_post` in package `diesel_demo_step_2_sqlite v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_2)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/write_post The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `write_post` in package `diesel_demo_step_3_mysql v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_3)` has the same output filename as the bin target `write_post` in package `diesel_demo_step_2_sqlite v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_2)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/write_post.dwp The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `delete_post` in package `diesel_demo_step_3_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)` has the same output filename as the bin target `delete_post` in package `diesel_demo_step_3_mysql v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_3)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/delete_post The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `delete_post` in package `diesel_demo_step_3_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)` has the same output filename as the bin target `delete_post` in package `diesel_demo_step_3_mysql v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_3)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/delete_post.dwp The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `get_post` in package `diesel_demo_step_3_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)` has the same output filename as the bin target `get_post` in package `diesel_demo_step_3_mysql v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_3)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/get_post The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `get_post` in package `diesel_demo_step_3_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)` has the same output filename as the bin target `get_post` in package `diesel_demo_step_3_mysql v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_3)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/get_post.dwp The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `publish_post` in package `diesel_demo_step_3_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)` has the same output filename as the bin target `publish_post` in package `diesel_demo_step_3_mysql v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_3)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/publish_post The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `publish_post` in package `diesel_demo_step_3_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)` has the same output filename as the bin target `publish_post` in package `diesel_demo_step_3_mysql v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_3)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/publish_post.dwp The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `show_posts` in package `diesel_demo_step_3_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)` has the same output filename as the bin target `show_posts` in package `diesel_demo_step_3_mysql v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_3)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/show_posts The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `show_posts` in package `diesel_demo_step_3_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)` has the same output filename as the bin target `show_posts` in package `diesel_demo_step_3_mysql v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_3)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/show_posts.dwp The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `write_post` in package `diesel_demo_step_3_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)` has the same output filename as the bin target `write_post` in package `diesel_demo_step_3_mysql v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_3)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/write_post The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `write_post` in package `diesel_demo_step_3_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)` has the same output filename as the bin target `write_post` in package `diesel_demo_step_3_mysql v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_3)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/write_post.dwp The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `delete_post` in package `diesel_demo_step_3_sqlite v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_3)` has the same output filename as the bin target `delete_post` in package `diesel_demo_step_3_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/delete_post The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `delete_post` in package `diesel_demo_step_3_sqlite v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_3)` has the same output filename as the bin target `delete_post` in package `diesel_demo_step_3_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/delete_post.dwp The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `get_post` in package `diesel_demo_step_3_sqlite v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_3)` has the same output filename as the bin target `get_post` in package `diesel_demo_step_3_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/get_post The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `get_post` in package `diesel_demo_step_3_sqlite v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_3)` has the same output filename as the bin target `get_post` in package `diesel_demo_step_3_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/get_post.dwp The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `publish_post` in package `diesel_demo_step_3_sqlite v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_3)` has the same output filename as the bin target `publish_post` in package `diesel_demo_step_3_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/publish_post The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `publish_post` in package `diesel_demo_step_3_sqlite v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_3)` has the same output filename as the bin target `publish_post` in package `diesel_demo_step_3_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/publish_post.dwp The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `show_posts` in package `diesel_demo_step_3_sqlite v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_3)` has the same output filename as the bin target `show_posts` in package `diesel_demo_step_3_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/show_posts The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `show_posts` in package `diesel_demo_step_3_sqlite v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_3)` has the same output filename as the bin target `show_posts` in package `diesel_demo_step_3_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/show_posts.dwp The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `write_post` in package `diesel_demo_step_3_sqlite v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_3)` has the same output filename as the bin target `write_post` in package `diesel_demo_step_3_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/write_post The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . warning: output filename collision. The bin target `write_post` in package `diesel_demo_step_3_sqlite v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_3)` has the same output filename as the bin target `write_post` in package `diesel_demo_step_3_pg v0.1.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)`. Colliding filename is: /pbulk/work/databases/diesel-cli/work/diesel-2.2.8/target/release/write_post.dwp The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see . Compiling proc-macro2 v1.0.94 Compiling unicode-ident v1.0.18 Compiling serde v1.0.218 Compiling libc v0.2.170 Compiling stable_deref_trait v1.2.0 Compiling cfg-if v1.0.0 Compiling autocfg v1.4.0 Compiling memchr v2.7.4 Compiling writeable v0.5.5 Compiling fnv v1.0.7 Compiling strsim v0.11.1 Compiling ident_case v1.0.1 Compiling litemap v0.7.5 Compiling regex-syntax v0.8.5 Compiling num-traits v0.2.19 Compiling aho-corasick v1.1.3 Compiling heck v0.5.0 Compiling pkg-config v0.3.32 Compiling icu_locid_transform_data v1.5.0 Compiling smallvec v1.14.0 Compiling byteorder v1.5.0 Compiling icu_properties_data v1.5.0 Compiling quote v1.0.39 Compiling getrandom v0.2.15 Compiling syn v2.0.99 Compiling rand_core v0.6.4 Compiling utf16_iter v1.0.5 Compiling utf8_iter v1.0.4 Compiling write16 v1.0.0 Compiling log v0.4.26 Compiling icu_normalizer_data v1.5.0 Compiling shlex v1.3.0 Compiling vcpkg v0.2.15 Compiling either v1.15.0 Compiling cc v1.2.16 Compiling libm v0.2.11 Compiling mysqlclient-sys v0.4.2 Compiling num-integer v0.1.46 Compiling bigdecimal v0.4.7 Compiling pq-sys v0.7.0 Compiling regex-automata v0.4.9 Compiling percent-encoding v2.3.1 Compiling bitflags v2.9.0 Compiling serde_json v1.0.140 Compiling form_urlencoded v1.2.1 Compiling num-bigint v0.4.6 Compiling itoa v1.0.15 Compiling iana-time-zone v0.1.61 Compiling libsqlite3-sys v0.31.0 Compiling ryu v1.0.20 Compiling chrono v0.4.40 Compiling synstructure v0.13.1 Compiling darling_core v0.20.10 Compiling diesel_table_macro_syntax v0.2.0 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/diesel_table_macro_syntax) Compiling serde_derive v1.0.218 Compiling zerofrom-derive v0.1.6 Compiling yoke-derive v0.7.5 Compiling zerovec-derive v0.10.3 Compiling displaydoc v0.2.5 Compiling icu_provider_macros v1.5.0 Compiling darling_macro v0.20.10 Compiling zerocopy-derive v0.7.35 Compiling regex v1.11.1 Compiling darling v0.20.10 Compiling dsl_auto_type v0.1.3 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/dsl_auto_type) Compiling env_logger v0.8.4 Compiling zerofrom v0.1.6 Compiling yoke v0.7.5 Compiling zerovec v0.10.4 Compiling diesel_derives v2.2.4 (/pbulk/work/databases/diesel-cli/work/diesel-2.2.8/diesel_derives) Compiling zerocopy v0.7.35 Compiling ppv-lite86 v0.2.20 Compiling rand_chacha v0.3.1 Compiling uuid v1.15.1 Compiling tinystr v0.7.6 Compiling icu_collections v1.5.0 Compiling rand v0.8.5 Compiling icu_locid v1.5.0 Compiling icu_provider v1.5.0 Compiling icu_locid_transform v1.5.0 Compiling quickcheck v1.0.3 Compiling ipnetwork v0.21.1 Compiling icu_properties v1.5.1 Compiling ipnet v2.11.0 Compiling icu_normalizer v1.5.0 error: failed to parse bitcode for LTO module: Bitwidth for integer type out of range (Producer: 'LLVM18.1.8' Reader: 'LLVM 18.1.8') Compiling dotenvy v0.15.7 error: could not compile `quickcheck` (lib) due to 1 previous error warning: build failed, waiting for other jobs to finish... *** Error code 101 Stop. make[1]: stopped in /usr/pkgsrc/databases/diesel-cli *** Error code 1 Stop. make: stopped in /usr/pkgsrc/databases/diesel-cli