On 12/4/06, FreeBSD WickerBill <[EMAIL PROTECTED]> wrote:
"can't cd to /usr/ports"
I'm getting this in every port I try to make...it begins the make and then
errors out with 'Error code 2' telling me it can't cd into the ports
work/portname directory. This has been happening for about a week. I
Current FreeBSD problem reports
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including experimental
development code and obsolete releases.
Bugs can be in one of several states:
o - open
A problem report has bee
On 12/3/06, FreeBSD WickerBill <[EMAIL PROTECTED]> wrote:
"can't cd to /usr/ports"
I'm getting this in every port I try to make...it begins the make and then
errors out with 'Error code 2' telling me it can't cd into the ports
work/portname directory. This has been happening for about a week. I
No Problem:
[/usr/ports/x11/nvidia-settings] # make install clean
cd: can't cd to /usr/ports/x11/nvidia-settings/work/nvidia-settings-1.0
*** Error code 2
===> Cleaning for gmake-3.81_1
===> Cleaning for intltool-0.35.0
===> Cleaning for pkg-config-0.21
===> Cleaning for atk-1.12.3
===> Clea
> Like I originally posted, every make I try winds up like this. The make
> doesn't create the port that it tries to cd into but this wasn't a problem
> last week or for the 8 months this box has been live...Thanks again for
> your
> responses.
Don't you need to make before you make install?
--
On Sun, Dec 03, 2006 at 09:44:18PM +, Robert Davison wrote:
> I've recently updated my ports, and openwebmail is no longer working,
> giving me the following error...
> Software error:
> Undefined subroutine &Compress::Zlib::memGzip called at
> /usr/local/www/cgi-bin/openwebmail/shares/ow-sha
FreeBSD WickerBill wrote:
> No Problem:
>
> [/usr/ports/x11/nvidia-settings] # make install clean
> cd: can't cd to /usr/ports/x11/nvidia-settings/work/nvidia-settings-1.0
> *** Error code 2
> ...
Are you running 'make -j'? Also post your make.conf and your environment
(printenv).
__
That was it...I totally spaced out that I had created an alias make -j4...a
big Thank You LoN_Kamikaze and all the rest that answered.
On 12/4/06, [LoN]Kamikaze <[EMAIL PROTECTED]> wrote:
FreeBSD WickerBill wrote:
> No Problem:
>
> [/usr/ports/x11/nvidia-settings] # make install clean
> cd: can
FreeBSD WickerBill wrote:
> That was it...I totally spaced out that I had created an alias make -j4...a
> big Thank You LoN_Kamikaze and all the rest that answered.
Please don't top-post. Also if you want to use make -j in combination with
portupgrade, install sysutils/bsdadminscripts and read th
> Yeah, I was able to reproduce the error! Try to replace
> the Makefile with the one attached here.
Now it looks it depends on gnat-gcc34. which fails with the follwing:
Making GCC gnat-gcc-3.4.6 for FreeBSD 6.2 target=i386-portbld-freebsd6.2
===> Extracting for gnat-gcc-3.4.6_2
=> MD5 Checksum
Hi:
Ok, source compiles fine although I haven't tested it also works. But: I
created this port on my working laptop which has a bunch of other apps.
So I was wondering, how do I figure out direct dependencies? And how do
I figure out whether these should be LIB_DEPENDS, BUILD_DEPENDS or
RUN_
On Dec 4, 2006, at 12:01 PM, Erik Norgaard wrote:
So I was wondering, how do I figure out direct dependencies? And
how do I figure out whether these should be LIB_DEPENDS,
BUILD_DEPENDS or RUN_DEPENDS or some other?
The fine documentation in the Porters Handbook discusses this:
http://www
On Mon, Dec 04, 2006 at 09:01:27PM +0100, Erik Norgaard wrote:
> Ok, source compiles fine although I haven't tested it also works. But: I
> created this port on my working laptop which has a bunch of other apps.
>
> So I was wondering, how do I figure out direct dependencies? And how do
> I fig
On Sun, 03 Dec 2006 09:43:06 -0600
Eric Schuele <[EMAIL PROTECTED]> mentioned:
> Hello,
>
> I recently installed e17. I am having difficulty getting the "Lock
> Screen" feature to accept a password. Presently it accepts any input
> (even blank) as valid.
>
> It my understanding that the problem
On Mon, 04 Dec 2006 21:01:27 +0100
Erik Norgaard <[EMAIL PROTECTED]> wrote:
> Hi:
>
> Ok, source compiles fine although I haven't tested it also works.
> But: I created this port on my working laptop which has a bunch of
> other apps.
>
> So I was wondering, how do I figure out direct dependenci
On Mon, Nov 27, 2006 at 03:12:41PM -0800, Doug Barton wrote:
> Robert Huff wrote:
> > Let's suppose I have a list of tarballs
> > (e.g. foobar-1.23.456.tar.gz). How do I tell which port each file
> > belongs to? "pkg_info" only lists the end results.
>
> The correct answer is, "not easily."
Wesley Shields wrote:
> On Mon, Nov 27, 2006 at 03:12:41PM -0800, Doug Barton wrote:
>> Robert Huff wrote:
>>> Let's suppose I have a list of tarballs
>>> (e.g. foobar-1.23.456.tar.gz). How do I tell which port each file
>>> belongs to? "pkg_info" only lists the end results.
>> The correct an
On Mon, Dec 04, 2006 at 01:56:40PM -0800, Doug Barton wrote:
> Wesley Shields wrote:
> > On Mon, Nov 27, 2006 at 03:12:41PM -0800, Doug Barton wrote:
> >> Robert Huff wrote:
> >>> Let's suppose I have a list of tarballs
> >>> (e.g. foobar-1.23.456.tar.gz). How do I tell which port each file
> >>
> > Yeah, I was able to reproduce the error! Try to replace
> > the Makefile with the one attached here.
>
> Now it looks it depends on gnat-gcc34. which fails with the follwing:
>
> Making GCC gnat-gcc-3.4.6 for FreeBSD 6.2 target=i386-portbld-freebsd6.2
> ===> Extracting for gnat-gcc-3.4.6_2
> =
On 12/04/06 13:39, Stanislav Sedov wrote:
On Sun, 03 Dec 2006 09:43:06 -0600
Eric Schuele <[EMAIL PROTECTED]> mentioned:
Hello,
I recently installed e17. I am having difficulty getting the "Lock
Screen" feature to accept a password. Presently it accepts any input
(even blank) as valid.
It m
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming Convention
21 matches
Mail list logo
