2016-07-26 10:40 GMT+02:00 Rainer Gerhards <[email protected]>: > Yeah, I think we could also build packages with the wrong names, but > as the trouble two and a half week ago has shown, this is no solution > we can provide to the general public.
But Florian just proved that we can indeed create these packages with wrong name, and they work. This means I can at least get Travis to work again... Rainer >Also, I admit that I did so many > different tests that I am not even sure we actually could succesfully > build them. > > I have adjusted scripts and controls files so that the correct package > names are build. However, there is one thing that I simply cannot get > right and that is the "-fPIC error message": > > /usr/bin/ld.bfd.real: > /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libfastjson.a(libfastjson_la-json_object.o): > relocation R_X86_64_32 against `.rodata.str1.1' can not be used when > making a shared object; recompile with -fPIC > /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libfastjson.a: error > adding symbols: Bad value > > from: > https://launchpadlibrarian.net/274413157/buildlog_ubuntu-trusty-amd64.liblognorm_2.0.0~20160722053734-0adiscon1trusty_BUILDING.txt.gz > > This is not received when the libfastjson package is build/created, > but when it is being used (in the case above liblognorm is build). > That same error message also shows up in travis when I try to use > those packages. The problem does not occur if I just manually build > libfastjson. Now the advise "recompile with -fPIC" sounds like a > simple solution, but I tried to do so (via CFLAGS in rules file), but > it didn't change anything. I then tried a myriad of things before I > finally gave up. It's probably just a very minimal (and possibly > simplistic) thing, but I am out of ideas of what it could be. Also, I > have lost a lot of time, which means the backlog is even larger now > ;-) > > Rainer > > 2016-07-25 20:51 GMT+02:00 David Lang <[email protected]>: >> On Mon, 25 Jul 2016, David Lang wrote: >> >>> Date: Mon, 25 Jul 2016 11:42:15 -0700 (PDT) >>> From: David Lang <[email protected]> >>> Reply-To: rsyslog-users <[email protected]> >>> To: rsyslog-users <[email protected]> >>> Subject: Re: [rsyslog] Ubuntu binary packages (PPA) discontinued >>> >>> >>> On Mon, 25 Jul 2016, David Lang wrote: >>> >>>> On Mon, 25 Jul 2016, David Lang wrote: >>>> >>>>> On Sun, 24 Jul 2016, Rainer Gerhards wrote: >>>>> >>>>>>> >>>>>>> I assume we're all aware that the lack of Ubuntu package (provided by >>>>>>> Adiscon or someone else, doesn't really matter) is a major barrier in >>>>>>> rsyslog adoption. So I'm thinking that even a ugly/crazy solution >>>>>>> would do, as long as we end up with (reliable) packages. So I think it >>>>>>> would be nice to have all the information needed for anyone to chime >>>>>>> in with ideas and possible solutions. Unless that information is >>>>>>> already somewhere and I missed it... in which case excuse my ignorance >>>>>>> :-S >>>>>> >>>>>> >>>>>> I fully agree it would be good to fix this, I just honestly don't know >>>>>> how. And I unfortunately have no time budget left to spend another two >>>>>> weeks on it. I think to do it right, I would need to learn Ubuntu >>>>>> packaging from the roots, and that's beyond my current time budget. >>>>>> :-( >>>>>> >>>>>> The problem is somewhere in the rsyslog-pkg-ubuntu project, and >>>>>> related to this script >>>>>> >>>>>> >>>>>> https://github.com/rsyslog/rsyslog-pkg-ubuntu/blob/master/scripts/auto_daily_project.sh >>>>>> >>>>>> and the associated control files. >>>>> >>>>> >>>>> I didn't have time to do my own compiles this development cycle, but I >>>>> am also seeing failures building locally using this script/process. >>>>> >>>>> investigating now. >>>> >>>> >>>> In my first pass, I'm seeing that all the new libraries are being built, >>>> but then when rsyslog goes to compile, old versions of the libraries are >>>> being loaded into the pbuilder image, and so things are failing. >>>> >>>> I thought I had things configured so that the pbuilder image also looked >>>> at a local directory as a repository I recreated the index for that >>>> repository between each package that's built so that it will build with the >>>> library versions that I just compiled, but it appears that that didn't work >>>> for some reason this time. >>>> >>>> I'm continuing to investigate, starting by updating my pbuilder images. >>> >>> >>> That was enough to let my build work >>> >>> rsyslog-pkg-ubuntu# git diff HEAD >>> diff --git a/scripts/auto_daily_project.sh b/scripts/auto_daily_project.sh >>> index 1e27081..51f2c1a 100755 >>> --- a/scripts/auto_daily_project.sh >>> +++ b/scripts/auto_daily_project.sh >>> @@ -50,10 +50,10 @@ if [ -z "$szPlatform" ]; then >>> echo "variable szPlatform is unset" | mutt -s "$0 script error" >>> $RS_NOTIFY_EMAIL >>> exit >>> fi >>> -if [ -z "$PPA" ]; then >>> - echo "variable PPA is unset" | mutt -s "$0 script error" >>> $RS_NOTIFY_EMAIL >>> - exit >>> -fi >>> +#if [ -z "$PPA" ]; then >>> +# echo "variable PPA is unset" | mutt -s "$0 script error" >>> $RS_NOTIFY_EMAIL >>> +# exit >>> +#fi >>> >>> # $VERSION_FILE must not exist. If it does not exist, an >>> # error message is emitted (this is OK) and the build is >>> diff --git a/scripts/config.sh b/scripts/config.sh >>> index 676d659..a4842df 100644 >>> --- a/scripts/config.sh >>> +++ b/scripts/config.sh >>> @@ -2,8 +2,8 @@ PLATFORM="precise trusty vivid wily xenial yakkety" >>> ARCHTECT="amd64 i386" >>> BRANCHES="v8-stable v8-stable-testing" >>> # GPG KEY >>> -KEY_ID=AEF0CF8E >>> -PPA=ppa:adiscon >>> +#KEY_ID=AEF0CF8E >>> +#PPA=ppa:adiscon >>> # Mine >>> # KEY_ID=F6A93574 >>> >>> >>> versions used: >>> >>> # cat build.config.201607251834 >>> ./rsyslog/ branch: * master >>> ./rsyslog/ version: v8.17.0-465-g8684fd2 >>> ./liblognorm/ branch: * master >>> ./liblognorm/ version: v2.0.0-7-g22aa93b >>> ./rsyslog-doc/ branch: * master >>> ./rsyslog-doc/ version: v8.3.5-400-g76a53c0 >>> ./liblogging/ branch: * master >>> ./liblogging/ version: v1.0.5-12-gb883f16 >>> ./librelp/ branch: * master >>> ./librelp/ version: v1.2.12-1-g1ea0d3b >>> ./libestr/ branch: * master >>> ./libestr/ version: v0.1.10-3-gb60d2ce >>> ./rsyslog-pkg-ubuntu/ branch: * master >>> ./rsyslog-pkg-ubuntu/ version: cdc8308 >>> ./libfastjson/ branch: * master >>> ./libfastjson/ version: 2fc4c65 >>> ./json-c/ branch: * libfastjson >>> ./json-c/ version: b366750 >>> >> >> slight correction, it's still building the librelp0 and liblognorm1 >> packages, not librelp1 and liblognorm2 packages (the .so libraries are the >> correct versions, it's just the package names that are wrong) >> >> >> David Lang >> _______________________________________________ >> rsyslog mailing list >> http://lists.adiscon.net/mailman/listinfo/rsyslog >> http://www.rsyslog.com/professional-services/ >> What's up with rsyslog? Follow https://twitter.com/rgerhards >> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of >> sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T >> LIKE THAT. _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
