Discussion:
error building libpmc_events.c
(too old to reply)
Claude Buisson
2018-06-04 15:34:10 UTC
Permalink
Hi,

During a buildworld of head on amd64, from 332518 to 334590, the build
stops with:

--- all_subdir_lib/libpmc ---
===> lib/libpmc (all)
--- libpmc_events.c ---
./pmu-events/jevents "x86" /home/src/lib/libpmc/pmu-events/arch
libpmc_events.c
sh: ./pmu-events/jevents: not found
*** [libpmc_events.c] Error code 127
...

TIA

CBu
Claude Buisson
2018-06-05 17:18:16 UTC
Permalink
Replying to my own mail for more details, and ccing potential commiters
Post by Claude Buisson
Hi,
During a buildworld of head on amd64, from 332518 to 334590, the build
--- all_subdir_lib/libpmc ---
===> lib/libpmc (all)
--- libpmc_events.c ---
./pmu-events/jevents "x86" /home/src/lib/libpmc/pmu-events/arch
libpmc_events.c
sh: ./pmu-events/jevents: not found
*** [libpmc_events.c] Error code 127
...
This was during the lib32 build: jevents is not built in this context

The same error has been described by kevans@ on svn-src-all@ as a
consequence of svn 334226 (by bdrewery), pmu-events having since been
moved in svn r334242 (by mmacy)

CBu
Bryan Drewery
2018-06-06 14:20:49 UTC
Permalink
I think I know the issue. Will try looking later today or tomorrow.

Regards,
Bryan Drewery
Post by Claude Buisson
Replying to my own mail for more details, and ccing potential commiters
Post by Claude Buisson
Hi,
--- all_subdir_lib/libpmc ---
===> lib/libpmc (all)
--- libpmc_events.c ---
./pmu-events/jevents "x86" /home/src/lib/libpmc/pmu-events/arch libpmc_events.c
sh: ./pmu-events/jevents: not found
*** [libpmc_events.c] Error code 127
...
This was during the lib32 build: jevents is not built in this context
CBu
Claude Buisson
2018-06-06 15:22:42 UTC
Permalink
Post by Bryan Drewery
I think I know the issue. Will try looking later today or tomorrow.
Regards,
Bryan Drewery
Post by Claude Buisson
Replying to my own mail for more details, and ccing potential commiters
Post by Claude Buisson
Hi,
--- all_subdir_lib/libpmc ---
===> lib/libpmc (all)
--- libpmc_events.c ---
./pmu-events/jevents "x86" /home/src/lib/libpmc/pmu-events/arch libpmc_events.c
sh: ./pmu-events/jevents: not found
*** [libpmc_events.c] Error code 127
...
This was during the lib32 build: jevents is not built in this context
CBu
After further investigations, I found that jevents was effectively
built, but in the src directory, instead of obj-lib32

Commenting WITHOUT_AUTO_OBJ in src-env.conf has been sufficient to get a
successful buildword !

So the question becomes: must WITHOUT_AUTO_OBJ be supported by the build
infrastructure ?

Thanks for your time

CBu
Bryan Drewery
2018-06-06 15:35:55 UTC
Permalink
Post by Claude Buisson
Post by Bryan Drewery
I think I know the issue. Will try looking later today or tomorrow.
Regards,
Bryan Drewery
Post by Claude Buisson
Replying to my own mail for more details, and ccing potential commiters
Post by Claude Buisson
Hi,
--- all_subdir_lib/libpmc ---
===> lib/libpmc (all)
--- libpmc_events.c ---
./pmu-events/jevents "x86" /home/src/lib/libpmc/pmu-events/arch libpmc_events.c
sh: ./pmu-events/jevents: not found
*** [libpmc_events.c] Error code 127
...
This was during the lib32 build: jevents is not built in this context
consequence of svn 334226 (by bdrewery), pmu-events having since been
moved in svn r334242 (by mmacy)
CBu
After further investigations, I found that jevents was effectively
built, but in the src directory, instead of obj-lib32
Commenting WITHOUT_AUTO_OBJ in src-env.conf has been sufficient to get a
successful buildword !
So the question becomes: must WITHOUT_AUTO_OBJ be supported by the build
infrastructure ?
Well it's exactly why WITH_AUTO_OBJ is a thing. There's no reason
jevents should be in your source tree when using buildworld. If you were
building manually in the directories then that's why WITH_AUTO_OBJ is
there, to prevent the binary from being written to the source tree later
leading to build problems like this.

WITHOUT_AUTO_OBJ is "supported" as much as it was before, expect
problems like this. I don't recommend setting WITHOUT_AUTO_OBJ. Feedback
on why you were using it would help.
Post by Claude Buisson
Thanks for your time
CBu
--
Regards,
Bryan Drewery
Loading...