Hey Tom,
Thanks for helping me out, I replaced all the hardcoded directories with
macros and the build is now successful for all architectures .
Here is the successful koji build
https://koji.fedoraproject.org/koji/taskinfo?taskID=41450255
Thanks again,
Harsh
On Mon, Feb 10, 2020 at 9:46 PM Tom
You have hard coded /usr/lib64 in your spec but that is not the path
on 32 bit systems - use %{_libdir} instead and it will work.
In general you should be using macros rather than hard coding paths
in fact - this is just one case where it goes very wrong if you don't.
Tom
On 10/02/2020 16:11,
but I still can't figure out where the errors are in the build logs .Sorry
the message was broken into 2 .
Thanks ,
Harsh
On Mon, Feb 10, 2020 at 9:40 PM Harsh Jain wrote:
> Thanks for telling me, turns out it was missing a few more dependencies, I
> rebuilt the package and it now seems to
Thanks for telling me, turns out it was missing a few more dependencies, I
rebuilt the package and it now seems to build on all except arch armv7hl
and i686
here is the new koji build
https://koji.fedoraproject.org/koji/taskinfo?taskID=41448837
, I've updated the spec file and rpm here
On 10/02/2020 13:31, Harsh Jain wrote:
I am trying to package elementary-tweaks and am getting failed build in
koji
I cannot find where the build is failing. This is my first time
packaging something and have no idea where to look for errors in the
build logs . Any help is appreciated . Here
Hey,
I am trying to package elementary-tweaks and am getting failed build in
koji
I cannot find where the build is failing. This is my first time packaging
something and have no idea where to look for errors in the build logs . Any
help is appreciated . Here is the build
Thanks, it worked.
I've used spectool to download the archive file and then used fedpkg
new-sources as you suggested.
Il giorno mar 3 lug 2018 alle 7:33, Vascom ha
scritto:
You need to add source file via command
fedpkg new-sources extractpdfmark-1.0.2.tar.gz
And push changes to git repo.
You need to add source file via command
fedpkg new-sources extractpdfmark-1.0.2.tar.gz
And push changes to git repo.
src.rpm builded always as noarch because it just archive.
вт, 3 июл. 2018 г., 8:29 Federico Bruni :
> Hello
>
> I'm trying to build a package in koji for the first time.
> You
Hello
I'm trying to build a package in koji for the first time.
You can see my (failed) attempt here:
https://koji.fedoraproject.org/koji/taskinfo?taskID=27996807
I run `fedpkg build` from the directory containing this git repository:
https://src.fedoraproject.org/rpms/extractpdfmark
I don't
Zach Carter z.car...@f5.com writes:
Howeverthe question remains, why did it build just fine with the function
header as-is on a rawhide machine and in my local mockbuild, but not when the
build was run on the koji server? Some difference in the autotools, g++
compiler, boost? Any
John5342 john5...@gmail.com writes:
Well the problem is obvious.
Very obvious, indeed.
The line in the test program should be:
boost::program_options::variables_map dummy()
and not:
boost::program_options::variables_map::variables_map dummy()
I however know very little about autotools
On Monday 19 July 2010 01:15:43 Andreas Schwab wrote:
John5342 john5...@gmail.com writes:
Well the problem is obvious.
Very obvious, indeed.
The line in the test program should be:
boost::program_options::variables_map dummy()
and not:
Zach Carter z.car...@f5.com writes:
Any insight, tips or pointers would be much appreciated.
You could modify the spec file to cat the config.log file on error,
which should give you more clues.
Andreas.
--
Andreas Schwab, sch...@redhat.com
GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84
On Friday 16 July 2010 00:36:31 Andreas Schwab wrote:
Any insight, tips or pointers would be much appreciated.
You could modify the spec file to cat the config.log file on error,
which should give you more clues.
Thanks for the suggestion. I did that and got a more verbose and detailed
On Fri, Jul 16, 2010 at 20:52, Zach Carter z.car...@f5.com wrote:
On Friday 16 July 2010 00:36:31 Andreas Schwab wrote:
Any insight, tips or pointers would be much appreciated.
You could modify the spec file to cat the config.log file on error,
which should give you more clues.
Thanks for
Hi:
I've got this build error:
http://koji.fedoraproject.org/koji/taskinfo?taskID=2322203
However, on my local machine make mockbuild does not seem to reproduce it.
What's a good set of steps for me to reproduce an environment that is the same
as koji is using? I'd like to avoid
16 matches
Mail list logo
