[Risolto] rpmbuild termina con errore "detected a broken RPATH"

Ciao a tutti,
provando a compilare un rpm dal solito spec escono questi messaggi:

[code]$ rpmbuild -ba gtkradiant.spec
Esecuzione(%prep) in corso: /bin/sh -e /var/tmp/rpm-tmp.4HFl4j

  • umask 022
  • cd /home/makerpm/rpmbuild/BUILD
  • LANG=C
  • export LANG
  • unset DISPLAY
  • tar -xzvf /home/makerpm/rpmbuild/SOURCES/GtkRadiant-1.6-Linux-x86_64-20121007.tar.gz
    GtkRadiant-1.6-Linux-x86_64-20121007/
    GtkRadiant-1.6-Linux-x86_64-20121007/installs/

    GtkRadiant-1.6-Linux-x86_64-20121007/bitmaps/icon.bmp
    GtkRadiant-1.6-Linux-x86_64-20121007/bitmaps/logo.bmp
    GtkRadiant-1.6-Linux-x86_64-20121007/bitmaps/file_save.bmp
    GtkRadiant-1.6-Linux-x86_64-20121007/bitmaps/window4.bmp
    GtkRadiant-1.6-Linux-x86_64-20121007/bitmaps/logo.png
    GtkRadiant-1.6-Linux-x86_64-20121007/bitmaps/view_cubicclipping.bmp
    GtkRadiant-1.6-Linux-x86_64-20121007/bitmaps/patch_weld.bmp
    GtkRadiant-1.6-Linux-x86_64-20121007/bitmaps/brush_rotatey.bmp
    GtkRadiant-1.6-Linux-x86_64-20121007/bitmaps/brush_flipz.bmp
    GtkRadiant-1.6-Linux-x86_64-20121007/q3data
    GtkRadiant-1.6-Linux-x86_64-20121007/libpng12.so.0
  • exit 0
    Esecuzione(%build) in corso: /bin/sh -e /var/tmp/rpm-tmp.pIf2hx
  • umask 022
  • cd /home/makerpm/rpmbuild/BUILD
  • LANG=C
  • export LANG
  • unset DISPLAY
  • exit 0
    Esecuzione(%install) in corso: /bin/sh -e /var/tmp/rpm-tmp.hCYHkI
  • umask 022
  • cd /home/makerpm/rpmbuild/BUILD
  • ‘’ /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64 ‘!=’ / ‘]’
  • rm -rf /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64
    ++ dirname /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64
  • mkdir -p /home/makerpm/rpmbuild/BUILDROOT
  • mkdir /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64
  • LANG=C
  • export LANG
  • unset DISPLAY
  • rm -rf /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64
  • mkdir -p /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/usr/bin
  • mkdir -p /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/usr/share
  • mkdir -p /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/usr/share/icons/hicolor/128x128/apps
    ++ uname -p
  • cp -Rf GtkRadiant-1.6-Linux-x86_64-20121007/ /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/usr/share/gtkradiant
  • install -p -m 755 /home/makerpm/rpmbuild/SOURCES/gtkradiant.desktop /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/usr/bin/gtkradiant
  • desktop-file-install --dir /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/usr/share/applications /home/makerpm/rpmbuild/SOURCES/gtkradiant.desktop
  • install -p -m 644 /home/makerpm/rpmbuild/SOURCES/gtkradiant.png /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/usr/share/icons/hicolor/128x128/apps
  • /usr/lib/rpm/check-rpaths /usr/lib/rpm/check-buildroot

  • WARNING: ‘check-rpaths’ detected a broken RPATH and will cause ‘rpmbuild’
  •      to fail. To ignore these errors, you can set the '$QA_RPATHS'
    
  •      environment variable which is a bitmask allowing the values
    
  •      below. The current value of QA_RPATHS is 0x0000.
    
  • 0x0001 … standard RPATHs (e.g. /usr/lib); such RPATHs are a minor
  •           issue but are introducing redundant searchpaths without
    
  •           providing a benefit. They can also cause errors in multilib
    
  •           environments.
    
  • 0x0002 … invalid RPATHs; these are RPATHs which are neither absolute
  •           nor relative filenames and can therefore be a SECURITY risk
    
  • 0x0004 … insecure RPATHs; these are relative RPATHs which are a
  •           SECURITY risk
    
  • 0x0008 … the special ‘$ORIGIN’ RPATHs are appearing after other
  •           RPATHs; this is just a minor issue but usually unwanted
    
  • 0x0010 … the RPATH is empty; there is no reason for such RPATHs
  •           and they cause unneeded work while loading libraries
    
  • 0x0020 … an RPATH references ‘…’ of an absolute path; this will break
  •           the functionality when the path before '..' is a symlink
    
  • Examples:
    • to ignore standard and empty RPATHs, execute ‘rpmbuild’ like
  • $ QA_RPATHS=$ 0x0001|0x0010 ] rpmbuild my-package.src.rpm
    • to check existing files, set $RPM_BUILD_ROOT and execute check-rpaths like
  • $ RPM_BUILD_ROOT= /usr/lib/rpm/check-rpaths

ERROR 0004: file ‘/usr/share/gtkradiant/q3data’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/q3map2’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/bobtoolz.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/model.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/ufoai.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/bkgrnd2d.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/camera.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/surface_heretic2.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/imagewal.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/map.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/vfswad.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/prtview.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/mapxml.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/entity.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/surface_ufoai.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/imagehl.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/imagepng.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/vfspk3.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/surface_quake2.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/shaders.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/spritemodel.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/fgd.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/imagem8.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/image.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/gtkgensurf.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/surface.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/textool.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/hydratoolz.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/vfspak.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/modules/vfsqlpk3.so’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/radiant.bin’ contains an insecure rpath ‘.’ in .]
ERROR 0004: file ‘/usr/share/gtkradiant/q3map2_urt’ contains an insecure rpath ‘.’ in .]
errore: Stato d’uscita errato da /var/tmp/rpm-tmp.hCYHkI (%install)

Errori di compilazione RPM:
Stato d’uscita errato da /var/tmp/rpm-tmp.hCYHkI (%install)
[[email protected] SPECS]$[/code]

La cosa strana è che questo errore me lo da solo con l’ultima versione, la http://icculus.org/pipermail/gtkradiant/2012-October/011825.html.
Provando a ricompilare la vecchia versione (20120520), quella sulla pagina http://icculus.org/gtkradiant/downloads.html#gtkr16 non ancora aggioranta, non si presentano problemi e la compilazione va a buon fine.

Mi pare di aver dedotto però che il problema è nel pacchetto e non in rpmbuild, anche perché non c’è niente da compilare nella sezione %build. Anche a qualcun altro sono successi problemi del genere? Sono warning importanti? Hanno senso di essere ascoltati? Se no, come fare per ignorarli?

Se servono maggiori info fatelo sapere.
Ciao!

Potresti allegare il file .spec ?

Ciao trpost, grazie per la risposta.
Ho caricato lo spec modificato http://sourceforge.net/projects/gtkradiant-rpms/files/sources/gtkradiant.spec_modified/download, e come puoi vedere da quello della versione precedente (nella stessa cartella) sono praticamente identici.

Edit: …tranne ovviamente per il numero di release e il changelog.
Notte!

Queste wiki potrebbero esserti utili: http://fedoraproject.org/wiki/Extras/Schedule/RpathCheckBuildsys, https://fedoraproject.org/wiki/Packaging:Guidelines?rd=Packaging/Guidelines#Beware_of_Rpath.

Fammi sapere. :wink:

Ciao trpost, grazie ancora per l’attenzione.
Ho dato una letta ai link e qualcosa (poco) ci ho capito: in pratica rpath si lamenta che ci sono librerie al di fuori delle cartelle di sistema impostate per le librerie, che dovrebbero essere /lib, /usr/lib, /lib64, /usr/lib64.
Teoricamente quindi dovrei spostare i file di cui si lamenta in una di queste librerie dallo spec così:

[code]…
%install
rm -rf “$RPM_BUILD_ROOT”
mkdir -p $RPM_BUILD_ROOT%{_bindir}
mkdir -p $RPM_BUILD_ROOT%{_datadir}
mkdir -p $RPM_BUILD_ROOT%{_datadir}/icons/hicolor/128x128/apps

#moving the libraries
mv GtkRadiant-%{version}-Linux-$(uname -p)-%{version2}/modules/.so %{libdir}/%{name}/modules/
mv GtkRadiant-%{version}-Linux-$(uname -p)-%{version2}/q3
%{libdir}/%{name}/
mv GtkRadiant-%{version}-Linux-$(uname -p)-%{version2}/radiant.bin %{libdir}/%{name}/

set up the source

cp -Rf GtkRadiant-%{version}-Linux-$(uname -p)-%{version2}/
$RPM_BUILD_ROOT%{_datadir}/%{name}

set up the bin

install -p -m 755 %{SOURCE3} $RPM_BUILD_ROOT%{_bindir}/%{name}

install desktop files and images

desktop-file-install --dir $RPM_BUILD_ROOT%{_datadir}/applications
%{SOURCE3}
install -p -m 644 %{SOURCE4} $RPM_BUILD_ROOT%{_datadir}/icons/hicolor/128x128/apps

…[/code]

e in teoria adesso ho spostato tutti i file nelle librerie di sistema. O ho sbagliato?
devo creare dei link simbolici da queste nuove posizioni a /usr/share/gtkradiant giusto?

Grazie ancora.

Non ho mai usato questo tipo di strumento ma penso che dovresti indicare dove andare a prendere questi file.
Anche se non si capisce come siano stati costruiti …

[code]%build

nothing to build[/code]

:gratt:

Scusa, non ho capito cosa intendi.

[quote=trpost][code]%build

nothing to build[/code]

:gratt:[/quote]

Questo perché i pacchetti sorgente sono già compilati per 32 e 64 bit e non necessitano compilazioni. Lo sviluppatore mi ha spiegato in ML che è perché [quote]we are taking the ‘compile once, package for multiple distributions’ approach.[/quote]
la parte build l’ho messa solo per far vedere che non me la sono dimenticata ma perché realmente non c’è niente da compilare.

Ho guardato lo spec di un pacchetto (libpwquality, ma non è importante) e penso dovrei fare una cosa così:

.. pushd GtkRadiant-%{version}-Linux-$(uname -p)-%{version2} mv modules/*.so $RPM_BUILD_ROOT/%{_lib}/ mv q3* $RPM_BUILD_ROOT/%{_lib}/ mv radiant.bin $RPM_BUILD_ROOT/%{_lib}/ popd ..

Ps: https://fedoraproject.org/wiki/Packaging:RPMMacros#Other_macros_and_variables_for_paths credo sia un errore la mancanza dello slash davanti a lib, no?

Ho modificato ancora la parte install, ora è così:

[code]%install
rm -rf “$RPM_BUILD_ROOT”
mkdir -p $RPM_BUILD_ROOT%{_bindir}
mkdir -p $RPM_BUILD_ROOT%{_datadir}
mkdir -p $RPM_BUILD_ROOT%{_datadir}/icons/hicolor/128x128/apps
mkdir -p $RPM_BUILD_ROOT/%{_lib}/modules/

set up the source

mv -f GtkRadiant-%{version}-Linux-$(uname -p)-%{version2}/
$RPM_BUILD_ROOT%{_datadir}/%{name}

linking modules

pushd $RPM_BUILD_ROOT%{_datadir}/%{name}/
mv modules/.so $RPM_BUILD_ROOT/%{_lib}/
mv q3
$RPM_BUILD_ROOT/%{_lib}/
mv radiant.bin $RPM_BUILD_ROOT/%{_lib}/
ln -sf $RPM_BUILD_ROOT/%{_lib}/modules/.so modules/.so
ln -sf $RPM_BUILD_ROOT/%{_lib}/* *
popd

set up the bin

install -p -m 755 %{SOURCE3} $RPM_BUILD_ROOT%{_bindir}/%{name}

install desktop files and images

desktop-file-install --dir $RPM_BUILD_ROOT%{_datadir}/applications
%{SOURCE3}
install -p -m 644 %{SOURCE4} $RPM_BUILD_ROOT%{_datadir}/icons/hicolor/128x128/apps

[/code]

il problema adesso è che non mi fa correttamente i link, ecco il risultato:

[code]

rm -rf /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64

  • mkdir -p /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/usr/bin
  • mkdir -p /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/usr/share
  • mkdir -p /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/usr/share/icons/hicolor/128x128/apps
  • mkdir -p /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/modules/
    ++ uname -p
  • mv -f GtkRadiant-1.6-Linux-x86_64-20121007/ /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/usr/share/gtkradiant
  • pushd /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/usr/share/gtkradiant/
    ~/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/usr/share/gtkradiant ~/rpmbuild/BUILD
  • mv modules/bkgrnd2d.so modules/bobtoolz.so modules/camera.so modules/entity.so modules/fgd.so modules/gtkgensurf.so modules/hydratoolz.so modules/image.so modules/imagehl.so modules/imagem8.so modules/imagepng.so modules/imagewal.so modules/map.so modules/mapxml.so modules/model.so modules/prtview.so modules/shaders.so modules/spritemodel.so modules/surface.so modules/surface_heretic2.so modules/surface_quake2.so modules/surface_ufoai.so modules/textool.so modules/ufoai.so modules/vfspak.so modules/vfspk3.so modules/vfsqlpk3.so modules/vfswad.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/
  • mv q3data q3map2 q3map2_urt /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/
  • mv radiant.bin /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/
  • ln -sf ‘/home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/modules/.so’ 'modules/.so’
  • ln -sf /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/bkgrnd2d.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/bobtoolz.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/camera.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/entity.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/fgd.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/gtkgensurf.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/hydratoolz.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/image.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/imagehl.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/imagem8.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/imagepng.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/imagewal.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/map.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/mapxml.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/model.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/modules /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/prtview.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/q3data /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/q3map2 /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/q3map2_urt /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/radiant.bin /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/shaders.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/spritemodel.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/surface.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/surface_heretic2.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/surface_quake2.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/surface_ufoai.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/textool.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/ufoai.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/vfspak.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/vfspk3.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/vfsqlpk3.so /home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/lib64/vfswad.so bitmaps bspc installs libjpeg.so.62 libpng12.so.0 modules
    ln: `modules/bitmaps’: cannot overwrite directory
    errore: Stato d’uscita errato da /var/tmp/rpm-tmp.W2pejt (%install)

Errori di compilazione RPM:
Stato d’uscita errato da /var/tmp/rpm-tmp.W2pejt (%install)
$ [/code]

dov’è l’errore ora? Mi sa che manca poco a risolvere…

Ciao!

Allora, sono riuscito a “risolvere” il problema con http://www.linuxquestions.org/questions/fedora-35/warning-check-rpaths-detected-a-broken-rpath-and-will-cause-rpmbuild-to-fail-606748/ risposta, infatti ero andato a modificare il file .rpmmacros tempo fa.

Cambiato anche spec, http://sourceforge.net/projects/gtkradiant-rpms/files/sources/gtkradiant.spec/download quello aggiornato.
Grazie ancora per l’assistenza trpost, considero risolto. Adesso vedo se su bugzilla mi prendono sto benedetto pacchetto :slight_smile:
Ciao!