Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

_debugsource_packages sometimes crashes due to non-existing debugsourcefiles.list #279

Closed
ignatenkobrain opened this issue Jul 25, 2017 · 6 comments

Comments

@ignatenkobrain
Copy link
Contributor

Partially found in #277, although I think it makes sense to track it here separately.

Processing files: gdb-debugsource-8.0-17.fc27.x86_64
RPM build errors:
error: Could not open %files file /builddir/build/BUILD/gdb-8.0/debugsourcefiles.list: No such file or directory
    Could not open %files file /builddir/build/BUILD/gdb-8.0/debugsourcefiles.list: No such file or directory
@rpm-maint
Copy link

rpm-maint commented Jul 26, 2017 via email

ignatenkobrain added a commit to ignatenkobrain/rpm that referenced this issue Jul 28, 2017
…under the builddir

The %_debugsource_template expects the debugsourcefiles.list file
to be in the (current) build dir. Make sure that is always the case
even if find-debuginfo.sh was invoked in a different (sub) directory
by prepending $BUILDDIR to the output file as written in description
"All file names in switches are relative to builddir (. if not given).".

Closes: rpm-software-management#279
Based-on-patch-by: Mark Wielaard <mark@klomp.org>
Signed-off-by: Igor Gnatenko <i.gnatenko.brain@gmail.com>
ffesti pushed a commit that referenced this issue Jul 28, 2017
…under the builddir

The %_debugsource_template expects the debugsourcefiles.list file
to be in the (current) build dir. Make sure that is always the case
even if find-debuginfo.sh was invoked in a different (sub) directory
by prepending $BUILDDIR to the output file as written in description
"All file names in switches are relative to builddir (. if not given).".

Closes: #279
Based-on-patch-by: Mark Wielaard <mark@klomp.org>
Signed-off-by: Igor Gnatenko <i.gnatenko.brain@gmail.com>
ydario pushed a commit to bitwiseworks/rpm that referenced this issue Oct 21, 2017
…under the builddir

The %_debugsource_template expects the debugsourcefiles.list file
to be in the (current) build dir. Make sure that is always the case
even if find-debuginfo.sh was invoked in a different (sub) directory
by prepending $BUILDDIR to the output file as written in description
"All file names in switches are relative to builddir (. if not given).".

Closes: rpm-software-management#279
Based-on-patch-by: Mark Wielaard <mark@klomp.org>
Signed-off-by: Igor Gnatenko <i.gnatenko.brain@gmail.com>
@xsuchy
Copy link
Member

xsuchy commented Feb 14, 2019

This still happens to me on F29 (with most recent rpm). With exactly the same errors. The weird thing is that I am not alone, it happens to some participant of rpm packaging workshop too. The weird part is that when I generate src.rpm and then build it in mock, it passes without a problem.

@xsuchy
Copy link
Member

xsuchy commented Feb 14, 2019

My system tries to execute:

/usr/lib/rpm/find-debuginfo.sh -l4 --strict-build-id -m -i --build-id-seed 1.1-15.fc29 --unique-debug-suffix -1.1-15.fc29.x86_64 --unique-debug-src-base enum-1.1-15.fc29.x86_64 --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 -S debugsourcefiles.list /home/msuchy/rpmbuild/BUILD/enum-1.1

Which interestingly results to BUILDDIR=-l4 and then it goes wrong.

@pmatilai
Copy link
Member

Interesting. That -l4 is supposed to be -j4, and apparently find-debuginfo just takes anything unknown as the builddir.

@xsuchy , what does rpm --eval "%{_smp_mflags}" output on that system?

@xsuchy
Copy link
Member

xsuchy commented Feb 14, 2019

Got it. It is because:

rpm --eval '%{?_smp_mflags}'
-l4

which for Makefile has semantics:

       -l [load], --load-average[=load]
            Specifies  that  no  new jobs (commands) should be started if there are others jobs running and the load average is at least load (a floating-point
            number).  With no argument, removes a previous load limit.

But find-debuginfo.sh does not recognize it and interpet it differently.

I will open new issue for that.

@xsuchy
Copy link
Member

xsuchy commented Feb 14, 2019

I filed:
#630

TixoRebel pushed a commit to TixoRebel/debugedit that referenced this issue Jan 14, 2024
…under the builddir

The %_debugsource_template expects the debugsourcefiles.list file
to be in the (current) build dir. Make sure that is always the case
even if find-debuginfo.sh was invoked in a different (sub) directory
by prepending $BUILDDIR to the output file as written in description
"All file names in switches are relative to builddir (. if not given).".

Closes: rpm-software-management/rpm#279
Based-on-patch-by: Mark Wielaard <mark@klomp.org>
Signed-off-by: Igor Gnatenko <i.gnatenko.brain@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants