7;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 --
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 bo
On Thu, Sep 12, 2013 at 12:36 AM, Matthew Seaman
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 fou
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 up
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
27;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
- Original Message -
> From: Tijl Coosemans
> To: Quark
> Cc: "freebsd-questions@freebsd.org"
> Sent: Tuesday, 27 August 2013 1:41 PM
> Subject: Re: c++11 question: clang++ 3.3 header not found
>
> On Tue, 27 Aug 2013 15:22:49 +0800 (SGT) Quark wr
return 0;
> }
>
>
> error received is
> % clang++ -otest test.cc
>
> test.cc:2:10: fatal error: 'future' file not found
> #include
> ^
> 1 error generated.
>
> I guess clang is re-using system headers which belong to older gcc 4.2
> I
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
> ^
> 1
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
> ^
> 1 err
test.cc
test.cc:2:10: fatal error: 'future' file not found
#include
^
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?
_
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.
id
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 syste
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 b
ome 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
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 th
> 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 sphi
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? Obvio
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 sol
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 inst
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'
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 &quo
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.or
raries-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, se
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 refere
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
On Thu, 16 Feb 2012 09:08:54 -0600
Antonio Olivares wrote:
> On Thu, Feb 16, 2012 at 8:18 AM, Ryan Frederick
> 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 se
On Thu, Feb 16, 2012 at 9:08 AM, Antonio Olivares
wrote:
> On Thu, Feb 16, 2012 at 8:18 AM, Ryan Frederick
> 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
On Thu, Feb 16, 2012 at 8:18 AM, Ryan Frederick
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
' 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 &quo
x27;;'
/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
Antonio Olivares 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
>> 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
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 followe
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 problem
Thanks Rob and Lowell,
I will keep this information handy. It was helpful.
On Tue, Jan 31, 2012 at 4:22 AM, Rob Farmer wrote:
> On Mon, Jan 30, 2012 at 10:39 AM, Rick Miller
> wrote:
>> Thanks Rob...
>>
>> I put the kernel conf file in the source tree as opposed to linking to
>> it and it cer
On Mon, Jan 30, 2012 at 10:39 AM, Rick Miller 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 h
Rick Miller 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
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/kernel
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=/M
On Sun, Jan 29, 2012 at 9:03 AM, Rick Miller 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
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 configura
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,
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 mailto:jimmie...@gmail.com>> wrote:
Even after following said instruction in UPDATING, libxcb-aux.so.0
does not get install
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 mailto:jimmie...@gmail.com>> wrote:
Even after following said instruction in UPDATING, libxcb-aux.so.0
does not get install
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 mailto:jimmie...@gmail.com>> wrote:
Even after following said instruction in UPDATING, libxcb-aux.so.0
does not get install
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 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 w
On 01/17/12 15:39, Michael Johnson wrote:
On Tue, Jan 17, 2012 at 3:04 PM, Jimmie James 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'
On Tue, Jan 17, 2012 at 3:04 PM, Jimmie James 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
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
d, 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
> >
> > S
robably 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
>
>
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
On Wed, 2 Nov 2011 17:15:56 -0300
Zantgo 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.
h
On Wed, 2 Nov 2011 17:15:56 -0300
Zantgo 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?
2011/11/2, Zantgo :
> 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
El 02-11-2011, a las 18:19, Mark Felder escribió:
> On Wed, 02 Nov 2011 15:55:47 -0500, 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
On Wed, 02 Nov 2011 15:55:47 -0500, 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 plug&play though.
__
El 02-11-2011, a las 17:48, "Christopher J. Ruwe" escribió:
> On Wed, 2 Nov 2011 17:15:56 -0300
> Zantgo 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, whic
On Wed, 2 Nov 2011 17:15:56 -0300
Zantgo 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
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.freeb
On Mon, Sep 5, 2011 at 8:33 PM, Dan Nelson 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.
>>
>>
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
s/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.
ilure.
> >> >> 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
> >> >&
>> 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 f
orts
> >> 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/
&g
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-cre
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
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 fe
> 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/
&g
crtp/
/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 u
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
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
This file is relatively recent; When I used portsnap yesterday, it wasn't
there, and now it is.
I do a postrmaster on a
On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote:
> >> files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
> > This file is relatively recent; When I used portsnap yesterday, it wasn't
> > there, and now it is.
> I do a postrmaster on a nearly daily basis. This occ
running FreeBSD, the version of the OS (FBSD
8.2/9.0) doesn't
matter. What's up with the ports collection?
Probably nothing.
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not
found -- snapshot corrupt.
This looks like a portsnap error. Remove everything
ing FreeBSD, the version of the OS (FBSD
> >> 8.2/9.0) doesn't
> >> matter. What's up with the ports collection?
> >
> > Probably nothing.
> >
> >> files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
> >> not
>
the ports collection?
Probably nothing.
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not
found -- snapshot corrupt.
This looks like a portsnap error. Remove everything in /var/db/portsnap, and
run 'portsnap fetch extract'.
Roland
That was the first I di
matter. What's up with the ports collection?
>
> Probably nothing.
>
>> files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not
>> found -- snapshot corrupt.
>
> This looks like a portsnap error. Remove everything in /var/db/portsnap, and
> ru
the OS (FBSD 8.2/9.0) doesn't
> > matter. What's up with the ports collection?
>
> Probably nothing.
>
> > files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
> > not found -- snapshot corrupt.
>
> This looks like a portsnap error.
ion?
Probably nothing.
> files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not
> found -- snapshot corrupt.
This looks like a portsnap error. Remove everything in /var/db/portsnap, and
run 'portsnap fetch extract'.
Roland
--
R.F.Smith
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 cor
t's up with the ports collection?
>
> You're using portsnap? What if you try to update per CVS?
>
>
>
>> /usr/ports/devel/cdash/
>> files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not
>> found -- snapshot corrupt.
>
> I t
You're using portsnap? What if you try to update per CVS?
> /usr/ports/devel/cdash/
> files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not
> found -- snapshot corrupt.
I think this last message got a bit de-arranged by quoting.
The file with the long name bel
ash/
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 "fr
#x27;m getting this error message:
>
> /libexec/ld-elf.so.1: Shared object "libkipi.so.7" not found, required
> by "digikam"
>
> I've tried to rebuild digikam and all dependencies but it's still the
> same. My ports tree is updated. I'm runni
Hello,
I'm having hard times with digikam. It used to work properly but then,
after one of the updates (I'm not able to track it) it stopped.
When I try to run digikam I'm getting this error message:
/libexec/ld-elf.so.1: Shared object "libkipi.so.7" not found, requ
-sU
ELF interpreter /libexec/ld-elf.so.1 not found
Abort
locate ld-elf.so.1
/libexec/ld-elf.so.1
/usr/libexec/ld-elf.so.1
/usr/share/man/man1/ld-elf.so.1.1.gz
Len
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-q
On 01/27/11 00:21, b. f. wrote:
Da Rock wrote:
gcc -Wall -Wformat-security -Wno-format-zero-length -g -O3 -I.
-I/usr/include -I/usr/local/include -DLIBDIR='"/lib/l2tpns"'
-DETCDIR='"/etc/l2tpns"' -DSTATISTICS -DSTAT_CALLS -DRINGBUFFER
-DHAVE_EPOLL -DBGP -c -o arp.o arp.c
In file included f
Da Rock wrote:
> gcc -Wall -Wformat-security -Wno-format-zero-length -g -O3 -I.
> -I/usr/include -I/usr/local/include -DLIBDIR='"/lib/l2tpns"'
> -DETCDIR='"/etc/l2tpns"' -DSTATISTICS -DSTAT_CALLS -DRINGBUFFER
> -DHAVE_EPOLL -DBGP -c -o arp.o arp.c
> In file included from arp.c:8:
> /usr/include/n
'AF_PACKET' undeclared (first use in this function)
arp.c:29: warning: unused variable 'sll'
gmake: *** [arp.o] Error 1
Incidentally I changed the include in arp.c from linux/if_packet.h to
netinet/if_ether.h. My problem lies in the file not found error for
libcli.h, though.
st use in this function)
arp.c:29: warning: unused variable 'sll'
gmake: *** [arp.o] Error 1
Incidentally I changed the include in arp.c from linux/if_packet.h to
netinet/if_ether.h. My problem lies in the file not found error for
libcli.h, though. ls /usr/local/include shows libcl
epkey 0120119850 weptxkey 1 up
wlan0
r...@olimpico-freebsd 21:59:54 ~ # [0]
I see the following in dmesg output:
wlan0: Ethernet address: 90:4c:e5:21:44:ec
bwn_v4_lp_ucode15: firmware image loaded, but did not register
bwn0: the fw file(bwn_v4_lp_ucode15) not found
bwn-open_v4_lp_ucode15: could no
Krad,
Thank you for the tip. I've changed the "." to the correct value.
Matthew
On 1 October 2010 21:16, CyberLeo Kitsana wrote:
On 10/01/2010 12:52 PM, Matthew wrote:
I would be grateful for any pointers on how to resolve this. I suspect
the error message may not be exactly descri
CyberLeo Kitsana,
Thank you so much for the history and evolution on Bind expected
directory structures. It enabled me to jump through that tough spot.
Thanks again,
Matthew
On 10/01/2010 12:52 PM, Matthew wrote:
I would be grateful for any pointers on how to resolve this. I suspect
the
On 1 October 2010 21:16, CyberLeo Kitsana wrote:
> On 10/01/2010 12:52 PM, Matthew wrote:
> > I would be grateful for any pointers on how to resolve this. I suspect
> > the error message may not be exactly descriptive of whats happening.
>
> Kinda.
>
> Here's a few points to keep in mind when wo
On 10/01/2010 12:52 PM, Matthew wrote:
> I would be grateful for any pointers on how to resolve this. I suspect
> the error message may not be exactly descriptive of whats happening.
Kinda.
Here's a few points to keep in mind when working with bind in FreeBSD:
* By default, named runs in a chro
addrs' '--disable-linux-caps'
'--with-openssl=/usr' '--with-randomdev=/dev/random' '--without-idn'
'--without-libxml2'
Oct 1 12:36:35 www named[4663]: *could not configure root hints from
'named.root': file not found*
Oct 1 12:36
On Monday 21 June 2010 00:57:17 Caleb Stein wrote:
> Whenever I try running an application that relies on GTK+ or QT, I get
> that error message. How should I fix this?
You must have upgraded libpng at some point and didn't notice or follow the
instructions in /usr/ports/UPDATING which tells you
In the last episode (Jun 20), Caleb Stein said:
> Whenever I try running an application that relies on GTK+ or QT, I get
> that error message. How should I fix this?
You must have upgraded your libpng port, and either the application or one
of the shared libraries it uses hasn't been rebuilt sinc
1 - 100 of 852 matches
Mail list logo