We could use something like this instead:```%{__sed} --in-place=.backup --regexp-extended --_expression_='/^lt_cv_sys_global_symbol_to_cdecl=/{:start;s/""//;s/^(.*)\\$/\1/;T end;N;s/\n//;t start;:end}' configurediff -u configure.backup configure && mv configure.backup configure``` It is a bit more
On 8/14/2022 6:29 AM, Jarryd Lisher via devel wrote:
Hey,
I figured out that this is mainly caused by the configure script
containing multi-line definitions. So, the hacks only operate on the
first part and land up leaving random lines of nonsense in the file.
You can fix this by adding the f
On 8/3/2022 2:00 PM, Kevin Kofler via devel wrote:
Jeff Law wrote:
That would eliminate the need for those crazy macros. The problem is
many packages have configury bits that are ancient and can't be rebuilt
with modern autotools.
I have a hard time believing that.
Well, having been the one
Hey, I figured out that this is mainly caused by the configure script containing multi-line definitions. So, the hacks only operate on the first part and land up leaving random lines of nonsense in the file. You can fix this by adding the following "unwrap" `sed` script just before the `%{configure
Jeff Law wrote:
> That would eliminate the need for those crazy macros. The problem is
> many packages have configury bits that are ancient and can't be rebuilt
> with modern autotools.
I have a hard time believing that.
Even the gigantic KDE 3 autotools mess last updated by upstream in 2008 can
Richard W.M. Jones wrote:
> At some point we should just require autoreconf.
I have been arguing for that for years. IMHO, it is a logical consequence of
the general rule that everything in Fedora must be built from source.
Generated files are NOT source code. Patching anything in the configure
On 8/3/2022 6:55 AM, Richard W.M. Jones wrote:
On Sun, Jul 31, 2022 at 03:33:51PM +0200, Kevin Kofler via devel wrote:
Jerry James wrote:
On Sat, Jul 30, 2022 at 10:35 AM Kevin Kofler via devel
wrote:
What I see is that the hacks that you apply to configure are apparently
not working:
che
On Sun, Jul 31, 2022 at 03:33:51PM +0200, Kevin Kofler via devel wrote:
> Jerry James wrote:
>
> > On Sat, Jul 30, 2022 at 10:35 AM Kevin Kofler via devel
> > wrote:
> >> What I see is that the hacks that you apply to configure are apparently
> >> not working:
> >>
> >> checking command to parse
Jerry James wrote:
> On Sat, Jul 30, 2022 at 10:35 AM Kevin Kofler via devel
> wrote:
>> What I see is that the hacks that you apply to configure are apparently
>> not working:
>>
>> checking command to parse /usr/bin/nm -B output from gcc object...
>> ./configure: line 7304: -e 's/^T .* \(.*\)$
Il 30/07/22 18:28, Jerry James ha scritto:
> On Sat, Jul 30, 2022 at 9:53 AM Mattia Verga via devel
> wrote:
>> Hello folks,
>>
>> I've been trying to update healpix package to latest version, so that I
>> can submit a PR to the package maintainer. Current version is a couple
>> of years old.
>>
>
On Sat, Jul 30, 2022 at 10:35 AM Kevin Kofler via devel
wrote:
> What I see is that the hacks that you apply to configure are apparently not
> working:
>
> checking command to parse /usr/bin/nm -B output from gcc object...
> ./configure: line 7304: -e 's/^T .* \(.*\)$/extern int \1();/p' -e
> 's/
Mattia Verga via devel wrote:
> I'm at a dead end, can someone have a look at the scratch build [1] and
> explain me where's the fault?
What I see is that the hacks that you apply to configure are apparently not
working:
checking command to parse /usr/bin/nm -B output from gcc object...
./confi
On Sat, Jul 30, 2022 at 9:53 AM Mattia Verga via devel
wrote:
> Hello folks,
>
> I've been trying to update healpix package to latest version, so that I
> can submit a PR to the package maintainer. Current version is a couple
> of years old.
>
> Unfortunately, the automated build process available
Hello folks,
I've been trying to update healpix package to latest version, so that I
can submit a PR to the package maintainer. Current version is a couple
of years old.
Unfortunately, the automated build process available in the package
itself isn't suitable for our needs, so each component (cur
14 matches
Mail list logo
