On Tue, Jul 16, 2013 at 2:39 PM, Jason Garrett wrote:
> Hello all,
>
> I am configuring a new system to run FreeBSD. I was in the middle of
> installing lxde-meta which depends on automake. This is where the install
> bails, and I'll include my uname -ar. Any help is
Hello all,
I am configuring a new system to run FreeBSD. I was in the middle of
installing lxde-meta which depends on automake. This is where the install
bails, and I'll include my uname -ar. Any help is greatly appreciated.
FreeBSD something.com 9.2-PRERELEASE FreeBSD 9.2-PRERELEA
On Thu, Dec 9, 2010 at 2:23 PM, Tim Daneliuk wrote:
> On 12/9/2010 12:54 PM, Steven Friedrich wrote:
>
> pkgdb -L
> pkgdb -Fa
>
-o replace the installed port with a port from a different origin (From
'portmaster')
-o, --origin=ORIGIN Specify a port to upgrade the following pkg with
(fr
On 12/9/2010 12:54 PM, Steven Friedrich wrote:
> I'm having trouble with the latest advice in ports/UPDATING:
>
> 20101208:
> AFFECTS: autotools
> AUTHOR: autoto...@freebsd.org
>
>
Here's how I did it:
1) Delete all the existing ports manually:
pkg_delete -f portname
2) Install the new
re is now only the concept of legacy and current
versions.
# portmaster -o devel/autoconf devel/autoconf268
# portmaster -o devel/automake devel/automake111
# portmaster -o devel/libtool devel/libtool22
# portmaster -o devel/libltdl devel/libltdl22
substitute 'portupgrade'
On Sat, Oct 16, 2010 at 12:16 PM, Warren Block wrote:
> On Sat, 16 Oct 2010, Arthur Barlow wrote:
>
> Recently I did my usual ports upgrade by using portsnap . The
>> "pkg_version"
>> program shows that "automake-1.9" and "automake-1.10" a
On Sat, 16 Oct 2010, Arthur Barlow wrote:
Recently I did my usual ports upgrade by using portsnap . The "pkg_version"
program shows that "automake-1.9" and "automake-1.10" and no longer current,
but for some reason the message "comparison failed" shows u
Recently I did my usual ports upgrade by using portsnap . The "pkg_version"
program shows that "automake-1.9" and "automake-1.10" and no longer current,
but for some reason the message "comparison failed" shows up when I check
the ports versions. I've
Hi,
Try this:
portmaster -od /usr/ports/devel/automake19/ automake-1.4.6_5
or your automake version, look it up with "pkg_info | grep automake"
Hope this helps! If needed try to update everything that was depending on
automake!
BR,
Balazs.
On 24 September 2010 23:20, aj
Today I tried on my FreeBSD 8.0
portmaster -ad
===>>> Gathering distinfo list for installed ports
===>>> Starting check of installed ports for available updates
===>>> The devel/automake15 port has been deleted: Outdated, ports migrated to
automake19
===>>> Aborting update
Thanks in advance.
On 24 July 2010 12:19, Jos Chrispijn wrote:
> Just had a quick look in my installed ports and found out that I have
> multiple versions of automake installed:
>
> automake-1.10.1: ok
> automake-1.4.6_5: ok
> automake-1.5_5,1: ok
> automake-1.9.6_3: ok
> automake-wrapper-
On Sat, Jul 24, 2010 at 11:49 AM, Jos Chrispijn wrote:
> Is this common or should I get rid of all automake-1.9.x versions? How could
> I do such best?
There are numerous tools for doing this; e.g.,
pkg_cutleaves and pkg_rmleaves.
This is common because not all ports build with a given au
On Sat, 24 Jul 2010 18:19:56 +0200
Jos Chrispijn wrote:
> Just had a quick look in my installed ports and found out that I have
> multiple versions of automake installed:
> ...
> Is this common
yes, it's normal
___
freebsd-ques
Just had a quick look in my installed ports and found out that I have
multiple versions of automake installed:
automake-1.10.1: ok
automake-1.4.6_5: ok
automake-1.5_5,1: ok
automake-1.9.6_3: ok
automake-wrapper-20071109: ok
Is this common or should I get rid of all automake-1.9.x versions? How
Hello,
I am trying to upgrade autoconf from 1.9.6_1 to 1.9.6_2 and I am
facing a problem :
===> Building for automake-1.9.6_2
Making all in .
rm -f automake automake.tmp
sed -e 's,[EMAIL PROTECTED]@],1.9,g' -e 's,[EMAIL PROTECTED]
[EMAIL PROTECTED],automake,g'
On Wed, 10 Jan 2007 10:29:30 +0100
Rico Secada <[EMAIL PROTECTED]> wrote:
Hmm, ./configure --mandir=/usr/local/man, when installed on freebsd. Didn't
think of that.
> Hi
>
> I am using autoconf/automake to try to build portable makefiles for some
> software I wrote. I a
Hi
I am using autoconf/automake to try to build portable makefiles for some
software I wrote. I am a newbie in makefiles.
If I don't add my man page, all works out fine. But as soon as I add my man
page 2 problems arises.
1. I can't use make distcheck, I get the following error:
m
Michael Pope <[EMAIL PROTECTED]> writes:
> I'm having a problem with aclocal and Automake when I'm running
> configgen.sh for inkscape on FreeBSD 5.4.
>
> Here is the error:
>
> ===> Running aclocal...
> aclocal: couldn't open directory
> /usr/loc
I'm having a problem with aclocal and Automake when I'm running
configgen.sh for inkscape on FreeBSD 5.4.
Here is the error:
===> Running aclocal...
aclocal: couldn't open directory
`/usr/local/gnu-autotools/share/aclocal': No such file or directory
===> Running
; While building 'portmanager', I noticed this error message:
> > > >
> > > > Making all in libMG
> > > > Making all in src
> > > > cd ../.. && /bin/sh
> > > > /usr/ports/sysutils/portmanager/work/portmanager-0.4.1/missing
s error message:
> > >
> > > Making all in libMG
> > > Making all in src
> > > cd ../.. && /bin/sh
> > > /usr/ports/sysutils/portmanager/work/portmanager-0.4.1/missing --run
> > > automake --gnu libMG/src/Makefile
> > > automake
. && /bin/sh
> > /usr/ports/sysutils/portmanager/work/portmanager-0.4.1/missing --run
> > automake --gnu libMG/src/Makefile
> > automake: not found
> > WARNING: `automake' is missing on your system. You should only need it if
> > you mo
nager/work/portmanager-0.4.1/missing --run
> automake --gnu libMG/src/Makefile
> automake: not found
> WARNING: `automake' is missing on your system. You should only need it if
> you modified `Makefile.am', `acinclude.m4' or `configure.ac'.
> You might
On Saturday 25 February 2006 15:23, Gerard Seibert wrote:
> Using FreeBSD 5.4
>
> While building 'portmanager', I noticed this error message:
>
> Making all in libMG
> Making all in src
> cd ../.. && /bin/sh
> /usr/ports/sysutils/portmanager/work/portma
Using FreeBSD 5.4
While building 'portmanager', I noticed this error message:
Making all in libMG
Making all in src
cd ../.. && /bin/sh
/usr/ports/sysutils/portmanager/work/portmanager-0.4.1/missing --run
automake --gnu libMG/src/Makefile
automake: not found
WARNING: `au
On Sat, Nov 19, 2005 at 06:53:43PM -0500, Gerard Seibert wrote:
> This is probably a dumb question, but I never let that bother me before. I
> have multiple copies of both:
>
> automake: 2.13.000227_5; 2.53_3; 2.59_2
> autoconf: 1.4.6_2; 1.5_2,1; 1.96
>
> Is it really
This is probably a dumb question, but I never let that bother me before. I
have multiple copies of both:
automake: 2.13.000227_5; 2.53_3; 2.59_2
autoconf: 1.4.6_2; 1.5_2,1; 1.96
Is it really necessary to have the older versions installed, or can I just
remove them? Actually, I did remove an
On Wed, Jun 08, 2005 at 09:54:51AM -0500, Phil Cryer wrote:
>
> >> #
> >> USE_AUTOMAKE_VER=19
> >
> >*ahem*
> >
> >Kris
>
> Whew, thank you! I knew automake was being misdirected somewhere, but didn't
> think of /etc/make.conf, c
>> #
>> USE_AUTOMAKE_VER=19
>
>*ahem*
>
>Kris
Whew, thank you! I knew automake was being misdirected somewhere, but didn't
think of /etc/make.conf, can't remember putting that in there, but I suppose I
did. Commented that line out, and things are back
On Tue, Jun 07, 2005 at 07:01:47PM -0500, Phil Cryer wrote:
> #
> USE_AUTOMAKE_VER=19
*ahem*
Kris
pgp0KEDLd1Ck8.pgp
Description: PGP signature
> What variables do you have set in your environment and in /etc/make.conf?
> Kris
CPUTYPE?=k7
CFLAGS= -O2 -pipe
COPTFLAGS= -O2 -pipe
MASTER_SITE_OVERRIDE="http://freebsd.mirrors.pair.com/pub/FreeBSD/distfiles/${DIST_SUBDIR}/"#
# added by use.perl 2005-03-12 23:47:15
PERL_VER=5.8.6
PERL_VERSION=5.
/usr/ports/*/*/work
> and everything else suggested. Here's the error when I try to install
> automake19:
>
> [EMAIL PROTECTED] /usr/ports]# cd devel/automake19
> [EMAIL PROTECTED] /usr/ports/devel/automake19]# make install
> ===> automake-1.9.5 depends on file: /usr/local/
try to install automake19:
[EMAIL PROTECTED] /usr/ports]# cd devel/automake19
[EMAIL PROTECTED] /usr/ports/devel/automake19]# make install
===> automake-1.9.5 depends on file: /usr/local/bin/perl5.8.6 - found
===> automake-1.9.5 depends on file: /usr/local/bin/automake19 - not found
===&
t; Please use devel/automake19 instead.
>
> ===> Vulnerability check disabled, database not found
> ===> Extracting for automake-1.5_2,1
> => Checksum mismatch for automake-1.5.tar.gz.
> ===> Refetch for 1 more times files: automake-1.5.tar.gz
> ===> NOTICE:
>
>
/bin/automake15
> - not found
> ===>Verifying install for /usr/local/bin/automake15 in
> /usr/ports/devel/automake15
> ===> NOTICE:
>
> This port is deprecated; you may wish to reconsider installing it:
>
> Please use devel/automake19 instead.
>
> =
n
/usr/ports/devel/automake15
===> NOTICE:
This port is deprecated; you may wish to reconsider installing it:
Please use devel/automake19 instead.
===> Vulnerability check disabled, database not found
===> Extracting for automake-1.5_2,1
=> Checksum mismatch for automake-1.5.tar
On 2005-01-13 20:13, Tom Huppi <[EMAIL PROTECTED]> wrote:
>On Thu, 13 Jan 2005, Giorgos Keramidas wrote:
>> I use autoconf/automake and libtool daily at work[1].
>>
>> The programs I write have to run on at least 3 different operating
>> systems (FreeBSD, Linux
On Thu, 13 Jan 2005, Giorgos Keramidas wrote:
> I use autoconf/automake and libtool daily at work[1].
>
> The programs I write have to run on at least 3 different operating
> systems (FreeBSD, Linux and Solaris) without the need for constant
> manual tweaking of the source.
To: Tom Huppi
Cc: Keith Bottner; freebsd-questions@freebsd.org; [EMAIL PROTECTED]
Org
Subject: Re: automake, autoconf compiling
PLEASE DON'T TOP-POST. THANK YOU :-)
On 2005-01-13 16:24, Tom Huppi <[EMAIL PROTECTED]> wrote:
>On Thu, 13 Jan 2005, Keith Bottner wrote:
>>
PLEASE DON'T TOP-POST. THANK YOU :-)
On 2005-01-13 16:24, Tom Huppi <[EMAIL PROTECTED]> wrote:
>On Thu, 13 Jan 2005, Keith Bottner wrote:
>> I am trying to get a development system setup and am having trouble
>> identifying how FreeBSD handles automake, autoconf an
ely arcane ones.
Thanks,
- Tom
On Thu, 13 Jan 2005, Keith Bottner wrote:
> First let me say that I am definitely a newbie to FreeBSD but not to Linux
> or Windows.
>
> I am trying to get a development system setup and am having trouble
> identifying how FreeBSD handles automak
Ted Mittelstaedt wrote:
Keep it Simple Stupid. A Makefile that has options settible
by editing with a text editor, and a nice readme file that tells
what all the settible options are, is infinitely superior than
all the configure crap. That is all that the RPM and ports
creators want from you. A
On Sun, Dec 19, 2004 at 01:14:48AM -0800, Ted Mittelstaedt wrote:
: WHY?
:
--8<--
:
: You don't need an install script. Whomever is building the RPM
: or whomever is creating the FreeBSD port has their own ideas of
: where they want things to be installed and has no interest in
: interfe
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Jonathon
> McKitrick
> Sent: Friday, December 17, 2004 3:53 PM
> To: Matthias Buelow
> Cc: Giorgos Keramidas; [EMAIL PROTECTED]
> Subject: Re: BSD equivalents of autoconf, auto
On 2004-12-17 23:52, Jonathon McKitrick <[EMAIL PROTECTED]> wrote:
> : system? Autoconf (and automake/libtool) was, as originally
> : intended, designed to ease cross-platform portability.
>
> I'm starting to wonder. But if I want to work on my new project at
> home,
autoconf.
:
: Why do you want to use autoconf at all, if you want to build on only one
At first I was only going to start a new personal project, and that can be
BSD only.
: system? Autoconf (and automake/libtool) was, as originally intended,
: designed to ease cross-platform portability.
I&#
One of the reasons I have been asking this is I will be spearheading a side
project at work to port a device driver (a library, really) from Win32 to
Linux.
I *really* don't want to use Linux to write this. Since it's really just
going to be a shared library that talks to a serial port, most of
autoconf.
:
: Why do you want to use autoconf at all, if you want to build on only one
: system? Autoconf (and automake/libtool) was, as originally intended,
: designed to ease cross-platform portability.
Well, I might want to make my project available, I'm not sure. But either
way, anyth
ne
system? Autoconf (and automake/libtool) was, as originally intended,
designed to ease cross-platform portability.
mkb.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On 2004-11-18 16:59, Jonathon McKitrick <[EMAIL PROTECTED]> wrote:
> On Thu, Nov 18, 2004 at 06:32:21PM +0200, Giorgos Keramidas wrote:
> : The minimal Makefile for building a program in FreeBSD looks something
> : like this:
> :
> : PROG= foo
> :
> : .include
> :
> : I can't even begin
On Thu, Nov 18, 2004 at 06:32:21PM +0200, Giorgos Keramidas wrote:
: The minimal Makefile for building a program in FreeBSD looks something
: like this:
:
: PROG= foo
:
: .include
:
: I can't even begin to describe all the 'make magic' that is hidden in
: /usr/share/mk/*.mk, but
> I'm starting to dabble in these self-contained self-building
> > > scripts and tools and so on, like automake, autoconf, libtool,
> > > and so on.
>
> I wouldn't go anywhere near these huge, hideous monsters of a shell
> script, unless someone was paying m
On 2004-11-18 10:18, "Conrad J. Sabatier" <[EMAIL PROTECTED]> wrote:
> On Thu, 18 Nov 2004 16:05:31 +, Jonathon McKitrick
> <[EMAIL PROTECTED]> wrote:
> > I'm starting to dabble in these self-contained self-building
> > scripts and tools and so on,
On Thu, 18 Nov 2004 16:05:31 +, Jonathon McKitrick
<[EMAIL PROTECTED]> wrote:
>
> I'm starting to dabble in these self-contained self-building scripts
> and tools and so on, like automake, autoconf, libtool, and so on.
>
> Are these the preferred way of doing thin
I'm starting to dabble in these self-contained self-building scripts and
tools and so on, like automake, autoconf, libtool, and so on.
Are these the preferred way of doing things on FreeBSD, or is there a better
or more BSD-way of doing them?
Some time ago, Terry Lambert suggested that
On Mon, 05 Jul 2004 13:26:28 +0200, Dag-Erling Smørgrav <[EMAIL PROTECTED]> wrote:
> Just pkg_delete them before running portupgrade.
Yes. Thanks. That seems to be the least destructive path. And now my
x11/kde3 is compiling fine through portugrade
Thanks
--
---
aeefyu
"Al.Aeefyu" <[EMAIL PROTECTED]> writes:
> How do I safely handle automake/autoconf versions built from ports?
Just pkg_delete them before running portupgrade.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED
> There should be no ports left which reference the removed versions of autoconf
> and automake, perhaps you cvsup'd in the middle of the commit.
That cant be the problem. I am trying to update my x11/kde3 from last
week, and one of its dependencies is automake/autoconf. It fails w
On Monday 05 July 2004 08:30, Al.Aeefyu wrote:
> Hi there!
>
> How do I safely handle automake/autoconf versions built from ports??
> Recently, some of my port builds (x11/kde3 specifically) failed
> because automake and autoconf has been MOVED. Do I absolutely have to
> wait f
Hi there!
How do I safely handle automake/autoconf versions built from ports??
Recently, some of my port builds (x11/kde3 specifically) failed
because automake and autoconf has been MOVED. Do I absolutely have to
wait for the maintainers to update the ports' Makefiles?
There are referenc
ing whether gmake sets $(MAKE)... yes
checking for working aclocal-1.4... missing
checking for working autoconf... found
checking for working automake-1.4... missing
Note that aclocal and automake are noted as missing, but do exist on
this 4.10-PRERELEASE system.
[EMAIL PROTECTED] bsb]$ locate autom
On Fri, Nov 28, 2003 at 08:17:39PM -0500, Aaron Walker wrote:
> I was getting ready to install the automake and autoconf ports, when I
> noticed there's 4 different versions of each. How do I know which ones
> to install?
Unless you need a specific version, install the latest
In the last episode (Nov 28), Aaron Walker said:
> I was getting ready to install the automake and autoconf ports, when I
> noticed there's 4 different versions of each. How do I know which ones
> to install?
Install the version you need :) The numbered ports will all coexist.
I was getting ready to install the automake and autoconf ports, when I
noticed there's 4 different versions of each. How do I know which ones
to install?
Thanks,
Aaron
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/lis
ausing the compile to fail) and it was recommended I
hack the configure.in and re-run automake/autoconf to generate a new
configure script. I've done this but configure now searches for
automake-1.4 and aclocal-1.4 (which don't exists -- I have automake14
and aclocal14). Previously the c
65 matches
Mail list logo
