Martin Weber <[EMAIL PROTECTED]> writes:
> There seems to be a problem in configure. If I use a freshly installed
> Linux without the headers of the kernel sources installed, configure runs
> without any error, but doesn't define certain variables. So the whole couldn'
There seems to be a problem in configure. If I use a freshly installed
Linux without the headers of the kernel sources installed, configure runs
without any error, but doesn't define certain variables. So the whole couldn't
compile. The thing is that configure should check for the head
"Uwe Koloska" <[EMAIL PROTECTED]> writes:
> "./configure --help" gives a wrong default for "--enable-gimpdir":
> --enable-gimpdir=DIRchange default gimpdir from .gimp to DIR
> must be
>
Hello,
"./configure --help" gives a wrong default for "--enable-gimpdir":
--enable-gimpdir=DIRchange default gimpdir from .gimp to DIR
must be
.gimp-1.2
Same change in INSTALL. (I don't know wether I can u
On Mon, Nov 06, 2000 at 03:23:32PM +0100, Raphael Quinet <[EMAIL PROTECTED]> wrote:
> I suppose that on most other systems, "perl5" is newer or the same as
> "perl", so the current test in configure.in is probably the best
> solution (and it has been like that for more than two years). You can
>
and has all the required modules
installed, it was taking /opt/local/perl5/bin/perl which comes later
in my path. This older perl executable is also symlinked from
/bin/perl and /usr/bin/perl, but all these directories come after
/Local/bin.
Here is the output from the top-level configure script
ect: failure with gimp 1.1.23 (was Re: [Bug #116288] configure fails
withgimp 1.1.17)
In-Reply-To: <[EMAIL PROTECTED]>
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sorry to bug you again about this, but I have found an honest bug in
configure for print-4.0.b[23].
I gave up on gimp 1.1.17
is a good choice (none would use the "prefix" for a normal
> installation except the ones who would build a binary rpm).
If you don't want to use RPMs features, why do you want to use it at
all? configure;make install is much simpler and cleaner and if you
want to package it
On Mon, 2 Oct 2000 [EMAIL PROTECTED] wrote:
> We build the gimp-perl plugin from the CPAN sources and disable it in
> the GIMP distribution because it makes too much problems there especially
> on recent SPARCs, alphas and ia64. We don't use the BuildRoot features
> of RPM however because it has s
On 1 Oct, Marc Lehmann wrote:
>> I haven't fixed yet the GIMP Perl plugins installation, please could
>> anyone fix it or tell me a workaround?
> The README.perl suggests PREFIX= for just this case. Daniel Egger
> could probably get more info as he works for suse and suse has quite a
> few per
On Sun, Oct 01, 2000 at 09:55:33PM +0200, Marco Lamberto <[EMAIL PROTECTED]> wrote:
> I haven't fixed yet the GIMP Perl plugins installation, please could anyone fix
> it or tell me a workaround?
The README.perl suggests PREFIX= for just this case. Daniel Egger could
probably get more info as he
May be I've posted a stupid question! ;P
I suppose that now the DESTDIR var should be used instead of prefix and PREFIX
when installing elsewhere, however the gimp.spec.in should be changed and
there are few bugs into the Makefile.in.in into some of the po* dirs.
I've attached a patch for fixing t
s. I
> should update someting or someone has forgotten something? ;) Actually
You shouldn't use make prefix=something install. This is mostly useful
for buildrooting rpms but may produce silly results for everything else
(because programs may have a different prefix hammered in at configu
I've got a little trouble while rebuilding the rpm of gimp 1.1.26, when running
the "make prefix={a_new_prefix} install" it tries to install into "/usr"
discarding the "prefix" and "PREFIX" values.
I should update someting or someone has forgotten something? ;)
Actually I've installed the followin
On Thu, Sep 14, 2000 at 04:30:34PM +, Jay Cox <[EMAIL PROTECTED]> wrote:
> If those of you with MP machines could beat on it for a while and report back how
> it works
> for you I would appreciate it.
I built --with-mp=yes since about it was created (but disabled
--enable-threads quite quickl
Jay Cox wrote:
> Jon Winters wrote:
> >
> > Hi,
> >
> > Here is a screengrab if anyone is interested... [Jon Winters had reproduced #10595
>with 1.1.25 distribution GRO]
> >
> > http://www.obscurasite.com/images/screengrabs/funky-tots.jpg
> >
> > Enjoy!
> >
>
> EEK!
>
> I hope that isn't from th
I've got a multiprocessor machine. What exactly do I need to do to test
this stuff? I haven't been following the entire thread.
I should...
./configure --with-mp=yes
Then do make and make install correct?
Then what???
Just use gimp or do something specific to test.
I
"Garry R. Osgood" wrote:
>
> <#10595 addenda snipped: see http://bugs.gnome.org/db/24/24188.html>
>
> For the (speculative) 1.2 release:
>
> 1. Do we support this option (and fix the bugs)?
>
> 2. or do we shut down option --with-mp=yes ?
>
> Leaving the situation as-is I regard unacceptable
On Wed, Sep 13, 2000 at 07:49:13AM -0400, thus said Garry R. Osgood:
> <#10595 addenda snipped: see http://bugs.gnome.org/db/24/24188.html>
>
> For the (speculative) 1.2 release:
>
> 1. Do we support this option (and fix the bugs)?
>
> 2. or do we shut down option --with-mp=yes ?
>
> Leaving
l* not
properly displayinglayer mode,
reported by Thaddeus Parkinson <[EMAIL PROTECTED]>
http://bugs.gnome.org/db/24/24188.html
occur only when gimp is built with configure option --with-mp=yes. (multiprocessor
support).
#24188 substantially compromises Gimp functiona
Vikas wrote:
>
>
> I even ran autoconf on the directory and it did generate the configure
> script but the script did not run. There were errors at startup itself.
> I do not remeber them right now.
>
> _
> Do You
"Garry R. Osgood" wrote:
>
> Vikas wrote:
>
> > I downloaded entire CVS'ed sources of GIMP and to start I could not find
> > configure script. Can anybody send me that file or tell me where can I
> > find it ot
Vikas wrote:
> I downloaded entire CVS'ed sources of GIMP and to start I could not find
> configure script. Can anybody send me that file or tell me where can I
> find it other that doing CVS again (It is a long job).
>
> __
>
On Wed, Sep 06, 2000 at 12:14:50PM +0530, Vikas <[EMAIL PROTECTED]> wrote:
> I downloaded entire CVS'ed sources of GIMP and to start I could not find
> configure script. Can anybody send me that file or tell me where can I
> find it other that doing CVS again (It is a long j
I downloaded entire CVS'ed sources of GIMP and to start I could not find
configure script. Can anybody send me that file or tell me where can I
find it other that doing CVS again (It is a long job).
__
Do You Yahoo!?
Talk to your friends o
error message "/bin/sh: no: command not found" is produced by an error by
configure. If the
package "gettext" is broken or not installed then "no" gets placed in the makefile -
instead of
the name and path of gettext.
The solution is to install or fix gettext, and for
Marc Lehmann wrote:
>
> The --enable-perl option specifies the perl prefix to install the
> pelr modules, not the perl executable path. Specifying a file will be
> disastrous.
Doh. OK - I didn't read that very closely.
> I think that the option should be named "--enable-perl-prefix" ...
> If so
On Mon, 29 May 2000, Marc Lehmann <[EMAIL PROTECTED]> wrote:
> On Sun, May 28, 2000 at 06:46:43PM -0400, Warren Hedley <[EMAIL PROTECTED]>
>wrote:
> > Also, configure ignores the perl executable argument specified
> > in the --enable-perl option (see configure line
On Sun, May 28, 2000 at 06:46:43PM -0400, Warren Hedley <[EMAIL PROTECTED]>
wrote:
> Also, configure ignores the perl executable argument specified
> in the --enable-perl option (see configure line above, for example),
The --enable-perl option specifies the perl prefix to inst
tarts trying to create my personal directories
/usr/local/share/gimp/1.1/user_install does not exist. ...
My configure line set the prefix like this:
./configure --enable-perl=/product/perl/bin/perl --disable-nls --prefix=/product/gimp
I've tried setting the GIMP_HOME environment variable t
Hi!
The following has happened with all gimps after 1.1.18,
even 1.1.20. I have now found the cause.
After doing a successful ./configure
"make" gives the following:
Making all in po
make[2]: Entering `/home/winters/gimp-1.1.18/po'
make[2]: *** No rule to make
Hi there,
starting with GIMP 1.1.19, you silently assume that glib.h can be found
by using the CFLAGS gnome-config provides. This breaks the test for
GTKXmHtml as it is not the case if you've got a local (newer) GLIB/GTK
installed separated from GNOME.
Fix: Add $GTK_CFLAGS to GTKXMHTML_FLAGS and
Hi,
Running the current configure fails for me, as I don't have GtkXMHTML installed.
This leaves $HELPBROWSER unset and causes a "test" failure.
Keith.
Here's a small patch to configure.in.
*** configure.in.orig Thu Mar 30 21:28:54 2000
--- configure.inThu
> This afternoon I downloaded and attempted to install the latest Gimp.
>
> ./configure failed to detect that I am running the latest versiong of
> gtk and bombed.
>
> The instructions given for those who know they have the latest version
> of gtk were not helpful.
>
&g
This afternoon I downloaded and attempted to install the latest Gimp.
./configure failed to detect that I am running the latest versiong of
gtk and bombed.
The instructions given for those who know they have the latest version
of gtk were not helpful.
I'm still stuck using an ancient
35 matches
Mail list logo
