Re: Shared object libaprutil-1.so.4 not found, required by libserf-1.so.0
Antonio Olivares olivares14031 at gmail.com writes: On Thu, Sep 12, 2013 at 12:36 AM, Matthew Seaman m.seaman at infracaninophile.co.uk wrote: On 11/09/2013 21:03, Antonio Olivares wrote: [Info 19:57:22] Updating 'freebsd_texlive' source ports tree with method 'svn'. Shared object libaprutil-1.so.4 not found, required by libserf-1.so.0 [Error 19:57:22] Subversion update failed. [Error 19:57:22] Failed to update the 'freebsd_texlive' ports tree. Yeah -- you need to update or install the package that provides libaprutil-1.so. If you're using pkg(8) against a package repository rather than compiling your own, you could use: pkg check -d subversion-1.8.3 For portmaster dependencies should be auto-updated when you run portmaster devel/subversion It might be useful to run portmaster --force-config -f devel/subversion so you can recheck all the options settings of dependencies, but this will rebuild portmaster and everything it depends on. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matthew at infracaninophile.co.uk Dear Dr. Matthew, Thank you very much for your excellent advice. Worked like a champ! Now if I can get iced-teaweb/openjdk to open *.jnlp files to use java, it appears that itweb-javaws is not working correctly. Firefox reports that the file *.jnlp downloaded, but it is not opened by java. Thank you very much sir for your help. Best Regards, Antonio ___ freebsd-questions at freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscribe at freebsd.org Hello, I've had the same problem, also using portshaker and freebsd-texlive ports. I think the solution was in /usr/ports/UPDATING : 20130706: AFFECTS: users of devel/apr1 AUTHOR: oha...@freebsd.org APR was updated to 1.4.8 and APR-util was updated to 1.5.2. Please rebuild all ports which are using functions from APR/APR-util such as apache, subversion ... # portmaster -r apr or # portupgrade -r devel/apr1 or # pkg install -fR devel/apr1 Best regards ___ 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: Shared object libaprutil-1.so.4 not found, required by libserf-1.so.0
On Thu, Sep 12, 2013 at 12:36 AM, Matthew Seaman m.sea...@infracaninophile.co.uk wrote: On 11/09/2013 21:03, Antonio Olivares wrote: [Info 19:57:22] Updating 'freebsd_texlive' source ports tree with method 'svn'. Shared object libaprutil-1.so.4 not found, required by libserf-1.so.0 [Error 19:57:22] Subversion update failed. [Error 19:57:22] Failed to update the 'freebsd_texlive' ports tree. Yeah -- you need to update or install the package that provides libaprutil-1.so. If you're using pkg(8) against a package repository rather than compiling your own, you could use: pkg check -d subversion-1.8.3 For portmaster dependencies should be auto-updated when you run portmaster devel/subversion It might be useful to run portmaster --force-config -f devel/subversion so you can recheck all the options settings of dependencies, but this will rebuild portmaster and everything it depends on. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matt...@infracaninophile.co.uk Dear Dr. Matthew, Thank you very much for your excellent advice. Worked like a champ! Now if I can get iced-teaweb/openjdk to open *.jnlp files to use java, it appears that itweb-javaws is not working correctly. Firefox reports that the file *.jnlp downloaded, but it is not opened by java. Thank you very much sir for your help. Best Regards, Antonio ___ 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
lprof startup issue, QAssistantClient not found
After installing (and reinstalling) devel/lprof, I keep getting the error: The QAssistantClient executable was not found. Make sure that assistant(.exe)is located either in your PATH or in the $QTDIR/bin directory. Help will not be availble until this is corrected. I have both devel/qt4-assistant devel/qt4-assistant-adp installed, but that doesn't seem to make any difference. assistant-qt4 and assistant_adp both exist in /usr/local/bin If I create a symbolic link of assistant to either of the assistant* executables I no longer get the error message, but no help shows up either... ideas? ___ 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
Shared object libaprutil-1.so.4 not found, required by libserf-1.so.0
Dear folks, I am having problems with subject line. I have to fix error by reinstalling subversion, but it keeps coming back with this error message. Shared object libaprutil-1.so.4 not found, required by libserf-1.so.0 === Returning to list of ports depending on subversion-1.8.3 === Updating done for ports that depend on subversion-1.8.3 === The following actions were performed: Re-installation of subversion-1.8.3 Re-installation of portshaker-1.0.8 Re-installation of portshaker-config-1.0.8 === Exiting I did a # portmaster -d -r subversion I configured subversion to use serf because I am used to freebsd_texlive_* I run to update and I get [Info 19:57:22] Updating 'freebsd_texlive' source ports tree with method 'svn'. Shared object libaprutil-1.so.4 not found, required by libserf-1.so.0 [Error 19:57:22] Subversion update failed. [Error 19:57:22] Failed to update the 'freebsd_texlive' ports tree. machine has not been updated since 05/27, I read entry: 20130619: AFFECTS: users of devel/subversion AUTHOR: oha...@freebsd.org devel/subversion has been upgraded from 1.7.10 to 1.8.0 If you want to upgrade, and use http/https access to repositories, please check, that the SERF option is enabled, as NEON support is gone. Also, mod_dontdothat and svnauthz_validate are now enabled with one option TOOLS, among other new tools and SVNMUCC is enabled always. subversion-1.7.x is available as devel/subversion17 To stay on subversion-1.7.x set in /etc/make.conf WITH_SUBVERSION_VER=17 and use the following command # pkg set -o devel/subversion:devel/subversion17 or # portmaster -o devel/subversion17 devel/subversion I configured subversion to use serf option and tried it. Thanks for advice/ideas suggestions. Best Regards, Antonio ___ 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: Shared object libaprutil-1.so.4 not found, required by libserf-1.so.0
On 11/09/2013 21:03, Antonio Olivares wrote: [Info 19:57:22] Updating 'freebsd_texlive' source ports tree with method 'svn'. Shared object libaprutil-1.so.4 not found, required by libserf-1.so.0 [Error 19:57:22] Subversion update failed. [Error 19:57:22] Failed to update the 'freebsd_texlive' ports tree. Yeah -- you need to update or install the package that provides libaprutil-1.so. If you're using pkg(8) against a package repository rather than compiling your own, you could use: pkg check -d subversion-1.8.3 For portmaster dependencies should be auto-updated when you run portmaster devel/subversion It might be useful to run portmaster --force-config -f devel/subversion so you can recheck all the options settings of dependencies, but this will rebuild portmaster and everything it depends on. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matt...@infracaninophile.co.uk signature.asc Description: OpenPGP digital signature
Shared library not found after upgrade to 9.2-PRERELEASE
I recently upgraded a system to FreeBSD t42.umpquanet.com 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0 r254977: Wed Aug 28 19:58:37 PDT 2013 r...@t42.umpquanet.com:/usr/obj/usr/src/sys/GENERIC i386 I then deleted all the installed ports, and am rebuilding the ones I still use. I've encountered several instances where although a required port is already installed, a dependent port build will claim that the required library isn't found, and attempt a (re-)install of that port. In this example, jbig2dec claims that shared library libpng15.so is not found, although 'ls' says it is in /usr/local/lib, and 'make missing' reports no uninstalled dependencies. What can I do to remedy this, short of setting FORCE_PKG_REGISTER and spending a lot of time rebuilding ports that are already installed? Please Cc: me on replies. Thank you! Jim # cd /usr/ports/graphics/jbig2dec # ls -l /usr/local/lib/libpng15* -rw-r--r-- 1 root wheel 202762 Sep 1 16:10 /usr/local/lib/libpng15.a lrwxr-xr-x 1 root wheel 14 Sep 1 16:10 /usr/local/lib/libpng15.so@ - libpng15.so.15 -rwxr-xr-x 1 root wheel 175596 Sep 1 16:10 /usr/local/lib/libpng15.so.15* # make clean === Cleaning for png-1.5.17 === Cleaning for jbig2dec-0.11_1 # make missing # make === License GPLv3 accepted by the user === Found saved configuration for jbig2dec-0.11 === Fetching all distfiles required by jbig2dec-0.11_1 for building === Extracting for jbig2dec-0.11_1 = SHA256 Checksum OK for jbig2dec-0.11.tar.xz. === Patching for jbig2dec-0.11_1 === Applying extra patch /usr/ports/graphics/jbig2dec/files/simpler-test-patch === Applying FreeBSD patches for jbig2dec-0.11_1 /usr/bin/sed -i.bak -E 's|SHA1_Final\( *([^,]+), *([^\)]+)\)|SHA1_Final(\2, \1)|' /usr/ports/graphics/jbig2dec/work/jbig2dec-0.11/jbig2dec.c /usr/ports/graphics/jbig2dec/work/jbig2dec-0.11/sha1.c === jbig2dec-0.11_1 depends on shared library: libpng15.so - not found ===Verifying for libpng15.so in /usr/ports/graphics/png === Found saved configuration for png-1.5.12 === Fetching all distfiles required by png-1.5.17 for building === Extracting for png-1.5.17 = SHA256 Checksum OK for libpng-1.5.17.tar.xz. = SHA256 Checksum OK for libpng-1.5.17-apng.patch.gz. /bin/cp /usr/ports/distfiles//libpng-1.5.17-apng.patch.gz /usr/ports/graphics/png/work/libpng-1.5.17/ /usr/bin/gzip -nf -9 -d /usr/ports/graphics/png/work/libpng-1.5.17/libpng-1.5.17-apng.patch.gz === Patching for png-1.5.17 === Applying extra patch /usr/ports/graphics/png/work/libpng-1.5.17/libpng-1.5.17-apng.patch === Applying FreeBSD patches for png-1.5.17 /usr/bin/sed -i.bak -e 's|RELEASE}.0|RELEASE}|' -e 's|LIBDIR}/pkgconfig|LIBDIR}data/pkgconfig|' /usr/ports/graphics/png/work/libpng-1.5.17/CMakeLists.txt === png-1.5.17 depends on file: /usr/local/bin/cmake - found === Configuring for png-1.5.17 === Performing in-source build /bin/mkdir -p /usr/ports/graphics/png/work/libpng-1.5.17 -- The C compiler identification is GNU 4.2.1 ... snip ... [100%] Built target pngvalid /usr/local/bin/cmake -E cmake_progress_start /usr/ports/graphics/png/work/libpng-1.5.17/CMakeFiles 0 Running tests... /usr/local/bin/ctest --force-new-ctest-process Test project /usr/ports/graphics/png/work/libpng-1.5.17 Start 1: pngtest 1/2 Test #1: pngtest .. Passed0.02 sec Start 2: pngvalid 2/2 Test #2: pngvalid . Passed 43.20 sec 100% tests passed, 0 tests failed out of 2 Total Test time (real) = 43.23 sec === Installing for png-1.5.17 === Generating temporary packing list === Checking if graphics/png already installed === png-1.5.17 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of graphics/png without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** [check-already-installed] Error code 1 Stop in /usr/ports/graphics/png. *** [lib-depends] Error code 1 Stop in /usr/ports/graphics/jbig2dec. ___ 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
c++11 question: clang++ 3.3 future header not found
% uname -a
FreeBSD cobalt 9.2-RC3 FreeBSD 9.2-RC3 #0 r254795: Sat Aug 24 20:25:04 UTC 2013
r...@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
% clang++ --version
FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
Target: x86_64-unknown-freebsd9.2
Thread model: posix
test program
#include iostream
#include future
int main( int argc, char* argv[])
{
auto f = std::async( [] () {
std::cout Hello, World! std::endl;
});
f.wait();
return 0;
}
error received is
% clang++ -otest test.cc
test.cc:2:10: fatal error: 'future' file not found
#include future
^
1 error generated.
I guess clang is re-using system headers which belong to older gcc 4.2
I also have gcc48 installed, how can I make clang to refer gcc48 headers?
___
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: c++11 question: clang++ 3.3 future header not found
list, please pardon
my stupid mail client hung, giving me impression that e-mail was not sent.
apologies for spam.
- Original Message -
From: Quark unixuser2000-f...@yahoo.com
To: freebsd-questions@freebsd.org freebsd-questions@freebsd.org
Cc:
Sent: Tuesday, 27 August 2013 12:52 PM
Subject: c++11 question: clang++ 3.3 future header not found
% uname -a
FreeBSD cobalt 9.2-RC3 FreeBSD 9.2-RC3 #0 r254795: Sat Aug 24 20:25:04 UTC
2013
r...@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
% clang++ --version
FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
Target: x86_64-unknown-freebsd9.2
Thread model: posix
test program
#include iostream
#include future
int main( int argc, char* argv[])
{
auto f = std::async( [] () {
std::cout Hello, World!
std::endl;
});
f.wait();
return 0;
}
error received is
% clang++ -otest test.cc
test.cc:2:10: fatal error: 'future' file not found
#include future
^
1 error generated.
I guess clang is re-using system headers which belong to older gcc 4.2
I also have gcc48 installed, how can I make clang to refer gcc48 headers?
___
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
___
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: c++11 question: clang++ 3.3 future header not found
On Tue, 27 Aug 2013 15:22:49 +0800 (SGT) Quark wrote:
% uname -a
FreeBSD cobalt 9.2-RC3 FreeBSD 9.2-RC3 #0 r254795: Sat Aug 24 20:25:04 UTC
2013 r...@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
% clang++ --version
FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
Target: x86_64-unknown-freebsd9.2
Thread model: posix
test program
#include iostream
#include future
int main( int argc, char* argv[])
{
auto f = std::async( [] () {
std::cout Hello, World! std::endl;
});
f.wait();
return 0;
}
error received is
% clang++ -otest test.cc
test.cc:2:10: fatal error: 'future' file not found
#include future
^
1 error generated.
I guess clang is re-using system headers which belong to older gcc 4.2
I also have gcc48 installed, how can I make clang to refer gcc48 headers?
There two C++ runtime libraries, the old gcc libstdc++ which is used by
default and the new C++11 libc++. You can use the latter like this:
clang++ -std=c++11 -stdlib=libc++ -otest test.cc
signature.asc
Description: PGP signature
Fwd: c++11 question: clang++ 3.3 future header not found
AFAIK, the easiest way to get C++11 support in clang is to use libc++ (see
http://blogs.freebsdish.org/theraven/2013/01/03/the-new-c-stack-in-9-1/).
See also
https://lists.freebsd.org/pipermail/freebsd-toolchain/2013-May/000841.html .
2013/8/27 Quark unixuser2000-f...@yahoo.com
% uname -a
FreeBSD cobalt 9.2-RC3 FreeBSD 9.2-RC3 #0 r254795: Sat Aug 24 20:25:04 UTC
2013 r...@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
% clang++ --version
FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
Target: x86_64-unknown-freebsd9.2
Thread model: posix
test program
#include iostream
#include future
int main( int argc, char* argv[])
{
auto f = std::async( [] () {
std::cout Hello, World! std::endl;
});
f.wait();
return 0;
}
error received is
% clang++ -otest test.cc
test.cc:2:10: fatal error: 'future' file not found
#include future
^
1 error generated.
I guess clang is re-using system headers which belong to older gcc 4.2
I also have gcc48 installed, how can I make clang to refer gcc48 headers?
___
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
___
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: c++11 question: clang++ 3.3 future header not found
- Original Message -
From: Tijl Coosemans t...@coosemans.org
To: Quark unixuser2000-f...@yahoo.com
Cc: freebsd-questions@freebsd.org freebsd-questions@freebsd.org
Sent: Tuesday, 27 August 2013 1:41 PM
Subject: Re: c++11 question: clang++ 3.3 future header not found
On Tue, 27 Aug 2013 15:22:49 +0800 (SGT) Quark wrote:
% uname -a
FreeBSD cobalt 9.2-RC3 FreeBSD 9.2-RC3 #0 r254795: Sat Aug 24 20:25:04 UTC
2013 r...@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
% clang++ --version
FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
Target: x86_64-unknown-freebsd9.2
Thread model: posix
test program
#include iostream
#include future
int main( int argc, char* argv[])
{
auto f = std::async( [] () {
std::cout Hello, World!
std::endl;
});
f.wait();
return 0;
}
error received is
% clang++ -otest test.cc
test.cc:2:10: fatal error: 'future' file not found
#include future
^
1 error generated.
I guess clang is re-using system headers which belong to older gcc 4.2
I also have gcc48 installed, how can I make clang to refer gcc48 headers?
There two C++ runtime libraries, the old gcc libstdc++ which is used by
default and the new C++11 libc++. You can use the latter like this:
clang++ -std=c++11 -stdlib=libc++ -otest test.cc
thanks, it worked.
___
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
supported cdrom not found by 8.4 setup
i'm trying to install 8.4 on a thinkpad x230, which uses a usb cdrom. according to the hardward docs, 8.4 supports teac cd-210pu. that is what i am using. the box boots up fine from the installation cd. but when it comes to choosing an installation medium, the system doesn't find the device. idea, anyone? thx. david coder ___ 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
question, following error Shared object libc.so.6 not found, required by fortune
I was trying to use the content management system for our website. I needed to restart on terminal but I keep coming up with the following error: I don't know programing at all, so don't know if this is something I can fix. Shared object libc.so.6 not found, required by fortune Neither the JAVA_HOME nor the JRE_HOME environment variable is defined At least one of these environment variable is needed to run this program root@psumc:/usr/local/tomcat5.5 # bin/startup.sh Neither the JAVA_HOME nor the JRE_HOME environment variable is defined At least one of these environment variable is needed to run this program root@psumc:/usr/local/tomcat5.5 # su -c 'killall -9 java' ___ 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: question, following error Shared object libc.so.6 not found, required by fortune
On Sat, 29 Jun 2013 10:48:38 -0400, Rev Herbert Miller wrote: I was trying to use the content management system for our website. I needed to restart on terminal but I keep coming up with the following error: I don't know programing at all, so don't know if this is something I can fix. In worst case, notify your system administrator. Shared object libc.so.6 not found, required by fortune This kind of error often indicates an incomplete system update were libraries are out of date or missing. What way of system update has been performed? root@psumc:/usr/local/tomcat5.5 # bin/startup.sh Neither the JAVA_HOME nor the JRE_HOME environment variable is defined At least one of these environment variable is needed to run this program That can be a side effect, maybe some accidentally overwritten configuration file or a program that's unable to run due to a missing dependency? What happens if you manually define those variables to the proper valies and try again, e. g. # setenv JAVA_HOME=/usr/local/where your JAVA stuff is # setenv JRE_HOME=/usr/local/where your runtime lives # bin/startup,sh Does this produce a different result? root@psumc:/usr/local/tomcat5.5 # su -c 'killall -9 java' That command doesn't make sense. The prompt indicates that you are already root. The -c parameter for the su command is missing an argument, the class. See man su for details, no programming knowledge required. ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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
Pkg in FreeBSD 9.1 release, file not found
Hi guys! :)
I put in .cshrc:
setenv PACKAGESITE
ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9-stable/Latest;
and afterwards #pkg_add -r pkg to use pkg
But currently i can not use pkg :(, but i remember that few days ago i
was using I used pkg to update and install some binary package, but
today I can not use pkg.
today when i put pkg update:
pkg:
ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9-stable/Latest//repo.txz:File
unavailable (e.g., file not found, no access)
currently i have:
#~pkg info pkg
pkg-1.0.1 New generation manager
I copy the file pkg.conf.sample to /usr/local/etc/pkg.conf
#less /usr/local/etc/pkg.conf
[...]
#Configuraton options
PACKAGESITE:http://pkg.freebsd.org/${ABI}/Latest
[...]
But it does not works :(, help me please :(, thanks in advice for you reply
--
UNIX is basically a simple operating system,
but you have to be a genius to understand the simplicity.
-- Dennis M. Ritchie
Mis bits:
http://bitsenlared.wordpress.com
Live free or die!
___
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
LaTeX Error: File `utf8x.def' not found
List, I installed ``latex`` from packages. That part worked. When using latex however, it gives me an error:: LaTeX Error: File `utf8x.def' not found. Where do I get this file? Obviously I'm missing some package of extras or something. Google reveals linux users solving this problem by installing ``unicode-tex``, but I didn't find a ``unicode-tex`` package in the FreeBSD packages list on ftp.freebsd.org. Any pointers? I'm using this with Sphinx on FreeBSD 8.3-RELEASE if that matters. Thanks! -Modulok- ___ 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: LaTeX Error: File `utf8x.def' not found
On Sun, 20 Jan 2013 19:35:31 -0700, Modulok wrote:
List,
I installed ``latex`` from packages. That part worked. When using latex
however, it gives me an error::
LaTeX Error: File `utf8x.def' not found.
Where do I get this file? Obviously I'm missing some package of extras or
something.
In your LaTeX source file, you have \usepackage[utf8x]{inputenc}
somewhere, and you're using UTF-8 characters for whatever reason.
You need to install the port latex-ucs (in the print category)
to make this work. I assume there's also a package for this.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
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: LaTeX Error: File `utf8x.def' not found
In your LaTeX source file, you have \usepackage[utf8x]{inputenc}
somewhere, and you're using UTF-8 characters for whatever reason.
You need to install the port latex-ucs (in the print category)
to make this work. I assume there's also a package for this.
Hmmm. LaTeX is called by sphinx to render some math in my python docs, so I'm
not sure where the utf-8 reference occurs, probably somewhere in the sphinx
framework.
I tried to install latex-ucs as suggested, which itself worked, but some of its
dependents didn't (output shown below). Also, why is teTeX a dependency? I
thought it was no longer maintained?
Thanks!
-Modulok-
Command output shown below:
# pkg_add -r latex-ucs
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/Latest/latex-ucs.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/printproto-1.0.5.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libwww-5.4.0_4.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/tex-texmflocal-1.9.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/font-amsfonts-3.02_1.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/teTeX-texmf-3.0_8.tbz...
Done.
pkg_add: package 'teTeX-texmf-3.0_8' conflicts with latex2e-2003.12_1
pkg_add: package 'teTeX-texmf-3.0_8' conflicts with tex-3.14159_3
pkg_add: please use pkg_delete first to remove conflicting package(s)
or -f to force installation
pkg_add: pkg_add of dependency 'teTeX-texmf-3.0_8' failed!
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/texi2html-1.82,1.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/gd-2.0.35_7,1.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libXext-1.3.0_1,1.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libXp-1.0.1,1.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libXt-1.0.9,1.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libXmu-1.1.0,1.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libXpm-3.5.9.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libXaw-1.0.8,2.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/t1lib-5.1.2_1,1.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/ghostscript9-9.05_3.tbz...
Done.
pkg_add: package 'ghostscript9-9.05_3' conflicts with ghostscript9-nox11-9.05_3
pkg_add: please use pkg_delete first to remove conflicting package(s)
or -f to force installation
pkg_add: pkg_add of dependency 'ghostscript9-9.05_3' failed!
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/teTeX-base-3.0_22.tbz...
Done.
pkg_add: package 'teTeX-base-3.0_22' conflicts with latex2e-2003.12_1
pkg_add: package 'teTeX-base-3.0_22' conflicts with tex-3.14159_3
pkg_add: please use pkg_delete first to remove conflicting package(s)
or -f to force installation
pkg_add: pkg_add of dependency 'teTeX-base-3.0_22' failed!
___
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: LaTeX Error: File `utf8x.def' not found
On Sun, 20 Jan 2013 23:17:22 -0700, Modulok wrote:
In your LaTeX source file, you have \usepackage[utf8x]{inputenc}
somewhere, and you're using UTF-8 characters for whatever reason.
You need to install the port latex-ucs (in the print category)
to make this work. I assume there's also a package for this.
Hmmm. LaTeX is called by sphinx to render some math in my python docs, so I'm
not sure where the utf-8 reference occurs, probably somewhere in the sphinx
framework.
I assume it uses UTF-8 as input language for widest portability.
You could check some intermediate LaTeX source file for occurances
of \usepackage[utf8x]{inputenc} or check if there are some UTF-8
characters present in input.
I tried to install latex-ucs as suggested, which itself worked, but some of
its
dependents didn't (output shown below).
Maybe those specific dependencies aren't needed? Does the result
work?
As I understand from the error messages, you've been installing
LaTeX components manually or by TeXLive, whereas teTeX is a
package of lots of related LaTeX stuff.
You can see from this example list that some additional software
relies on teTeX, as you can judge from their names:
teTeX-3.0_5
teTeX-base-3.0_22
teTeX-texmf-3.0_8
dvipsk-tetex-5.95a_5
ifxetex-20090124_3
latex-cjk-4.8.2_5
latex-ucs-20041017_5
teTeX-texmf-3.0_8
tex-texmflocal-1.9
xdvik-tetex-22.84.16_3
On a system maintained via the TeXLive installer, this might look
different.
Also, why is teTeX a dependency? I
thought it was no longer maintained?
I'm still using teTeX here, but TeXLive is recommended today.
It seems that still some ports define teTeX as the LaTeX
dependency, as there is no means to specify _which_ LaTeX
to use (the one that is installed, or via some option like
WITH_TETEX or WITH_TEXLIVE).
Command output shown below:
# pkg_add -r latex-ucs
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/Latest/latex-ucs.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/printproto-1.0.5.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libwww-5.4.0_4.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/tex-texmflocal-1.9.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/font-amsfonts-3.02_1.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/teTeX-texmf-3.0_8.tbz...
Done.
pkg_add: package 'teTeX-texmf-3.0_8' conflicts with latex2e-2003.12_1
pkg_add: package 'teTeX-texmf-3.0_8' conflicts with tex-3.14159_3
pkg_add: please use pkg_delete first to remove conflicting package(s)
or -f to force installation
pkg_add: pkg_add of dependency 'teTeX-texmf-3.0_8' failed!
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/texi2html-1.82,1.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/gd-2.0.35_7,1.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libXext-1.3.0_1,1.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libXp-1.0.1,1.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libXt-1.0.9,1.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libXmu-1.1.0,1.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libXpm-3.5.9.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libXaw-1.0.8,2.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/t1lib-5.1.2_1,1.tbz...
Done.
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/ghostscript9-9.05_3.tbz...
Done.
pkg_add: package 'ghostscript9-9.05_3' conflicts with
ghostscript9-nox11-9.05_3
pkg_add: please use pkg_delete first to remove conflicting package(s)
or -f to force installation
pkg_add: pkg_add of dependency 'ghostscript9-9.05_3' failed!
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/teTeX-base-3.0_22.tbz...
Done.
pkg_add: package 'teTeX-base-3.0_22' conflicts with latex2e-2003.12_1
pkg_add: package 'teTeX-base-3.0_22' conflicts with tex-3.14159_3
pkg_add: please use pkg_delete first to remove conflicting package(s)
or -f to force installation
pkg_add: pkg_add of dependency 'teTeX-base-3.0_22' failed!
Seems that latex-ucs has some back-reference on teTeX (the
LaTeX dependency) and also to ghostscript. In worst case, why
not simply install teTeX and see if it does everything you need?
I know there are things that don't work in teTeX (but do in
TeXLive), but I've not encountered one
make print-index error: Generating INDEX-9 - please wait..perl: not found
I've done a clean install of FBSD 9, installed subversion from package, and then I have: svn co svn://svn.freebsd.org/ports/head/ /usr/ports svn co svn://svn.freebsd.org/base/releng/9.1 /usr/src svn co svn://svn.freebsd.org/doc/release/9.1.0/en_US.ISO8859-1 /usr/doc which all went just fine. Then I: cd /usr/ports make print-index and this is my result: Generating INDEX-9 - please wait..perl: not found Makefile, line 31: warning: perl -V:archname returned non-zero status perl: not found Done. O.K., I'm stumped...what's wrong? Ed ___ 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: make print-index error: Generating INDEX-9 - please wait..perl: not found
On 28/09/2012 21:27, Ed Flecko wrote: Generating INDEX-9 - please wait..perl: not found Makefile, line 31: warning: perl -V:archname returned non-zero status perl: not found Done. O.K., I'm stumped...what's wrong? You need to install perl in order to build an INDEX from scratch. That's true if you use the default 'make index' target or my p5-FreeBSD-Portindex code. Building an INDEX is a fairly time consuming task, and honestly, most people don't need to do it. You can download a pre-built INDEX by 'make fetchindex' which will be perfectly adequate for the vast majority of users. What you don't get by using the pre-built INDEX is the effect of any local customizations or options settings. This means that the INDEX may disagree in detail about exactly what dependencies some ports have. However, the INDEX is not used as part of actually building anything, so those discrepancies are mere annoyances rather than real obstacles. And, indeed, you can build and install ports very happily without any sort of INDEX on your system at all. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Cannot --enable-pcretest-libedit because libedit library was not found
8.2-RELEASE FreeBSD 8.2-RELEASE #0 with current portsnap mtr, postfix-current, pcre all fail to install with error: ** Cannot --enable-pcretest-libedit because libedit library was not found. === Script configure failed unexpectedly. Please report the problem to m...@freebsd.org [maintainer] and attach the /usr/ports/devel/pcre/work/pcre-8.30/config.log including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. an `ls /var/db/pkg`). *** Error code 1 thanks Len ___ 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: Cannot --enable-pcretest-libedit because libedit library was not found
On 20/05/2012 17:22, Len Conrad wrote: 8.2-RELEASE FreeBSD 8.2-RELEASE #0 with current portsnap mtr, postfix-current, pcre all fail to install with error: ** Cannot --enable-pcretest-libedit because libedit library was not found. === Script configure failed unexpectedly. Please report the problem to m...@freebsd.org [maintainer] and attach the /usr/ports/devel/pcre/work/pcre-8.30/config.log including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. an `ls /var/db/pkg`). *** Error code 1 So why are you posting this somewhat thin report here rather than following the quite clear and simple instructions printed in that error message? Quite apart from anything else, the config.log that was mentioned is going to be necessary for anyone to work out what went wrong. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Ports Libraries - Shared object libz.so.5 not found
I'm on 9.0 Release AMD64 and did not have Compat8x installed from ports which fixed the issue, but I am wondering what (apart from upgrading *all* ports) would be the correct approach to find out which port needs to be updated so that whatever references the libz.so.5 version instead of libz.so.6 gets updated? This is very confusing to me because I got the error with php, and I am on the very latest php5-5.3.10_1 version which I would expect to reference current libraries. Now I also have a problem with libssl.so.7, which popped up with Samba36. Again I'm wondering what version provides the .7 incarnation. I found a comment (http://forums.freebsd.org/showthread.php?t=21886) that this library is part of security/openssl but a reinstall just now of openssl only gave me libssl.so.8, so that's no longer valid. Creating a link to libssl.so.7 fixes the problem but is probably not the correct approach. I guess the summary of the above is the question how one should go about keeping/getting the right library versions. Or is that really a port problem because they do not keep step with dependencies? An explanation in layman's terms would be appreciated :-) Thanks, Caro ___ 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: Ports Libraries - Shared object libz.so.5 not found
On 24.04.2012 10:07, Carolyn Longfoot wrote: I'm on 9.0 Release AMD64 and did not have Compat8x installed from ports which fixed the issue, but I am wondering what (apart from upgrading *all* ports) would be the correct approach to find out which port needs to be updated so that whatever references the libz.so.5 version instead of libz.so.6 gets updated? This is very confusing to me because I got the error with php, and I am on the very latest php5-5.3.10_1 version which I would expect to reference current libraries. Now I also have a problem with libssl.so.7, which popped up with Samba36. Again I'm wondering what version provides the .7 incarnation. I found a comment (http://forums.freebsd.org/showthread.php?t=21886) that this library is part of security/openssl but a reinstall just now of openssl only gave me libssl.so.8, so that's no longer valid. Creating a link to libssl.so.7 fixes the problem but is probably not the correct approach. I guess the summary of the above is the question how one should go about keeping/getting the right library versions. Or is that really a port problem because they do not keep step with dependencies? An explanation in layman's terms would be appreciated :-) Thanks, Caro ___ 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 pkg_libchk from the sysutils/bsdadminscripts port should show you anything that is pointing to a missing shared library. Yes you should rebuild the samba36 port so that it links against the new libssl.so.8 library. I ran into a few of these when upgrading from openssl-1.0.0_10 to openssl-1.0.1, I also believe I hit the libcrypto.so.7 missing as well. I temporary linked them as you did, then rebuilt all ports just to be safe. if you use portmaster to update ports, doing a -r on the openssl port would have recompiled all the ports dependent on it. However in my case it blew up because of these missing libraries, adding a -w (causes shared libraries to be kept) as well resolved this on the additional machines I updated. -- Thanks, Dean E. Weimer dwei...@dweimer.net http://www.dweimer.net/ ___ 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: Ports Libraries - Shared object libz.so.5 not found
ls -l /lib/libz* lrwxr-xr-x 1 root wheel9 4 22 09:00 /lib/libz.so.5@ - libz.so.6 When i installed wine, it reported the same error which is fixed simply by a symbolic link. - e^(π.i) + 1 = 0 -- View this message in context: http://freebsd.1045724.n5.nabble.com/Ports-Libraries-Shared-object-libz-so-5-not-found-tp5662329p5663803.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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
lost+found dir placement
Hi, Each fs should have its own lost+found directory. It is used by fsck for placing recovered corrupted fs files in there. This implies the dir must have already existed (it may not be mounted ad hoc e.g. at boot time, during fs recovery). In FreeBSD 9, I found lost+found dir under /mnt. This is incorrect - /mnt is defined under all standards (Filesystem Hierarchy Standard, Unix directory structure) as contains filesystem mount points. So, lost+found dir should exist under root dir as /lost+found. Any comments before I file a PR request ? jb ___ 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: lost+found dir placement
On Tue, Mar 13, 2012 at 2:58 AM, jb jb.1234a...@gmail.com wrote: Hi, Each fs should have its own lost+found directory. It is used by fsck for placing recovered corrupted fs files in there. This implies the dir must have already existed (it may not be mounted ad hoc e.g. at boot time, during fs recovery). In FreeBSD 9, I found lost+found dir under /mnt. This is incorrect - /mnt is defined under all standards (Filesystem Hierarchy Standard, Unix directory structure) as contains filesystem mount points. So, lost+found dir should exist under root dir as /lost+found. Any comments before I file a PR request ? jb The directory is created in the top of the filesystem, so you should check what is mounted on /mnt. Filesystem Hierarchy Standard -- This is a Linux standard. For info on FreeBSD hierarchy see man hier(7) -- Adam Vande More ___ 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: lost+found dir placement
On Tue, 13 Mar 2012 07:58:09 + (UTC), jb wrote: Hi, Each fs should have its own lost+found directory. It is used by fsck for placing recovered corrupted fs files in there. Correct. This implies the dir must have already existed (it may not be mounted ad hoc e.g. at boot time, during fs recovery). No. This implication does not exist. If I read /usr/src/sbin/fsck_ffs/dir.c correctly, the lost+found/ directory will be created by fsck if it is required and _not_ present. It will do so on a inode based method (instead of utilizing a file system oriented call to make a directory). This is a requirement because (as you correctly mentioned) the partition checked will not be writable (or even be mounted), so mkdir() and related fs functions cannot be used. Also see an evidence for that idea in man fsck_ffs. In FreeBSD 9, I found lost+found dir under /mnt. This is incorrect - /mnt is defined under all standards (Filesystem Hierarchy Standard, Unix directory structure) as contains filesystem mount points. According to man hier (mandatory for interpreting the file system hierarchy on FreeBSD) this your assumption sounds correct: /mnt is explained to be an empty directory commonly used by system administrators as a temporary mount point, so having a lost+found/ directory in there doesn't seem to have any purpose and looks wrong. So, lost+found dir should exist under root dir as /lost+found. Correct. It will be assigned to the results of possible recoveries of lost data of the / partition correctly. Any comments before I file a PR request ? If this directory has been created by the installation process, I think you should. Maybe you verify the issue on the freebsd-fs@ list? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: lost+found dir placement
jb jb.1234a...@gmail.com wrote: Hi, Each fs should have its own lost+found directory. It is used by fsck for placing recovered corrupted fs files in there. This implies the dir must have already existed (it may not be mounted ad hoc e.g. at boot time, during fs recovery). In FreeBSD 9, I found lost+found dir under /mnt. This is incorrect - /mnt is defined under all standards (Filesystem Hierarchy Standard, Unix directory structure) as contains filesystem mount points. So, lost+found dir should exist under root dir as /lost+found. Do you have a filesystem mounted on /mnt? Any comments before I file a PR request ? The fsck_ffs manpage says that 'lost+found' is _created_ *when*needed*, in the root of a filesystem, if not already present. The presense of /mnt/lost+found is _not_ an error. just a surperfluous file that ended up there 'somehow'. *IF* you're going to file a PR, it should be for the filesystem initialization process -- which should (a) create the lost+found directory, (b) create some 'reasonable' number of files in that directory, and (c) then delete all those files. This ensures that the directory exists and has disk-space allocated for a 'reasonable' number of 'recovered' file entries. The existing fsck_ffs has a catastrophic failure mode if there is no space on the disk for the lost+found directory to grow to acomodate the recovered file entries. ___ 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: /lib/exec/ld-elf.so.1: Shared object libpcre.so.0 not found, required by libxfsm-4.6.so.0 amd64 FreeBSD 8.2
On Thu, Feb 16, 2012 at 9:08 AM, Antonio Olivares olivares14...@gmail.com wrote: On Thu, Feb 16, 2012 at 8:18 AM, Ryan Frederick ryanrfreder...@gmail.com wrote: It looks like others have run into this problem with avahi-app as well: http://lists.freebsd.org/pipermail/freebsd-ports/2011-July/068658.html A cursory search shows that uninstalling avahi-app then reinstalling should take care of the compilation failure. Afterward you should be able to run portmaster as shown in the error message (minus 'net/avahi-app') to finish recompiling the ports that depend on pcre. Ryan This does make the desktop work again :) I followed the advice and am back in the saddle. Some things failed to compile, but I used -x parameter to not update them. I will track those ports later. I appreciate the help and advice provided. It appears that a new pcre update hits the ports later. I wonder if it bypasses the original problem. Regards, Antonio ___ 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: /lib/exec/ld-elf.so.1: Shared object libpcre.so.0 not found, required by libxfsm-4.6.so.0 amd64 FreeBSD 8.2
On Thu, 16 Feb 2012 09:08:54 -0600 Antonio Olivares wrote: On Thu, Feb 16, 2012 at 8:18 AM, Ryan Frederick ryanrfreder...@gmail.com wrote: It looks like others have run into this problem with avahi-app as well: http://lists.freebsd.org/pipermail/freebsd-ports/2011-July/068658.html A cursory search shows that uninstalling avahi-app then reinstalling should take care of the compilation failure. Afterward you should be able to run portmaster as shown in the error message (minus 'net/avahi-app') to finish recompiling the ports that depend on pcre. Thanks Ryan when I get home tonight, I will remove avahi-app and reinstall it and then recompile all the ports that depend on pcre. I ran into this problem yesterday and removing avahi-ap didn't fix it for me. In the end I identified some orphaned libraries under /usr/local/ and deleting those fixed the problem. ___ 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: /lib/exec/ld-elf.so.1: Shared object libpcre.so.0 not found, required by libxfsm-4.6.so.0 amd64 FreeBSD 8.2
It looks like others have run into this problem with avahi-app as well:
http://lists.freebsd.org/pipermail/freebsd-ports/2011-July/068658.html
A cursory search shows that uninstalling avahi-app then reinstalling
should take care of the compilation failure. Afterward you should be
able to run portmaster as shown in the error message (minus
'net/avahi-app') to finish recompiling the ports that depend on pcre.
Ryan
On 02/15/2012 10:55 PM, Antonio Olivares wrote:
On Wed, Feb 15, 2012 at 9:33 PM, Robert Bonomibon...@mail.r-bonomi.com wrote:
Antonio Olivaresolivares14...@gmail.com wrote;
I am doing this and see how it goes. I used ldd to check for
libprce.so and I got :
ldd /usr/local/lib/libprce.so:
libc.so.7 = /lib/libc.so.7 (0x800647000)
ldd /usr/local/lib/libprce.so.1:
libc.so.7 = /lib/libc.so.7 (0x800647000)
There are two of them :( Should there be only one?
This is _normal_. The .so (with no further sufix), is generally just a link
to the 'latest' .so *with* a numeric suffix.
I am in a not good state now. I broke two machines by updating to
latest and get the same error on both machines.
I get the /libexec/ld-elf.so.1: Shared object libpcre.so.0 is needed
by * and nothing works, I run
# portmaster -r pcre-8.30
and it bombs out with the following:
signals-marshal.c:186: warning: ISO C forbids conversion of object
pointer to function pointer type
CC libavahi_gobject_la-ga-client-enumtypes.lo
CC libavahi_gobject_la-ga-entry-group-enumtypes.lo
CC libavahi_gobject_la-ga-enums-enumtypes.lo
CCLD libavahi-gobject.la
GISCAN Avahi-0.6.gir
g-ir-scanner: warning: Option --strip-prefix has been deprecated;
see --identifier-prefix and --symbol-prefix.
/usr/include/machine/endian.h:123: syntax error, unexpected '{' in '
return (__extension__ ({ register __uint64_t __X = (_x); __asm (bswap
%0 : +r (__X)); __X; }));' at '{'
/usr/include/machine/endian.h:123: syntax error, unexpected ';' in '
return (__extension__ ({ register __uint64_t __X = (_x); __asm (bswap
%0 : +r (__X)); __X; }));' at ';'
/usr/include/machine/endian.h:130: syntax error, unexpected '{' in '
return (__extension__ ({ register __uint32_t __X = (_x); __asm (bswap
%0 : +r (__X)); __X; }));' at '{'
/usr/include/machine/endian.h:130: syntax error, unexpected ';' in '
return (__extension__ ({ register __uint32_t __X = (_x); __asm (bswap
%0 : +r (__X)); __X; }));' at ';'
/libexec/ld-elf.so.1: Shared object libpcre.so.0 not found, required
by libavahi-glib.so.1
Command
'['/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject/tmp-introspectGYNEXM/Avahi-0.6',
'--introspect-dump=/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject/tmp-introspectGYNEXM/types.txt,/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject/tmp-introspectGYNEXM/dump.xml']'
returned non-zero exit status 1
gmake[3]: *** [Avahi-0.6.gir] Error 1
gmake[3]: Leaving directory
`/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory
`/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/ports/net/avahi-app/work/avahi-0.6.29'
gmake: *** [all] Error 2
*** Error code 1
Stop in /usr/ports/net/avahi-app.
=== make failed for net/avahi-app
=== Aborting update
=== Update for avahi-app-0.6.29_1 failed
=== Aborting update
=== Update for gvfs-1.6.6_2 failed
=== Aborting update
=== Update for Thunar-1.3.0 failed
=== Aborting update
Terminated
=== There are messages from installed ports to display,
but first take a moment to review the error messages
above. Then press Enter when ready to proceed.
=== pkg-message for gamin-0.1.10_4
===
Gamin will only provide realtime notification of changes for at most n files,
where n is the minimum value between (kern.maxfiles * 0.7) and
(kern.maxfilesperproc - 200). Beyond that limit, files will be polled.
If you often open several large folders with Nautilus, you might want to
increase the kern.maxfiles tunable (you do not need to set
kern.maxfilesperproc, since it is computed at boot time from kern.maxfiles).
For a typical desktop, add the following line to /boot/loader.conf, then
reboot the system:
kern.maxfiles=25000
The behavior of gamin can be controlled via the various gaminrc files.
See http://www.gnome.org/~veillard/gamin/config.html on how to create
these files. In particular, if you find gam_server is taking up too much
CPU time polling for changes, something like the following may help
in one of the gaminrc files:
# reduce polling frequency to once per 10 seconds
# for UFS file systems in order to lower CPU load
fsset ufs poll 10
===
=== pkg-message for liblqr-1-0.4.1_2
Re: /lib/exec/ld-elf.so.1: Shared object libpcre.so.0 not found, required by libxfsm-4.6.so.0 amd64 FreeBSD 8.2
On Thu, Feb 16, 2012 at 8:18 AM, Ryan Frederick ryanrfreder...@gmail.com wrote: It looks like others have run into this problem with avahi-app as well: http://lists.freebsd.org/pipermail/freebsd-ports/2011-July/068658.html A cursory search shows that uninstalling avahi-app then reinstalling should take care of the compilation failure. Afterward you should be able to run portmaster as shown in the error message (minus 'net/avahi-app') to finish recompiling the ports that depend on pcre. Ryan Thanks Ryan when I get home tonight, I will remove avahi-app and reinstall it and then recompile all the ports that depend on pcre. Then if successfull hopefully, I will report back. Thanks for your help guidance. Regards, Antonio ___ 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
/lib/exec/ld-elf.so.1: Shared object libpcre.so.0 not found, required by libxfsm-4.6.so.0 amd64 FreeBSD 8.2
Dear folks, I updated ports and one failed, gimp-app. I checked /usr/src/UPDATING and I followed advice there to run # portmaster -w devel/pcre and I did this, and now machine won't get X. How can I bypass this mistake? I am now hesitant to update the other machines :(, I will get into problems starting X because of some update of a certain lib. Any thoughts, ideas or suggestions? Regards, Antonio ___ 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: /lib/exec/ld-elf.so.1: Shared object libpcre.so.0 not found, required by libxfsm-4.6.so.0 amd64 FreeBSD 8.2
You can recompile all ports that depend on pcre so that they'll use the new shared library. You can do so with: # portmaster -r pcre-8.30 Ryan On 02/15/2012 08:42 PM, Antonio Olivares wrote: Dear folks, I updated ports and one failed, gimp-app. I checked /usr/src/UPDATING and I followed advice there to run # portmaster -w devel/pcre and I did this, and now machine won't get X. How can I bypass this mistake? I am now hesitant to update the other machines :(, I will get into problems starting X because of some update of a certain lib. Any thoughts, ideas or suggestions? Regards, Antonio ___ 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 ___ 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: /lib/exec/ld-elf.so.1: Shared object libpcre.so.0 not found, required by libxfsm-4.6.so.0 amd64 FreeBSD 8.2
You can recompile all ports that depend on pcre so that they'll use the new shared library. You can do so with: # portmaster -r pcre-8.30 Ryan On 02/15/2012 08:42 PM, Antonio Olivares wrote: Dear folks, I updated ports and one failed, gimp-app. I checked /usr/src/UPDATING and I followed advice there to run # portmaster -w devel/pcre and I did this, and now machine won't get X. How can I bypass this mistake? I am now hesitant to update the other machines :(, I will get into problems starting X because of some update of a certain lib. Any thoughts, ideas or suggestions? Regards, Antonio ___ I am doing this and see how it goes. I used ldd to check for libprce.so and I got : ldd /usr/local/lib/libprce.so: libc.so.7 = /lib/libc.so.7 (0x800647000) ldd /usr/local/lib/libprce.so.1: libc.so.7 = /lib/libc.so.7 (0x800647000) There are two of them :( Should there be only one? Thanks for your advice. Regards, Antonio ___ 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: /lib/exec/ld-elf.so.1: Shared object libpcre.so.0 not found, required by libxfsm-4.6.so.0 amd64 FreeBSD 8.2
Antonio Olivares olivares14...@gmail.com wrote; I am doing this and see how it goes. I used ldd to check for libprce.so and I got : ldd /usr/local/lib/libprce.so: libc.so.7 = /lib/libc.so.7 (0x800647000) ldd /usr/local/lib/libprce.so.1: libc.so.7 = /lib/libc.so.7 (0x800647000) There are two of them :( Should there be only one? This is _normal_. The .so (with no further sufix), is generally just a link to the 'latest' .so *with* a numeric suffix. ___ 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: /lib/exec/ld-elf.so.1: Shared object libpcre.so.0 not found, required by libxfsm-4.6.so.0 amd64 FreeBSD 8.2
On Wed, Feb 15, 2012 at 9:33 PM, Robert Bonomi bon...@mail.r-bonomi.com wrote:
Antonio Olivares olivares14...@gmail.com wrote;
I am doing this and see how it goes. I used ldd to check for
libprce.so and I got :
ldd /usr/local/lib/libprce.so:
libc.so.7 = /lib/libc.so.7 (0x800647000)
ldd /usr/local/lib/libprce.so.1:
libc.so.7 = /lib/libc.so.7 (0x800647000)
There are two of them :( Should there be only one?
This is _normal_. The .so (with no further sufix), is generally just a link
to the 'latest' .so *with* a numeric suffix.
I am in a not good state now. I broke two machines by updating to
latest and get the same error on both machines.
I get the /libexec/ld-elf.so.1: Shared object libpcre.so.0 is needed
by * and nothing works, I run
# portmaster -r pcre-8.30
and it bombs out with the following:
signals-marshal.c:186: warning: ISO C forbids conversion of object
pointer to function pointer type
CC libavahi_gobject_la-ga-client-enumtypes.lo
CC libavahi_gobject_la-ga-entry-group-enumtypes.lo
CC libavahi_gobject_la-ga-enums-enumtypes.lo
CCLD libavahi-gobject.la
GISCAN Avahi-0.6.gir
g-ir-scanner: warning: Option --strip-prefix has been deprecated;
see --identifier-prefix and --symbol-prefix.
/usr/include/machine/endian.h:123: syntax error, unexpected '{' in '
return (__extension__ ({ register __uint64_t __X = (_x); __asm (bswap
%0 : +r (__X)); __X; }));' at '{'
/usr/include/machine/endian.h:123: syntax error, unexpected ';' in '
return (__extension__ ({ register __uint64_t __X = (_x); __asm (bswap
%0 : +r (__X)); __X; }));' at ';'
/usr/include/machine/endian.h:130: syntax error, unexpected '{' in '
return (__extension__ ({ register __uint32_t __X = (_x); __asm (bswap
%0 : +r (__X)); __X; }));' at '{'
/usr/include/machine/endian.h:130: syntax error, unexpected ';' in '
return (__extension__ ({ register __uint32_t __X = (_x); __asm (bswap
%0 : +r (__X)); __X; }));' at ';'
/libexec/ld-elf.so.1: Shared object libpcre.so.0 not found, required
by libavahi-glib.so.1
Command
'['/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject/tmp-introspectGYNEXM/Avahi-0.6',
'--introspect-dump=/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject/tmp-introspectGYNEXM/types.txt,/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject/tmp-introspectGYNEXM/dump.xml']'
returned non-zero exit status 1
gmake[3]: *** [Avahi-0.6.gir] Error 1
gmake[3]: Leaving directory
`/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory
`/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/ports/net/avahi-app/work/avahi-0.6.29'
gmake: *** [all] Error 2
*** Error code 1
Stop in /usr/ports/net/avahi-app.
=== make failed for net/avahi-app
=== Aborting update
=== Update for avahi-app-0.6.29_1 failed
=== Aborting update
=== Update for gvfs-1.6.6_2 failed
=== Aborting update
=== Update for Thunar-1.3.0 failed
=== Aborting update
Terminated
=== There are messages from installed ports to display,
but first take a moment to review the error messages
above. Then press Enter when ready to proceed.
=== pkg-message for gamin-0.1.10_4
===
Gamin will only provide realtime notification of changes for at most n files,
where n is the minimum value between (kern.maxfiles * 0.7) and
(kern.maxfilesperproc - 200). Beyond that limit, files will be polled.
If you often open several large folders with Nautilus, you might want to
increase the kern.maxfiles tunable (you do not need to set
kern.maxfilesperproc, since it is computed at boot time from kern.maxfiles).
For a typical desktop, add the following line to /boot/loader.conf, then
reboot the system:
kern.maxfiles=25000
The behavior of gamin can be controlled via the various gaminrc files.
See http://www.gnome.org/~veillard/gamin/config.html on how to create
these files. In particular, if you find gam_server is taking up too much
CPU time polling for changes, something like the following may help
in one of the gaminrc files:
# reduce polling frequency to once per 10 seconds
# for UFS file systems in order to lower CPU load
fsset ufs poll 10
===
=== pkg-message for liblqr-1-0.4.1_2
==
NOTE: In order to compile examples for liblqr, you will
also need pngwriter port (/usr/ports/graphics/pngwriter).
Examples are located in /usr/local/share/examples/liblqr-1
==
=== Done displaying pkg-message files
=== The following actions were performed:
Re-installation of pcre-8.30
Re-installation of glib-2.28.8_4
Re-installation of gamin-0.1.10_4
Re-installation of gio-fam-backend
Re: make release custom kernel conf not found
On Mon, Jan 30, 2012 at 10:39 AM, Rick Miller vmil...@hostileadmin.com wrote: Thanks Rob... I put the kernel conf file in the source tree as opposed to linking to it and it certainly did compile the custom kernel. What confuses me (not that I expect you to have the answer) is that Chapter 9 of the handbook has a tip that recommends keeping the kernel config in /root/kernels and symlinking to it from the source tree. If it doesn't work, why is there a tip recommending this practice? I think the idea is to avoid accidentally deleting it - sometimes people who get weird build errors are told to delete /usr/src and /usr/obj, to make sure everything is in a consistent state. The symlink will work fine for normal builds, which is what the handbook covers, but the release building process installs a new copy of the base system and then runs within it, to try and ensure a completely stock environment. Any changes you made to the main system (make.conf, custom kernels, etc.) are intentionally ignored. As Lowell points out, the right way to do this is make either a patch or a script to add your changes and have the release framework apply it. Copying it in is the quick and dirty fix. -- Rob Farmer ___ 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: make release custom kernel conf not found
Thanks Rob and Lowell, I will keep this information handy. It was helpful. On Tue, Jan 31, 2012 at 4:22 AM, Rob Farmer rfar...@predatorlabs.net wrote: On Mon, Jan 30, 2012 at 10:39 AM, Rick Miller vmil...@hostileadmin.com wrote: Thanks Rob... I put the kernel conf file in the source tree as opposed to linking to it and it certainly did compile the custom kernel. What confuses me (not that I expect you to have the answer) is that Chapter 9 of the handbook has a tip that recommends keeping the kernel config in /root/kernels and symlinking to it from the source tree. If it doesn't work, why is there a tip recommending this practice? I think the idea is to avoid accidentally deleting it - sometimes people who get weird build errors are told to delete /usr/src and /usr/obj, to make sure everything is in a consistent state. The symlink will work fine for normal builds, which is what the handbook covers, but the release building process installs a new copy of the base system and then runs within it, to try and ensure a completely stock environment. Any changes you made to the main system (make.conf, custom kernels, etc.) are intentionally ignored. As Lowell points out, the right way to do this is make either a patch or a script to add your changes and have the release framework apply it. Copying it in is the quick and dirty fix. -- Rob Farmer -- Take care Rick Miller ___ 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: make release custom kernel conf not found
Thanks Rob... I put the kernel conf file in the source tree as opposed to linking to it and it certainly did compile the custom kernel. What confuses me (not that I expect you to have the answer) is that Chapter 9 of the handbook has a tip that recommends keeping the kernel config in /root/kernels and symlinking to it from the source tree. If it doesn't work, why is there a tip recommending this practice? On Sun, Jan 29, 2012 at 10:14 PM, Rob Farmer rfar...@predatorlabs.net wrote: On Sun, Jan 29, 2012 at 9:03 AM, Rick Miller vmil...@hostileadmin.com wrote: Hi All, I am performing a `make release` to build a new release with a custom kernel. The `make release` fails with the following error: cd /usr/src/release/..; make TARGET_ARCH=amd64 TARGET=amd64 KERNCONF=MYKERNEL kernel DESTDIR=/R/stage/kernels KODIR=/MYKERNEL ERROR: Missing kernel configuration file(s) (MYKERNEL). *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src/release. + umount /dev *** Error code 1 Stop in /usr/src/release. I have the kernel config at /root/kernels/MYKERNEL and /usr/src/sys/amd64/conf/MYKERNEL is a symlink to the kernel config. The applicable environment variables are set in my .profile as follows: BUILDNAME=8.2-RELEASE-MYKERNEL-1.1 CHROOTDIR=/app/release CVSROOT=/home/cvs EXTPORTSDIR=/usr/ports EXTSRCDIR=/usr/src KERNELS=GENERIC MYKERNEL MAKE_DVD=YES NODOC=YES NO_FLOPPIES=YES I am unsure how to get `make release` to realize the location of the kernel config. Also, I notice that in the command to make the kernel, DESTDIR is set to /R/stage/kernels while the CHROOTDIR (and the location where I want the release to be built) is /app/release. I am wondering if someone knows how I may resolve the issue so I can get the release built. I appreciate any advice and feedback. Thanks. The kernel is built inside the chroot, so all paths are really /app/release/whatever. Your symlink points to /app/release/root/kernels/MYKERNEL. It will be easiest to get rid of the symlink and copy the actual file into your EXTSRCDIR before starting the make release; alternately you could use the LOCAL_PATCHES or LOCAL_SCRIPT variables to import it. -- Rob Farmer -- Take care Rick Miller ___ 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: make release custom kernel conf not found
Rick Miller vmil...@hostileadmin.com writes: Thanks Rob... I put the kernel conf file in the source tree as opposed to linking to it and it certainly did compile the custom kernel. What confuses me (not that I expect you to have the answer) is that Chapter 9 of the handbook has a tip that recommends keeping the kernel config in /root/kernels and symlinking to it from the source tree. If it doesn't work, why is there a tip recommending this practice? It works fine; sounds like you just don't understand what a chroot is. Once a process is chroot'd to /app/release/, its idea of /root/kernels is what non-chroot'd processes see as /app/release/kernels. It can't see *any* files that aren't under /app/release. I would tend to recommend adding to your build script a command that copies the kernel file into the chroot before starting the chroot, but I'm sure others have other preferred approaches. - Lowell ___ 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
make release custom kernel conf not found
Hi All, I am performing a `make release` to build a new release with a custom kernel. The `make release` fails with the following error: cd /usr/src/release/..; make TARGET_ARCH=amd64 TARGET=amd64 KERNCONF=MYKERNEL kernel DESTDIR=/R/stage/kernels KODIR=/MYKERNEL ERROR: Missing kernel configuration file(s) (MYKERNEL). *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src/release. + umount /dev *** Error code 1 Stop in /usr/src/release. I have the kernel config at /root/kernels/MYKERNEL and /usr/src/sys/amd64/conf/MYKERNEL is a symlink to the kernel config. The applicable environment variables are set in my .profile as follows: BUILDNAME=8.2-RELEASE-MYKERNEL-1.1 CHROOTDIR=/app/release CVSROOT=/home/cvs EXTPORTSDIR=/usr/ports EXTSRCDIR=/usr/src KERNELS=GENERIC MYKERNEL MAKE_DVD=YES NODOC=YES NO_FLOPPIES=YES I am unsure how to get `make release` to realize the location of the kernel config. Also, I notice that in the command to make the kernel, DESTDIR is set to /R/stage/kernels while the CHROOTDIR (and the location where I want the release to be built) is /app/release. I am wondering if someone knows how I may resolve the issue so I can get the release built. I appreciate any advice and feedback. Thanks. -- Take care Rick Miller ___ 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: make release custom kernel conf not found
On Sun, Jan 29, 2012 at 9:03 AM, Rick Miller vmil...@hostileadmin.com wrote: Hi All, I am performing a `make release` to build a new release with a custom kernel. The `make release` fails with the following error: cd /usr/src/release/..; make TARGET_ARCH=amd64 TARGET=amd64 KERNCONF=MYKERNEL kernel DESTDIR=/R/stage/kernels KODIR=/MYKERNEL ERROR: Missing kernel configuration file(s) (MYKERNEL). *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src/release. + umount /dev *** Error code 1 Stop in /usr/src/release. I have the kernel config at /root/kernels/MYKERNEL and /usr/src/sys/amd64/conf/MYKERNEL is a symlink to the kernel config. The applicable environment variables are set in my .profile as follows: BUILDNAME=8.2-RELEASE-MYKERNEL-1.1 CHROOTDIR=/app/release CVSROOT=/home/cvs EXTPORTSDIR=/usr/ports EXTSRCDIR=/usr/src KERNELS=GENERIC MYKERNEL MAKE_DVD=YES NODOC=YES NO_FLOPPIES=YES I am unsure how to get `make release` to realize the location of the kernel config. Also, I notice that in the command to make the kernel, DESTDIR is set to /R/stage/kernels while the CHROOTDIR (and the location where I want the release to be built) is /app/release. I am wondering if someone knows how I may resolve the issue so I can get the release built. I appreciate any advice and feedback. Thanks. The kernel is built inside the chroot, so all paths are really /app/release/whatever. Your symlink points to /app/release/root/kernels/MYKERNEL. It will be easiest to get rid of the symlink and copy the actual file into your EXTSRCDIR before starting the make release; alternately you could use the LOCAL_PATCHES or LOCAL_SCRIPT variables to import it. -- Rob Farmer ___ 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: make release custom kernel conf not found
2012-01-29 18:03, Rick Miller skrev: Hi All, I am performing a `make release` to build a new release with a custom kernel. The `make release` fails with the following error: cd /usr/src/release/..; make TARGET_ARCH=amd64 TARGET=amd64 KERNCONF=MYKERNEL kernel DESTDIR=/R/stage/kernels KODIR=/MYKERNEL Shouldn't that be KERNCONF=MYKERNEL DESTDIR=/R/stage/kernels KODIR=/MYKERNEL ERROR: Missing kernel configuration file(s) (MYKERNEL). *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src/release. + umount /dev *** Error code 1 Stop in /usr/src/release. I have the kernel config at /root/kernels/MYKERNEL and /usr/src/sys/amd64/conf/MYKERNEL is a symlink to the kernel config. The applicable environment variables are set in my .profile as follows: BUILDNAME=8.2-RELEASE-MYKERNEL-1.1 CHROOTDIR=/app/release CVSROOT=/home/cvs EXTPORTSDIR=/usr/ports EXTSRCDIR=/usr/src KERNELS=GENERIC MYKERNEL MAKE_DVD=YES NODOC=YES NO_FLOPPIES=YES I am unsure how to get `make release` to realize the location of the kernel config. Also, I notice that in the command to make the kernel, DESTDIR is set to /R/stage/kernels while the CHROOTDIR (and the location where I want the release to be built) is /app/release. I am wondering if someone knows how I may resolve the issue so I can get the release built. I appreciate any advice and feedback. Thanks. ___ 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: FreeBSD 9.0 ICH8M trouble, no HDD found, unable to install.
Jasper Valentijn wrote: L.S., I'm not able to install FreeBSD on a Sony Vaio vgn-cr31s. The problem seems to be related to PR kern/153440, http://www.freebsd.org/cgi/query-pr.cgi?pr=153440cat=. The FreeBSD-9.0-RELEASE-i386-memstick.img was used to try the install and extraction of the information below, verbose dmesg output and pciconf output. Does anybody have a workaround for this problem? If I could/should provide more information, just ask. I do not have this hardware, so these are just a couple of wild guessses from the blue on my part. I am also looking only at 64 bit platforms here, so if there is any signifigant difference with 32 bit I can't look/see. First, you might try using the 2 option on the boot menu and then 'load acpi_sony' followed by 'boot'. If this works, then you are indeed fortunate. If this is the case, at the end of the install when it gives you the chance to edit files put acpi_sony_load=YES in /boot/loader.conf prior to rebooting. Second has to do with AHCI support, and I'm a little fuzzy here. IIRC Intel began AHCI support with the ICH6 chip. With the advent of FreeBSD 9 the underlying mechanism has changed to the new ATA_CAM layer, with ahci support a default. Check your BIOS (if possible) to see what options are available. You may try disabling AHCI by switching to Legacy IDE mode and see what changes. If it works when you do this it confirms this to be where the problem lies. Also ensure you are not using any BIOS config for AHCI+RAID. Now you don't really want to run a modern day box without AHCI as you lose things like NCQ resulting in performance loss. Especially for SSDs as they demand it. You may be able to play around a little using the loader (press 2) to set and unset various variables. For example, hint.ahci.X.msi=0 would turn off MSI support. As far as specific settings for controlling ATA_CAM and/or other AHCI support I'm fuzzy on this. Perhaps if you reach this point someone more knowlegable can chime in. But if you were to find a sysctl that made it magically work with AHCI you could put it in loader.conf to make it permanent. As far as what I can tell from the PR you mentioned, if you saw the exact same behavior after having installed FBSD 8.1 and then subsquently trying to upgrade to 8.2 it would nail it to matching the PR. Sometimes there are hardware identifiers like PCI ID's that just need to be added to source for some minor offshoot/revision chip to be recognized properly. If you got down to this by process of elimination you would probably at that point want to work with a developer (someone much smarter than me) to get support added. If this were to become the case this is desirable as it would remove the problem for anyone else coming along later. Hope this helps any, as it's just basically just a couple of wild guesses to maybe get you started. -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: FreeBSD 9.0 ICH8M trouble, no HDD found, unable to install.
Mike wrote: I do not have this hardware, so these are just a couple of wild guessses from the blue on my part. I am also looking only at 64 bit platforms here, so if there is any signifigant difference with 32 bit I can't look/see. Just to be on the safe side I've also tried the 9.0 amd64 image. Same results though. First, you might try using the 2 option on the boot menu and then 'load acpi_sony' followed by 'boot'. No change here, on both i386 and amd64. You may try disabling AHCI by switching to Legacy IDE mode and see what changes. If it works when you do this it confirms this to be where the problem lies. Also ensure you are not using any BIOS config for AHCI+RAID. Sony has completely stripped the bios, no options to set here. You may be able to play around a little using the loader (press 2) to set and unset various variables. For example, hint.ahci.X.msi=0 would turn off MSI support. No luck with this either. Have tried your suggestion and some others 'hint.ata.0.*'. As far as specific settings for controlling ATA_CAM and/or other AHCI support I'm fuzzy on this. Perhaps if you reach this point someone more knowlegable can chime in. Same here. As far as what I can tell from the PR you mentioned, if you saw the exact same behavior after having installed FBSD 8.1 and then subsquently trying to upgrade to 8.2 it would nail it to matching the PR. I have tried the 8.1 i386 memstick image and it does see the drive. I have tried the 8.2 i386 memstick image and it does not see the drive. I have tried the 9.0 i386 memstick image and it does not see the drive. I have tried the 9.0 amd64 memstick image and it does not see the drive. Didn't do an install of 8.1 and upgrade to 8.2 though. If needed I could try that, but I'd prefer to do a clean 9.0 install. Hope this helps any, as it's just basically just a couple of wild guesses to maybe get you started. Well, still no FBSD 9.0 on the box but it kept me busy. Thanks anyways! Jasper -- “We spend the first twelve months of our children's lives teaching them to walk and talk and the next twelve telling them to sit down and shut up.” ___ 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: Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD
Dear folks, I had a FreeBSD 9.0 BETA 2 Machine I was happily running since the release and only updated ports via portmaster -a, and now since Fedora 9 has officially been released, I ran make buildworld, make Correction here. Meant FreeBSD 9.0 not Fedora 9 :( Message probably ignored because of this. buildkernel, make installkernel and mergemaster -i, and make installworld and now X does not work, I get error in subject Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD any ideas/suggestions for a fix? Thanks in advance, Antonio Found a solution updated following advice in the other lib***.so message, recompiled the ports that depended on it and now I am running 9.0 Stable. $ uname -a FreeBSD e213-amd64-1.grullahighschool.org 9.0-STABLE FreeBSD 9.0-STABLE #1: Mon Jan 16 14:48:05 CST 2012 r...@e213-amd64-1.grullahighschool.org:/usr/obj/usr/src/sys/GENERIC amd64 $ uname -r 9.0-STABLE Regards, Antonio ___ 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: Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD
On Tue, Jan 17, 2012 at 12:05 PM, Antonio Olivares olivares14...@gmail.comwrote: Dear folks, I had a FreeBSD 9.0 BETA 2 Machine I was happily running since the release and only updated ports via portmaster -a, and now since Fedora 9 has officially been released, I ran make buildworld, make Correction here. Meant FreeBSD 9.0 not Fedora 9 :( Message probably ignored because of this. buildkernel, make installkernel and mergemaster -i, and make installworld and now X does not work, I get error in subject Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD any ideas/suggestions for a fix? Thanks in advance, Antonio Found a solution updated following advice in the other lib***.so message, recompiled the ports that depended on it and now I am running 9.0 Stable. $ uname -a FreeBSD e213-amd64-1.grullahighschool.org 9.0-STABLE FreeBSD 9.0-STABLE #1: Mon Jan 16 14:48:05 CST 2012 r...@e213-amd64-1.grullahighschool.org:/usr/obj/usr/src/sys/GENERIC amd64 $ uname -r 9.0-STABLE There is instructions in ports/UPDATING on how to update. http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/ports/UPDATING?rev=1.1193;content-type=text%2Fplain Regards, Antonio ___ 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 ___ 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: Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD
Even after following said instruction in UPDATING, libxcb-aux.so.0 does not get installed by any of the XCB ports #pkg_info |grep -i xcb libxcb-1.7 The X protocol C-language Binding (XCB) library xcb-proto-1.6 The X protocol C-language Binding (XCB) protocol xcb-util-0.3.8,1A module with libxcb/libX11 extension/replacement libraries xcb-util-renderutil-0.3.8 Convenience functions for the Render extension [15:02:44] root@jimmiejaz 156 [1] /usr/ports#grep -iR aux /usr/ports/x11/libxcb/ [15:02:46] root@jimmiejaz 157 [1] /usr/ports# [15:02:46] root@jimmiejaz 157 [1] /usr/ports#grep -iR aux /usr/ports/x11/xcb-proto/ [15:02:57] root@jimmiejaz 158 [1] /usr/ports# [15:02:57] root@jimmiejaz 158 [1] /usr/ports#grep -iR aux /usr/ports/x11/xcb-util/ /usr/ports/x11/xcb-util/pkg-descr:aux: Convenient access to connection setup and some core requests. /usr/ports/x11/xcb-util/pkg-plist:libdata/pkgconfig/xcb-aux.pc /usr/ports/x11/xcb-util/pkg-plist:include/xcb/xcb_aux.h [15:03:21] root@jimmiejaz 160 [1] /usr/ports#grep -iR aux /usr/ports/x11/xcb-util-renderutil/ [15:03:25] root@jimmiejaz 161 [1] /usr/ports# [15:03:49] root@jimmiejaz 162 [0] /usr/ports#ls -ali /usr/local/lib/libxcb* 4365562 -rw-r--r-- 1 root wheel5954 Jan 17 11:15 /usr/local/lib/libxcb-composite.a 4358679 -rwxr-xr-x 1 root wheel1122 Jan 17 11:15 /usr/local/lib/libxcb-composite.la 4358554 lrwxr-xr-x 1 root wheel 21 Jan 17 11:15 /usr/local/lib/libxcb-composite.so - libxcb-composite.so.0 4358144 -rwxr-xr-x 1 root wheel 10243 Jan 17 11:15 /usr/local/lib/libxcb-composite.so.0 4365621 -rw-r--r-- 1 root wheel3726 Jan 17 11:15 /usr/local/lib/libxcb-damage.a 4359908 -rwxr-xr-x 1 root wheel1101 Jan 17 11:15 /usr/local/lib/libxcb-damage.la 4359055 lrwxr-xr-x 1 root wheel 18 Jan 17 11:15 /usr/local/lib/libxcb-damage.so - libxcb-damage.so.0 4358823 -rwxr-xr-x 1 root wheel8124 Jan 17 11:15 /usr/local/lib/libxcb-damage.so.0 4365705 -rw-r--r-- 1 root wheel4934 Jan 17 11:15 /usr/local/lib/libxcb-dpms.a 4360413 -rwxr-xr-x 1 root wheel1087 Jan 17 11:15 /usr/local/lib/libxcb-dpms.la 4360286 lrwxr-xr-x 1 root wheel 16 Jan 17 11:15 /usr/local/lib/libxcb-dpms.so - libxcb-dpms.so.0 4360076 -rwxr-xr-x 1 root wheel9308 Jan 17 11:15 /usr/local/lib/libxcb-dpms.so.0 4365728 -rw-r--r-- 1 root wheel7446 Jan 17 11:15 /usr/local/lib/libxcb-dri2.a 4361232 -rwxr-xr-x 1 root wheel1087 Jan 17 11:15 /usr/local/lib/libxcb-dri2.la 4361186 lrwxr-xr-x 1 root wheel 16 Jan 17 11:15 /usr/local/lib/libxcb-dri2.so - libxcb-dri2.so.0 4360540 -rwxr-xr-x 1 root wheel 12443 Jan 17 11:15 /usr/local/lib/libxcb-dri2.so.0 4365820 -rw-r--r-- 1 root wheel 76298 Jan 17 11:15 /usr/local/lib/libxcb-glx.a 4360123 -rwxr-xr-x 1 root wheel1080 Jan 17 11:15 /usr/local/lib/libxcb-glx.la 4358974 lrwxr-xr-x 1 root wheel 15 Jan 17 11:15 /usr/local/lib/libxcb-glx.so - libxcb-glx.so.0 4357984 -rwxr-xr-x 1 root wheel 93658 Jan 17 11:15 /usr/local/lib/libxcb-glx.so.0 4365965 -rw-r--r-- 1 root wheel 33046 Jan 17 11:15 /usr/local/lib/libxcb-randr.a 4361383 -rwxr-xr-x 1 root wheel1094 Jan 17 11:15 /usr/local/lib/libxcb-randr.la 4361299 lrwxr-xr-x 1 root wheel 17 Jan 17 11:15 /usr/local/lib/libxcb-randr.so - libxcb-randr.so.1 4360759 -rwxr-xr-x 1 root wheel 42343 Jan 17 11:15 /usr/local/lib/libxcb-randr.so.1 4365973 -rw-r--r-- 1 root wheel8334 Jan 17 11:15 /usr/local/lib/libxcb-record.a 4361729 -rwxr-xr-x 1 root wheel1101 Jan 17 11:15 /usr/local/lib/libxcb-record.la 4361558 lrwxr-xr-x 1 root wheel 18 Jan 17 11:15 /usr/local/lib/libxcb-record.so - libxcb-record.so.0 4361389 -rwxr-xr-x 1 root wheel 13354 Jan 17 11:15 /usr/local/lib/libxcb-record.so.0 4364285 -rw-r--r-- 1 root wheel9352 Jan 17 11:17 /usr/local/lib/libxcb-render-util.a 4363760 -rwxr-xr-x 1 root wheel1160 Jan 17 11:17 /usr/local/lib/libxcb-render-util.la 4363404 lrwxr-xr-x 1 root wheel 23 Jan 17 11:17 /usr/local/lib/libxcb-render-util.so - libxcb-render-util.so.0 4361280 -rwxr-xr-x 1 root wheel 14635 Jan 17 11:17 /usr/local/lib/libxcb-render-util.so.0 4365981 -rw-r--r-- 1 root wheel 26920 Jan 17 11:15 /usr/local/lib/libxcb-render.a 4362055 -rwxr-xr-x 1 root wheel1101 Jan 17 11:15 /usr/local/lib/libxcb-render.la 4361857 lrwxr-xr-x 1 root wheel 18 Jan 17 11:15 /usr/local/lib/libxcb-render.so - libxcb-render.so.0 4361765 -rwxr-xr-x 1 root wheel 34109 Jan 17 11:15 /usr/local/lib/libxcb-render.so.0 4366287 -rw-r--r-- 1 root wheel4526 Jan 17 11:15 /usr/local/lib/libxcb-res.a 4362171 -rwxr-xr-x 1 root wheel1080 Jan 17 11:15 /usr/local/lib/libxcb-res.la 4362161 lrwxr-xr-x 1 root wheel 15 Jan 17 11:15 /usr/local/lib/libxcb-res.so - libxcb-res.so.0 4362061 -rwxr-xr-x 1 root wheel8938 Jan 17 11:15 /usr/local/lib/libxcb-res.so.0 4366313 -rw-r--r-- 1 root wheel
Re: Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD
On Tue, Jan 17, 2012 at 3:04 PM, Jimmie James jimmie...@gmail.com wrote: Even after following said instruction in UPDATING, libxcb-aux.so.0 does not get installed by any of the XCB ports It was replaced with libxcb-util.so.0. #pkg_info |grep -i xcb libxcb-1.7 The X protocol C-language Binding (XCB) library xcb-proto-1.6 The X protocol C-language Binding (XCB) protocol xcb-util-0.3.8,1A module with libxcb/libX11 extension/replacement libraries xcb-util-renderutil-0.3.8 Convenience functions for the Render extension [15:02:44] root@jimmiejaz 156 [1] /usr/ports#grep -iR aux /usr/ports/x11/libxcb/ [15:02:46] root@jimmiejaz 157 [1] /usr/ports# [15:02:46] root@jimmiejaz 157 [1] /usr/ports#grep -iR aux /usr/ports/x11/xcb-proto/ [15:02:57] root@jimmiejaz 158 [1] /usr/ports# [15:02:57] root@jimmiejaz 158 [1] /usr/ports#grep -iR aux /usr/ports/x11/xcb-util/ /usr/ports/x11/xcb-util/pkg-**descr:aux: Convenient access to connection setup and some core requests. /usr/ports/x11/xcb-util/pkg-**plist:libdata/pkgconfig/xcb-**aux.pc /usr/ports/x11/xcb-util/pkg-**plist:include/xcb/xcb_aux.h [15:03:21] root@jimmiejaz 160 [1] /usr/ports#grep -iR aux /usr/ports/x11/xcb-util-**renderutil/ [15:03:25] root@jimmiejaz 161 [1] /usr/ports# [15:03:49] root@jimmiejaz 162 [0] /usr/ports#ls -ali /usr/local/lib/libxcb* 4365562 -rw-r--r-- 1 root wheel5954 Jan 17 11:15 /usr/local/lib/libxcb-**composite.a 4358679 -rwxr-xr-x 1 root wheel1122 Jan 17 11:15 /usr/local/lib/ libxcb-**composite.la http://libxcb-composite.la 4358554 lrwxr-xr-x 1 root wheel 21 Jan 17 11:15 /usr/local/lib/libxcb-**composite.so - libxcb-composite.so.0 4358144 -rwxr-xr-x 1 root wheel 10243 Jan 17 11:15 /usr/local/lib/libxcb-**composite.so.0 4365621 -rw-r--r-- 1 root wheel3726 Jan 17 11:15 /usr/local/lib/libxcb-damage.a 4359908 -rwxr-xr-x 1 root wheel1101 Jan 17 11:15 /usr/local/lib/ libxcb-damage.**la http://libxcb-damage.la 4359055 lrwxr-xr-x 1 root wheel 18 Jan 17 11:15 /usr/local/lib/libxcb-damage.**so - libxcb-damage.so.0 4358823 -rwxr-xr-x 1 root wheel8124 Jan 17 11:15 /usr/local/lib/libxcb-damage.**so.0 4365705 -rw-r--r-- 1 root wheel4934 Jan 17 11:15 /usr/local/lib/libxcb-dpms.a 4360413 -rwxr-xr-x 1 root wheel1087 Jan 17 11:15 /usr/local/lib/ libxcb-dpms.la 4360286 lrwxr-xr-x 1 root wheel 16 Jan 17 11:15 /usr/local/lib/libxcb-dpms.so - libxcb-dpms.so.0 4360076 -rwxr-xr-x 1 root wheel9308 Jan 17 11:15 /usr/local/lib/libxcb-dpms.so.**0 4365728 -rw-r--r-- 1 root wheel7446 Jan 17 11:15 /usr/local/lib/libxcb-dri2.a 4361232 -rwxr-xr-x 1 root wheel1087 Jan 17 11:15 /usr/local/lib/ libxcb-dri2.la 4361186 lrwxr-xr-x 1 root wheel 16 Jan 17 11:15 /usr/local/lib/libxcb-dri2.so - libxcb-dri2.so.0 4360540 -rwxr-xr-x 1 root wheel 12443 Jan 17 11:15 /usr/local/lib/libxcb-dri2.so.**0 4365820 -rw-r--r-- 1 root wheel 76298 Jan 17 11:15 /usr/local/lib/libxcb-glx.a 4360123 -rwxr-xr-x 1 root wheel1080 Jan 17 11:15 /usr/local/lib/ libxcb-glx.la 4358974 lrwxr-xr-x 1 root wheel 15 Jan 17 11:15 /usr/local/lib/libxcb-glx.so - libxcb-glx.so.0 4357984 -rwxr-xr-x 1 root wheel 93658 Jan 17 11:15 /usr/local/lib/libxcb-glx.so.0 4365965 -rw-r--r-- 1 root wheel 33046 Jan 17 11:15 /usr/local/lib/libxcb-randr.a 4361383 -rwxr-xr-x 1 root wheel1094 Jan 17 11:15 /usr/local/lib/ libxcb-randr.la 4361299 lrwxr-xr-x 1 root wheel 17 Jan 17 11:15 /usr/local/lib/libxcb-randr.so - libxcb-randr.so.1 4360759 -rwxr-xr-x 1 root wheel 42343 Jan 17 11:15 /usr/local/lib/libxcb-randr.**so.1 4365973 -rw-r--r-- 1 root wheel8334 Jan 17 11:15 /usr/local/lib/libxcb-record.a 4361729 -rwxr-xr-x 1 root wheel1101 Jan 17 11:15 /usr/local/lib/ libxcb-record.**la http://libxcb-record.la 4361558 lrwxr-xr-x 1 root wheel 18 Jan 17 11:15 /usr/local/lib/libxcb-record.**so - libxcb-record.so.0 4361389 -rwxr-xr-x 1 root wheel 13354 Jan 17 11:15 /usr/local/lib/libxcb-record.**so.0 4364285 -rw-r--r-- 1 root wheel9352 Jan 17 11:17 /usr/local/lib/libxcb-render-**util.a 4363760 -rwxr-xr-x 1 root wheel1160 Jan 17 11:17 /usr/local/lib/ libxcb-render-**util.la http://libxcb-render-util.la 4363404 lrwxr-xr-x 1 root wheel 23 Jan 17 11:17 /usr/local/lib/libxcb-render-**util.so - libxcb-render-util.so.0 4361280 -rwxr-xr-x 1 root wheel 14635 Jan 17 11:17 /usr/local/lib/libxcb-render-**util.so.0 4365981 -rw-r--r-- 1 root wheel 26920 Jan 17 11:15 /usr/local/lib/libxcb-render.a 4362055 -rwxr-xr-x 1 root wheel1101 Jan 17 11:15 /usr/local/lib/ libxcb-render.**la http://libxcb-render.la 4361857 lrwxr-xr-x 1 root wheel 18 Jan 17 11:15 /usr/local/lib/libxcb-render.**so - libxcb-render.so.0 4361765 -rwxr-xr-x 1 root wheel 34109 Jan 17 11:15 /usr/local/lib/libxcb-render.**so.0 4366287 -rw-r--r-- 1 root wheel4526 Jan 17
Re: Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD
On 01/17/12 15:39, Michael Johnson wrote: On Tue, Jan 17, 2012 at 3:04 PM, Jimmie James jimmie...@gmail.com mailto:jimmie...@gmail.com wrote: Even after following said instruction in UPDATING, libxcb-aux.so.0 does not get installed by any of the XCB ports It was replaced with libxcb-util.so.0. So it's the xfce4-wm port that's broken now, since it's still looking for the old libs. When applications fail because they're looking for a library that's been removed, following UPDATING doesn't help. gmake[3]: Entering directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' CC xfwm4_settings-xfwm4-settings.o CCLD xfwm4-settings CC xfwm4_tweaks_settings-tweaks-settings.o CCLD xfwm4-tweaks-settings CC xfwm4_workspace_settings-workspace-settings.o CCLD xfwm4-workspace-settings libtool: link: cannot find the library `/usr/local/lib/libxcb-aux.la' or unhandled argument `/usr/local/lib/libxcb-aux.la' ___ 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: Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD
On Tue, 17 Jan 2012, Jimmie James wrote: On 01/17/12 15:39, Michael Johnson wrote: On Tue, Jan 17, 2012 at 3:04 PM, Jimmie James jimmie...@gmail.com mailto:jimmie...@gmail.com wrote: Even after following said instruction in UPDATING, libxcb-aux.so.0 does not get installed by any of the XCB ports It was replaced with libxcb-util.so.0. So it's the xfce4-wm port that's broken now, since it's still looking for the old libs. When applications fail because they're looking for a library that's been removed, following UPDATING doesn't help. Building xfce4-wm here just worked. It was rebuilt yesterday, too, as part of the portmaster xcb-util rebuild (which pretty much rebuilt everything). Did you do a 'make clean' before retrying? ___ 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: Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD
On 01/17/12 16:50, Warren Block wrote: On Tue, 17 Jan 2012, Jimmie James wrote: On 01/17/12 15:39, Michael Johnson wrote: On Tue, Jan 17, 2012 at 3:04 PM, Jimmie James jimmie...@gmail.com mailto:jimmie...@gmail.com wrote: Even after following said instruction in UPDATING, libxcb-aux.so.0 does not get installed by any of the XCB ports It was replaced with libxcb-util.so.0. So it's the xfce4-wm port that's broken now, since it's still looking for the old libs. When applications fail because they're looking for a library that's been removed, following UPDATING doesn't help. Building xfce4-wm here just worked. It was rebuilt yesterday, too, as part of the portmaster xcb-util rebuild (which pretty much rebuilt everything). Did you do a 'make clean' before retrying? Done a make clean. Even done pkg_delete with all the XCB ports installed, and re-installed them, still hitting libtool: link: cannot find the library `/usr/local/lib/libxcb-aux.la' or unhandled argument `/usr/local/lib/libxcb-aux.la' For S*@ts'n'Giggles, I'm going to re-run the portmaster option mentioned in UPDATING (for the 2nd time, 1st time I used the portupgrade method) and see if there's any difference. ___ 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: Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD
On 01/17/12 16:50, Warren Block wrote: On Tue, 17 Jan 2012, Jimmie James wrote: On 01/17/12 15:39, Michael Johnson wrote: On Tue, Jan 17, 2012 at 3:04 PM, Jimmie James jimmie...@gmail.com mailto:jimmie...@gmail.com wrote: Even after following said instruction in UPDATING, libxcb-aux.so.0 does not get installed by any of the XCB ports It was replaced with libxcb-util.so.0. So it's the xfce4-wm port that's broken now, since it's still looking for the old libs. When applications fail because they're looking for a library that's been removed, following UPDATING doesn't help. Building xfce4-wm here just worked. It was rebuilt yesterday, too, as part of the portmaster xcb-util rebuild (which pretty much rebuilt everything). Did you do a 'make clean' before retrying? I am totally out of ideas now. After portupgrade -r xcb-util-0\* AND portmaster -R -r xcb-util-0 which rebuild pretty much everything, a pkg_libchk | grep -E xcb-.+.so | sort is still showing: libxfce4gui-4.8.1: /usr/local/lib/libglade/2.0/libxfce4.so misses libxcb-atom.so.1 libxfce4gui-4.8.1: /usr/local/lib/libglade/2.0/libxfce4.so misses libxcb-aux.so.0 libxfce4gui-4.8.1: /usr/local/lib/libglade/2.0/libxfce4.so misses libxcb-event.so.1 libxfce4gui-4.8.1: /usr/local/lib/libxfcegui4.so.7 misses libxcb-atom.so.1 libxfce4gui-4.8.1: /usr/local/lib/libxfcegui4.so.7 misses libxcb-aux.so.0 libxfce4gui-4.8.1: /usr/local/lib/libxfcegui4.so.7 misses libxcb-event.so.1 mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-atom.so.1 mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-aux.so.0 mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-event.so.1 squeeze-0.2.3_2: /usr/local/bin/squeeze misses libxcb-atom.so.1 squeeze-0.2.3_2: /usr/local/bin/squeeze misses libxcb-aux.so.0 squeeze-0.2.3_2: /usr/local/bin/squeeze misses libxcb-event.so.1 thunar-vfs-1.2.0_1: /usr/local/lib/libthunar-vfs-1.so.5 misses libxcb-atom.so.1 thunar-vfs-1.2.0_1: /usr/local/lib/libthunar-vfs-1.so.5 misses libxcb-aux.so.0 thunar-vfs-1.2.0_1: /usr/local/lib/libthunar-vfs-1.so.5 misses libxcb-event.so.1 xfburn-0.4.3_2: /usr/local/bin/xfburn misses libxcb-atom.so.1 xfburn-0.4.3_2: /usr/local/bin/xfburn misses libxcb-aux.so.0 xfburn-0.4.3_2: /usr/local/bin/xfburn misses libxcb-event.so.1 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop misses libxcb-atom.so.1 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop misses libxcb-aux.so.0 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop misses libxcb-event.so.1 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop-settings misses libxcb-atom.so.1 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop-settings misses libxcb-aux.so.0 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop-settings misses libxcb-event.so.1 xfce4-mailwatch-plugin-1.1.0_13: /usr/local/libexec/xfce4/panel-plugins/xfce4-mailwatch-plugin misses libxcb-atom.so.1 xfce4-mailwatch-plugin-1.1.0_13: /usr/local/libexec/xfce4/panel-plugins/xfce4-mailwatch-plugin misses libxcb-aux.so.0 xfce4-mailwatch-plugin-1.1.0_13: /usr/local/libexec/xfce4/panel-plugins/xfce4-mailwatch-plugin misses libxcb-event.so.1 xfce4-notes-plugin-1.7.7: /usr/local/bin/xfce4-notes-settings misses libxcb-atom.so.1 xfce4-notes-plugin-1.7.7: /usr/local/bin/xfce4-notes-settings misses libxcb-aux.so.0 xfce4-notes-plugin-1.7.7: /usr/local/bin/xfce4-notes-settings misses libxcb-event.so.1 xfce4-notifyd-0.2.2_1: /usr/local/bin/xfce4-notifyd-config misses libxcb-atom.so.1 xfce4-notifyd-0.2.2_1: /usr/local/bin/xfce4-notifyd-config misses libxcb-aux.so.0 xfce4-notifyd-0.2.2_1: /usr/local/bin/xfce4-notifyd-config misses libxcb-event.so.1 xfce4-notifyd-0.2.2_1: /usr/local/lib/xfce4/notifyd/xfce4-notifyd misses libxcb-atom.so.1 xfce4-notifyd-0.2.2_1: /usr/local/lib/xfce4/notifyd/xfce4-notifyd misses libxcb-aux.so.0 xfce4-notifyd-0.2.2_1: /usr/local/lib/xfce4/notifyd/xfce4-notifyd misses libxcb-event.so.1 xfce4-parole-0.2.0.6_3: /usr/local/bin/parole misses libxcb-atom.so.1 xfce4-parole-0.2.0.6_3: /usr/local/bin/parole misses libxcb-aux.so.0 xfce4-parole-0.2.0.6_3: /usr/local/bin/parole misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint-settings misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint-settings misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/bin/xfprint-settings misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4 misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4 misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4 misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4-manager misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4-manager misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4-manager misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/lib/libxfprint.so.0 misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/lib/libxfprint.so.0 misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/lib/libxfprint.so.0 misses libxcb-event.so.1
Re: Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD
On 01/17/12 16:50, Warren Block wrote: On Tue, 17 Jan 2012, Jimmie James wrote: On 01/17/12 15:39, Michael Johnson wrote: On Tue, Jan 17, 2012 at 3:04 PM, Jimmie James jimmie...@gmail.com mailto:jimmie...@gmail.com wrote: Even after following said instruction in UPDATING, libxcb-aux.so.0 does not get installed by any of the XCB ports It was replaced with libxcb-util.so.0. So it's the xfce4-wm port that's broken now, since it's still looking for the old libs. When applications fail because they're looking for a library that's been removed, following UPDATING doesn't help. Building xfce4-wm here just worked. It was rebuilt yesterday, too, as part of the portmaster xcb-util rebuild (which pretty much rebuilt everything). Did you do a 'make clean' before retrying? As a follow up to http://docs.freebsd.org/cgi/getmsg.cgi?fetch=592587+0+current/freebsd-questions After a few hours of rebuilding various xcb bits, I've gotten most to build, xfce4-wm builds and installs fine, the rest here, I'm not sure of. #pkg_libchk | grep -E xcb-.+.so | sort mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-atom.so.1 mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-aux.so.0 mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-event.so.1 xfburn-0.4.3_2: /usr/local/bin/xfburn misses libxcb-atom.so.1 xfburn-0.4.3_2: /usr/local/bin/xfburn misses libxcb-aux.so.0 xfburn-0.4.3_2: /usr/local/bin/xfburn misses libxcb-event.so.1 xfce4-mailwatch-plugin-1.1.0_13: /usr/local/libexec/xfce4/panel-plugins/xfce4-mailwatch-plugin misses libxcb-atom.so.1 xfce4-mailwatch-plugin-1.1.0_13: /usr/local/libexec/xfce4/panel-plugins/xfce4-mailwatch-plugin misses libxcb-aux.so.0 xfce4-mailwatch-plugin-1.1.0_13: /usr/local/libexec/xfce4/panel-plugins/xfce4-mailwatch-plugin misses libxcb-event.so.1 xfce4-notes-plugin-1.7.7: /usr/local/bin/xfce4-notes-settings misses libxcb-atom.so.1 xfce4-notes-plugin-1.7.7: /usr/local/bin/xfce4-notes-settings misses libxcb-aux.so.0 xfce4-notes-plugin-1.7.7: /usr/local/bin/xfce4-notes-settings misses libxcb-event.so.1 xfce4-parole-0.2.0.6_3: /usr/local/bin/parole misses libxcb-atom.so.1 xfce4-parole-0.2.0.6_3: /usr/local/bin/parole misses libxcb-aux.so.0 xfce4-parole-0.2.0.6_3: /usr/local/bin/parole misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint-settings misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint-settings misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/bin/xfprint-settings misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4 misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4 misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4 misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4-manager misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4-manager misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4-manager misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/lib/libxfprint.so.0 misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/lib/libxfprint.so.0 misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/lib/libxfprint.so.0 misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/lib/xfce4/xfprint-plugins/bsdlpr_plugin.so misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/lib/xfce4/xfprint-plugins/bsdlpr_plugin.so misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/lib/xfce4/xfprint-plugins/bsdlpr_plugin.so misses libxcb-event.so.1 xfce4-weather-plugin-0.7.4_1: /usr/local/libexec/xfce4/panel-plugins/xfce4-weather-plugin misses libxcb-atom.so.1 xfce4-weather-plugin-0.7.4_1: /usr/local/libexec/xfce4/panel-plugins/xfce4-weather-plugin misses libxcb-aux.so.0 xfce4-weather-plugin-0.7.4_1: /usr/local/libexec/xfce4/panel-plugins/xfce4-weather-plugin misses libxcb-event.so.1 I do know the missing libs are living in /usr/local/lib/compat/pkg/ (though, I don't understand the dates listed) #ls -ali /usr/local/lib/compat/pkg/libxcb* 4404817 -rwxr-xr-x 1 root wheel 15146 Oct 20 2008 /usr/local/lib/compat/pkg/libxcb-atom.so.0 4405755 -rwxr-xr-x 1 root wheel 16291 Dec 20 01:29 /usr/local/lib/compat/pkg/libxcb-atom.so.1 4405756 -rwxr-xr-x 1 root wheel 12079 Dec 20 01:29 /usr/local/lib/compat/pkg/libxcb-aux.so.0 4404820 -rwxr-xr-x 1 root wheel6812 Oct 20 2008 /usr/local/lib/compat/pkg/libxcb-event.so.0 4405813 -rwxr-xr-x 1 root wheel 12878 Dec 20 01:29 /usr/local/lib/compat/pkg/libxcb-event.so.1 4404822 -rwxr-xr-x 1 root wheel 17302 Oct 20 2008 /usr/local/lib/compat/pkg/libxcb-icccm.so.0 4405815 -rwxr-xr-x 1 root wheel 1 Dec 20 01:29 /usr/local/lib/compat/pkg/libxcb-icccm.so.1 4405816 -rwxr-xr-x 1 root wheel 16678 Dec 20 01:30 /usr/local/lib/compat/pkg/libxcb-image.so.0 4404857 -rwxr-xr-x 1 root wheel8644 Feb 7 2009 /usr/local/lib/compat/pkg/libxcb-keysyms.so.0 4405817 -rwxr-xr-x 1 root wheel9126 Dec 20 01:30
Re: Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD [SOLVED]
Sorry for top posting in this message, but one reboot and a ldconfig -R allows everything to be rebuilt. Not sure which was the key here, but for others, I'd try ldconfig -R first. Not sure why portupgrade and portmaster failed though. On 01/18/12 00:11, Jimmie James wrote: On 01/17/12 16:50, Warren Block wrote: On Tue, 17 Jan 2012, Jimmie James wrote: On 01/17/12 15:39, Michael Johnson wrote: On Tue, Jan 17, 2012 at 3:04 PM, Jimmie James jimmie...@gmail.com mailto:jimmie...@gmail.com wrote: Even after following said instruction in UPDATING, libxcb-aux.so.0 does not get installed by any of the XCB ports It was replaced with libxcb-util.so.0. So it's the xfce4-wm port that's broken now, since it's still looking for the old libs. When applications fail because they're looking for a library that's been removed, following UPDATING doesn't help. Building xfce4-wm here just worked. It was rebuilt yesterday, too, as part of the portmaster xcb-util rebuild (which pretty much rebuilt everything). Did you do a 'make clean' before retrying? As a follow up to http://docs.freebsd.org/cgi/getmsg.cgi?fetch=592587+0+current/freebsd-questions After a few hours of rebuilding various xcb bits, I've gotten most to build, xfce4-wm builds and installs fine, the rest here, I'm not sure of. #pkg_libchk | grep -E xcb-.+.so | sort mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-atom.so.1 mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-aux.so.0 mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-event.so.1 xfburn-0.4.3_2: /usr/local/bin/xfburn misses libxcb-atom.so.1 xfburn-0.4.3_2: /usr/local/bin/xfburn misses libxcb-aux.so.0 xfburn-0.4.3_2: /usr/local/bin/xfburn misses libxcb-event.so.1 xfce4-mailwatch-plugin-1.1.0_13: /usr/local/libexec/xfce4/panel-plugins/xfce4-mailwatch-plugin misses libxcb-atom.so.1 xfce4-mailwatch-plugin-1.1.0_13: /usr/local/libexec/xfce4/panel-plugins/xfce4-mailwatch-plugin misses libxcb-aux.so.0 xfce4-mailwatch-plugin-1.1.0_13: /usr/local/libexec/xfce4/panel-plugins/xfce4-mailwatch-plugin misses libxcb-event.so.1 xfce4-notes-plugin-1.7.7: /usr/local/bin/xfce4-notes-settings misses libxcb-atom.so.1 xfce4-notes-plugin-1.7.7: /usr/local/bin/xfce4-notes-settings misses libxcb-aux.so.0 xfce4-notes-plugin-1.7.7: /usr/local/bin/xfce4-notes-settings misses libxcb-event.so.1 xfce4-parole-0.2.0.6_3: /usr/local/bin/parole misses libxcb-atom.so.1 xfce4-parole-0.2.0.6_3: /usr/local/bin/parole misses libxcb-aux.so.0 xfce4-parole-0.2.0.6_3: /usr/local/bin/parole misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint-settings misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint-settings misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/bin/xfprint-settings misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4 misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4 misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4 misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4-manager misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4-manager misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4-manager misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/lib/libxfprint.so.0 misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/lib/libxfprint.so.0 misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/lib/libxfprint.so.0 misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/lib/xfce4/xfprint-plugins/bsdlpr_plugin.so misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/lib/xfce4/xfprint-plugins/bsdlpr_plugin.so misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/lib/xfce4/xfprint-plugins/bsdlpr_plugin.so misses libxcb-event.so.1 xfce4-weather-plugin-0.7.4_1: /usr/local/libexec/xfce4/panel-plugins/xfce4-weather-plugin misses libxcb-atom.so.1 xfce4-weather-plugin-0.7.4_1: /usr/local/libexec/xfce4/panel-plugins/xfce4-weather-plugin misses libxcb-aux.so.0 xfce4-weather-plugin-0.7.4_1: /usr/local/libexec/xfce4/panel-plugins/xfce4-weather-plugin misses libxcb-event.so.1 I do know the missing libs are living in /usr/local/lib/compat/pkg/ (though, I don't understand the dates listed) #ls -ali /usr/local/lib/compat/pkg/libxcb* 4404817 -rwxr-xr-x 1 root wheel 15146 Oct 20 2008 /usr/local/lib/compat/pkg/libxcb-atom.so.0 4405755 -rwxr-xr-x 1 root wheel 16291 Dec 20 01:29 /usr/local/lib/compat/pkg/libxcb-atom.so.1 4405756 -rwxr-xr-x 1 root wheel 12079 Dec 20 01:29 /usr/local/lib/compat/pkg/libxcb-aux.so.0 4404820 -rwxr-xr-x 1 root wheel 6812 Oct 20 2008 /usr/local/lib/compat/pkg/libxcb-event.so.0 4405813 -rwxr-xr-x 1 root wheel 12878 Dec 20 01:29 /usr/local/lib/compat/pkg/libxcb-event.so.1 4404822 -rwxr-xr-x 1 root wheel 17302 Oct 20 2008 /usr/local/lib/compat/pkg/libxcb-icccm.so.0 4405815 -rwxr-xr-x 1 root wheel 1 Dec 20 01:29 /usr/local/lib/compat/pkg/libxcb-icccm.so.1 4405816 -rwxr-xr-x 1 root wheel 16678 Dec 20 01:30
Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD
Dear folks, I had a FreeBSD 9.0 BETA 2 Machine I was happily running since the release and only updated ports via portmaster -a, and now since Fedora 9 has officially been released, I ran make buildworld, make buildkernel, make installkernel and mergemaster -i, and make installworld and now X does not work, I get error in subject Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD any ideas/suggestions for a fix? Thanks in advance, Antonio ___ 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: Invalid fdisk partition table found (fwd)
On Sat, 26 Nov 2011 19:07:57 -0700 (MST) Warren Block wbl...@wonkity.com wrote: On Sat, 26 Nov 2011, Robert wrote: Some difference today. Not sure at what point this happened but one of my CF cards now reads: [robert@dell64] ~ fdisk /dev/da1 *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=2057 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=2057 heads=255 sectors/track=63 (16065 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 33045642 (16135 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 8/ head 254/ sector 63 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED Now showing 16GB but still not right. ... I also did this in single user with the same results. Ideally, I would like to change these cards to FAT32 but I cannot get there with fdisk and am not sure how to get there with gpart or if I can. Creating an MS-DOS layout with gpart(8), where the disk is da0: # gpart destroy -F da0 da0 destroyed # gpart create -s mbr da0 da0 created # gpart add -t \!11 da0 da0s1 added Warren, Thanks for hanging in there with me. I am about ready to give up, but here is where everything stands now. [robert@dell64] ~ gpart destroy -F da1 da1 destroyed [robert@dell64] ~ sudo gpart create -s mbr da1 Password: da1 created [robert@dell64] ~ sudo gpart add -t \!11 da1 da1s1 added [robert@dell64] ~ gpart show da1 = 32 60448 da1 MBR (29M) 32 604481 fat32 (29M) [robert@dell64] ~ newfs_msdos -F32 /dev/da1s1 /dev/da1s1: 60296 sectors in 7537 FAT32 clusters (4096 bytes/cluster) BytesPerSec=512 SecPerClust=8 ResSectors=32 FATs=2 Sectors=60448 Media=0xf0 SecPerTrack=32 Heads=64 HiddenSecs=0 FATsecs=59 RootCluster=2 FSInfo=1 Backup=2 [robert@dell64] ~ sudo mount_msdosfs /dev/da1s1 /mnt mount_msdosfs: /dev/da1s1: Invalid argument [robert@dell64] ~ fdisk /dev/da1 *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 32, size 59360 (28 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 28/ head 63/ sector 32 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED [robert@dell64] ~ sudo gpart destroy da1 Password: gpart: Device busy [robert@dell64] ~ dd if=/dev/null of=/dev/da1 0+0 records in 0+0 records out 0 bytes transferred in 0.18 secs (0 bytes/sec) [robert@dell64] ~ gpart show da1 gpart: No such geom: da1. [robert@dell64] ~ Now I lost the info that I created with gpart. 11 is 0x0b, the FAT32 partition type. There might be a more mnemonic string for it, this is the first time I've ever used gpart for FAT32. The exclamation is for gpart/GPT, and the backslash is to keep the shell from messing with it. # gpart show da0 = 63 15662997 da0 MBR (7.5G) 63 156629971 fat32 (7.5G) # ls /dev/da0* /dev/da0 /dev/da0s1 # newfs_msdos -F32 /dev/da0s1 fdisk(8) may be easier, just set the partition type to 11. I haven't had any luck with the second CF card as it still show 29MB. I will try some more later today or tomorrow. What happened to make the one card show 16G? I wish I knew :-). I was doing everything that you and Julian suggested and somewhere along the line it started showing 16G. Yesterday I got it to show FAT32 (tyoe 12) along with 16G but on da1 without a s1. I then put it in a WinXP box but it did not even bring up the drive. When I put it back in the FreeBSD box it was back to 28MB. This is the card that I show above. It acts like there is some sort of write protect on sector 1 or the cards are defective. Robert ___ 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: Invalid fdisk partition table found (fwd)
On Mon, 28 Nov 2011, Robert wrote: Thanks for hanging in there with me. I am about ready to give up, but here is where everything stands now. Before giving up, a few more suggestions. First, check the BIOS settings. It's possible the computer has a BIOS that protects the boot block from viruses by making it read-only. Second, sudo is not the same as being root, there are differences. So I'd also suggest trying these as root, just in case. [robert@dell64] ~ gpart destroy -F da1 da1 destroyed [robert@dell64] ~ sudo gpart create -s mbr da1 Password: da1 created [robert@dell64] ~ sudo gpart add -t \!11 da1 da1s1 added [robert@dell64] ~ gpart show da1 = 32 60448 da1 MBR (29M) 32 604481 fat32 (29M) [robert@dell64] ~ newfs_msdos -F32 /dev/da1s1 /dev/da1s1: 60296 sectors in 7537 FAT32 clusters (4096 bytes/cluster) BytesPerSec=512 SecPerClust=8 ResSectors=32 FATs=2 Sectors=60448 Media=0xf0 SecPerTrack=32 Heads=64 HiddenSecs=0 FATsecs=59 RootCluster=2 FSInfo=1 Backup=2 [robert@dell64] ~ sudo mount_msdosfs /dev/da1s1 /mnt mount_msdosfs: /dev/da1s1: Invalid argument That's odd. da1s1 went away after being formatted. Have these cards been heavily used to the point where they may be failing? If the card is failing, I'd expect there to be something in /var/log/messages. For that matter, even sysutils/smartmontools might work on these. [robert@dell64] ~ fdisk /dev/da1 Something I noticed when testing yesterday: fdisk results may not agree with gpart until the card has been reconnected. In particular fdisk showed the single FAT32 partition as the last instead of the first. *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found [robert@dell64] ~ sudo gpart destroy da1 Password: gpart: Device busy gpart won't destroy a GEOM unless it's unused. So either delete all the partitions first, or use 'gpart destroy -F'. Interesting that here the partition still exists, though. [robert@dell64] ~ dd if=/dev/null of=/dev/da1 0+0 records in 0+0 records out 0 bytes transferred in 0.18 secs (0 bytes/sec) This didn't write anything (0+0 records). Should be dd if=/dev/zero of=/dev/da1 bs=512 count=35 count=35 to make sure MBR/disklabel or primary GPT are wiped out. It acts like there is some sort of write protect on sector 1 This is what made me think of a BIOS virus-protect mentioned above. Hopefully that's the problem. or the cards are defective. It's worth contacting the manufacturer. Maybe they have a reset or reformat program. If you do get to the point of discarding the cards, I'd be interested in experimenting on them. ___ 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: Invalid fdisk partition table found (fwd)
On Mon, 28 Nov 2011 08:02:55 -0700 (MST) Warren Block wbl...@wonkity.com wrote: On Mon, 28 Nov 2011, Robert wrote: Thanks for hanging in there with me. I am about ready to give up, but here is where everything stands now. Before giving up, a few more suggestions. First, check the BIOS settings. It's possible the computer has a BIOS that protects the boot block from viruses by making it read-only. Second, sudo is not the same as being root, there are differences. So I'd also suggest trying these as root, just in case. I saw nothing in BIOS to suggest any protection. I am doing the testing on a Dell Precision 490. I did discover that an external card reader I was using on the Windows XP computer is defective. It had a bent pin and another recessed pin. I hope that is not what damaged these cards. Have these cards been heavily used to the point where they may be failing? I couldn't say for sure but I am waiting for answers from the photographer/owner about other questions. She does take an incredible amount of photos so I would guess they have been used and clear many times. If the card is failing, I'd expect there to be something in /var/log/messages. Nothing shows in /var/log/messages For that matter, even sysutils/smartmontools might work on these. [root@dell64] ~# smartctl /dev/da1 smartctl 5.42 2011-10-20 r3458 [FreeBSD 8.2-STABLE amd64] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net /dev/da1: Unknown USB bridge [0x0644:0x0200 (0x400)] Smartctl: please specify device type with the -d option. [root@dell64] ~# smartctl -d scsi -a /dev/da1 smartctl 5.42 2011-10-20 r3458 [FreeBSD 8.2-STABLE amd64] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net Vendor: TEAC Product: USB HS-CF Card Revision: 4.00 User Capacity:30,965,760 bytes [30.9 MB] Logical block size: 512 bytes Device type: disk Local Time is:Mon Nov 28 10:20:13 2011 PST Device does not support SMART Error Counter logging not supported Device does not support Self Test logging [robert@dell64] ~ fdisk /dev/da1 Something I noticed when testing yesterday: fdisk results may not agree with gpart until the card has been reconnected. In particular fdisk showed the single FAT32 partition as the last instead of the first. Interesting that here the partition still exists, though. [robert@dell64] ~ dd if=/dev/null of=/dev/da1 0+0 records in 0+0 records out 0 bytes transferred in 0.18 secs (0 bytes/sec) This didn't write anything (0+0 records). Should be dd if=/dev/zero of=/dev/da1 bs=512 count=35 I was attempting to force another look at /dev/da1 to see any change not actually zero out anything. I did a lot of my testing in single user but switched to multi so that I could more easily cut and paste tests and results. Her are the results as root: [root@dell64] ~# gpart create -s mbr da1 da1 created [root@dell64] ~# gpart add -t \!11 da1 da1s1 added [root@dell64] ~# gpart show da1 = 32 60448 da1 MBR (29M) 32 604481 fat32 (29M) [root@dell64] ~# newfs_msdos -F32 /dev/da1s1 /dev/da1s1: 60296 sectors in 7537 FAT32 clusters (4096 bytes/cluster) BytesPerSec=512 SecPerClust=8 ResSectors=32 FATs=2 Sectors=60448 Media=0xf0 SecPerTrack=32 Heads=64 HiddenSecs=0 FATsecs=59 RootCluster=2 FSInfo=1 Backup=2 At this point I removed the card and using a different external card reader placed it in the WinXP system. Windows said the card was not formatted and asked. I attempted to format but windows failed saying the card could not be formatted. I put it back in FreeBSD system and here is what I see. [root@dell64] ~# gpart show da1 = 32 60448 da1 MBR (29M) 32 604481 fat32 (29M) [root@dell64] ~# mount_msdosfs /dev/da1s1 /mnt mount_msdosfs: /dev/da1s1: Invalid argument [root@dell64] ~# gpart show da1 = 32 60448 da1 MBR (29M) 32 604481 fat32 (29M) It acts like there is some sort of write protect on sector 1 This is what made me think of a BIOS virus-protect mentioned above. Hopefully that's the problem. or the cards are defective. It's worth contacting the manufacturer. Maybe they have a reset or reformat program. If you do get to the point of discarding the cards, I'd be interested in experimenting on them. I will spend some time today or tomorrow on the manufacturer's chat. If I do give it up and it is OK with the owner I will contact you offline. Thanks for you help. Robert ___ 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: Invalid fdisk partition table found (fwd)
On Mon, 28 Nov 2011, Robert wrote: I did discover that an external card reader I was using on the Windows XP computer is defective. It had a bent pin and another recessed pin. I hope that is not what damaged these cards. Ouch. That sounds like a logical cause. Although the card itself has sockets, and would hopefully still work in a good reader... A bad pin would explain why they show similar but not identical capacity. Have these cards been heavily used to the point where they may be failing? I couldn't say for sure but I am waiting for answers from the photographer/owner about other questions. She does take an incredible amount of photos so I would guess they have been used and clear many times. I was thinking of them being used as drive in a computer application. In that kind of use, flash drives are reported to last 1.5 to 3 years. I was attempting to force another look at /dev/da1 to see any change not actually zero out anything. Oh. A little easier: true /dev/da0 I did a lot of my testing in single user but switched to multi so that I could more easily cut and paste tests and results. Sorry, forgot to mention that earlier. It really should make no difference here. ___ 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: Invalid fdisk partition table found (fwd)
On Fri, 25 Nov 2011 13:29:51 -0700 (MST) Warren Block wbl...@wonkity.com wrote: On Fri, 25 Nov 2011, Robert wrote: On Thu, 24 Nov 2011 13:45:37 -0700 (MST) Warren Block wbl...@wonkity.com wrote: On Thu, 24 Nov 2011, Robert wrote: [robert@dell64] ~ sudo gpart destroy -F da1 da1 destroyed clip And it starts with a default table equal to the size of the drive. Is it supposed to still show sysid 165 ? I was under the impression that dd if=/dev/zero would clean out everything including sector 1. The partition table was cleared, that's why it said invalid fdisk partition table found. Rather than starting with an invalid table, it created a valid default table in memory. Do both cards report the same size? Yes..sort of 28, 29 MB Some difference today. Not sure at what point this happened but one of my CF cards now reads: [robert@dell64] ~ fdisk /dev/da1 *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=2057 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=2057 heads=255 sectors/track=63 (16065 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 33045642 (16135 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 8/ head 254/ sector 63 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED Now showing 16GB but still not right. [robert@dell64] ~ sudo gpart destroy -F da1 Password: da1 destroyed [robert@dell64] ~ gpart create -s MBR da1 da1 created [robert@dell64] ~ gpart add -t freebsd -s 15G da1 da1s1 added [robert@dell64] ~ gpart set -a active -i 1 da1 active set on da1s1 [robert@dell64] ~ gpart bootcode -b /boot/boot0 da1 bootcode written to da1 [robert@dell64] ~ ls -l /dev/da1* crw-rw 1 root operator0, 145 Nov 26 08:48 /dev/da1 crw-rw 1 root operator0, 129 Nov 26 13:48 /dev/da1s1 [robert@dell64] ~ sudo mount /dev/da1s1 /mnt mount: /dev/da1s1 : Invalid argument I also did this in single user with the same results. Ideally, I would like to change these cards to FAT32 but I cannot get there with fdisk and am not sure how to get there with gpart or if I can. If they weren't the same, I was going to suggest maybe they've been heavily used and worn out. But I don't know if capacity shrinks as blocks go bad and spares are used up, or if they just quit working. And I'd expect them to be very different unless they had the exact same usage, like in a mirror. I haven't had any luck with the second CF card as it still show 29MB. I will try some more later today or tomorrow. robert ___ 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: Invalid fdisk partition table found (fwd)
On Sat, 26 Nov 2011, Robert wrote: Some difference today. Not sure at what point this happened but one of my CF cards now reads: [robert@dell64] ~ fdisk /dev/da1 *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=2057 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=2057 heads=255 sectors/track=63 (16065 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 33045642 (16135 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 8/ head 254/ sector 63 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED Now showing 16GB but still not right. ... I also did this in single user with the same results. Ideally, I would like to change these cards to FAT32 but I cannot get there with fdisk and am not sure how to get there with gpart or if I can. Creating an MS-DOS layout with gpart(8), where the disk is da0: # gpart destroy -F da0 da0 destroyed # gpart create -s mbr da0 da0 created # gpart add -t \!11 da0 da0s1 added 11 is 0x0b, the FAT32 partition type. There might be a more mnemonic string for it, this is the first time I've ever used gpart for FAT32. The exclamation is for gpart/GPT, and the backslash is to keep the shell from messing with it. # gpart show da0 = 63 15662997 da0 MBR (7.5G) 63 156629971 fat32 (7.5G) # ls /dev/da0* /dev/da0/dev/da0s1 # newfs_msdos -F32 /dev/da0s1 fdisk(8) may be easier, just set the partition type to 11. I haven't had any luck with the second CF card as it still show 29MB. I will try some more later today or tomorrow. What happened to make the one card show 16G? ___ 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: Invalid fdisk partition table found (fwd)
Robert wrote: Ideally, I would like to change these cards to FAT32 but I cannot get there with fdisk and am not sure how to get there with gpart or if I can. You can get a small script that erases the primary GPT table from the front of the HD and the secondary GPT table from the end of the HD. http://wiki.freenas.org/faq:0129 Then follow instructions found here. http://forums.freebsd.org/showthread.php?t=13780 This will leave you with fat32 format on your md cards. Then insert into ms/windows system and use windows explorer to select the drive letter of the md card, right mouse click for pull down menu, select format to reformat for ntfs format. ___ 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: Invalid fdisk partition table found (fwd)
Warren Block wrote: On Sat, 26 Nov 2011, Robert wrote: Some difference today. Not sure at what point this happened but one of my CF cards now reads: [robert@dell64] ~ fdisk /dev/da1 *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=2057 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=2057 heads=255 sectors/track=63 (16065 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 33045642 (16135 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 8/ head 254/ sector 63 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED Now showing 16GB but still not right. ... I also did this in single user with the same results. Ideally, I would like to change these cards to FAT32 but I cannot get there with fdisk and am not sure how to get there with gpart or if I can. Creating an MS-DOS layout with gpart(8), where the disk is da0: # gpart destroy -F da0 da0 destroyed # gpart create -s mbr da0 da0 created # gpart add -t \!11 da0 da0s1 added 11 is 0x0b, the FAT32 partition type. There might be a more mnemonic string for it, this is the first time I've ever used gpart for FAT32. The exclamation is for gpart/GPT, and the backslash is to keep the shell from messing with it. # gpart show da0 = 63 15662997 da0 MBR (7.5G) 63 156629971 fat32 (7.5G) # ls /dev/da0* /dev/da0/dev/da0s1 # newfs_msdos -F32 /dev/da0s1 fdisk(8) may be easier, just set the partition type to 11. The correct partition type is 12 not 11. ___ 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: Invalid fdisk partition table found
Robert travelin...@cox.net writes: Greetings [robert@dell64] ~ uname -a FreeBSD dell64.shasta204.local 8.2-STABLE FreeBSD 8.2-STABLE #34: Fri Nov 18 06:43:01 PST 2011 root@dell64.shasta204.local:/usr/obj/usr/src/sys/GENERIC amd64 I have two Lexar Professional 600X 16GB compact flash cards that are unusable. fdisk shows: [robert@dell64] ~ fdisk /dev/da1 *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 32, size 59360 (28 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 28/ head 63/ sector 32 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED It shows only 28 MB instead of 16GB. I have tried to change the type from 165 (FreeBSD) to msdosfs types 6 11 or 12 using fdisk -u and fdisk -i and also sade. I do not get an error but when finished it still shows the same data. I have tried to zero it out using dd if=/dev/zero of=/dev/da1 bs=1m and nothing changes. I have tried different block sizes and counts to no avail. If you zero it out and fdisk still sees a partition table, the write probably didn't really happen. [Modulo some possible issues with the kernel caching the disk parameters.] fdisk is sometimes a bit quiet about its errors, but dd isn't... ___ 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: Invalid fdisk partition table found (fwd)
On Thu, 24 Nov 2011 13:45:37 -0700 (MST) Warren Block wbl...@wonkity.com wrote: On Thu, 24 Nov 2011, Robert wrote: [robert@dell64] ~ sudo gpart destroy -F da1 da1 destroyed [robert@dell64] ~ fdisk /dev/da1 *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found The partition table was cleared. Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 32, size 59360 (28 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 28/ head 63/ sector 32 And it starts with a default table equal to the size of the drive. Is it supposed to still show sysid 165 ? I was under the impression that dd if=/dev/zero would clean out everything including sector 1. I see the flashing lights like it is writing to the CF card but nothing changes. More suggestions welcome. These are quite expensive CF cards. The dd/fdisk and gpart results show the same problem, so it likely isn't in the partitioning. Do both cards report the same size? Yes..sort of 28, 29 MB I found recently that there is some oddness with certain Sandisk flash memory that made it non-responsive to anything. FreeBSD couldn't do a thing with it. Before throwing it away, I tried it on a Windows Vista system... which recognized and formatted it without a complaint. Now it works on everything. Special vendor-specific code in Windows? XP Pro shows and error that the disk cannot be formatted. I tried it in the wifes Windows 7 and it shows no drive attached. Another option would be to attempt formatting the cards with a camera. I'll have to ask the camera owner if she tried that. OT. The last 2 times that I have sent replies to two list regarding this question, I have not seen it come through to me. Julian's relies as well as yours come through. Robert ___ 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: Invalid fdisk partition table found (fwd)
On Fri, 25 Nov 2011, Robert wrote: On Thu, 24 Nov 2011 13:45:37 -0700 (MST) Warren Block wbl...@wonkity.com wrote: On Thu, 24 Nov 2011, Robert wrote: [robert@dell64] ~ sudo gpart destroy -F da1 da1 destroyed [robert@dell64] ~ fdisk /dev/da1 *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found The partition table was cleared. Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 32, size 59360 (28 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 28/ head 63/ sector 32 And it starts with a default table equal to the size of the drive. Is it supposed to still show sysid 165 ? I was under the impression that dd if=/dev/zero would clean out everything including sector 1. The partition table was cleared, that's why it said invalid fdisk partition table found. Rather than starting with an invalid table, it created a valid default table in memory. Do both cards report the same size? Yes..sort of 28, 29 MB If they weren't the same, I was going to suggest maybe they've been heavily used and worn out. But I don't know if capacity shrinks as blocks go bad and spares are used up, or if they just quit working. And I'd expect them to be very different unless they had the exact same usage, like in a mirror. OT. The last 2 times that I have sent replies to two list regarding this question, I have not seen it come through to me. Julian's relies as well as yours come through. Maybe spam or duplicate filtering. ___ 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: Invalid fdisk partition table found (fwd)
Hi, Please keep this on list. Forwarded from: Julian Stacey j...@berklix.com http://www.berklix.com/~jhs/ --- Forwarded Message From travelin...@cox.net Thu Nov 24 05:15:33 2011 From: Robert travelin...@cox.net To: Julian H. Stacey j...@berklix.com Subject: Re: Invalid fdisk partition table found Message-ID: 2023192154.5b0a64ab@dell64 In-Reply-To: 20232108.panl80g3041...@fire.js.berklix.net References: 2023123347.4f439c9c@dell64 20232108.panl80g3041...@fire.js.berklix.net X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.6; amd64-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Julian and Warren thanks for the responses. On Wed, 23 Nov 2011 22:08:00 +0100 Julian H. Stacey j...@berklix.com wrote: Robert wrote: Greetings [robert@dell64] ~ uname -a FreeBSD dell64.shasta204.local 8.2-STABLE FreeBSD 8.2-STABLE #34: Fri Nov 18 06:43:01 PST 2011 root@dell64.shasta204.local:/usr/obj/usr/src/sys/GENERIC amd64 I have two Lexar Professional 600X 16GB compact flash cards that are unusable. fdisk shows: clip Is there any way I can restore these CF cards to 16GB? Any help or suggestions will be greatly appreciated. @ suggestions: 1 Try bsdlabel -B -w -r /dev/da1 [robert@dell64] ~ sudo bsdlabel -B -w -r /dev/da1 Password: [robert@dell64] ~ echo unplug, reinsert Not sure if you actually wanted me to unplug and reinsert the CF card...so I did both [robert@dell64] ~ echo unplug, reinsert unplug, reinsert and physically unplugged and reinserted the CF card newfs /dev/da1a ^ ??? [robert@dell64] ~ sudo newfs /dev/da1a newfs: /dev/da1a: could not find special device [robert@dell64] ~ sudo newfs /dev/da1 /dev/da1: 29.5MB (60480 sectors) block size 16384, fragment size 2048 using 4 cylinder groups of 7.39MB, 473 blks, 960 inodes. super-block backups (for fsck -b #) at: 160, 15296, 30432, 45568 cg 0: bad magic number [robert@dell64] ~ fdisk /dev/da1 *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 32, size 59360 (28 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 28/ head 63/ sector 32 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED No change from before. 2 Base of _my_ man fdisk When running multi user, you cannot write unless you first run this: sysctl kern.geom.debugflags=16 I had failed to mention in the original post that I had seen something in my searches about problems since 7.1. I had tried booting from an old 6.2 disk and attempted all of this under fixit with no luck. And also tried in single user mode. Warren, [robert@dell64] ~ sudo gpart destroy -F da1 gpart: geom 'da1': Invalid argument [robert@dell64] ~ sudo gpart create -s GPT da1 da1 created [robert@dell64] ~ sudo gpart bootcode -b /boot/pmbr da1 bootcode written to da1 [robert@dell64] ~ sudo gpart destroy -F da1 da1 destroyed [robert@dell64] ~ fdisk /dev/da1 *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 32, size 59360 (28 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 28/ head 63/ sector 32 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED I see the flashing lights like it is writing to the CF card but nothing changes. More suggestions welcome. These are quite expensive CF cards. Thanks again Robert --- End of Forwarded Message ___ 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: Invalid fdisk partition table found (fwd)
On Thu, 24 Nov 2011 12:16:17 +0100 Julian H. Stacey j...@berklix.com wrote: Hi, Please keep this on list. Hi Julian, I noticed soon after my response that I must have hit reply instead of all so I resent my information to questions@. This morning I didn't see my email to questions@ so I checked the archives and my response is there. No idea why it did not get sent out to the masses. Anyway, I am still having this problem so I will paste my response below. Julian and Warren thanks for the responses. On Wed, 23 Nov 2011 22:08:00 +0100 Julian H. Stacey j...@berklix.com wrote: Robert wrote: Greetings [robert@dell64] ~ uname -a FreeBSD dell64.shasta204.local 8.2-STABLE FreeBSD 8.2-STABLE #34: Fri Nov 18 06:43:01 PST 2011 root@dell64.shasta204.local:/usr/obj/usr/src/sys/GENERIC amd64 I have two Lexar Professional 600X 16GB compact flash cards that are unusable. fdisk shows: clip Is there any way I can restore these CF cards to 16GB? Any help or suggestions will be greatly appreciated. @ suggestions: 1 Try bsdlabel -B -w -r /dev/da1 [robert@dell64] ~ sudo bsdlabel -B -w -r /dev/da1 Password: [robert@dell64] ~ echo unplug, reinsert Not sure if you actually wanted me to unplug and reinsert the CF card...so I did both [robert@dell64] ~ echo unplug, reinsert unplug, reinsert and physically unplugged and reinserted the CF card newfs /dev/da1a ^ ??? [robert@dell64] ~ sudo newfs /dev/da1a newfs: /dev/da1a: could not find special device [robert@dell64] ~ sudo newfs /dev/da1 /dev/da1: 29.5MB (60480 sectors) block size 16384, fragment size 2048 using 4 cylinder groups of 7.39MB, 473 blks, 960 inodes. super-block backups (for fsck -b #) at: 160, 15296, 30432, 45568 cg 0: bad magic number [robert@dell64] ~ fdisk /dev/da1 *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 32, size 59360 (28 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 28/ head 63/ sector 32 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED No change from before. 2 Base of _my_ man fdisk When running multi user, you cannot write unless you first run this: sysctl kern.geom.debugflags=16 I had failed to mention in the original post that I had seen something in my searches about problems since 7.1. I had tried booting from an old 6.2 disk and attempted all of this under fixit with no luck. And also tried in single user mode. Warren, [robert@dell64] ~ sudo gpart destroy -F da1 gpart: geom 'da1': Invalid argument [robert@dell64] ~ sudo gpart create -s GPT da1 da1 created [robert@dell64] ~ sudo gpart bootcode -b /boot/pmbr da1 bootcode written to da1 [robert@dell64] ~ sudo gpart destroy -F da1 da1 destroyed [robert@dell64] ~ fdisk /dev/da1 *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 32, size 59360 (28 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 28/ head 63/ sector 32 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED I see the flashing lights like it is writing to the CF card but nothing changes. More suggestions welcome. These are quite expensive CF cards. Thanks again Robert ___ 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: Invalid fdisk partition table found (fwd)
On Thu, 24 Nov 2011, Robert wrote: [robert@dell64] ~ sudo gpart destroy -F da1 da1 destroyed [robert@dell64] ~ fdisk /dev/da1 *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found The partition table was cleared. Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 32, size 59360 (28 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 28/ head 63/ sector 32 And it starts with a default table equal to the size of the drive. I see the flashing lights like it is writing to the CF card but nothing changes. More suggestions welcome. These are quite expensive CF cards. The dd/fdisk and gpart results show the same problem, so it likely isn't in the partitioning. Do both cards report the same size? I found recently that there is some oddness with certain Sandisk flash memory that made it non-responsive to anything. FreeBSD couldn't do a thing with it. Before throwing it away, I tried it on a Windows Vista system... which recognized and formatted it without a complaint. Now it works on everything. Special vendor-specific code in Windows? Another option would be to attempt formatting the cards with a camera. ___ 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
Invalid fdisk partition table found
Greetings [robert@dell64] ~ uname -a FreeBSD dell64.shasta204.local 8.2-STABLE FreeBSD 8.2-STABLE #34: Fri Nov 18 06:43:01 PST 2011 root@dell64.shasta204.local:/usr/obj/usr/src/sys/GENERIC amd64 I have two Lexar Professional 600X 16GB compact flash cards that are unusable. fdisk shows: [robert@dell64] ~ fdisk /dev/da1 *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 32, size 59360 (28 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 28/ head 63/ sector 32 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED It shows only 28 MB instead of 16GB. I have tried to change the type from 165 (FreeBSD) to msdosfs types 6 11 or 12 using fdisk -u and fdisk -i and also sade. I do not get and error but when finished it still shows the same data. I have tried to zero it out using dd if=/dev/zero of=/dev/da1 bs=1m and nothing changes. I have tried different block sizes and counts to no avail. Is there any way I can restore these CF cards to 16GB? Any help or suggestions will be greatly appreciated. TIA Robert RobertRobert ___ 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: Invalid fdisk partition table found
Robert wrote: Greetings [robert@dell64] ~ uname -a FreeBSD dell64.shasta204.local 8.2-STABLE FreeBSD 8.2-STABLE #34: Fri Nov 18 06:43:01 PST 2011 root@dell64.shasta204.local:/usr/obj/usr/src/sys/GENERIC amd64 I have two Lexar Professional 600X 16GB compact flash cards that are unusable. fdisk shows: [robert@dell64] ~ fdisk /dev/da1 *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 32, size 59360 (28 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 28/ head 63/ sector 32 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED It shows only 28 MB instead of 16GB. I have tried to change the type from 165 (FreeBSD) to msdosfs types 6 11 or 12 using fdisk -u and fdisk -i and also sade. I do not get and error but when finished it still shows the same data. I have tried to zero it out using dd if=/dev/zero of=/dev/da1 bs=1m and nothing changes. I have tried different block sizes and counts to no avail. Is there any way I can restore these CF cards to 16GB? Any help or suggestions will be greatly appreciated. @ suggestions: 1 Try bsdlabel -B -w -r /dev/da1 echo unplug, reinsert newfs /dev/da1a 2 Base of _my_ man fdisk When running multi user, you cannot write unless you first run this: sysctl kern.geom.debugflags=16 It looks like I never got round to sending in a send-pr for that, so feel free looks like its been that way at ;east since 7.1.see http://berklix.com/~jhs/src/bsd/fixes/FreeBSD/src/gen/sbin/fdisk/ Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below not above, cumulative like a play script, indent with . Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. ___ 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: Invalid fdisk partition table found
Julian H. Stacey j...@berklix.com writes: @ suggestions: 1 Try bsdlabel -B -w -r /dev/da1 echo unplug, reinsert newfs /dev/da1a 2 Base of _my_ man fdisk When running multi user, you cannot write unless you first run this: sysctl kern.geom.debugflags=16 It looks like I never got round to sending in a send-pr for that, so feel free looks like its been that way at least since 7.1.see http://berklix.com/~jhs/src/bsd/fixes/FreeBSD/src/gen/sbin/fdisk/ I thought I had seen a mention of that somewhere, so I grep'ed the man pages. I found hints on geom(4) and boot0cfg(8), but they certainly aren't obvious. -- Carl Johnsonca...@peak.org ___ 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: Invalid fdisk partition table found
Hi, Reference: From: Carl Johnson ca...@peak.org Date: Wed, 23 Nov 2011 14:53:41 -0800 Message-id: 87bos2e9hm.fsf@oak.localnet Carl Johnson wrote: Julian H. Stacey j...@berklix.com writes: @ suggestions: 1 Try bsdlabel -B -w -r /dev/da1 echo unplug, reinsert newfs /dev/da1a 2 Base of _my_ man fdisk When running multi user, you cannot write unless you first run this: sysctl kern.geom.debugflags=16 It looks like I never got round to sending in a send-pr for that, so feel free looks like its been that way at least since 7.1.see http://berklix.com/~jhs/src/bsd/fixes/FreeBSD/src/gen/sbin/fdisk/ I thought I had seen a mention of that somewhere, so I grep'ed the man pages. I found hints on geom(4) and boot0cfg(8), but they certainly aren't obvious. Yup, bit me too long ago, presumably from my patch, bit me at 7.1 OK I'll bung in a quick send-pr Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below not above, cumulative like a play script, indent with . Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. ___ 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: Invalid fdisk partition table found
On Wed, 23 Nov 2011, Julian H. Stacey wrote:
2 Base of _my_ man fdisk
When running multi user, you cannot write unless you first run this:
sysctl kern.geom.debugflags=16
But that's not quite correct. Setting debugflags to 16 allows writes to
a partition that's mounted, something that should not normally be
needed. It will give an error instead of allowing writes in that case.
So if writes succeeded, that wasn't the problem.
'gpart -F destroy {device}' may help recover the CF cards.
___
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
Fw: Invalid fdisk partition table found
Just noticed that I did not include questions@. It has been a long day. Begin forwarded message: Date: Wed, 23 Nov 2011 19:21:54 -0800 From: Robert travelin...@cox.net To: Julian H. Stacey j...@berklix.com Subject: Re: Invalid fdisk partition table found Julian and Warren thanks for the responses. On Wed, 23 Nov 2011 22:08:00 +0100 Julian H. Stacey j...@berklix.com wrote: Robert wrote: Greetings [robert@dell64] ~ uname -a FreeBSD dell64.shasta204.local 8.2-STABLE FreeBSD 8.2-STABLE #34: Fri Nov 18 06:43:01 PST 2011 root@dell64.shasta204.local:/usr/obj/usr/src/sys/GENERIC amd64 I have two Lexar Professional 600X 16GB compact flash cards that are unusable. fdisk shows: clip Is there any way I can restore these CF cards to 16GB? Any help or suggestions will be greatly appreciated. @ suggestions: 1 Try bsdlabel -B -w -r /dev/da1 [robert@dell64] ~ sudo bsdlabel -B -w -r /dev/da1 Password: [robert@dell64] ~ echo unplug, reinsert Not sure if you actually wanted me to unplug and reinsert the CF card...so I did both [robert@dell64] ~ echo unplug, reinsert unplug, reinsert and physically unplugged and reinserted the CF card newfs /dev/da1a ^ ??? [robert@dell64] ~ sudo newfs /dev/da1a newfs: /dev/da1a: could not find special device [robert@dell64] ~ sudo newfs /dev/da1 /dev/da1: 29.5MB (60480 sectors) block size 16384, fragment size 2048 using 4 cylinder groups of 7.39MB, 473 blks, 960 inodes. super-block backups (for fsck -b #) at: 160, 15296, 30432, 45568 cg 0: bad magic number [robert@dell64] ~ fdisk /dev/da1 *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 32, size 59360 (28 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 28/ head 63/ sector 32 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED No change from before. 2 Base of _my_ man fdisk When running multi user, you cannot write unless you first run this: sysctl kern.geom.debugflags=16 I had failed to mention in the original post that I had seen something in my searches about problems since 7.1. I had tried booting from an old 6.2 disk and attempted all of this under fixit with no luck. And also tried in single user mode. Warren, [robert@dell64] ~ sudo gpart destroy -F da1 gpart: geom 'da1': Invalid argument [robert@dell64] ~ sudo gpart create -s GPT da1 da1 created [robert@dell64] ~ sudo gpart bootcode -b /boot/pmbr da1 bootcode written to da1 [robert@dell64] ~ sudo gpart destroy -F da1 da1 destroyed [robert@dell64] ~ fdisk /dev/da1 *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 32, size 59360 (28 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 28/ head 63/ sector 32 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED I see the flashing lights like it is writing to the CF card but nothing changes. More suggestions welcome. These are quite expensive CF cards. Thanks again Robert ___ 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: Not found slim
On Wed, 2 Nov 2011 17:15:56 -0300 Zantgo zan...@gmail.com wrote: I install slim and xfce4, and I put slim in the boot, What do you mean exactly, put slim in the boot??? when the system booting, everything works fine when login screen appears I can not type slim or move the mouse, which is the problem? Have you configured the X server properly first? Until you've done that, there's no chance of *any* X login manager (or any other X app, for that matter) working properly. READ THE HANDBOOK, *PLEASE*!!! It's available in more than one language. Follow the instructions given. Don't skip steps or cut corners. A lot of thought has gone into providing all of the documentation you need to maintain your system, but it's up to you to use it. -- Conrad J. Sabatier conr...@cox.net ___ 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: Not found slim
On Wed, 2 Nov 2011 17:15:56 -0300 Zantgo zan...@gmail.com wrote: I install slim and xfce4, and I put slim in the boot, when the system booting, everything works fine when login screen appears I can not type slim or move the mouse, which is the problem? Here's a link you *really* should read. Seriously. http://www.freebsd.org/doc/en/articles/freebsd-questions/article.html How to get the best results from the FreeBSD-questions mailing list -- Conrad J. Sabatier conr...@cox.net ___ 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
Not found slim
I install slim and xfce4, and I put slim in the boot, when the system booting, everything works fine when login screen appears I can not type slim or move the mouse, which is the problem? ___ 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: Not found slim
On Wed, 2 Nov 2011 17:15:56 -0300 Zantgo zan...@gmail.com wrote: I install slim and xfce4, and I put slim in the boot, when the system booting, everything works fine when login screen appears I can not type slim or move the mouse, which is the problem? My prime suspect would dbus not running. Had something similar and resolved it with dbus. Cheers, -- Christopher J. Ruwe TZ GMT + 1 ___ 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: Not found slim
El 02-11-2011, a las 17:48, Christopher J. Ruwe c...@cruwe.de escribió: On Wed, 2 Nov 2011 17:15:56 -0300 Zantgo zan...@gmail.com wrote: I install slim and xfce4, and I put slim in the boot, when the system booting, everything works fine when login screen appears I can not type slim or move the mouse, which is the problem? My prime suspect would dbus not running. Had something similar and resolved it with dbus. Cheers, But in my rc.conf said dbus_enable=YES -- Christopher J. Ruwe TZ GMT + 1 ___ 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 ___ 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: Not found slim
On Wed, 02 Nov 2011 15:55:47 -0500, zan...@gmail.com wrote: But in my rc.conf said dbus_enable=YES and HAL? Your Xorg was probably compiled with HAL. I've had this problem before though and the fix was to recompile X without HAL. Sucks to not be able to plugplay though. ___ 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: Not found slim
El 02-11-2011, a las 18:19, Mark Felder f...@feld.me escribió: On Wed, 02 Nov 2011 15:55:47 -0500, zan...@gmail.com wrote: But in my rc.conf said dbus_enable=YES and HAL? Your Xorg was probably compiled with HAL. I've had this problem before though and the fix was to recompile X without HAL. Sucks to not be able to plugplay though. hal also on that of the installation of Xorg, do not set anything after xorg pkg_add-r, nor have I installed the nvidia driver, which I configured in xorg? ___ 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 ___ 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: Not found slim
2011/11/2, Zantgo zan...@gmail.com: I install slim and xfce4, and I put slim in the boot, when the system booting, everything works fine when login screen appears I can not type slim or move the mouse, which is the problem? Did you read about xorg in handbook?, did you read the message when slim finished the installation?, check the file rc.conf, add slim_enable=YES, hald_enable=YES, dbus_enable=YES, also you should do Xorg -configure, friend you should do it, you SHOULD READ THE HANDBOOK or use man ___ 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 -- Edguitar ;) http://cybernautape.blogspot.com ___ 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: nss-3.12.11.with.ckbi.1.87.tar.gz: File unavailable (e.g., file not found, no access)
On Mon, Sep 5, 2011 at 8:33 PM, Dan Nelson dnel...@allantgroup.com wrote: In the last episode (Sep 05), Antonio Olivares said: Dear folks, sorry to bother you guys, but I am encountering a problem updating I need 4 ports only, but can't get past the error above: Building new INDEX files... done. === New version available: ca_root_nss-3.12.11_1 === New version available: gtk-2.24.6 === New version available: gtk-update-icon-cache-2.24.6 === New version available: firefox-6.0.1,1 === 402 total installed ports === 4 have new versions available grullahighschool# portmaster -a === License check disabled, port has not defined LICENSE === Found saved configuration for ca_root_nss-3.12.9 = nss-3.12.11.with.ckbi.1.87.tar.gz doesn't seem to exist in /usr/ports/distfiles//. = Attempting to fetch http://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz fetch: http://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz: No address record This is your main problem; you aren't able to resolve ftp.mozilla.org for some reason. The other sites are mirrors that either aren't mirroring the security subdirectory, or haven't updated their mirror recently enough to have a copy of that file. I tried to get the file manually, but it does not exist. Thanks for advice/suggestions/comments. It definitely does exist at the above url. Since you seem to be having DNS issues, try putting 63.245.209.137 ftp.mozilla.org in your /etc/hosts file and try fetching again, since that's what ftp.mozilla.org currently resolves to. Remember to remove the line after fetching, since the IP may change later. http://www.robtex.com/dns/ftp.mozilla.org#records -- Thank you very much Dan :) Adding the line to /etc/hosts does get the package and installs it. I am updated to latest. Appreciate the help. Regards, Antonio ___ 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
nss-3.12.11.with.ckbi.1.87.tar.gz: File unavailable (e.g., file not found, no access)
Dear folks, sorry to bother you guys, but I am encountering a problem updating I need 4 ports only, but can't get past the error above: Building new INDEX files... done. === New version available: ca_root_nss-3.12.11_1 === New version available: gtk-2.24.6 === New version available: gtk-update-icon-cache-2.24.6 === New version available: firefox-6.0.1,1 === 402 total installed ports === 4 have new versions available grullahighschool# portmaster -a === License check disabled, port has not defined LICENSE === Found saved configuration for ca_root_nss-3.12.9 = nss-3.12.11.with.ckbi.1.87.tar.gz doesn't seem to exist in /usr/ports/distfiles//. = Attempting to fetch http://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz fetch: http://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz: No address record = Attempting to fetch http://mirror3.mirrors.tds.net/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz fetch: http://mirror3.mirrors.tds.net/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz: Not Found = Attempting to fetch http://mozilla.isc.org/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz fetch: http://mozilla.isc.org/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz: Not Found = Attempting to fetch http://releases.mozilla.org/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz fetch: http://releases.mozilla.org/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz: No route to host = Attempting to fetch http://kyoto-mz-dl.sinet.ad.jp/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz fetch: http://kyoto-mz-dl.sinet.ad.jp/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz: Not Found = Attempting to fetch http://jp-nii01.mozilla.org/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz fetch: http://jp-nii01.mozilla.org/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz: Not Found = Attempting to fetch http://jp-nii02.mozilla.org/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz fetch: http://jp-nii02.mozilla.org/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz: Not Found = Attempting to fetch http://mozilla.mtk.nao.ac.jp/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz fetch: http://mozilla.mtk.nao.ac.jp/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz: Not Found = Attempting to fetch http://mirror.internode.on.net/pub/mozilla/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz fetch: http://mirror.internode.on.net/pub/mozilla/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz: Not Found = Attempting to fetch http://ftp.acc.umu.se/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz fetch: http://ftp.acc.umu.se/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz: Moved Temporarily = Attempting to fetch http://mozilla.c3sl.ufpr.br/releases/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz fetch: http://mozilla.c3sl.ufpr.br/releases/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz: Not Found = Attempting to fetch http://www.gtlib.cc.gatech.edu/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz fetch: http://www.gtlib.cc.gatech.edu/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz: Not Found = Attempting to fetch ftp://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz fetch: ftp://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz: No address record = Attempting to fetch ftp://ftp.fh-wolfenbuettel.de/pub/www/mozilla/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz fetch: ftp://ftp.fh-wolfenbuettel.de/pub/www/mozilla/security/nss
Re: nss-3.12.11.with.ckbi.1.87.tar.gz: File unavailable (e.g., file not found, no access)
In the last episode (Sep 05), Antonio Olivares said: Dear folks, sorry to bother you guys, but I am encountering a problem updating I need 4 ports only, but can't get past the error above: Building new INDEX files... done. === New version available: ca_root_nss-3.12.11_1 === New version available: gtk-2.24.6 === New version available: gtk-update-icon-cache-2.24.6 === New version available: firefox-6.0.1,1 === 402 total installed ports === 4 have new versions available grullahighschool# portmaster -a === License check disabled, port has not defined LICENSE === Found saved configuration for ca_root_nss-3.12.9 = nss-3.12.11.with.ckbi.1.87.tar.gz doesn't seem to exist in /usr/ports/distfiles//. = Attempting to fetch http://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz fetch: http://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi.1.87.tar.gz: No address record This is your main problem; you aren't able to resolve ftp.mozilla.org for some reason. The other sites are mirrors that either aren't mirroring the security subdirectory, or haven't updated their mirror recently enough to have a copy of that file. I tried to get the file manually, but it does not exist. Thanks for advice/suggestions/comments. It definitely does exist at the above url. Since you seem to be having DNS issues, try putting 63.245.209.137 ftp.mozilla.org in your /etc/hosts file and try fetching again, since that's what ftp.mozilla.org currently resolves to. Remember to remove the line after fetching, since the IP may change later. http://www.robtex.com/dns/ftp.mozilla.org#records -- Dan Nelson dnel...@allantgroup.com ___ 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: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
On 2011-08-13 12:08, Roland Smith wrote:
On Sat, Aug 13, 2011 at 09:51:41AM +0200, Hartmann, O. wrote:
On 08/13/11 09:26, Roland Smith wrote:
On Sat, Aug 13, 2011 at 12:43:52AM +0200, Hartmann, O. wrote:
On 08/12/11 22:54, Roland Smith wrote:
On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote:
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
Does this file actually exist if you extract the snapshot? And are the
permissions et cetera OK?
Roland
No, it does not.
What I did so far over night:
I deleted /var/db/portsnap as well as /usr/ports/. Then I tried again.
Again failure.
After that it got the ports tree via CVS (make update in /usr/ports).
Everything seems
all right. I tried portsnap again. portsnap compalins about a
non-portsnap-created /usr/ports
and please me to use 'extract'. I do ... but then I run into the very
same failure:
(portsnap fetch extract:)
/usr/ports/devel//
/usr/ports/devel/ccdoc/
/usr/ports/devel/ccrtp/
/usr/ports/devel/cdash/
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
not
found -- snapshot corrupt.
I've been looking at the portsnap shellscript. This error message is generated
by the shell's built-in test command, specifically '[ -r'. It is looking for a
file that was extracted with tar. So the place to look for the bug is IMO
1) the portsnap script itself (differences between 8.2 and 9?)
2) the sh(1)'s built-in test command (ditto)
3) tar (ditto)
When you run 'portsnap fetch' it downloads a tgz archive and unpacks it with
tar(1). What you could try is to comment out the line 'rm ${SNAPSHOTHASH}.tgz'
in portsnap, and test if the tgz file extracts differently using an
8.2-RELEASE tar and the 9-CURRENT tar. If so, that would be a bug!
Roland
Just a me too!. It happens for me on a recently updated 9-current
virtual machine, built with clang.
Regards!
--
Niclas
___
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: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
On 08/14/11 11:48, Niclas Zeising wrote:
On 2011-08-13 12:08, Roland Smith wrote:
On Sat, Aug 13, 2011 at 09:51:41AM +0200, Hartmann, O. wrote:
On 08/13/11 09:26, Roland Smith wrote:
On Sat, Aug 13, 2011 at 12:43:52AM +0200, Hartmann, O. wrote:
On 08/12/11 22:54, Roland Smith wrote:
On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote:
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
Does this file actually exist if you extract the snapshot? And are the
permissions et cetera OK?
Roland
No, it does not.
What I did so far over night:
I deleted /var/db/portsnap as well as /usr/ports/. Then I tried again.
Again failure.
After that it got the ports tree via CVS (make update in /usr/ports).
Everything seems
all right. I tried portsnap again. portsnap compalins about a
non-portsnap-created /usr/ports
and please me to use 'extract'. I do ... but then I run into the very
same failure:
(portsnap fetch extract:)
/usr/ports/devel//
/usr/ports/devel/ccdoc/
/usr/ports/devel/ccrtp/
/usr/ports/devel/cdash/
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not
found -- snapshot corrupt.
I've been looking at the portsnap shellscript. This error message is generated
by the shell's built-in test command, specifically '[ -r'. It is looking for a
file that was extracted with tar. So the place to look for the bug is IMO
1) the portsnap script itself (differences between 8.2 and 9?)
2) the sh(1)'s built-in test command (ditto)
3) tar (ditto)
When you run 'portsnap fetch' it downloads a tgz archive and unpacks it with
tar(1). What you could try is to comment out the line 'rm ${SNAPSHOTHASH}.tgz'
in portsnap, and test if the tgz file extracts differently using an
8.2-RELEASE tar and the 9-CURRENT tar. If so, that would be a bug!
Roland
Just a me too!. It happens for me on a recently updated 9-current
virtual machine, built with clang.
Regards!
Just got a notebook, build with the old gcc 4.2 of the system FreeBSD
9.0/amd64 -r224579: portsnap works as expected.
I will build a most recent system on that box (with systems's outdated
gcc 4.2) and I'll report if the problem is still present.
By the way: My boxes of failure are all built with CLANG.
Oliver
___
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: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
2011/8/14 Hartmann, O. ohart...@zedat.fu-berlin.de:
On 08/14/11 11:48, Niclas Zeising wrote:
On 2011-08-13 12:08, Roland Smith wrote:
On Sat, Aug 13, 2011 at 09:51:41AM +0200, Hartmann, O. wrote:
On 08/13/11 09:26, Roland Smith wrote:
On Sat, Aug 13, 2011 at 12:43:52AM +0200, Hartmann, O. wrote:
On 08/12/11 22:54, Roland Smith wrote:
On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote:
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
Does this file actually exist if you extract the snapshot? And are the
permissions et cetera OK?
Roland
No, it does not.
What I did so far over night:
I deleted /var/db/portsnap as well as /usr/ports/. Then I tried again.
Again failure.
After that it got the ports tree via CVS (make update in /usr/ports).
Everything seems
all right. I tried portsnap again. portsnap compalins about a
non-portsnap-created /usr/ports
and please me to use 'extract'. I do ... but then I run into the very
same failure:
(portsnap fetch extract:)
/usr/ports/devel//
/usr/ports/devel/ccdoc/
/usr/ports/devel/ccrtp/
/usr/ports/devel/cdash/
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
not
found -- snapshot corrupt.
I've been looking at the portsnap shellscript. This error message is
generated
by the shell's built-in test command, specifically '[ -r'. It is looking
for a
file that was extracted with tar. So the place to look for the bug is IMO
1) the portsnap script itself (differences between 8.2 and 9?)
2) the sh(1)'s built-in test command (ditto)
3) tar (ditto)
When you run 'portsnap fetch' it downloads a tgz archive and unpacks it
with
tar(1). What you could try is to comment out the line 'rm
${SNAPSHOTHASH}.tgz'
in portsnap, and test if the tgz file extracts differently using an
8.2-RELEASE tar and the 9-CURRENT tar. If so, that would be a bug!
Roland
Just a me too!. It happens for me on a recently updated 9-current
virtual machine, built with clang.
Regards!
Just got a notebook, build with the old gcc 4.2 of the system FreeBSD
9.0/amd64 -r224579: portsnap works as expected.
I will build a most recent system on that box (with systems's outdated gcc
4.2) and I'll report if the problem is still present.
By the way: My boxes of failure are all built with CLANG.
Oliver
Trying again today, with my 9.0-BETA1 amd64 box built with clang.
Not the same error, but the same kind when using portsnap extract :
/usr/ports/lang/p5-JavaScript-Value-Escape/
/usr/ports/lang/p5-JavaScript/
/usr/ports/lang/p5-List-MoreUtils/
/usr/ports/lang/p5-Modern-Perl/
/usr/ports/lang/p5-POE-Component-Hailo/
files/b54a58da6d23d31f19a9105f70af03ef797aba8db6bdbc03d6deb72e62011d56.gz
not found -- snapshot corrupt.
This file is not present in /var/db/portsnap/files/.
# ll /var/db/portsnap/files/ | wc -l
22862
This was after removing /var/db/portsnap/files/ and
/var/db/portsnap/t* and a fresh portsnap fetch, on the portsnap5
mirror.
# fetch
http://portsnap5.freebsd.org/s/c9a2c992e8bde0c98309f76a0ecfb00eb76558c7c3dcbd0405a88316b775e66b.tgz
# tar tf c9a2c992e8bde0c98309f76a0ecfb00eb76558c7c3dcbd0405a88316b775e66b.tgz
| grep b54a58
nothing...
I tried on portsnap2 and the file was not present in
c9a2c992e8bde0c98309f76a0ecfb00eb76558c7c3dcbd0405a88316b775e66b.tgz
--
Olivier Smedts _
ASCII ribbon campaign ( )
e-mail: oliv...@gid0.org - against HTML email vCards X
www: http://www.gid0.org - against proprietary attachments / \
Il y a seulement 10 sortes de gens dans le monde :
ceux qui comprennent le binaire,
et ceux qui ne le comprennent pas.
___
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: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
On Sun Aug 14 11, Niclas Zeising wrote:
On 2011-08-13 12:08, Roland Smith wrote:
On Sat, Aug 13, 2011 at 09:51:41AM +0200, Hartmann, O. wrote:
On 08/13/11 09:26, Roland Smith wrote:
On Sat, Aug 13, 2011 at 12:43:52AM +0200, Hartmann, O. wrote:
On 08/12/11 22:54, Roland Smith wrote:
On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote:
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
Does this file actually exist if you extract the snapshot? And are the
permissions et cetera OK?
Roland
No, it does not.
What I did so far over night:
I deleted /var/db/portsnap as well as /usr/ports/. Then I tried again.
Again failure.
After that it got the ports tree via CVS (make update in /usr/ports).
Everything seems
all right. I tried portsnap again. portsnap compalins about a
non-portsnap-created /usr/ports
and please me to use 'extract'. I do ... but then I run into the very
same failure:
(portsnap fetch extract:)
/usr/ports/devel//
/usr/ports/devel/ccdoc/
/usr/ports/devel/ccrtp/
/usr/ports/devel/cdash/
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
not
found -- snapshot corrupt.
I've been looking at the portsnap shellscript. This error message is
generated
by the shell's built-in test command, specifically '[ -r'. It is looking
for a
file that was extracted with tar. So the place to look for the bug is IMO
1) the portsnap script itself (differences between 8.2 and 9?)
2) the sh(1)'s built-in test command (ditto)
3) tar (ditto)
When you run 'portsnap fetch' it downloads a tgz archive and unpacks it with
tar(1). What you could try is to comment out the line 'rm
${SNAPSHOTHASH}.tgz'
in portsnap, and test if the tgz file extracts differently using an
8.2-RELEASE tar and the 9-CURRENT tar. If so, that would be a bug!
Roland
Just a me too!. It happens for me on a recently updated 9-current
virtual machine, built with clang.
same here:
/usr/ports/databases/gigabase/
/usr/ports/databases/godis/
files/39644d98f9e9b9d9a362cbfc075a996683e8a611a4362d883247c9a2e2fa2658.gz not
found -- snapshot corrupt.
running r224841 on amd64 built with base clang.
Regards!
--
Niclas
___
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: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
2011/8/14 Alexander Best arun...@freebsd.org:
On Sun Aug 14 11, Niclas Zeising wrote:
On 2011-08-13 12:08, Roland Smith wrote:
On Sat, Aug 13, 2011 at 09:51:41AM +0200, Hartmann, O. wrote:
On 08/13/11 09:26, Roland Smith wrote:
On Sat, Aug 13, 2011 at 12:43:52AM +0200, Hartmann, O. wrote:
On 08/12/11 22:54, Roland Smith wrote:
On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote:
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
Does this file actually exist if you extract the snapshot? And are the
permissions et cetera OK?
Roland
No, it does not.
What I did so far over night:
I deleted /var/db/portsnap as well as /usr/ports/. Then I tried again.
Again failure.
After that it got the ports tree via CVS (make update in /usr/ports).
Everything seems
all right. I tried portsnap again. portsnap compalins about a
non-portsnap-created /usr/ports
and please me to use 'extract'. I do ... but then I run into the very
same failure:
(portsnap fetch extract:)
/usr/ports/devel//
/usr/ports/devel/ccdoc/
/usr/ports/devel/ccrtp/
/usr/ports/devel/cdash/
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
not
found -- snapshot corrupt.
I've been looking at the portsnap shellscript. This error message is
generated
by the shell's built-in test command, specifically '[ -r'. It is looking
for a
file that was extracted with tar. So the place to look for the bug is IMO
1) the portsnap script itself (differences between 8.2 and 9?)
2) the sh(1)'s built-in test command (ditto)
3) tar (ditto)
When you run 'portsnap fetch' it downloads a tgz archive and unpacks it
with
tar(1). What you could try is to comment out the line 'rm
${SNAPSHOTHASH}.tgz'
in portsnap, and test if the tgz file extracts differently using an
8.2-RELEASE tar and the 9-CURRENT tar. If so, that would be a bug!
Roland
Just a me too!. It happens for me on a recently updated 9-current
virtual machine, built with clang.
same here:
/usr/ports/databases/gigabase/
/usr/ports/databases/godis/
files/39644d98f9e9b9d9a362cbfc075a996683e8a611a4362d883247c9a2e2fa2658.gz not
found -- snapshot corrupt.
running r224841 on amd64 built with base clang.
Aparently fixed with latest HEAD *kernel* :
# svn log -v -r224842
r224842 | rwatson | 2011-08-13 18:03:40 +0200 (sam 13 aoû 2011) | 10 lignes
Chemins modifiés :
M /head/sys/kern/vfs_syscalls.c
When falloc() was broken into separate falloc_noinstall() and finstall(),
a bug was introduced in kern_openat() such that the error from the vnode
open operation was overwritten before it was passed as an argument to
dupfdopen(). This broke operations on /dev/{stdin,stdout,stderr}. Fix
by preserving the original error number across finstall() so that it is
still available.
Approved by:re (kib)
Reported by:cognet
You won't be able to buildworld with the buggy kernel, but you can
buildkernel and reboot on the new kernel. No problems with portsnap
after that (don't know if you have to clean the old portsnap files, I
did it).
--
Olivier Smedts _
ASCII ribbon campaign ( )
e-mail: oliv...@gid0.org - against HTML email vCards X
www: http://www.gid0.org - against proprietary attachments / \
Il y a seulement 10 sortes de gens dans le monde :
ceux qui comprennent le binaire,
et ceux qui ne le comprennent pas.
___
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: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
On Sun Aug 14 11, Olivier Smedts wrote:
2011/8/14 Alexander Best arun...@freebsd.org:
On Sun Aug 14 11, Niclas Zeising wrote:
On 2011-08-13 12:08, Roland Smith wrote:
On Sat, Aug 13, 2011 at 09:51:41AM +0200, Hartmann, O. wrote:
On 08/13/11 09:26, Roland Smith wrote:
On Sat, Aug 13, 2011 at 12:43:52AM +0200, Hartmann, O. wrote:
On 08/12/11 22:54, Roland Smith wrote:
On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote:
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
Does this file actually exist if you extract the snapshot? And are the
permissions et cetera OK?
Roland
No, it does not.
What I did so far over night:
I deleted /var/db/portsnap as well as /usr/ports/. Then I tried again.
Again failure.
After that it got the ports tree via CVS (make update in /usr/ports).
Everything seems
all right. I tried portsnap again. portsnap compalins about a
non-portsnap-created /usr/ports
and please me to use 'extract'. I do ... but then I run into the very
same failure:
(portsnap fetch extract:)
/usr/ports/devel//
/usr/ports/devel/ccdoc/
/usr/ports/devel/ccrtp/
/usr/ports/devel/cdash/
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
not
found -- snapshot corrupt.
I've been looking at the portsnap shellscript. This error message is
generated
by the shell's built-in test command, specifically '[ -r'. It is looking
for a
file that was extracted with tar. So the place to look for the bug is IMO
1) the portsnap script itself (differences between 8.2 and 9?)
2) the sh(1)'s built-in test command (ditto)
3) tar (ditto)
When you run 'portsnap fetch' it downloads a tgz archive and unpacks it
with
tar(1). What you could try is to comment out the line 'rm
${SNAPSHOTHASH}.tgz'
in portsnap, and test if the tgz file extracts differently using an
8.2-RELEASE tar and the 9-CURRENT tar. If so, that would be a bug!
Roland
Just a me too!. It happens for me on a recently updated 9-current
virtual machine, built with clang.
same here:
/usr/ports/databases/gigabase/
/usr/ports/databases/godis/
files/39644d98f9e9b9d9a362cbfc075a996683e8a611a4362d883247c9a2e2fa2658.gz
not found -- snapshot corrupt.
running r224841 on amd64 built with base clang.
Aparently fixed with latest HEAD *kernel* :
# svn log -v -r224842
r224842 | rwatson | 2011-08-13 18:03:40 +0200 (sam 13 aoû 2011) | 10 lignes
Chemins modifiés :
M /head/sys/kern/vfs_syscalls.c
When falloc() was broken into separate falloc_noinstall() and finstall(),
a bug was introduced in kern_openat() such that the error from the vnode
open operation was overwritten before it was passed as an argument to
dupfdopen(). This broke operations on /dev/{stdin,stdout,stderr}. Fix
by preserving the original error number across finstall() so that it is
still available.
Approved by:re (kib)
Reported by:cognet
You won't be able to buildworld with the buggy kernel, but you can
buildkernel and reboot on the new kernel. No problems with portsnap
after that (don't know if you have to clean the old portsnap files, I
did it).
thanks. switching to a newer revision alone didn't solve the issue. however
after doing
rm -r /var/db/portsnap/files/; rm /var/db/portsnap/t*; portsnap fetch update
everything's back to normal. :)
--
Olivier Smedts _
ASCII ribbon campaign ( )
e-mail: oliv...@gid0.org - against HTML email vCards X
www: http://www.gid0.org - against proprietary attachments / \
Il y a seulement 10 sortes de gens dans le monde :
ceux qui comprennent le binaire,
et ceux qui ne le comprennent pas.
___
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: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
On Sat, Aug 13, 2011 at 12:43:52AM +0200, Hartmann, O. wrote: On 08/12/11 22:54, Roland Smith wrote: On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz Does this file actually exist if you extract the snapshot? And are the permissions et cetera OK? Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpXSyMn0lIgR.pgp Description: PGP signature
Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
On 08/13/11 09:26, Roland Smith wrote: On Sat, Aug 13, 2011 at 12:43:52AM +0200, Hartmann, O. wrote: On 08/12/11 22:54, Roland Smith wrote: On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz Does this file actually exist if you extract the snapshot? And are the permissions et cetera OK? Roland No, it does not. What I did so far over night: I deleted /var/db/portsnap as well as /usr/ports/. Then I tried again. Again failure. After that it got the ports tree via CVS (make update in /usr/ports). Everything seems all right. I tried portsnap again. portsnap compalins about a non-portsnap-created /usr/ports and please me to use 'extract'. I do ... but then I run into the very same failure: (portsnap fetch extract:) /usr/ports/devel// /usr/ports/devel/ccdoc/ /usr/ports/devel/ccrtp/ /usr/ports/devel/cdash/ files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt. Oliver ___ 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: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
On Sat, Aug 13, 2011 at 09:51:41AM +0200, Hartmann, O. wrote:
On 08/13/11 09:26, Roland Smith wrote:
On Sat, Aug 13, 2011 at 12:43:52AM +0200, Hartmann, O. wrote:
On 08/12/11 22:54, Roland Smith wrote:
On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote:
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
Does this file actually exist if you extract the snapshot? And are the
permissions et cetera OK?
Roland
No, it does not.
What I did so far over night:
I deleted /var/db/portsnap as well as /usr/ports/. Then I tried again.
Again failure.
After that it got the ports tree via CVS (make update in /usr/ports).
Everything seems
all right. I tried portsnap again. portsnap compalins about a
non-portsnap-created /usr/ports
and please me to use 'extract'. I do ... but then I run into the very
same failure:
(portsnap fetch extract:)
/usr/ports/devel//
/usr/ports/devel/ccdoc/
/usr/ports/devel/ccrtp/
/usr/ports/devel/cdash/
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not
found -- snapshot corrupt.
I've been looking at the portsnap shellscript. This error message is generated
by the shell's built-in test command, specifically '[ -r'. It is looking for a
file that was extracted with tar. So the place to look for the bug is IMO
1) the portsnap script itself (differences between 8.2 and 9?)
2) the sh(1)'s built-in test command (ditto)
3) tar (ditto)
When you run 'portsnap fetch' it downloads a tgz archive and unpacks it with
tar(1). What you could try is to comment out the line 'rm ${SNAPSHOTHASH}.tgz'
in portsnap, and test if the tgz file extracts differently using an
8.2-RELEASE tar and the 9-CURRENT tar. If so, that would be a bug!
Roland
--
R.F.Smith http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
pgpZ0qmATYvWX.pgp
Description: PGP signature
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
Since today, I can not update my ports tree due to this error as follows. This happens on all boxes running FreeBSD, the version of the OS (FBSD 8.2/9.0) doesn't matter. What's up with the ports collection? Regards, Oliver Extracting new files: /usr/ports/GIDs /usr/ports/UIDs /usr/ports/audio/teamspeak3-server/ /usr/ports/audio/xmms-fc/ /usr/ports/cad/admesh/ /usr/ports/databases/postgresql82-server/ /usr/ports/databases/postgresql83-server/ /usr/ports/databases/postgresql84-server/ /usr/ports/databases/postgresql90-server/ /usr/ports/devel/Makefile /usr/ports/devel/cdash/ files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt. ___ 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
