Re: Enough Is Enough
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 30/03/2010 02:58:13, Programmer In Training wrote:
>> find /usr/local/bin /usr/local/lib -name -type f | \
> Is the 'f' a typo? I had to remove it because find kept on erroring on it.
There is a typo, but it's to do with the -name predicate. -name needs
an argument -- but as the quoted script seems to be trying to scan for
the libraries linked to be everything in ${PREFIX}/bin and
${PREFIX}/lib you don't need to filter by name at all. Just use:
find /usr/local/bin /usr/local/lib -type f | \
'-type f' says 'only regular files, not directories or sym-links'
Note that using grep(1) to work out what a binary links to is
exceedingly bizarre. ldd(1) is the correct tool for that job.
In any case, there are better solutions to this problem: try using the
sysutils/libchk port.
Cheers,
Matthew
- --
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkuxp9kACgkQ8Mjk52CukIzmqgCfVX1vLd0TW/AZ01SLEVtKUvPP
nEwAnjFHrOj+CdtF09CqC6/VAaoP2ERP
=Tlgk
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Enough Is Enough
On 03/28/10 09:46, Sergio de Almeida Lenzi wrote:
> this scripts outputs the commands needed to fix the system
I'm having some problems with the script.
> watch out
> ==
> #!/bin/sh
>
> endp() {
> rm -f $t
> exit $1
> }
>
> t=/tmp/$$
>
> if [ $# -ne 1 ]
> then
> echo use $0 library
> endp 1
> fi
>
> lib=$1
>
> find /usr/local/bin /usr/local/lib -name -type f | \
Is the 'f' a typo? I had to remove it because find kept on erroring on it.
> while read x
> do
> grep $lib $x | \
> awk '{print $3}' | \
> while read y
> do
> pkg_info -W $y >> $t
> done
> done
> awk '{print $NF}' $t | sort -u > /tmp/buildpkglist
> echo nice portmaster -Bdg `cat /tmp/buildpkglist`
> endp 0
The final output (after removing the stray 'f'):
./portmaster-script jpeg
awk: can't open file /tmp/42352
source line number 1
nice portmaster -Bdg
ran as regular user and root to no different affect.
I switched out all instances of awk for grep with the following result:
./portmaster-script jpeg
grep: /tmp/42436: No such file or directory
nice portmaster -Bdg
Thanks for the suggestion, but this script doesn't seem to work on my
system and I can't seem to figure out what exactly is causing it to fail.
--
Yours In Christ,
PIT
Emails are not formal business letters, whatever businesses may want.
Original content copyright under the OWL http://owl.apotheon.org
Please do not CC me. If I'm posting to a list it is because I am subscribed.
signature.asc
Description: OpenPGP digital signature
Re: Enough Is Enough
On 03/28/10 09:46, Sergio de Almeida Lenzi wrote: > this scripts outputs the commands needed to fix the system Thanks! I'll give it a whirl tomorrow. -- Yours In Christ, PIT Emails are not formal business letters, whatever businesses may want. Original content copyright under the OWL http://owl.apotheon.org Please do not CC me. If I'm posting to a list it is because I am subscribed. signature.asc Description: OpenPGP digital signature
Re: Enough Is Enough
I do not doubt the "power" of portmaster and portupgrade, but
in my system (I have a "master" 4core,8Gb and several "slaves" about 40
of them , that upgrade via portmaster -P -aBdg)
in the master system there are about 1200 packages installed...
so a portmaster -r png will last forever...
I made a shell script that tests for the existance of the library
in /usr/local/lib/*.so, /usr/local/bin/*
sort it and tells me what ports really need upgrade...
with about 1200 ports, only 120 needed upgrade... (a question of 2
hours) in the "master cpu",
or about 20 minutes in the "slaves"
this scripts outputs the commands needed to fix the system
watch out
==
#!/bin/sh
endp() {
rm -f $t
exit $1
}
t=/tmp/$$
if [ $# -ne 1 ]
then
echo use $0 library
endp 1
fi
lib=$1
find /usr/local/bin /usr/local/lib -name -type f | \
while read x
do
grep $lib $x | \
awk '{print $3}' | \
while read y
do
pkg_info -W $y >> $t
done
done
awk '{print $NF}' $t | sort -u > /tmp/buildpkglist
echo nice portmaster -Bdg `cat /tmp/buildpkglist`
endp 0
=
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Enough Is Enough
On 27.03.2010 20:10, Erik Trulsson wrote: > On Sat, Mar 27, 2010 at 01:28:26PM -0500, Programmer In Training wrote: >> On 03/27/10 13:06, Tijl Coosemans wrote: >> >>> In /usr/ports/UPDATING look for the 20100205 entry for "users of Qt 3 >>> and KDE 3". >> >> Pointless in as far as that does not address the underlying problem of >> rebuilding EVERYTHING that needs to link against the jpeg library. GIMP >> and gegl failed because a dependency for it is linked against jpeg-7 and >> not jpeg-8. >> >> If I cannot basically reinstall the entire system via portupgrade -a I'm >> reduced to fixing the problem ad-hoc and that is unacceptable because >> eventually I'll have to deal with programs that link to whatever just >> got rebuilt. In essence, this is a problem that is not easily solved >> just by reading /usr/ports/UPDATING for Qt because it involves more than >> Qt (by the way, thanks for the hat tip on Qt, but it's not high on my >> priority list for being fixed right now, GIMP, Scribus and possibly a >> few other apps that I'm currently unaware of there being an issue with >> ARE). > > So don't use portupgrade if doesn't do what is needed. > > The simple solution is to *first* deinstall *all* ports (or at least > all ports that depend, directly or indirectly, on jpeg in this case) > and then reinstall them all. This might require a bit more manual > intervention than using portupgrade would have, but on the other hand > it is almost guaranteed to work correctly every time. > > The problems you are running into is essentially due to trying to build > updated binaries while still having old binaries installed (and having > this trigger bugs in the build mechanism of various ports.) > If you first remove all the old binaries and then build new ones you > avoid many potential problems. > > > portupgrade -afr jpeg-8 there, done. //Svein -- +---+--- /"\ |Svein Skogen | sv...@d80.iso100.no \ / |Solberg Østli 9| PGP Key: 0xE5E76831 X|2020 Skedsmokorset | sv...@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | sv...@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listm...@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +---+--- |msn messenger: | Mobile Phone: +47 907 03 575 |sv...@jernhuset.no | RIPE handle:SS16503-RIPE +---+--- If you really are in a hurry, mail me at svein-mob...@stillbilde.net This mailbox goes directly to my cellphone and is checked even when I'm not in front of my computer. Picture Gallery: https://gallery.stillbilde.net/v/svein/ signature.asc Description: OpenPGP digital signature
Re: Enough Is Enough
On Sat, Mar 27, 2010 at 01:28:26PM -0500, Programmer In Training wrote: > On 03/27/10 13:06, Tijl Coosemans wrote: > > > In /usr/ports/UPDATING look for the 20100205 entry for "users of Qt 3 > > and KDE 3". > > Pointless in as far as that does not address the underlying problem of > rebuilding EVERYTHING that needs to link against the jpeg library. GIMP > and gegl failed because a dependency for it is linked against jpeg-7 and > not jpeg-8. > > If I cannot basically reinstall the entire system via portupgrade -a I'm > reduced to fixing the problem ad-hoc and that is unacceptable because > eventually I'll have to deal with programs that link to whatever just > got rebuilt. In essence, this is a problem that is not easily solved > just by reading /usr/ports/UPDATING for Qt because it involves more than > Qt (by the way, thanks for the hat tip on Qt, but it's not high on my > priority list for being fixed right now, GIMP, Scribus and possibly a > few other apps that I'm currently unaware of there being an issue with > ARE). So don't use portupgrade if doesn't do what is needed. The simple solution is to *first* deinstall *all* ports (or at least all ports that depend, directly or indirectly, on jpeg in this case) and then reinstall them all. This might require a bit more manual intervention than using portupgrade would have, but on the other hand it is almost guaranteed to work correctly every time. The problems you are running into is essentially due to trying to build updated binaries while still having old binaries installed (and having this trigger bugs in the build mechanism of various ports.) If you first remove all the old binaries and then build new ones you avoid many potential problems. -- Erik Trulsson ertr1...@student.uu.se ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Enough Is Enough
Programmer In Training wrote: [snip] > > When jpeg-x (not a typo) is built, the port needs to be automatically > looking forward to see what all depends on it (and if anything depends > on that) and possibly asking the user if they want to upgrade all those > programs to ensure they link to the proper version of jpeg at all times. > Or they could all statically compile in jpeg support (as I assume FF > does because I can still see jpegs in the file upload preview pane) so > this is never an issue at all. I am currently able to manipulate any > jpeg at all (and now unable to use an increasing number of apps) which > is crippling my ability to edit images for any use. > So man portupgrade and see what the -r and -R switches do. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Enough Is Enough
On 27 March 2010 13:20, Programmer In Training wrote: > Ever since I installed jpeg-8 I have had nothing but problems. > > I ran portupgrade -a hoping to take care of all those problems, well no > such luck. > portupgrade -fa -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Enough Is Enough
On 03/27/10 13:06, Tijl Coosemans wrote: > In /usr/ports/UPDATING look for the 20100205 entry for "users of Qt 3 > and KDE 3". Pointless in as far as that does not address the underlying problem of rebuilding EVERYTHING that needs to link against the jpeg library. GIMP and gegl failed because a dependency for it is linked against jpeg-7 and not jpeg-8. If I cannot basically reinstall the entire system via portupgrade -a I'm reduced to fixing the problem ad-hoc and that is unacceptable because eventually I'll have to deal with programs that link to whatever just got rebuilt. In essence, this is a problem that is not easily solved just by reading /usr/ports/UPDATING for Qt because it involves more than Qt (by the way, thanks for the hat tip on Qt, but it's not high on my priority list for being fixed right now, GIMP, Scribus and possibly a few other apps that I'm currently unaware of there being an issue with ARE). When jpeg-x (not a typo) is built, the port needs to be automatically looking forward to see what all depends on it (and if anything depends on that) and possibly asking the user if they want to upgrade all those programs to ensure they link to the proper version of jpeg at all times. Or they could all statically compile in jpeg support (as I assume FF does because I can still see jpegs in the file upload preview pane) so this is never an issue at all. I am currently able to manipulate any jpeg at all (and now unable to use an increasing number of apps) which is crippling my ability to edit images for any use. I'm really loving FreeBSD, but I can no longer use The GIMP to open JPEG's (and this is really the biggest issue I'm having as I need to be able to edit jpeg's so I can continue on with designing the site on my box, otherwise I will have to move back over to another computer (and right now the only one available is running WinXP, something I'd rather avoid using if I can), I cannot even launch Scribus (and a few other apps whose names escape me at the moment). Other apps open but have loads of errors regarding jpeg. I'm unable (as of about a month ago) to install Filezilla because of this (it stopped launching when I upgraded jpeg, so I uninstalled and reinstalled thinking that would work). Every time I think I've tracked down the one other library or whatever that something links against and needs jpeg, something new crops up and stops me from building. Again. Anyway, time I got off the comp. I'll be back later this evening to finish this discussion. -- Yours In Christ, PIT Emails are not formal business letters, whatever businesses may want. Original content copyright under the OWL http://owl.apotheon.org Please do not CC me. If I'm posting to a list it is because I am subscribed. signature.asc Description: OpenPGP digital signature
Re: Enough Is Enough
On Saturday 27 March 2010 18:20:28 Programmer In Training wrote: > Ever since I installed jpeg-8 I have had nothing but problems. > > I ran portupgrade -a hoping to take care of all those problems, well > no such luck. > > Let's start with the first error I caught: > > libqt > /usr/bin/ld: warning: libjpeg.so.10, needed by > /usr/local/lib/libqt-mt.so, not found (try using -rpath or -rpath-link) > /usr/local/lib/libqt-mt.so: undefined reference to > `jpeg_start_decompr...@libjpeg_7.0' > /usr/local/lib/libqt-mt.so: undefined reference to > `jpeg_resync_to_rest...@libjpeg_7.0' > /usr/local/lib/libqt-mt.so: undefined reference to > `jpeg_read_scanli...@libjpeg_7.0' > /usr/local/lib/libqt-mt.so: undefined reference to > `jpeg_start_compr...@libjpeg_7.0' > /usr/local/lib/libqt-mt.so: undefined reference to > `jpeg_finish_compr...@libjpeg_7.0' > /usr/local/lib/libqt-mt.so: undefined reference to > `jpeg_finish_decompr...@libjpeg_7.0' > /usr/local/lib/libqt-mt.so: undefined reference to > `jpeg_createcompr...@libjpeg_7.0' > /usr/local/lib/libqt-mt.so: undefined reference to > `jpeg_set_defau...@libjpeg_7.0' > /usr/local/lib/libqt-mt.so: undefined reference to > `jpeg_read_hea...@libjpeg_7.0' > /usr/local/lib/libqt-mt.so: undefined reference to > `jpeg_createdecompr...@libjpeg_7.0' > /usr/local/lib/libqt-mt.so: undefined reference to > `jpeg_std_er...@libjpeg_7.0' > /usr/local/lib/libqt-mt.so: undefined reference to > `jpeg_destroy_compr...@libjpeg_7.0' > /usr/local/lib/libqt-mt.so: undefined reference to > `jpeg_destroy_decompr...@libjpeg_7.0' > /usr/local/lib/libqt-mt.so: undefined reference to > `jpeg_write_scanli...@libjpeg_7.0' > /usr/local/lib/libqt-mt.so: undefined reference to > `jpeg_set_qual...@libjpeg_7.0' > *** Error code 1 > > Stop in > /usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/tools/designer/uic. > *** Error code 1 > > Stop in > /usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/tools/designer/uic. > *** Error code 1 > > Stop in /usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/tools/designer. > *** Error code 1 > > Stop in /usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/tools. > *** Error code 1 > > Stop in /usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8. > *** Error code 1 > > Stop in /usr/ports/x11-toolkits/qt33. > *** Error code 1 > > Stop in /usr/ports/x11-toolkits/qt33. > ** Command failed [exit code 1]: /usr/bin/script -qa > /tmp/portupgrade20100324-4351-6tihzj-0 env UPGRADE_TOOL=portupgrade > UPGRADE_PORT=qt-copy-3.3.8_10 UPGRADE_PORT_VER=3.3.8_10 make > ** Fix the problem and try again. > > The next error was for OOo (for which I need to follow the directions > and email the maintainer). After portupgrade -a reaches the end > (apparently, as it exits): > > ---> Skipping 'editors/openoffice.org-3' (openoffice.org-3.1.1) because > it has already failed > ** Listing the failed packages (-:ignored / *:skipped / !:failed) > - textproc/docbook-xml-440 (docbook-xml-4.4_1) > - textproc/docbook-sk (docbook-sk-4.1.2_4) > ! x11-toolkits/qt33 (qt-copy-3.3.8_10) (linker error) > * audio/arts (arts-1.5.10_2,1) > * devel/sdl12 (sdl-1.2.14,2) > * graphics/sdl_image (sdl_image-1.2.10) > - textproc/docbook-xml-430 (docbook-xml-4.3) > * multimedia/ffmpeg (ffmpeg-0.5_2,1) > * multimedia/vlc (vlc-1.0.5,3) > * graphics/gegl (gegl-0.0.22_6) > * graphics/gimp-app (gimp-app-2.6.8,1) > * graphics/py-gimp (py26-gimp-app-2.6.8) > * print/gimp-gutenprint (gimp-gutenprint-5.2.4) > * print/scribus (scribus-1.3.3.13_1) > * security/pinentry (pinentry-0.7.6_2) > * sysutils/k3b (k3b-1.0.5_2) > * multimedia/libxine (libxine-1.1.16.3_2) > * multimedia/phonon-xine (phonon-xine-4.3.1_3) > * games/gcompris (gcompris-8.4.12_3) > ! editors/openoffice.org-3 (en-openoffice.org-US-3.1.1) > (configure error) > * editors/openoffice.org-3 (openoffice.org-3.1.1) > > > A good deal of these (including Scribus and GIMP and a few others I > believe) are from errors with my upgrading from jpeg-7 to jpeg-8. > > I was ready for many, many days of compiling (mainly because of OOo). > Instead I'm lucky to go 36 hours total. > > Why has upgrading my jpeg library completely BROKEN so many apps? I > cannot even start scribus now. > > /libexec/ld-elf.so.1: Shared object "libjpeg.so.10" not found, > required by "scribus" > > Enough is enough. I've been trying to fix this problem on my own and > I cannot. It is not from a lack of trying or looking to solve this > issue. In /usr/ports/UPDATING look for the 20100205 entry for "users of Qt 3 and KDE 3". ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
