Mock tips
Dne 10. 05. 22 v 13:32 Richard Shaw napsal(a):
On Tue, May 10, 2022 at 3:09 AM John Reiser
<jreiser(a)bitwagon.com> wrote:
Suggestion: extract mqtt.c.o from libmqttc.a, then run "readelf
--all --wide mqtt.c.o > foo"
and look in file foo for more information about:
relocation R_X86_64_PC32 against symbol `mqtt_fixed_header_rules'
I'll take a look, but this is one place where building in mock
sucks... I can shell in to the chroot but not everything "works"
exactly the same, especially vim, which I have to manually install :)
You can use your local VIM outside of the mock to edit some file inside
mock, e.g.:
~~~
$ vim
/var/lib/mock/fedora-rawhide-x86_64/root/builddir/build/BUILD/your-project-1.2.3/your-file
~~~
You don't even need root privileges editing files in the /builddir
directory.
BTW sometimes it might also be useful to bind mount your local directory
into mock. There is even mock plugin which makes it automatic for
specific config file. You need to add there something like:
~~~
config_opts['plugin_conf']['bind_mount_enable'] = True
config_opts['plugin_conf']['bind_mount_opts']['dirs'].append(('/home/vondruch/projects/your-project',
'/your-project/' ))
~~~
Vít
Attachments:
- attachment.html (text/html — 2.4 KB)
- OpenPGP_signature.sig (application/pgp-signature — 840 bytes)