===> 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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_1)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_1)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_1)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_1)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_1)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_1)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_2)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_2)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_2)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_2)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_2)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_2)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_2)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_2)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_2)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_2)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_2)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/sqlite/getting_started_step_2)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_3)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_3)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_3)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_3)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_3)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_3)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_3)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_3)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_3)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/mysql/getting_started_step_3)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)`. Colliding filename is: /usr/pkgsrc/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 (/usr/pkgsrc/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 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/examples/postgres/getting_started_step_3)`. Colliding filename is: /usr/pkgsrc/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 quote v1.0.39 Compiling syn v2.0.99 Compiling serde v1.0.218 Compiling serde_derive v1.0.218 Compiling synstructure v0.13.1 Compiling libc v0.2.170 Compiling zerofrom-derive v0.1.6 Compiling zerofrom v0.1.6 Compiling yoke-derive v0.7.5 Compiling stable_deref_trait v1.2.0 Compiling yoke v0.7.5 Compiling zerovec-derive v0.10.3 Compiling cfg-if v1.0.0 Compiling zerovec v0.10.4 Compiling displaydoc v0.2.5 Compiling autocfg v1.4.0 Compiling tinystr v0.7.6 Compiling strsim v0.11.1 Compiling litemap v0.7.5 Compiling memchr v2.7.4 Compiling writeable v0.5.5 Compiling fnv v1.0.7 Compiling ident_case v1.0.1 Compiling darling_core v0.20.10 Compiling icu_locid v1.5.0 Compiling icu_provider_macros v1.5.0 Compiling icu_provider v1.5.0 Compiling darling_macro v0.20.10 Compiling aho-corasick v1.1.3 Compiling num-traits v0.2.19 Compiling getrandom v0.2.15 Compiling pkg-config v0.3.32 Compiling regex-syntax v0.8.5 Compiling heck v0.5.0 Compiling icu_locid_transform_data v1.5.0 Compiling icu_locid_transform v1.5.0 Compiling regex-automata v0.4.9 Compiling rand_core v0.6.4 Compiling icu_collections v1.5.0 Compiling zerocopy-derive v0.7.35 Compiling icu_properties_data v1.5.0 Compiling smallvec v1.14.0 Compiling byteorder v1.5.0 Compiling zerocopy v0.7.35 Compiling icu_properties v1.5.1 Compiling regex v1.11.1 Compiling icu_normalizer_data v1.5.0 Compiling write16 v1.0.0 Compiling shlex v1.3.0 Compiling utf8_iter v1.0.4 Compiling utf16_iter v1.0.5 Compiling log v0.4.26 Compiling icu_normalizer v1.5.0 Compiling cc v1.2.16 Compiling ppv-lite86 v0.2.20 Compiling darling v0.20.10 Compiling either v1.15.0 Compiling vcpkg v0.2.15 Compiling libm v0.2.11 Compiling libsqlite3-sys v0.31.0 Compiling dsl_auto_type v0.1.3 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/dsl_auto_type) Compiling rand_chacha v0.3.1 Compiling idna_adapter v1.2.0 Compiling num-integer v0.1.46 Compiling mysqlclient-sys v0.4.2 Compiling bigdecimal v0.4.7 Compiling diesel_table_macro_syntax v0.2.0 (/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/diesel_table_macro_syntax) Compiling serde_json v1.0.140 Compiling bitflags v2.9.0 Compiling pq-sys v0.7.0 Compiling percent-encoding v2.3.1 Compiling form_urlencoded v1.2.1 error: failed to run custom build command for `mysqlclient-sys v0.4.2` Caused by: process didn't exit successfully: `/usr/pkgsrc/databases/diesel-cli/work/diesel-2.2.8/target/release/build/mysqlclient-sys-88c1dd830507270f/build-script-build` (exit status: 101) --- stdout cargo::rerun-if-env-changed=MYSQLCLIENT_VERSION cargo::rerun-if-env-changed=MYSQLCLIENT_INCLUDE_DIR cargo::rerun-if-env-changed=MYSQLCLIENT_INCLUDE_DIR_POWERPC_UNKNOWN_NETBSD cargo::rerun-if-env-changed=MYSQLCLIENT_LIB cargo::rerun-if-env-changed=MYSQLCLIENT_LIB_DIR cargo::rerun-if-env-changed=MYSQLCLIENT_LIB_DIR_POWERPC_UNKNOWN_NETBSD cargo::rerun-if-env-changed=MYSQLCLIENT_LIBNAME cargo::rerun-if-env-changed=MYSQLCLIENT_LIBNAME_POWERPC_UNKNOWN_NETBSD cargo::rerun-if-env-changed=MYSQLCLIENT_STATIC cargo::rerun-if-env-changed=MYSQLCLIENT_VERSION_POWERPC_UNKNOWN_NETBSD cargo::rerun-if-env-changed=MYSQLCLIENT_LIB_POWERPC_UNKNOWN_NETBSD cargo::rerun-if-env-changed=MYSQLCLIENT_STATIC_POWERPC_UNKNOWN_NETBSD cargo:rerun-if-env-changed=MYSQLCLIENT_NO_PKG_CONFIG cargo:rerun-if-env-changed=PKG_CONFIG_powerpc-unknown-netbsd cargo:rerun-if-env-changed=PKG_CONFIG_powerpc_unknown_netbsd cargo:rerun-if-env-changed=HOST_PKG_CONFIG cargo:rerun-if-env-changed=PKG_CONFIG cargo:rerun-if-env-changed=MYSQLCLIENT_STATIC cargo:rerun-if-env-changed=MYSQLCLIENT_DYNAMIC cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC cargo:rerun-if-env-changed=PKG_CONFIG_PATH_powerpc-unknown-netbsd cargo:rerun-if-env-changed=PKG_CONFIG_PATH_powerpc_unknown_netbsd cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH cargo:rerun-if-env-changed=PKG_CONFIG_PATH cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_powerpc-unknown-netbsd cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_powerpc_unknown_netbsd cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_powerpc-unknown-netbsd cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_powerpc_unknown_netbsd cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR cargo:rerun-if-env-changed=LIBMARIADB_NO_PKG_CONFIG cargo:rerun-if-env-changed=PKG_CONFIG_powerpc-unknown-netbsd cargo:rerun-if-env-changed=PKG_CONFIG_powerpc_unknown_netbsd cargo:rerun-if-env-changed=HOST_PKG_CONFIG cargo:rerun-if-env-changed=PKG_CONFIG cargo:rerun-if-env-changed=LIBMARIADB_STATIC cargo:rerun-if-env-changed=LIBMARIADB_DYNAMIC cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC cargo:rerun-if-env-changed=PKG_CONFIG_PATH_powerpc-unknown-netbsd cargo:rerun-if-env-changed=PKG_CONFIG_PATH_powerpc_unknown_netbsd cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH cargo:rerun-if-env-changed=PKG_CONFIG_PATH cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_powerpc-unknown-netbsd cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_powerpc_unknown_netbsd cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_powerpc-unknown-netbsd cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_powerpc_unknown_netbsd cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR cargo:rerun-if-env-changed=SYSROOT cargo:rerun-if-env-changed=LIBMARIADB_STATIC cargo:rerun-if-env-changed=LIBMARIADB_DYNAMIC cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC cargo:rustc-link-search=native=/usr/pkg/lib/ cargo:rustc-link-lib=mariadb cargo:rustc-link-arg=-Wl,-R/usr/pkg/lib/ cargo:rerun-if-env-changed=PKG_CONFIG_powerpc-unknown-netbsd cargo:rerun-if-env-changed=PKG_CONFIG_powerpc_unknown_netbsd cargo:rerun-if-env-changed=HOST_PKG_CONFIG cargo:rerun-if-env-changed=PKG_CONFIG cargo:rerun-if-env-changed=LIBMARIADB_STATIC cargo:rerun-if-env-changed=LIBMARIADB_DYNAMIC cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC cargo:rerun-if-env-changed=PKG_CONFIG_PATH_powerpc-unknown-netbsd cargo:rerun-if-env-changed=PKG_CONFIG_PATH_powerpc_unknown_netbsd cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH cargo:rerun-if-env-changed=PKG_CONFIG_PATH cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_powerpc-unknown-netbsd cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_powerpc_unknown_netbsd cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_powerpc-unknown-netbsd cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_powerpc_unknown_netbsd cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR cargo::rerun-if-changed=/usr/pkg/lib/ cargo::rustc-check-cfg=cfg(mysql_5_7_x) cargo::rustc-check-cfg=cfg(mysql_8_0_x) cargo::rustc-check-cfg=cfg(mysql_8_3_x) cargo::rustc-check-cfg=cfg(mysql_8_4_x) cargo::rustc-check-cfg=cfg(mysql_9_0_x) cargo::rustc-check-cfg=cfg(mariadb_10_x) cargo:rustc-cfg=mariadb_10_x --- stderr thread 'main' panicked at /usr/pkgsrc/databases/diesel-cli/work/vendor/mysqlclient-sys-0.4.2/build.rs:234:13: mysqlclient-sys does not provide bundled bindings for libmysqlclient `3.4.4` for the target `powerpc-unknown-netbsd`. Consider using the `buildtime_bindgen` feature or contribute bindings to the crate Debug information: (version: Some(MariaDb10), target_arch: powerpc, ptr_size: 32) note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace *** 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