Problem building ImageMagick-nox11

[andre]

I'm running into the issue below while trying to build 
ImageMagick-nox11.  This is in a jail on FreeBSD 8.2-p2.  I've just 
upgraded perl 5.10.x to 5.12.4 (followed the steps givin in 
/usr/ports/UPDATING) and this issue occurred while attempting to rebuild 
all packages depending on perl.


Here is the error:

gmake[3]: Entering directory 
`/var/ports/basejail/usr/ports/graphics/ImageMagick-nox11/work/ImageMagick-6.7.0-10/PerlMagick'
/usr/local/bin/perl5.12.4 
/usr/local/lib/perl5/site_perl/5.12.4/ExtUtils/xsubpp  -typemap 
/usr/local/lib/perl5/5.12.4/ExtUtils/typemap  Magick.xs > Magick.xsc && 
mv Magick.xsc Magick.c
Could not find a typemap for C type 'Image::Magick' in Magick.xs, line 
2404

gmake[3]: *** [Magick.c] Error 1
gmake[3]: Leaving directory 
`/var/ports/basejail/usr/ports/graphics/ImageMagick-nox11/work/ImageMagick-6.7.0-10/PerlMagick'

gmake[2]: *** [install-exec-perl] Error 2
gmake[2]: Leaving directory 
`/var/ports/basejail/usr/ports/graphics/ImageMagick-nox11/work/ImageMagick-6.7.0-10'

gmake[1]: *** [install-am] Error 2
gmake[1]: Leaving directory 
`/var/ports/basejail/usr/ports/graphics/ImageMagick-nox11/work/ImageMagick-6.7.0-10'

gmake: *** [install] Error 2
*** Error code 2

Stop in /basejail/usr/ports/graphics/ImageMagick-nox11.
*** Error code 1

Stop in /basejail/usr/ports/graphics/ImageMagick-nox11.



I've seen the error on some very recent (8/11/11) gentoo lists as well 
so I'm thinking this may be a bug in p5-ExtUtils-ParseXS. 
(http://forums.gentoo.org/viewtopic-p-6780342.html)


--
Andre Goree
an...@drenet.info
___
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: Install ImageMagick configured with Autotrace switch

[Pan Tsu]

Warren Block  writes:

> On Wed, 1 Jun 2011, Angelo wrote:
>
>> Thanks Peter but I can't seem to build this thing.
>
> Please don't top-post, and please trim responses.
>
>> I've tried just about everything I can think of to pass the argument
>> "--with-autotrace" and it throws exceptions or just ignores the command.
>
> Patching the ImageMagick Makefile is not too bad:
>
> --- graphics/ImageMagick/Makefile.orig    2011-06-02 08:13:35.0 
> -0600
> +++ graphics/ImageMagick/Makefile 2011-06-02 08:22:51.0 -0600
> @@ -40,6 +40,7 @@
>
>  OPTIONS=\
>   IMAGEMAGICK_16BIT_PIXEL "16bit pixel support" on \
> + IMAGEMAGICK_AUTOTRACE   "Autotrace support" off \
>   IMAGEMAGICK_BZLIB   "Bzlib support" on \
>   IMAGEMAGICK_DJVU"DJVU format support (needs threads)" off \
>   IMAGEMAGICK_DOT "GraphViz dot graphs support" off \
> @@ -228,6 +229,11 @@
>  CONFIGURE_ARGS+= --without-fftw
>  .endif
>
> +.if defined(WITH_IMAGEMAGICK_AUTOTRACE)
> +LIB_DEPENDS+=   autotrace:${PORTSDIR}/graphics/autotrace
> +CONFIGURE_ARGS+=--with-autotrace
> +.endif
> +
>  # Produce BZip compressed MIFF images
>  .if defined(WITHOUT_IMAGEMAGICK_BZLIB)
>  CONFIGURE_ARGS+= --without-bzlib
>
> And that seems to produce a working ImageMagick, at least one that can
> convert jpeg to svg.  There may be correctness issues, like whether
> autotrace requires other ImageMagick options to be enabled (like SVG).
>
> The problem is that autotrace depends on ImageMagick, and the patched
> ImageMagick now depends on autotrace.  I don't know enough about
> either port to fix that.  Hopefully someone can, because this seems
> like a useful addition.

In a circular dependency with x264 (lavf input) <-> ffmpeg (x264 encoder)
was resolved in favor of x264 autodetecting presence of ffmpeg which
makes x264 in the package unable to read popular formats. I wonder
which frontend is more useful for enconding in h264...

As autotrace leverages ImageMagick for reading more formats but can work 
without.
Why not make it autodetect it then?

%%
Index: graphics/autotrace/Makefile
===
RCS file: /a/.cvsup/ports/graphics/autotrace/Makefile,v
retrieving revision 1.52
diff -u -p -r1.52 Makefile
--- graphics/autotrace/Makefile 2 May 2011 12:44:35 -   1.52
+++ graphics/autotrace/Makefile 2 Jun 2011 16:13:03 -
@@ -14,8 +14,7 @@ MASTER_SITES= SF/${PORTNAME}/AutoTrace/$
 MAINTAINER=po...@freebsd.org
 COMMENT=   Convert bitmap to vector graphics
 
-LIB_DEPENDS=   png.6:${PORTSDIR}/graphics/png \
-   MagickWand.4:${PORTSDIR}/graphics/ImageMagick
+LIB_DEPENDS=   png.6:${PORTSDIR}/graphics/png
 
 USE_AUTOTOOLS= libtool
 USE_LDCONFIG=  yes
%%
___
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: Install ImageMagick configured with Autotrace switch

[Warren Block]

On Wed, 1 Jun 2011, Angelo wrote:


Thanks Peter but I can't seem to build this thing.


Please don't top-post, and please trim responses.


I've tried just about everything I can think of to pass the argument
"--with-autotrace" and it throws exceptions or just ignores the command.


Patching the ImageMagick Makefile is not too bad:

--- graphics/ImageMagick/Makefile.orig  2011-06-02 08:13:35.0 -0600
+++ graphics/ImageMagick/Makefile   2011-06-02 08:22:51.0 -0600
@@ -40,6 +40,7 @@

 OPTIONS=\
IMAGEMAGICK_16BIT_PIXEL "16bit pixel support" on \
+   IMAGEMAGICK_AUTOTRACE   "Autotrace support" off \
IMAGEMAGICK_BZLIB   "Bzlib support" on \
IMAGEMAGICK_DJVU"DJVU format support (needs threads)" off \
IMAGEMAGICK_DOT "GraphViz dot graphs support" off \
@@ -228,6 +229,11 @@
 CONFIGURE_ARGS+=   --without-fftw
 .endif

+.if defined(WITH_IMAGEMAGICK_AUTOTRACE)
+LIB_DEPENDS+=   autotrace:${PORTSDIR}/graphics/autotrace
+CONFIGURE_ARGS+=--with-autotrace
+.endif
+
 # Produce BZip compressed MIFF images
 .if defined(WITHOUT_IMAGEMAGICK_BZLIB)
 CONFIGURE_ARGS+=   --without-bzlib

And that seems to produce a working ImageMagick, at least one that can 
convert jpeg to svg.  There may be correctness issues, like whether 
autotrace requires other ImageMagick options to be enabled (like SVG).


The problem is that autotrace depends on ImageMagick, and the patched 
ImageMagick now depends on autotrace.  I don't know enough about either 
port to fix that.  Hopefully someone can, because this seems like a 
useful addition.

___
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"

Install ImageMagick configured with Autotrace switch

[Angelo]

 Thanks Peter but I can't seem to build this thing.

I've tried just about everything I can think of to pass the argument
"--with-autotrace" and it throws exceptions or just ignores the command.

The output of the configure in ImageMagick's delegate configuration is
--with-autotrace=no and I'm trying to change it to =yes before I build.

When I run "make configure --with-autotrace=yes" ("./configure" won't work)
or any other combination, the build is without the option set to yes just
the default no. When I add the argument to the make file directly, it stops
at "/usr/bin/ld: cannot find -lMagickWand"

Also, make doesn't recognize "-- -" and throws exceptions there too when I
enclose it with ' '.

When I install autotrace first, it automatically installs ImageMagick as
well but the delegate config in ImageMagick is still set to no.

Last but not least (this may be tied to the problem or add clues) when I
install ImageMagick and test (passes all internal tests), the system won't
recognize any shell commands like "convert" but will in a php script via
IMagick which still doesn't produce the correct svg xml since autotrace
isn't being used for the vectorization conversion. Would be nice to run php
scripting with ImageMagick commands from the shell but at this point I'll
take just about anything.

Cheers! Angelo


__
A> I am trying to install ImageMagick and Autotrace ports but I need to
A> configure Imagemagick to work with Autotrace so it processes raster
images
A> to the vector svg format properly.
A>
A> This is what is recommended from the imagemagick website to do, but I
don't
A> know the commands to type in freebsd to accomplish: Quote: "For this to
work
A> however the 'development' "AutoTrace" library must be installed, and IM
A> configured with a "--with-autotrace" switch.

You'd better tweak the graphics/ImageMagick port for this. Its Makefile
should have the 'CONFIGURE_ARGS =+' -like strings you can use as a sample
for the WITH_* option you can easily add. Be sure to include the DEPENDS
variable update for your library, too.


Feel free to submit patch for that port then. The dependence library port
should be already present on the ports tree, too.

A> So do I install with "make --with-autotrace" then "make
A> install --with-autotrace" and lastly "make clean"?

This is about ImageMagick's ./configure I think.

A> I already have ImageMagick and Autotrace installed but not configured
A> together so I'm assuming I will have to uninstall imagemagick first then
A> reinstall it with the autotrace switch?


uninstall and compile anew, 'make clean' is the best to ensure this before
'make'.

73! Peter pgp: A0E26627 (4A42 6841 2871 5EA7 52AB  12F8 0CE1 4AAC A0E2 6627)
--
http://vereshagin.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: Install ImageMagick configured with Autotrace switch

[Peter Vereshagin]

Concrete jungle, oh freebsd-questions, you've got to do your best...
2011/05/22 10:43:52 -0700 Angelo  => To 
freebsd-questions@freebsd.org :
A> I am trying to install ImageMagick and Autotrace ports but I need to
A> configure Imagemagick to work with Autotrace so it processes raster images
A> to the vector svg format properly.
A> 
A> This is what is recommended from the imagemagick website to do, but I don't
A> know the commands to type in freebsd to accomplish: Quote: "For this to work
A> however the 'development' "AutoTrace" library must be installed, and IM
A> configured with a "--with-autotrace" switch.

You'd better tweak the graphics/ImageMagick port for this. Its Makefile should 
have the 'CONFIGURE_ARGS =+' -like strings you can use as a sample for the 
WITH_* option you can easily add. Be sure to include the DEPENDS variable 
update for your library, too.

Feel free to submit patch for that port then. The dependence library port 
should be already present on the ports tree, too.

A> So do I install with "make --with-autotrace" then "make
A> install --with-autotrace" and lastly "make clean"?

This is about ImageMagick's ./configure I think.

A> I already have ImageMagick and Autotrace installed but not configured
A> together so I'm assuming I will have to uninstall imagemagick first then
A> reinstall it with the autotrace switch?


uninstall and compile anew, 'make clean' is the best to ensure this before 
'make'.

73! Peter pgp: A0E26627 (4A42 6841 2871 5EA7 52AB  12F8 0CE1 4AAC A0E2 6627)
--
http://vereshagin.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"

Install ImageMagick configured with Autotrace switch

[Angelo]

Hello,

I am trying to install ImageMagick and Autotrace ports but I need to
configure Imagemagick to work with Autotrace so it processes raster images
to the vector svg format properly.

This is what is recommended from the imagemagick website to do, but I don't
know the commands to type in freebsd to accomplish: Quote: "For this to work
however the 'development' "AutoTrace" library must be installed, and IM
configured with a "--with-autotrace" switch.

So do I install with "make --with-autotrace" then "make
install --with-autotrace" and lastly "make clean"?

I already have ImageMagick and Autotrace installed but not configured
together so I'm assuming I will have to uninstall imagemagick first then
reinstall it with the autotrace switch?

Thanks all!

Angelo
___
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"

ImageMagick, pecl-imagick (FreeBSD vs Ubuntu) problem (djvu as well?)

[B. Cook]

I have a server that I just put together to work with image creation.

Its running lighttpd with php being handled by php-fpm all from ports 
running 8.2 amd64.


My problem is quite strange; a simple php script reading in a djvu file 
(via Imagick()) causes php to hang and not do anything. - no errors, 
nothing.


Running the script via php -f also does the same thing..

cat -n something.php
 1  setImageFormat('png');// force output format to PNG
 4  
 5  // now write to browser
 6  header('Content-type: '.$im->getImageFormat());
 7  echo $im->getimageblob();
 8  ?>

So aside from the problem that this php does not do anything..

root@fbsd [/tmp]# 28 > convert /tmp/c3067.djvu /tmp/file.png && echo $?
0

root@fbsd [/tmp]# 29 > file file.png
file.png: PNG image, 957 x 1063, 8-bit/color RGBA, non-interlaced

Running the command to convert the djvu file manually seems to have no 
problems at all..


The problem lies in that the developer of this (I am not the main 
developer) says that "all this works perfectly on my Ubuntu 10.04 LTS 
server at home".. *sigh*


He sent me a php -m to compare my minimal setup to his bloated one; and 
I built every damn module to match.. no difference..


I've asked for a: `convert -list format` output from the lts machine to 
compare it against my own; as well as a `convert -list configure`


Tried to do an strace to see what I could see.. but strace doesn't work 
on amd64..


So can someone offer *something* that I could start to look at or use to 
look at what is causing this to happen? Otherwise it is looking like I 
will be loosing a perfectly good FreeBSD machine to an Ubuntu one.. *sniff*


Thanks in advance.
___
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"

Upgrading ImageMagick fails 2 of 48 tests

[Mike Clarke]

I'm trying to upgrade ImageMagick from 6.6.5.10 to 6.6.6-10 on FreeBSD 
8.1-RELEASE but 2 tests fail with segmentation faults - 
validate-formats-in-memory.sh and validate-formats-on-disk.sh.

I'll stick with 6.6.5.10 for now but would welcome suggestions on how to 
deal with this problem

=====
   ImageMagick 6.6.6: ./test-suite.log
=

2 of 48 tests failed.

.. contents:: :depth: 2egmentation fault


FAIL: tests/validate-formats-in-memory.sh (exit: 139)
=

Version: ImageMagick 6.6.6-10 2011-02-14 Q16 http://www.imagemagick.org
Copyright: Copyright (C) 1999-2011 ImageMagick Studio LLC

ImageMagick Validation Suite (FormatsInMemory)

validate image formats in memory:
  test 0: ART/Undefined/TrueColor/8-bits... pass.
  test 1: ART/Undefined/TrueColorMatte/8-bits... pass.
  test 2: ART/Undefined/Grayscale/8-bits... pass.

[Snip lots of passes]

  test 291: JPEG/Undefined/PaletteMatte/8-bits... pass.
  test 292: JPEG/Undefined/PaletteBilevelMatte/8-bits... pass.
  test 293: JPEG/Undefined/Bilevel/1-bits... pass.
  teSegmentation fault

FAIL: tests/validate-formats-on-disk.sh (exit: 139)
===

Version: ImageMagick 6.6.6-10 2011-02-14 Q16 http://www.imagemagick.org
Copyright: Copyright (C) 1999-2011 ImageMagick Studio LLC

ImageMagick Validation Suite (FormatsOnDisk)

validate image formats on disk:
  test 0: ART/Undefined/TrueColor/8-bits... pass.
  test 1: ART/Undefined/TrueColorMatte/8-bits... pass.
  test 2: ART/Undefined/Grayscale/8-bits... pass.

[Snip lots more passes]

  test 291: JPEG/Undefined/PaletteMatte/8-bits... pass.
  test 292: JPEG/Undefined/PaletteBilevelMatte/8-bits... pass.
  test 293: JPEG/Undefined/Bilevel/1-bits... pass.
  test 2Segmentation fault

-- 
Mike Clarke
___
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: ImageMagick-6.6.6-10 Port

[Julian H. Stacey]

Hi,
Reference:
> From: Steve Suhre  
> Date: Fri, 07 Jan 2011 08:45:47 -0700 
> Message-id:   <6.2.0.14.2.20110107084225.179e6...@nano.net> 

Steve Suhre wrote:
> 
> 
> 
> 
> I wasn't sure who to send this to.... I just grabbed the 
> ImageMagick-6.6.6-10 port from the FreeBSD.com ports collection and there's 
> a problem with the source code. When I run 'make' it croaks looking for 
> "ImageMagick-6.6.6-10.tar.gz" in the distinfo file, but the distinfo file 
> references "ImageMagick-6.6.6-10.tar.xz".
> 
> 
> 
> I'll find it somewhere else, but I thought you'd want to know...

Hi,
Good of you to report a bug, but questions@ is not the correct address.
See list remits:  
http://lists.freebsd.org/mailman/listinfo/freebsd-questions

po...@freebsd.org would be a better list address
http://lists.freebsd.org/mailman/listinfo

better than taht though, just whoever is marked as MAINTAINER in Makefile

& best if you run send-pr & CC that MAINTAINER with a bug report or fix.
man send-pr ; send=pr

Thanks
Julian
-- 
Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
Mail plain text;  Not quoted-printable, or HTML or base 64.
Avoid top posting, it cripples itemised cumulative responses.
___
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: ImageMagick-6.6.6-10 Port

[Odhiambo Washington]

On Fri, Jan 7, 2011 at 6:45 PM, Steve Suhre  wrote:

>
>
>
>
> I wasn't sure who to send this to I just grabbed the
> ImageMagick-6.6.6-10 port from the FreeBSD.com ports collection and there's
> a problem with the source code. When I run 'make' it croaks looking for
> "ImageMagick-6.6.6-10.tar.gz" in the distinfo file, but the distinfo file
> references "ImageMagick-6.6.6-10.tar.xz".
>
>
>
> I'll find it somewhere else, but I thought you'd want to know...
>
>
You grabbed the unofficial port, so not entirely unexpected.


-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Damn!!
___
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"

ImageMagick-6.6.6-10 Port

[Steve Suhre]

I wasn't sure who to send this to I just grabbed the 
ImageMagick-6.6.6-10 port from the FreeBSD.com ports collection and there's 
a problem with the source code. When I run 'make' it croaks looking for 
"ImageMagick-6.6.6-10.tar.gz" in the distinfo file, but the distinfo file 
references "ImageMagick-6.6.6-10.tar.xz".




I'll find it somewhere else, but I thought you'd want to know...





--
Steve Suhre
Antero web technologies
st...@antero.com
719.634.8161


___
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"

[SOLVED] Re: ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating

[Da Rock]

On 12/28/10 21:55, David Southwell wrote:


> > > On 12/27/10, David Southwell  wrote:

> > > >> On 12/27/10, David Southwell  wrote:

> > > > Agreed - but following Doug's commit I can vouch that the

> > > > PERL_THREADED hack

> > > > was still needed for 7.2 p3 systems on amd64.

> > >

> > > It shouldn't be needed. Can you remove this definition from any

> > > locally-modified Makefiles, and provide the same information 
that was


> > > requested from Da Rock? (Why do I feel like a WWE announcer when I

> > > type that? ...)

> > >

> > > b.

> >

> > I do not want to rebuild WITHOUT_IMAGEMAGICK_PERL on a running system

> > with active user access which needs perl.

> >

> > Have you got the replies from Da Rock?

>

> Before going any further I would suggest that Da Rock be advised to 
update


> his ports tree followed by

>

> # pkgdb -F

> Fix any problems then. If there are any problems he cannot fix at this

> stage then report those. Then:

>

> # portmaster -a or portupgrade -a

>

>

> If he gets any failure which may possibly be linked to a Perl problem he

> should rebuild perl with upward and downward recursion. e.g

> #portupgrade -rR lang/perl5.8

I dare say I'd come back with an error given I have 5.10 installed on 
the system.


>

> Until that is completed any other report could send us off on a wild 
goose


> chase.

>

> My twopennorth

>

I can do what you suggested when we have a report from Da Rock with 
his results from a system with thoroughly updated ports. My guess is 
that his probs will be solved by the above.



Ok, so it took a while and I'm still reviewing some other issues. The 
real problem is that the error msg sends all on a wild goose chase. I 
got it updated but the problem had absolutely nothing to do with perl, 
djvu, and their threads.


After some scratching about with configs and Makefiles, I discover there 
is an option not selected (not sure why) dealing with ImageMagick's 
threads- not perls or djvus! Now, IF those options are selected (and 
remember this is an upgrade) why not assume threads and print an info 
msg saying so? And why does the error msg not even allude to this 
instead of sending everyone on a chase after a mythical error that is 
not even the fault of the dependency?


Thanks for the hints guys, but I'm now trying to figure a method that 
may resolve this type of issue in the future- I remember using dialog 
boxes in extremely old installs of linux (and BSD packages I think) that 
automatically selects or deselects based on a selections 
required/incompatible dependencies. That would save hours of fart-arsing 
about for many- even searching for known answers takes time, easily 
resolved if something stable can be figured this way.


Thanks again.
___
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: ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating

[David Southwell]

> > > On 12/27/10, David Southwell  wrote:
> > > >> On 12/27/10, David Southwell  wrote:
> > > > Agreed - but  following Doug's  commit I can vouch that the
> > > > PERL_THREADED hack
> > > > was still needed  for 7.2 p3 systems on amd64.
> > > 
> > > It shouldn't be needed.  Can you remove this definition from any
> > > locally-modified Makefiles, and provide the same information that was
> > > requested from Da Rock? (Why do I feel like a WWE announcer when I
> > > type that? ...)
> > > 
> > > b.
> > 
> > I do not want to rebuild WITHOUT_IMAGEMAGICK_PERL on a running system
> > with active user access which needs perl.
> > 
> > Have you got the replies from Da Rock?
> 
> Before going any further I would suggest that Da Rock  be advised to update
> his ports tree followed by
> 
> # pkgdb -F
> Fix any problems then. If there are any problems he cannot fix at this
> stage then report those. Then:
> 
> # portmaster -a or portupgrade -a
> 
> 
> If he gets any failure which may possibly be linked to a Perl problem he
> should rebuild perl with upward and downward recursion. e.g
> #portupgrade -rR lang/perl5.8
> 
> Until that is completed any other report could send us off on a wild goose
> chase.
> 
> My twopennorth
> 
 I can do what you suggested when we have a report from Da Rock with his 
results from a system with thoroughly updated ports. My guess is that his 
probs will be solved by the above.

David


Photographic Artist
Permanent Installations & Design
Creative Imagery and Advanced Digital Techniques
High Dynamic Range Photography & Official Portraiture
Combined darkroom & digital creations
& Systems Adminstrator for the vizion2000.net network
___
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: ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating

[b. f.]

On 12/28/10, David Southwell  wrote:
>> On 12/27/10, David Southwell  wrote:
>> >> On 12/27/10, David Southwell  wrote:
>> > Agreed - but  following Doug's  commit I can vouch that the
>> > PERL_THREADED
>> > hack
>> > was still needed  for 7.2 p3 systems on amd64.
>>
>> It shouldn't be needed.  Can you remove this definition from any
>> locally-modified Makefiles, and provide the same information that was
>> requested from Da Rock? (Why do I feel like a WWE announcer when I
>> type that? ...)
>>
>> b.
> I do not want to rebuild WITHOUT_IMAGEMAGICK_PERL on a running system with
> active user access which needs perl.

Oh, I didn't intend for you to do that.  (This particular problem
shouldn't arise if perl support is disabled.)  I meant to show the
output of 'make -C $PORTSDIR/graphics/ImageMagick -V PERL_THREADED',
'make -C $PORTSDIR/graphics/ImageMagick showconfig', and 'perl
--version' on a system where the build failed if you didn't define
PERL_THREADED manually. (A transcript of a failed build would also be
helpful.)  You needn't (de)install anything.

> Have you got the replies from Da Rock?

Not yet.

b.
___
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: ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating

[David Southwell]

> > On 12/27/10, David Southwell  wrote:
> > >> On 12/27/10, David Southwell  wrote:
> > > Agreed - but  following Doug's  commit I can vouch that the
> > > PERL_THREADED hack
> > > was still needed  for 7.2 p3 systems on amd64.
> > 
> > It shouldn't be needed.  Can you remove this definition from any
> > locally-modified Makefiles, and provide the same information that was
> > requested from Da Rock? (Why do I feel like a WWE announcer when I
> > type that? ...)
> > 
> > b.
> 
> I do not want to rebuild WITHOUT_IMAGEMAGICK_PERL on a running system with
> active user access which needs perl.
> 
> Have you got the replies from Da Rock?
> 
Before going any further I would suggest that Da Rock  be advised to update 
his ports tree followed by

# pkgdb -F
Fix any problems then. If there are any problems he cannot fix at this stage 
then report those. Then:

# portmaster -a or portupgrade -a


If he gets any failure which may possibly be linked to a Perl problem he 
should rebuild perl with upward and downward recursion. e.g
#portupgrade -rR lang/perl5.8

Until that is completed any other report could send us off on a wild goose 
chase.

My twopennorth

David



Photographic Artist
Permanent Installations & Design
Creative Imagery and Advanced Digital Techniques
High Dynamic Range Photography & Official Portraiture
Combined darkroom & digital creations
& Systems Adminstrator for the vizion2000.net network
___
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: ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating

[David Southwell]

> On 12/27/10, David Southwell  wrote:
> >> On 12/27/10, David Southwell  wrote:
> > Agreed - but  following Doug's  commit I can vouch that the PERL_THREADED
> > hack
> > was still needed  for 7.2 p3 systems on amd64.
> 
> It shouldn't be needed.  Can you remove this definition from any
> locally-modified Makefiles, and provide the same information that was
> requested from Da Rock? (Why do I feel like a WWE announcer when I
> type that? ...)
> 
> b.
I do not want to rebuild WITHOUT_IMAGEMAGICK_PERL on a running system with 
active user access which needs perl.

Have you got the replies from Da Rock?

David

Photographic Artist
Permanent Installations & Design
Creative Imagery and Advanced Digital Techniques
High Dynamic Range Photography & Official Portraiture
Combined darkroom & digital creations
& Systems Adminstrator for the vizion2000.net network
___
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: ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating

[b. f.]

On 12/27/10, David Southwell  wrote:
>> On 12/27/10, David Southwell  wrote:

> Agreed - but  following Doug's  commit I can vouch that the PERL_THREADED
> hack
> was still needed  for 7.2 p3 systems on amd64.

It shouldn't be needed.  Can you remove this definition from any
locally-modified Makefiles, and provide the same information that was
requested from Da Rock? (Why do I feel like a WWE announcer when I
type that? ...)

b.
___
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: ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating

[David Southwell]

> On 12/27/10, David Southwell  wrote:
> >> > > > > What concerns me is perl-threaded _is_ installed but it can't
> >> > > > > see it.
> >> > > > 
> >> > > > Do you have in:
> >> > > > 
> >> > > > etc/make.conf
> >> > > > 
> >> > > > PERL_THREADED=true
> >> > > 
> >> > > Perhaps I'm a little daft atm. Either way I want to be clear: Are
> >> > > you saying the define needs to be in the make.conf so that it will
> >> > > build correctly? It _does not_ actually look at what perl is
> >> > > installed?
> >> > > 
> >> > > IF that is the case, then wtf? Either ImageMagick should be checking
> >> > > the actual pkg installed, or the perl port should be defining this
> >> > > in the make.conf, right? Seeing as perl already makes a define in
> >> > > make.conf...
> >> > > 
> >> > > Meanwhile I'll check it out. Cheers
> >> > 
> >> > Yep you need that line in make.conf
> >> 
> >> Who made this claim?  This is not some standard, user-configurable
> >> knob -- it is only used by 5 ports, and each of them assigns a value
> >> to it in the port Makefile.  It shouldn't be set in make.conf.  As for
> >> why it isn't working in Da Rock's case, he hasn't answered any of the
> >> questions I asked him earlier.
> > 
> > I suggest you see an earlier thread on same topic [ImageMagick Upgrade
> > Problem].
> 
> That thread (I'm assuming you're referring to the one in Nov. on
> FreeBSD-ports) is no longer relevant after Doug's commit (which was
> announced in that thread):

That was why I wondered whether all the OP's ports are up to date. 
> 
> http://www.freebsd.org/cgi/cvsweb.cgi/ports/graphics/ImageMagick/Makefile.d
> iff?r1=1.313;r2=1.314
> 
> The suggestion that users set that variable was a temporary hack that
> should never have been needed, were it not for the earlier problems
> with the port, which have since been resolved (in part, anyway).
> PERL_THREADED should only be defined when it is used, and should
> record whether the perl port being used is threaded, and not some
> user-selected value.
> 
Agreed - but  following Doug's  commit I can vouch that the PERL_THREADED hack 
was still needed  for 7.2 p3 systems on amd64.

> The questions I originally asked were in:
> 
> http://lists.freebsd.org/pipermail/freebsd-questions/2010-December/225501.h
> tml

The current thread did not make that clear.
> 
> (This thread is a little hard to follow because it's spread between
> two lists, -questions and -ports, with some replies not being sent to
> -ports.)
> 
> > I also wonder if the OP's ports tree is up to date.
> 
> That's a good question.  He mentioned that he was updating a lot of
> ports, so I'm assuming that it is, but it's something that he should
> check.
> 
His comments made me wonder :-;


Photographic Artist
Permanent Installations & Design
Creative Imagery and Advanced Digital Techniques
High Dynamic Range Photography & Official Portraiture
Combined darkroom & digital creations
& Systems Adminstrator for the vizion2000.net network
___
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: ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating

[b. f.]

On 12/27/10, David Southwell  wrote:
>> > > > > What concerns me is perl-threaded _is_ installed but it can't see
>> > > > > it.
>> > > >
>> > > > Do you have in:
>> > > >
>> > > > etc/make.conf
>> > > >
>> > > > PERL_THREADED=true
>> > >
>> > > Perhaps I'm a little daft atm. Either way I want to be clear: Are you
>> > > saying the define needs to be in the make.conf so that it will build
>> > > correctly? It _does not_ actually look at what perl is installed?
>> > >
>> > > IF that is the case, then wtf? Either ImageMagick should be checking
>> > > the actual pkg installed, or the perl port should be defining this in
>> > > the make.conf, right? Seeing as perl already makes a define in
>> > > make.conf...
>> > >
>> > > Meanwhile I'll check it out. Cheers
>> >
>> > Yep you need that line in make.conf
>>
>> Who made this claim?  This is not some standard, user-configurable
>> knob -- it is only used by 5 ports, and each of them assigns a value
>> to it in the port Makefile.  It shouldn't be set in make.conf.  As for
>> why it isn't working in Da Rock's case, he hasn't answered any of the
>> questions I asked him earlier.

> I suggest you see an earlier thread on same topic [ImageMagick Upgrade
> Problem].

That thread (I'm assuming you're referring to the one in Nov. on
FreeBSD-ports) is no longer relevant after Doug's commit (which was
announced in that thread):

http://www.freebsd.org/cgi/cvsweb.cgi/ports/graphics/ImageMagick/Makefile.diff?r1=1.313;r2=1.314

The suggestion that users set that variable was a temporary hack that
should never have been needed, were it not for the earlier problems
with the port, which have since been resolved (in part, anyway).
PERL_THREADED should only be defined when it is used, and should
record whether the perl port being used is threaded, and not some
user-selected value.

The questions I originally asked were in:

http://lists.freebsd.org/pipermail/freebsd-questions/2010-December/225501.html

(This thread is a little hard to follow because it's spread between
two lists, -questions and -ports, with some replies not being sent to
-ports.)

> I also wonder if the OP's ports tree is up to date.

That's a good question.  He mentioned that he was updating a lot of
ports, so I'm assuming that it is, but it's something that he should
check.

b.
___
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: ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating

[David Southwell]

> > > > > What concerns me is perl-threaded _is_ installed but it can't see
> > > > > it.
> > > > 
> > > > Do you have in:
> > > > 
> > > > etc/make.conf
> > > > 
> > > > PERL_THREADED=true
> > > 
> > > Perhaps I'm a little daft atm. Either way I want to be clear: Are you
> > > saying the define needs to be in the make.conf so that it will build
> > > correctly? It _does not_ actually look at what perl is installed?
> > > 
> > > IF that is the case, then wtf? Either ImageMagick should be checking
> > > the actual pkg installed, or the perl port should be defining this in
> > > the make.conf, right? Seeing as perl already makes a define in
> > > make.conf...
> > > 
> > > Meanwhile I'll check it out. Cheers
> > 
> > Yep you need that line in make.conf
> 
> Who made this claim?  This is not some standard, user-configurable
> knob -- it is only used by 5 ports, and each of them assigns a value
> to it in the port Makefile.  It shouldn't be set in make.conf.  As for
> why it isn't working in Da Rock's case, he hasn't answered any of the
> questions I asked him earlier.
> 
> b.
I suggest you see an earlier thread on same topic [ImageMagick Upgrade 
Problem].
I also wonder if the OP's ports tree is up to date.

David

Photographic Artist
Permanent Installations & Design
Creative Imagery and Advanced Digital Techniques
High Dynamic Range Photography & Official Portraiture
Combined darkroom & digital creations
& Systems Adminstrator for the vizion2000.net network
___
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: ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating

[b. f.]

> Well I did offer the info in the OP, albeit pkg_version style. Anyhoo
> perl --version outputs:
>

Yes, but the output of 'perl --version' is what really matters in this
case, because it is used to determine PERL_THREADED for this port, as
you can see in the port Makefile.

> This is perl, v5.10.1 (*) built for amd64-freebsd-thread-multi
>
> And pkg_version -v:
>
> perl-threaded-5.10.1_3
>
> So its there.  Unfortunately I'm still running various updates so I

Well, it's registered in PKG_DBDIR, anyway. In general, it's possible
for the package database or the installed package to be corrupt,
although neither of these seem to be your problem. When you get a
chance, show us the output of 'make -V PERL_THREADED' and 'make
showconfig' for this port. Both of those do little more than parse the
Makefiles, so they shouldn't disrupt your other builds.

b.
___
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: ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating

[Da Rock]

On 12/27/10 22:54, b. f. wrote:

What concerns me is perl-threaded _is_ installed but it can't see it.
   

Do you have in:

etc/make.conf

PERL_THREADED=true
 

Perhaps I'm a little daft atm. Either way I want to be clear: Are you
saying the define needs to be in the make.conf so that it will build
correctly? It _does not_ actually look at what perl is installed?

IF that is the case, then wtf? Either ImageMagick should be checking the
actual pkg installed, or the perl port should be defining this in the
make.conf, right? Seeing as perl already makes a define in make.conf...

Meanwhile I'll check it out. Cheers
   

Yep you need that line in make.conf
 


Who made this claim?  This is not some standard, user-configurable
knob -- it is only used by 5 ports, and each of them assigns a value
to it in the port Makefile.  It shouldn't be set in make.conf.  As for
why it isn't working in Da Rock's case, he hasn't answered any of the
questions I asked him earlier.
   
Well I did offer the info in the OP, albeit pkg_version style. Anyhoo 
perl --version outputs:


This is perl, v5.10.1 (*) built for amd64-freebsd-thread-multi

And pkg_version -v:

perl-threaded-5.10.1_3

So its there.  Unfortunately I'm still running various updates so I 
can't really offer the make -C yet- somehow OOO has managed scam itself 
into my updates that really takes time on the laptop. So I'm still doing 
'spring cleaning' so to speak :) The time of year really lends to the 
cause...

___
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: ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating

[b. f.]

> > > > What concerns me is perl-threaded _is_ installed but it can't see it.
> > >
> > > Do you have in:
> > >
> > > etc/make.conf
> > >
> > > PERL_THREADED=true
> >
> > Perhaps I'm a little daft atm. Either way I want to be clear: Are you
> > saying the define needs to be in the make.conf so that it will build
> > correctly? It _does not_ actually look at what perl is installed?
> >
> > IF that is the case, then wtf? Either ImageMagick should be checking the
> > actual pkg installed, or the perl port should be defining this in the
> > make.conf, right? Seeing as perl already makes a define in make.conf...
> >
> > Meanwhile I'll check it out. Cheers
> Yep you need that line in make.conf


Who made this claim?  This is not some standard, user-configurable
knob -- it is only used by 5 ports, and each of them assigns a value
to it in the port Makefile.  It shouldn't be set in make.conf.  As for
why it isn't working in Da Rock's case, he hasn't answered any of the
questions I asked him earlier.

b.
___
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: ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating

[Da Rock]

On 12/27/10 21:32, David Southwell wrote:

On 12/27/10 20:22, David Southwell wrote:
 

On 12/27/10 01:05, Roland Smith wrote:
 

On Sun, Dec 26, 2010 at 11:42:37PM +1000, Da Rock wrote:
   

Something I'm missing here? A fix would be nice, I should be used

to it though- ImageMagick _always_ has issues for me. I just

thought it'd be nice to get it updated for once- it looked so

close :)
 

I'm getting something similar, have been for a couple of weeks:

** Port marked as IGNORE: graphics/ImageMagick:

OpenEXR requires threads. . Perl is non-threaded. Reinstall Perl
   

with

   

threads or undefine WITH_IMAGEMAGICK_PERL



** Listing the failed packages (-:ignored / *:skipped / !:failed)



- graphics/ImageMagick (marked as IGNORE)



(Follow-ups redirected to ports@, or I tried to.)
   

Hmm. I'm not alone then. I'll do some poking then and see what comes

up... :)



Any hints guys?
     

Try building ImageMagick without perl support. Works for me, with
EXR,

but haven't tested with Djvu;



cd /usr/ports/graphics/ImageMagick

make config



┌──

──┐ │ Options for ImageMagick 6.6.5.10

│ │

┌^(-)┐

│



...



│ │[X] IMAGEMAGICK_OPENEXR OpenEXR support (needs threads)

│ │ │ │[X] IMAGEMAGICK_OPENMP OpenMP for SMP (needs threads)

│ │ │ │[ ] IMAGEMAGICK_PDF PDF format support

│ │ │ │[ ] IMAGEMAGICK_PERL Perl support

│ │



...



Roland
   

ImageMagick is already installed, so getting something to work is not a

problem. Its updating it...



What concerns me is perl-threaded _is_ installed but it can't see it.
 

Do you have in:

etc/make.conf

PERL_THREADED=true
   

Perhaps I'm a little daft atm. Either way I want to be clear: Are you
saying the define needs to be in the make.conf so that it will build
correctly? It _does not_ actually look at what perl is installed?

IF that is the case, then wtf? Either ImageMagick should be checking the
actual pkg installed, or the perl port should be defining this in the
make.conf, right? Seeing as perl already makes a define in make.conf...

Meanwhile I'll check it out. Cheers
 

Yep you need that line in make.conf

Also are ALL your ports up to date?
I cannot remember when but there was a recent patch to fix the problem you
describe. When you have that line in make.conf you may need to recompile perl
and all ports that depend upon it.
   
I'm running an update now, hence the issue :) but I'm not sure how 
recent you mean. I also just do a run through and check major probs if 
necessary, so I do just do what I can- this is not an enterprise system 
after all, just my heap of crap.


I didn't notice it in UPDATING but I guess I also wasn't really looking 
either- I'll look for it specifically now though. Hopefully I'll get a 
fully up-to-date system this holidays :)


So at the end of it all does the perl port put the define in then once 
installed?

___
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: ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating

[David Southwell]

> On 12/27/10 20:22, David Southwell wrote:
> > > On 12/27/10 01:05, Roland Smith wrote:
> > > > On Sun, Dec 26, 2010 at 11:42:37PM +1000, Da Rock wrote:
> > > >>>> Something I'm missing here? A fix would be nice, I should be used
> > > >>>> 
> > > >>>> to it though- ImageMagick _always_ has issues for me. I just
> > > >>>> 
> > > >>>> thought it'd be nice to get it updated for once- it looked so
> > > >>>> 
> > > >>>> close :)
> > > >>> 
> > > >>> I'm getting something similar, have been for a couple of weeks:
> > > >>> 
> > > >>> ** Port marked as IGNORE: graphics/ImageMagick:
> > > >>> 
> > > >>> OpenEXR requires threads. . Perl is non-threaded. Reinstall Perl
> > 
> > with
> > 
> > > >>> threads or undefine WITH_IMAGEMAGICK_PERL
> > > >>> 
> > > >>> 
> > > >>> 
> > > >>> ** Listing the failed packages (-:ignored / *:skipped / !:failed)
> > > >>> 
> > > >>> 
> > > >>> 
> > > >>> - graphics/ImageMagick (marked as IGNORE)
> > > >>> 
> > > >>> 
> > > >>> 
> > > >>> (Follow-ups redirected to ports@, or I tried to.)
> > > >> 
> > > >> Hmm. I'm not alone then. I'll do some poking then and see what comes
> > > >> 
> > > >> up... :)
> > > >> 
> > > >> 
> > > >> 
> > > >> Any hints guys?
> > > > 
> > > > Try building ImageMagick without perl support. Works for me, with
> > > > EXR,
> > > > 
> > > > but haven't tested with Djvu;
> > > > 
> > > > 
> > > > 
> > > > cd /usr/ports/graphics/ImageMagick
> > > > 
> > > > make config
> > > > 
> > > > 
> > > > 
> > > > ┌──
> > > > 
> > > > ──┐ │ Options for ImageMagick 6.6.5.10
> > > > 
> > > > │ │
> > > > 
> > > > ┌^(-)┐
> > > > 
> > > > │
> > > > 
> > > > 
> > > > 
> > > > ...
> > > > 
> > > > 
> > > > 
> > > > │ │[X] IMAGEMAGICK_OPENEXR OpenEXR support (needs threads)
> > > > 
> > > > │ │ │ │[X] IMAGEMAGICK_OPENMP OpenMP for SMP (needs threads)
> > > > 
> > > > │ │ │ │[ ] IMAGEMAGICK_PDF PDF format support
> > > > 
> > > > │ │ │ │[ ] IMAGEMAGICK_PERL Perl support
> > > > 
> > > > │ │
> > > > 
> > > > 
> > > > 
> > > > ...
> > > > 
> > > > 
> > > > 
> > > > Roland
> > > 
> > > ImageMagick is already installed, so getting something to work is not a
> > > 
> > > problem. Its updating it...
> > > 
> > > 
> > > 
> > > What concerns me is perl-threaded _is_ installed but it can't see it.
> > 
> > Do you have in:
> > 
> > etc/make.conf
> > 
> > PERL_THREADED=true
> 
> Perhaps I'm a little daft atm. Either way I want to be clear: Are you
> saying the define needs to be in the make.conf so that it will build
> correctly? It _does not_ actually look at what perl is installed?
> 
> IF that is the case, then wtf? Either ImageMagick should be checking the
> actual pkg installed, or the perl port should be defining this in the
> make.conf, right? Seeing as perl already makes a define in make.conf...
> 
> Meanwhile I'll check it out. Cheers
Yep you need that line in make.conf

Also are ALL your ports up to date?
I cannot remember when but there was a recent patch to fix the problem you 
describe. When you have that line in make.conf you may need to recompile perl 
and all ports that depend upon it.

David

Photographic Artist
Permanent Installations & Design
Creative Imagery and Advanced Digital Techniques
High Dynamic Range Photography & Official Portraiture
Combined darkroom & digital creations
& Systems Adminstrator for the vizion2000.net network
___
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: ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating

[Da Rock]

On 12/27/10 20:22, David Southwell wrote:


> On 12/27/10 01:05, Roland Smith wrote:

> > On Sun, Dec 26, 2010 at 11:42:37PM +1000, Da Rock wrote:

> >>>> Something I'm missing here? A fix would be nice, I should be used

> >>>> to it though- ImageMagick _always_ has issues for me. I just

> >>>> thought it'd be nice to get it updated for once- it looked so

> >>>> close :)

> >>>

> >>> I'm getting something similar, have been for a couple of weeks:

> >>> ** Port marked as IGNORE: graphics/ImageMagick:

> >>> OpenEXR requires threads. . Perl is non-threaded. Reinstall Perl 
with


> >>> threads or undefine WITH_IMAGEMAGICK_PERL

> >>>

> >>> ** Listing the failed packages (-:ignored / *:skipped / !:failed)

> >>>

> >>> - graphics/ImageMagick (marked as IGNORE)

> >>>

> >>> (Follow-ups redirected to ports@, or I tried to.)

> >>

> >> Hmm. I'm not alone then. I'll do some poking then and see what comes

> >> up... :)

> >>

> >> Any hints guys?

> >

> > Try building ImageMagick without perl support. Works for me, with EXR,

> > but haven't tested with Djvu;

> >

> > cd /usr/ports/graphics/ImageMagick

> > make config

> >

> > ┌──

> > ──┐ │ Options for ImageMagick 6.6.5.10

> > │ │

> > ┌^(-)────────┐

> > │

> >

> > ...

> >

> > │ │[X] IMAGEMAGICK_OPENEXR OpenEXR support (needs threads)

> > │ │ │ │[X] IMAGEMAGICK_OPENMP OpenMP for SMP (needs threads)

> > │ │ │ │[ ] IMAGEMAGICK_PDF PDF format support

> > │ │ │ │[ ] IMAGEMAGICK_PERL Perl support

> > │ │

> >

> > ...

> >

> > Roland

>

> ImageMagick is already installed, so getting something to work is not a

> problem. Its updating it...

>

> What concerns me is perl-threaded _is_ installed but it can't see it.

Do you have in:

etc/make.conf

PERL_THREADED=true


Perhaps I'm a little daft atm. Either way I want to be clear: Are you 
saying the define needs to be in the make.conf so that it will build 
correctly? It _does not_ actually look at what perl is installed?


IF that is the case, then wtf? Either ImageMagick should be checking the 
actual pkg installed, or the perl port should be defining this in the 
make.conf, right? Seeing as perl already makes a define in make.conf...


Meanwhile I'll check it out. Cheers
___
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: ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating

[David Southwell]

> On 12/27/10 01:05, Roland Smith wrote:
> > On Sun, Dec 26, 2010 at 11:42:37PM +1000, Da Rock wrote:
> >>>>Something I'm missing here? A fix would be nice, I should be used
> >>>>to it though- ImageMagick _always_ has issues for me. I just
> >>>>thought it'd be nice to get it updated for once- it looked so
> >>>>close :)
> >>>   
> >>>   I'm getting something similar, have been for a couple of weeks:
> >>> ** Port marked as IGNORE: graphics/ImageMagick:
> >>>   OpenEXR requires threads. . Perl is non-threaded. Reinstall Perl with
> >>>   threads or undefine WITH_IMAGEMAGICK_PERL
> >>> 
> >>> ** Listing the failed packages (-:ignored / *:skipped / !:failed)
> >>> 
> >>>   - graphics/ImageMagick (marked as IGNORE)
> >>>   
> >>>   (Follow-ups redirected to ports@, or I tried to.)
> >> 
> >> Hmm. I'm not alone then. I'll do some poking then and see what comes
> >> up... :)
> >> 
> >> Any hints guys?
> > 
> > Try building ImageMagick without perl support. Works for me, with EXR,
> > but haven't tested with Djvu;
> > 
> >  cd /usr/ports/graphics/ImageMagick
> >  make config
> >  
> >   ┌──
> >   ──┐ │ Options for ImageMagick 6.6.5.10 
> >│ │
> >   ┌^(-)┐
> >   │
> >  
> >  ...
> >  
> >   │ │[X] IMAGEMAGICK_OPENEXR  OpenEXR support (needs threads)   
> >   │ │ │ │[X] IMAGEMAGICK_OPENMP   OpenMP for SMP (needs threads)
> >   │ │ │ │[ ] IMAGEMAGICK_PDF  PDF format support
> >   │ │ │ │[ ] IMAGEMAGICK_PERL Perl support  
> >   │ │
> >  
> >  ...
> > 
> > Roland
> 
> ImageMagick is already installed, so getting something to work is not a
> problem. Its updating it...
> 
> What concerns me is perl-threaded _is_ installed but it can't see it.
Do you have in:
etc/make.conf
PERL_THREADED=true
??

David
Photographic Artist
Permanent Installations & Design
Creative Imagery and Advanced Digital Techniques
High Dynamic Range Photography & Official Portraiture
Combined darkroom & digital creations
& Systems Adminstrator for the vizion2000.net network
___
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: ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating

[Da Rock]

On 12/27/10 01:05, Roland Smith wrote:

On Sun, Dec 26, 2010 at 11:42:37PM +1000, Da Rock wrote:
   

   Something I'm missing here? A fix would be nice, I should be used to it
   though- ImageMagick _always_ has issues for me. I just thought it'd be
   nice to get it updated for once- it looked so close :)

 

I'm getting something similar, have been for a couple of weeks:

** Port marked as IGNORE: graphics/ImageMagick:
OpenEXR requires threads. . Perl is non-threaded. Reinstall Perl with 
threads or undefine WITH_IMAGEMAGICK_PERL
** Listing the failed packages (-:ignored / *:skipped / !:failed)
- graphics/ImageMagick (marked as IGNORE)

(Follow-ups redirected to ports@, or I tried to.)


   

Hmm. I'm not alone then. I'll do some poking then and see what comes
up... :)

Any hints guys?
 

Try building ImageMagick without perl support. Works for me, with EXR, but
haven't tested with Djvu;

 cd /usr/ports/graphics/ImageMagick
 make config
  ┌┐
  │     Options for ImageMagick 6.6.5.10   │
  │ ┌^(-)┐ │
 ...
  │ │[X] IMAGEMAGICK_OPENEXR  OpenEXR support (needs threads)│ │
  │ │[X] IMAGEMAGICK_OPENMP   OpenMP for SMP (needs threads) │ │
  │ │[ ] IMAGEMAGICK_PDF  PDF format support │ │
  │ │[ ] IMAGEMAGICK_PERL Perl support   │ │
     ...

Roland
   
ImageMagick is already installed, so getting something to work is not a 
problem. Its updating it...


What concerns me is perl-threaded _is_ installed but it can't see it.
___
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: ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating

[b. f.]

Da Rock wrote:
>>>I run portupgrade and it tells me it can't update ImageMagick because
>>>the Djvu option requires threads, and needs perl, therefore perl needs
>>>to be threaded. So it comes up with an IGNORE which is nuts because I
>>>run threaded perl.
...
>Any hints guys?

So, as the others wrote, build the port WITHOUT_IMAGEMAGICK_PERL, if
you don't need perl support; or fix the checks that are failing.  What
precisely is the message displayed when you've explicitly selected
WITH_THREADS, WITH_IMAGEMAGICK_PERL, and WITH_IMAGEMAGICK_DJVU?  Is it
a message generated by the ImageMagick Makefile, or by portupgrade?
If it is generated by the Makefile ( "... Perl is non-threaded.
Reinstall Perl with threads or undefine WITH_IMAGEMAGICK_PERL."), and
you've selected the above three options, then what is the output of
"perl --version" and "make -C $PORTSDIR/*/ImageMagick -V
PERL_THREADED"?

b.
___
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: ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating

[Roland Smith]

On Sun, Dec 26, 2010 at 11:42:37PM +1000, Da Rock wrote:
> >>   Something I'm missing here? A fix would be nice, I should be used to it
> >>   though- ImageMagick _always_ has issues for me. I just thought it'd be
> >>   nice to get it updated for once- it looked so close :)
> >>  
> > I'm getting something similar, have been for a couple of weeks:
> >
> > ** Port marked as IGNORE: graphics/ImageMagick:
> > OpenEXR requires threads. . Perl is non-threaded. Reinstall Perl with 
> > threads or undefine WITH_IMAGEMAGICK_PERL
> > ** Listing the failed packages (-:ignored / *:skipped / !:failed)
> > - graphics/ImageMagick (marked as IGNORE)
> >
> > (Follow-ups redirected to ports@, or I tried to.)
> >
> >
> Hmm. I'm not alone then. I'll do some poking then and see what comes 
> up... :)
> 
> Any hints guys?

Try building ImageMagick without perl support. Works for me, with EXR, but
haven't tested with Djvu;

cd /usr/ports/graphics/ImageMagick
make config
 ┌┐ 
 │ Options for ImageMagick 6.6.5.10   │ 
 │ ┌^(-)┐ │ 
...
 │ │[X] IMAGEMAGICK_OPENEXR  OpenEXR support (needs threads)│ │ 
 │ │[X] IMAGEMAGICK_OPENMP   OpenMP for SMP (needs threads) │ │ 
 │ │[ ] IMAGEMAGICK_PDF  PDF format support │ │ 
 │ │[ ] IMAGEMAGICK_PERL Perl support   │ │ 
...

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)


pgpXkTYs4Qx5X.pgp
Description: PGP signature

Re: ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating

[Da Rock]

On 12/26/10 23:04, Robert Huff wrote:

Da Rock writes:
   

  I'm running another set of updates, and I can't for the life of me get
  rid of this erroneous behaviour.

  I run portupgrade and it tells me it can't update ImageMagick because
  the Djvu option requires threads, and needs perl, therefore perl needs
  to be threaded. So it comes up with an IGNORE which is nuts because I
  run threaded perl.

  #pkg_version -v | grep perl
  mod_perl2-2.0.4_2,3 =   up-to-date with port
  perl-threaded-5.10.1_3  =   up-to-date with port

  Something I'm missing here? A fix would be nice, I should be used to it
  though- ImageMagick _always_ has issues for me. I just thought it'd be
  nice to get it updated for once- it looked so close :)
 

I'm getting something similar, have been for a couple of weeks:

** Port marked as IGNORE: graphics/ImageMagick:
OpenEXR requires threads. . Perl is non-threaded. Reinstall Perl with 
threads or undefine WITH_IMAGEMAGICK_PERL
** Listing the failed packages (-:ignored / *:skipped / !:failed)
- graphics/ImageMagick (marked as IGNORE)

(Follow-ups redirected to ports@, or I tried to.)

   
Hmm. I'm not alone then. I'll do some poking then and see what comes 
up... :)


Any hints guys?
___
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"

ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating

[Robert Huff]

Da Rock writes:
>  I'm running another set of updates, and I can't for the life of me get 
>  rid of this erroneous behaviour.
>  
>  I run portupgrade and it tells me it can't update ImageMagick because 
>  the Djvu option requires threads, and needs perl, therefore perl needs 
>  to be threaded. So it comes up with an IGNORE which is nuts because I 
>  run threaded perl.
>  
>  #pkg_version -v | grep perl
>  mod_perl2-2.0.4_2,3 =   up-to-date with port
>  perl-threaded-5.10.1_3  =   up-to-date with port
>  
>  Something I'm missing here? A fix would be nice, I should be used to it 
>  though- ImageMagick _always_ has issues for me. I just thought it'd be 
>  nice to get it updated for once- it looked so close :)

I'm getting something similar, have been for a couple of weeks:

** Port marked as IGNORE: graphics/ImageMagick:
OpenEXR requires threads. . Perl is non-threaded. Reinstall Perl with 
threads or undefine WITH_IMAGEMAGICK_PERL
** Listing the failed packages (-:ignored / *:skipped / !:failed)
- graphics/ImageMagick (marked as IGNORE)

(Follow-ups redirected to ports@, or I tried to.)


Robert Huff
___
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"

ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating

[Da Rock]

I'm running another set of updates, and I can't for the life of me get 
rid of this erroneous behaviour.


I run portupgrade and it tells me it can't update ImageMagick because 
the Djvu option requires threads, and needs perl, therefore perl needs 
to be threaded. So it comes up with an IGNORE which is nuts because I 
run threaded perl.


#pkg_version -v | grep perl
mod_perl2-2.0.4_2,3 =   up-to-date with port
perl-threaded-5.10.1_3  =   up-to-date with port

Something I'm missing here? A fix would be nice, I should be used to it 
though- ImageMagick _always_ has issues for me. I just thought it'd be 
nice to get it updated for once- it looked so close :)

___
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"

imagemagick/tiff lib - inverted tiffs since upgrade

[Olivier Mueller]

Hello,

I just spent some time with an issue: after a "standard" upgrade (by
luck on a test server), the image generation/conversion part of a
webpage is not working correctly anymore: pictures (which are
dynamically re-sized with pecl-imagick) are simply inverted (but only
TIFF's).

Before:

ImageMagick-nox11-6.4.9.3 Image processing tools
gd-2.0.35,1 A graphics library for fast creation of images
pecl-imagick-2.2.1_1 Provides a wrapper to the
ImageMagick/GraphicsMagick librar
tiff-3.8.2_3Tools and library routines for working with TIFF
images

After:

ImageMagick-nox11-6.5.5.10 Image processing tools
gd-2.0.35_2,1   A graphics library for fast creation of images
pecl-imagick-2.3.0  Provides a wrapper to the ImageMagick/GraphicsMagick
librar
tiff-3.9.2  Tools and library routines for working with TIFF
images


I tried to downgrade some or all of these ports with portsdowngrade, but
without luck until now (there are many dependencies). Maybe somebody
around is having the same issue and an idea how to fix it? 

Regards,
Olivier


___
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: graphics/ImageMagick seemingly not using OpenMP

[Scott Bennett]

 On Tue, 11 Aug 2009 09:38:52 -0500 Kirk Strauser 
wrote:
>On Aug 11, 2009, at 6:54 AM, Anton Shterenlikht wrote:
>
>> On Mon, Aug 10, 2009 at 11:18:43AM -0500, Kirk Strauser wrote:
>>> On my FreeBSD 7.2-STABLE system (from July 29), I'm trying to enable
>>> OpenMP for the graphics/ImageMagick port.  With the  
>>> IMAGEMAGICK_OPENMP
>>> option set, I get this from "make configure":
>>>
>>> checking for cc -std=gnu99 option to support OpenMP... (cached)  
>>> unsupported
>>> checking for cc -std=gnu99 option to support OpenMP... -fopenmp
>>>
>>> If I go on to build it, there's no other mention of OpenMP in the
>>> output.  What am I doing wrong?
>
>> I think the second like shows that OMP is indeed supported.
>> Have you tested on any OMP test?
>
>But the rest of the build doesn't give any indication. Specifically,  
>the "-fopenmp" flag isn't used anywhere.  I've tested that OMP works -  
>or at least compiles - but I don't know of any way to find if a given  
>binary was actually compiled with it.

 Have you tried nm(1)?  Unless the symbols were removed via strip(1),
nm(1) should be able to extract an external symbol dictionary from the
ImageMagick binary.  You can then search through that for OpenMP symbols.


  Scott Bennett, Comm. ASMELG, CFIAG
**
* Internet:   bennett at cs.niu.edu  *
**
* "A well regulated and disciplined militia, is at all times a good  *
* objection to the introduction of that bane of all free governments *
* -- a standing army."   *
*-- Gov. John Hancock, New York Journal, 28 January 1790 *
**
___
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: graphics/ImageMagick seemingly not using OpenMP

[Kirk Strauser]

On Aug 11, 2009, at 9:53 AM, Anton Shterenlikht wrote:


Have you also built perl-threaded?



I just now recompiled Perl with threads enabled, then Imagemagick,  
with identical results.

--
Kirk Strauser




___
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: graphics/ImageMagick seemingly not using OpenMP

[Anton Shterenlikht]

On Tue, Aug 11, 2009 at 09:38:52AM -0500, Kirk Strauser wrote:
> On Aug 11, 2009, at 6:54 AM, Anton Shterenlikht wrote:
> 
> >On Mon, Aug 10, 2009 at 11:18:43AM -0500, Kirk Strauser wrote:
> >>On my FreeBSD 7.2-STABLE system (from July 29), I'm trying to enable
> >>OpenMP for the graphics/ImageMagick port.  With the
> >>IMAGEMAGICK_OPENMP
> >>option set, I get this from "make configure":
> >>
> >>checking for cc -std=gnu99 option to support OpenMP... (cached)
> >>unsupported
> >>checking for cc -std=gnu99 option to support OpenMP... -fopenmp
> >>
> >>If I go on to build it, there's no other mention of OpenMP in the
> >>output.  What am I doing wrong?
> 
> >I think the second like shows that OMP is indeed supported.
> >Have you tested on any OMP test?
> 
> But the rest of the build doesn't give any indication. Specifically,
> the "-fopenmp" flag isn't used anywhere.  I've tested that OMP works
> - or at least compiles - but I don't know of any way to find if a
> given binary was actually compiled with it.

I haven't got any SMP IM tests, so cannot advise on this.
If you know of some, let me know, I'd like to test my SMP
box.
Have you also built perl-threaded?

-- 
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 928 8233 
Fax: +44 (0)117 929 4423
___
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: graphics/ImageMagick seemingly not using OpenMP

[Kirk Strauser]

On Aug 11, 2009, at 6:54 AM, Anton Shterenlikht wrote:


On Mon, Aug 10, 2009 at 11:18:43AM -0500, Kirk Strauser wrote:

On my FreeBSD 7.2-STABLE system (from July 29), I'm trying to enable
OpenMP for the graphics/ImageMagick port.  With the  
IMAGEMAGICK_OPENMP

option set, I get this from "make configure":

checking for cc -std=gnu99 option to support OpenMP... (cached)  
unsupported

checking for cc -std=gnu99 option to support OpenMP... -fopenmp

If I go on to build it, there's no other mention of OpenMP in the
output.  What am I doing wrong?



I think the second like shows that OMP is indeed supported.
Have you tested on any OMP test?


But the rest of the build doesn't give any indication. Specifically,  
the "-fopenmp" flag isn't used anywhere.  I've tested that OMP works -  
or at least compiles - but I don't know of any way to find if a given  
binary was actually compiled with it.

--
Kirk Strauser
___
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: graphics/ImageMagick seemingly not using OpenMP

[Anton Shterenlikht]

On Mon, Aug 10, 2009 at 11:18:43AM -0500, Kirk Strauser wrote:
> On my FreeBSD 7.2-STABLE system (from July 29), I'm trying to enable
> OpenMP for the graphics/ImageMagick port.  With the IMAGEMAGICK_OPENMP
> option set, I get this from "make configure":
> 
> checking for cc -std=gnu99 option to support OpenMP... (cached) unsupported
> checking for cc -std=gnu99 option to support OpenMP... -fopenmp
> 
> If I go on to build it, there's no other mention of OpenMP in the
> output.  What am I doing wrong?

I think the second like shows that OMP is indeed supported.
Have you tested on any OMP test?

-- 
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 928 8233 
Fax: +44 (0)117 929 4423
___
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"

graphics/ImageMagick seemingly not using OpenMP

[Kirk Strauser]

On my FreeBSD 7.2-STABLE system (from July 29), I'm trying to enable
OpenMP for the graphics/ImageMagick port.  With the IMAGEMAGICK_OPENMP
option set, I get this from "make configure":

checking for cc -std=gnu99 option to support OpenMP... (cached) unsupported
checking for cc -std=gnu99 option to support OpenMP... -fopenmp

If I go on to build it, there's no other mention of OpenMP in the 
output.  What am I doing wrong?

--
Kirk Strauser
___
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"

no port ralcgm - render CGM graphics with ImageMagick?

[Anton Shterenlikht]

I use ImageMagick quite a lot. Never came across this before, but
now I need to view some CGM drawings and realised that I need
ralcgm:
http://www.imagemagick.org/script/formats.php
http://www.agocg.ac.uk/train/cgm/ralcgm.htm

As far as I can search, there is no ralcgm port for FBSD.
Is that so?

Is there anybody else who is interested in having this port?
I might try to create one, if there is some support from the
community.

many thanks
anton

-- 
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 928 8233 
Fax: +44 (0)117 929 4423
___
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: imagemagick convert: japanese text broken in freebsd

[Glen Barber]

On Mon, Dec 15, 2008 at 6:21 AM, Giorgos Keramidas
 wrote:
> On Sun, 14 Dec 2008 23:17:38 -0800, Charlie Kester  
> wrote:
>> The conversations on ports@ seem to be mostly concerned with the needs
>> of port maintainers rather than the users of ports.  If you have
>> problems getting a port to build or a package added, it feels like the
>> right place to get help.
>>
>> But I'm not sure whether it's the place for questions that come up after
>> the initial install.  questions@ seems to be the place for those.
>
> I think you got that right.  lists.freebsd.org says:
>
> freebsd-ports   Porting software to FreeBSD
> freebsd-questions   User questions
>
> It's nice to have a list for people who are *porting* software, but the
> list for general `user questions' is here.
>

I certainly agree, and hope every time Wojciech posts "NTG" or "OT"
the OP's thread doesn't get turned into a flamewar on "Where this post
should go.".


-- 
Glen Barber
___
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: imagemagick convert: japanese text broken in freebsd

[Giorgos Keramidas]

On Sun, 14 Dec 2008 23:17:38 -0800, Charlie Kester  
wrote:
> The conversations on ports@ seem to be mostly concerned with the needs
> of port maintainers rather than the users of ports.  If you have
> problems getting a port to build or a package added, it feels like the
> right place to get help.
>
> But I'm not sure whether it's the place for questions that come up after
> the initial install.  questions@ seems to be the place for those.

I think you got that right.  lists.freebsd.org says:

freebsd-ports   Porting software to FreeBSD
freebsd-questions   User questions

It's nice to have a list for people who are *porting* software, but the
list for general `user questions' is 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: imagemagick convert: japanese text broken in freebsd

[Charlie Kester]

On Sun 14 Dec 2008 at 19:45:24 PST Robert Huff wrote:


Glen Barber writes:


Umm ... while one can ask those questions here (questions@) and hore
to get answered, I believe the sanctioned forum is po...@.  It's
rather lower traffic, which is not a bad thing.


I agree that they probably *should* be asked on ports@, but
because it is lower traffic, there is a lesser chance of getting
a solution to a problem.


Not necessarily.  I've heard of knowledgable poeple who are on ports@
but not questi...@.


The conversations on ports@ seem to be mostly concerned with the needs
of port maintainers rather than the users of ports.  If you have
problems getting a port to build or a package added, it feels like the
right place to get help.  


But I'm not sure whether it's the place for questions that come up after
the initial install.  questions@ seems to be the place for those.

I haven't been on either list very long, however, and I could have been
misled by a small sample size.

___
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: imagemagick convert: japanese text broken in freebsd

[Robert Huff]

Glen Barber writes:

>  >Umm ... while one can ask those questions here (questions@) and
>  > hore to get answered, I believe the sanctioned forum is po...@.
>  > It's rather lower traffic, which is not a bad thing.
>  
>  I agree that they probably *should* be asked on ports@, but
>  because it is lower traffic, there is a lesser chance of getting
>  a solution to a problem.

Not necessarily.  I've heard of knowledgable poeple who are on
ports@ but not questi...@.


Robert Huff

___
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: imagemagick convert: japanese text broken in freebsd

[Glen Barber]

On Sun, Dec 14, 2008 at 10:31 PM, Robert Huff  wrote:
> Giorgos Keramidas writes:
>
>>  Some of us disagree with the 'off topic police'.  If you have
>>  questions about programs that _run_ on FreeBSD, please keep
>>  asking here.  Nothing has changed.
>
>Umm ... while one can ask those questions here (questions@) and
> hore to get answered, I believe the sanctioned forum is po...@.
> It's rather lower traffic, which is not a bad thing.
>

I agree that they probably *should* be asked on ports@, but because it
is lower traffic, there is a lesser chance of getting a solution to a
problem.

I didn't see any clear definition on the lists.freebsd.org site
stating questions@ was "base only".

-- 
Glen Barber
___
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: imagemagick convert: japanese text broken in freebsd

[Robert Huff]

Giorgos Keramidas writes:

>  Some of us disagree with the 'off topic police'.  If you have
>  questions about programs that _run_ on FreeBSD, please keep
>  asking here.  Nothing has changed.

Umm ... while one can ask those questions here (questions@) and
hore to get answered, I believe the sanctioned forum is po...@.
It's rather lower traffic, which is not a bad thing.


Robert Huff


___
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: imagemagick convert: japanese text broken in freebsd

[Giorgos Keramidas]

On Sun, 14 Dec 2008 17:51:23 -0800 (PST), vuthecuong  
wrote:
> Hi all
> Firstly I'm terribly sorry for wrongly posted question not related to
> freebsd.  I will pay attention so that this wrong posting will not
> occurr again.  This is my fault.
>
> But I admit that freebsd-questions mailing list is really really very
> active mailing list which is have not only guru in OS itself but many
> many professionials of apps/servers running on top of it. (In fact I
> also posted this to imagemagick-nabble and imagemagick forum also, the
> result is I always get most useful/friendly/step-by-step answers from
> freebsd-questions that I can not reveive from the others).

Some of us disagree with the 'off topic police'.  If you have questions
about programs that _run_ on FreeBSD, please keep asking here.  Nothing
has changed.

___
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: imagemagick convert: japanese text broken in freebsd

[matt donovan]

On Sun, Dec 14, 2008 at 8:58 PM, Glen Barber wrote:

> On Sun, Dec 14, 2008 at 8:51 PM, vuthecuong  wrote:
> >
> > Hi all
> > Firstly I'm terribly sorry for wrongly posted question not related to
> > freebsd.
> > I will pay attention so that this wrong posting  will not occurr again.
> > This is my fault.
>
> No, it is not.  Questions@ is a general list for general FreeBSD
> questions.
>
> Getting something FreeBSD related to work, regardless of
> base-vs-ports, is FreeBSD related.
>
> --
> Glen Barber
> ___
> 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"
>

a Glen stated anything dealing with FreeBSD base-vs-ports is FreeBSD
related. Many of us I know are starting to get tired of the "police". And it
seems like he won't be bothering us with posts for a while since  he told a
FreeBSDd person "off" on this thread.
___
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: imagemagick convert: japanese text broken in freebsd

[Glen Barber]

On Sun, Dec 14, 2008 at 8:51 PM, vuthecuong  wrote:
>
> Hi all
> Firstly I'm terribly sorry for wrongly posted question not related to
> freebsd.
> I will pay attention so that this wrong posting  will not occurr again.
> This is my fault.

No, it is not.  Questions@ is a general list for general FreeBSD questions.

Getting something FreeBSD related to work, regardless of
base-vs-ports, is FreeBSD related.

-- 
Glen Barber
___
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: imagemagick convert: japanese text broken in freebsd

[vuthecuong]

Glen Barber-2 wrote:
> 
> On Sun, Dec 14, 2008 at 8:25 PM, Wojciech Puchar
>  wrote:
>>>
>>> The name is `freebsd-questions' not
>>> `freebsd-questions-about-the-base-system-only'.
>>>
>>> Wojciech, I am aware that this is probably going to be hardly enough to
>>> convince you, but you are _harming_ the Project by posting this sort of
>>
>> it's only Your opinion. My opinion is different. This list gets totally
>> polluted by OT traffic that DO HARM the Project, because it's more and
>> more
>> difficult to get help, and give help to people that posts ON-TOPIC.
>> It's complete mess!
>>
>> So i WILL respond "NTG" or "OT" to questions that are NTG/OT.
> 
> I really wish I had your free time.  I am happy, however, that you
> were promoted to questions@ police.
> 
>>
>> EOT from me about this.
> 
> How about making it EOT from you about everything that is not
> contributional?
> 
>> ___
>> 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"
>>
> 
> 
> 
> -- 
> Glen Barber
> ___
> 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"
> 
> 

Hi all
Firstly I'm terribly sorry for wrongly posted question not related to
freebsd.
I will pay attention so that this wrong posting  will not occurr again.
This is my fault. 

But I admit that freebsd-questions mailing list is really really very active
mailing list which is have not only guru in OS itself but many many
professionials of apps/servers running on top of it. (In fact I also posted
this to imagemagick-nabble and imagemagick forum also, the result is I
always get most useful/friendly/step-by-step answers from freebsd-questions
that I can not reveive from the others).
Once again, sorry you.
Best regards,
====
PS: But one thing I still could not understand is that in the past, the
others and I posted many many questions about Gnome, KDE, xfce, fluxbox,
php, java, squid, clamav, tripwire, anything but no any complaints, right?


-- 
View this message in context: 
http://www.nabble.com/imagemagick-convert%3A-japanese-text-broken-in-freebsd-tp20997257p21007145.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"

Re: imagemagick convert: japanese text broken in freebsd

[Glen Barber]

On Sun, Dec 14, 2008 at 8:25 PM, Wojciech Puchar
 wrote:
>>
>> The name is `freebsd-questions' not
>> `freebsd-questions-about-the-base-system-only'.
>>
>> Wojciech, I am aware that this is probably going to be hardly enough to
>> convince you, but you are _harming_ the Project by posting this sort of
>
> it's only Your opinion. My opinion is different. This list gets totally
> polluted by OT traffic that DO HARM the Project, because it's more and more
> difficult to get help, and give help to people that posts ON-TOPIC.
> It's complete mess!
>
> So i WILL respond "NTG" or "OT" to questions that are NTG/OT.

I really wish I had your free time.  I am happy, however, that you
were promoted to questions@ police.

>
> EOT from me about this.

How about making it EOT from you about everything that is not contributional?

> ___
> 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"
>



-- 
Glen Barber
___
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: imagemagick convert: japanese text broken in freebsd

[Wojciech Puchar]

The name is `freebsd-questions' not 
`freebsd-questions-about-the-base-system-only'.

Wojciech, I am aware that this is probably going to be hardly enough to
convince you, but you are _harming_ the Project by posting this sort of


it's only Your opinion. My opinion is different. This list gets totally 
polluted by OT traffic that DO HARM the Project, because it's more and 
more difficult to get help, and give help to people that posts ON-TOPIC.

It's complete mess!

So i WILL respond "NTG" or "OT" to questions that are NTG/OT.

EOT from me about this.
___
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: imagemagick convert: japanese text broken in freebsd

[Giorgos Keramidas]

On Sun, 14 Dec 2008 23:18:47 +0100 (CET), Wojciech Puchar 
 wrote:
>> There are some of us here who are interested in all things related to
>> Unicode and complex scripts questions; we are interested to have such
>> things working on FreeBSD. The OP's question was very interesting to me
>> _as a FreeBSD user_. You are of course not obliged to reply at all.
>>
>> The fact that people often get better replies about "application X
>> running on FreeBSD" on FreeBSD list than on a native list/forum reveals
>> something good about FreeBSD community IMHO.
>
> or very bad app X support.
>
> anyway - it's NTG! it's really HARD today to browse that list and see
> anything about FreeBSD.
>
> if it has to be "every app on the world support" - why it's not called
>
> everything-quest...@freebsd.org

It *is* called what you don't want to believe its name is.

The name is `freebsd-questions' not 
`freebsd-questions-about-the-base-system-only'.

Wojciech, I am aware that this is probably going to be hardly enough to
convince you, but you are _harming_ the Project by posting this sort of
thing to the list of `_general_ questions about FreeBSD'.  Please, STOP
doing that.  We may have to block you from posting to the lists if this
keeps going and increasing in intensity.



pgpSoyOuuQeh2.pgp
Description: PGP signature

Re: imagemagick convert: japanese text broken in freebsd

[Charlie Kester]

On Sun 14 Dec 2008 at 11:17:27 PST Nikola Le??i?? wrote:

There are some of us here who are interested in all things related to
Unicode and complex scripts questions; we are interested to have such
things working on FreeBSD. The OP's question was very interesting to me
_as a FreeBSD user_. You are of course not obliged to reply at all.

The fact that people often get better replies about "application X
running on FreeBSD" on FreeBSD list than on a native list/forum reveals
something good about FreeBSD community IMHO.


By posting here, the OP is more likely to get an answer from other users
who are using app X on FreeBSD.  


Asking in the App X forum is likely to get an unhelpful answer from
*their* local curmudgeons: "No one here uses FreeBSD, and it's not a
priority for the App X developers. Go away."

My point being, getting App X working on FreeBSD is often a higher
priority for us than it is for them, and someone here might have already
gone to the trouble of figuring it out.  I see nothing wrong in asking
whether that's the case.


___
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: imagemagick convert: japanese text broken in freebsd

[Wojciech Puchar]

There are some of us here who are interested in all things related to
Unicode and complex scripts questions; we are interested to have such
things working on FreeBSD. The OP's question was very interesting to me
_as a FreeBSD user_. You are of course not obliged to reply at all.

The fact that people often get better replies about "application X
running on FreeBSD" on FreeBSD list than on a native list/forum reveals
something good about FreeBSD community IMHO.


or very bad app X support.

anyway - it's NTG! it's really HARD today to browse that list and see 
anything about FreeBSD.


if it has to be "every app on the world support" - why it's not called

everything-quest...@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: imagemagick convert: japanese text broken in freebsd

[Nikola Lečić]

-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160

On Sun, 14 Dec 2008 10:03:18 +0100 (CET)
Wojciech Puchar  wrote:
 
> NTG
> please do ask on imagemagick support!

Interestingly, he did (and, as it appears, before you replied):

  http://www.imagemagick.org/discourse-server/viewtopic.php?f=1&t=12713

There are some of us here who are interested in all things related to
Unicode and complex scripts questions; we are interested to have such
things working on FreeBSD. The OP's question was very interesting to me
_as a FreeBSD user_. You are of course not obliged to reply at all.

The fact that people often get better replies about "application X
running on FreeBSD" on FreeBSD list than on a native list/forum reveals
something good about FreeBSD community IMHO.

Best regards.
- -- 
Nikola Lečić = Никола Лечић
fingerprint : FEF3 66AF C90E EDC3 D878  7CDC 956D F4AB A377 1C9B

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (FreeBSD)

iJwEAQEDAAYFAklFW9AACgkQ/MM/0rYIoZhMNQQAn9qEQwOEw3aNwTG7quq+KbnX
z7tp0dDevcooHbEkWTLqf24D8OiFrjl1dyC7zuE9Wwe3fAGKjVWbYBtshTW0Yusk
CbARjQCq85JKAz0LUmTJChJWCmbwy0M4SSNYJ20F/aX2lbFcEUGKL3pZudMWu+tj
npo9qKOF+jvjS0P3Vr0=
=0IHu
-END PGP SIGNATURE-
___
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: imagemagick convert: japanese text broken in freebsd

[Nikola Lečić]

-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160

On Sat, 13 Dec 2008 20:20:23 -0800 (PST)
cuongvt  wrote:

> Hi,
> I know that IM support japanese text.
> On Freebsd 7.0 with latest imagemagick built from port (6.4.7) and
> msgothic.ttc copied from windows partition,
> imagick extension of PHP installed by pecl.
> in terminal (zsh) I type:
> 
> convert origin.jpg -fill white -font
> /usr/X11R6/lib/X11/fonts/TrueType/msgothic.ttc -pointsize 125 -stroke
> blue -strokewidth 1 -draw "text 20,130 'がくせい'" straight.jpg
> 
> IM did not informed any error, but the result is japanese text broken
> (question marks).

Hello,

It works for me with ImageMagick-6.4.5.5 and ImageMagick-6.4.7.5.
First, please make sure that the cause of the problem is not something
simple, i.e. make sure that

  a) you don't have a wrong /non-UTF-8/ locale (not very likely since
 you wouldn't get question marks);

  b) you compiled ImageMagick with IMAGEMAGICK_TTF and
 IMAGEMAGICK_FONTCONFIG.

If these are the case, then it's almost certain that fontconfig is
somehow confused with that Microsoft font. For example, see this
thread on XeTeX mailing list about Microsoft YaHei font:

  http://www.tug.org/pipermail/xetex/2007-May/006539.html

If you use -text directive without -font specified, ImageMagick will
use the fonts from

  /usr/local/lib/ImageMagick-6.4.7/config/type-ghostscript.xml

and this will produce question marks with Japanese UTF-8 string, which
seems to be the case. So, if you don't want to use some free
non-Microsoft font, you can try to do this:

  1) Regenerate fontconfig cache ('fc-cache -f -v' as root).

  2) Check if MS Gothic is visible to ImageMagick, i.e. try

   %convert -list font

 The output should contain

   Font: ＭＳ-ゴシック-標準
 family: ＭＳ ゴシック
 style: Normal
 stretch: Normal
 weight: 400
 glyphs: /path/to/msgothic.ttc

 in ja_JP.UTF-8, or

   Font: MS-Gothic-Regular
 family: MS Gothic

 in en_US.UTF-8 locale.

  3) Then try

   %convert orig.jpg -font ＭＳ-ゴシック-標準 -verbose -fill white \
 -pointsize 125 -stroke blue -strokewidth 1 \
 -draw "text 20,130 'がくせい'" straight.jpg

 if you use ja_JP.* locale (-font MS-Gothic-Regular if you use
 en_US.UTF-8 -- note that the command is locale-sensitive) and see
 if this makes any difference.

Best regards.
- -- 
Nikola Lečić = Никола Лечић
fingerprint : FEF3 66AF C90E EDC3 D878  7CDC 956D F4AB A377 1C9B

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (FreeBSD)

iJwEAQEDAAYFAklFVtMACgkQ/MM/0rYIoZin4wP/Zhlf++1GS8jWitrcT0wq0Rkr
cROjjb0DOusXnZnq9LdWac3kjOv5mAUENu7jVy+9rGqvmGhDFkgBi4/mBrcSePGv
cTzSMqsWAeeF+JTizyqJCyRjaz2iOuEjQ1y6zvkOj5D9EE+udXmR6BE7u3HdgZKL
mknYg8Y4ARyu1N+tiOw=
=W84X
-END PGP SIGNATURE-
___
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: imagemagick convert: japanese text broken in freebsd

[Wojciech Puchar]

Hi,
I know that IM support japanese text.
On Freebsd 7.0 with latest imagemagick built from port (6.4.7) and
msgothic.ttc copied from windows partition,
imagick extension of PHP installed by pecl.
in terminal (zsh) I type:

convert origin.jpg -fill white -font
/usr/X11R6/lib/X11/fonts/TrueType/msgothic.ttc -pointsize 125 -stroke blue
-strokewidth 1 -draw "text 20,130 ''" straight.jpg

IM did not informed any error, but the result is japanese text broken
(question marks).
However, if I ran PHp script (see below), japanese displayed in image fine.
What is the reason and how can I solve that?
thansk and regards,


NTG
please do ask on imagemagick support! it's not part of FreeBSD and this 
problem doesn't look like FreeBSD specific.


If you find it FreeBSD port specific, ask at freebsd-ports___
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"

imagemagick convert: japanese text broken in freebsd

[cuongvt]

Hi,
I know that IM support japanese text.
On Freebsd 7.0 with latest imagemagick built from port (6.4.7) and
msgothic.ttc copied from windows partition,
imagick extension of PHP installed by pecl.
in terminal (zsh) I type:

convert origin.jpg -fill white -font
/usr/X11R6/lib/X11/fonts/TrueType/msgothic.ttc -pointsize 125 -stroke blue
-strokewidth 1 -draw "text 20,130 'がくせい'" straight.jpg

IM did not informed any error, but the result is japanese text broken
(question marks).
However, if I ran PHp script (see below), japanese displayed in image fine.
What is the reason and how can I solve that?
thansk and regards,

Below is PHP script:
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
http://www.w3.org/1999/xhtml"; lang="ja" xml:lang="ja"
dir="ltr">

sample373


setFont("/usr/X11R6/lib/X11/fonts/TrueType/msgothic.ttc");
/* フォントサイズ設定 */
$idraw->setFontSize(32);
/* gravity設定 */
$idraw->setGravity(Imagick::GRAVITY_CENTER);
$im->annotateImage($idraw, 0, 0, 0, "日本語");
$im->writeImage('sample373a.jpg');
/* $idraw->clear(); 2008/09/30追記：destroyと同様にClearDrawingWandを呼ぶので必要なし */
$idraw->destroy();
/* $im->clear(); 2008/09/30追記：destroyと同様にClearMagicWandを呼ぶので必要なし */
$im->destroy();
?>




-- 
View this message in context: 
http://www.nabble.com/imagemagick-convert%3A-japanese-text-broken-in-freebsd-tp20997257p20997257.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"

Re: build ImageMagick 6.4.4.1_1 from ports failed...

[Anton Shterenlikht]

On Wed, Oct 29, 2008 at 04:30:35PM +0200, Aggelidis Nikos wrote:
> On Wed, Oct 29, 2008 at 3:49 PM, Anton Shterenlikht <[EMAIL PROTECTED]> wrote:
> >
> > perhaps you just haven't built perlmagick, or use some old libraries -
> > just a guess.
> >
> I haven't build perlmagick. I only tried to build imagemagick {because
> it was required by kile}...
> 
> Could it be this? The problems that i find are at the test of
> magick++ i pass successfully every other test...
> 
> > I'm surprised you haven't got at least this in your /etc/make.conf
> >
> > CFLAGS= -O -pipe
> > MAKE_SHELL=sh
> > BDECFLAGS=  -W -Wall -ansi -pedantic -Wbad-function-cast -Wcast-align \
> >-Wcast-qual -Wchar-subscripts -Winline \
> >-Wmissing-prototypes -Wnested-externs -Wpointer-arith \
> >-Wredundant-decls -Wshadow -Wstrict-prototypes 
> > -Wwrite-strings
> > COPTFLAGS= -O -pipe
> > INSTALL=install -C
> i have the "default" make.conf if i recall correctly... should i add them?

have a look at the example, typically at /usr/share/examples/etc/make.conf

-- 
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 928 8233 
Fax: +44 (0)117 929 4423
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: build ImageMagick 6.4.4.1_1 from ports failed...

[Aggelidis Nikos]

On Wed, Oct 29, 2008 at 3:49 PM, Anton Shterenlikht <[EMAIL PROTECTED]> wrote:
>
> perhaps you just haven't built perlmagick, or use some old libraries -
> just a guess.
>
I haven't build perlmagick. I only tried to build imagemagick {because
it was required by kile}...

Could it be this? The problems that i find are at the test of
magick++ i pass successfully every other test...

> I'm surprised you haven't got at least this in your /etc/make.conf
>
> CFLAGS= -O -pipe
> MAKE_SHELL=sh
> BDECFLAGS=  -W -Wall -ansi -pedantic -Wbad-function-cast -Wcast-align \
>-Wcast-qual -Wchar-subscripts -Winline \
>-Wmissing-prototypes -Wnested-externs -Wpointer-arith \
>-Wredundant-decls -Wshadow -Wstrict-prototypes -Wwrite-strings
> COPTFLAGS= -O -pipe
> INSTALL=install -C
i have the "default" make.conf if i recall correctly... should i add them?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: build ImageMagick 6.4.4.1_1 from ports failed...

[Aggelidis Nikos]

On Wed, Oct 29, 2008 at 3:34 PM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
> Your "NO_OPENSSH = YES" line is broken, by the way.  You have a space
> between the "H" and the "=".
>
thank you! i fixed it.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: build ImageMagick 6.4.4.1_1 from ports failed...

[Anton Shterenlikht]

On Wed, Oct 29, 2008 at 01:17:23PM +0200, Manolis Kiagias wrote:
> Aggelidis Nikos wrote:
> > hi to all the list,
> >
> > i am trying to install ImageMagick 6.4.4.1_1 from the ports system.
> > The problem seems to be that i can't complete succesfully the tests of
> > imagemagick. In particular i fail in all the Magick++ tests
> >
> > [snip]
> >
> >
> >   
> 
> If I remember well, this is a known issue.  Change to the port's 
> directory, execute make config, and deselect IMAGEMAGICK_TESTS from the 
> options dialog. It should build and install fine.

on i386 7.0-release:

[skip]

PASS: utilities/tests/wave.sh
PASS: utilities/tests/montage.sh

All 699 tests passed

cd PerlMagick && make CC='cc -std=gnu99' test
/bin/sh ../magick.sh PERL_DL_NONLAZY=1 /usr/local/bin/perl5.8.8 "-MExtUtils::Com
mand::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/bzlib/*.t t/fp
x/*.t t/jbig/*.t t/jpeg/*.t t/jp2/*.t t/png/*.t t/tiff/*.t t/wmf/*.t t/zlib/*.t
t/blobok
t/bzlib/read..ok
t/bzlib/write.ok
t/composite...ok
t/filter..ok
t/fpx/readok
t/fpx/write...ok
t/getattributeok
t/jbig/read...ok
t/jbig/write..ok
t/jp2/readok
t/jpeg/read...ok
t/jpeg/write..ok
t/montage.ok
t/png/read-16.ok
t/png/readok
t/png/write-16ok
t/png/write...ok
t/readok
t/setattributeok
t/tiff/read...ok
t/tiff/write..ok
t/wmf/readok
t/write...ok
t/zlib/read...ok
t/zlib/write..ok
All tests successful.
Files=26, Tests=343, 130 wallclock secs ( 0.45 cusr +  0.06 csys =  0.52 CPU)
#

on i386 8.0-current (faster box):

PASS: utilities/tests/wave.sh
PASS: utilities/tests/montage.sh

All 699 tests passed

cd PerlMagick && make CC='cc -std=gnu99' test
/bin/sh ../magick.sh PERL_DL_NONLAZY=1 /usr/local/bin/perl5.8.8 "-MExtUtils::Com
mand::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/bzlib/*.t t/fp
x/*.t t/jbig/*.t t/jpeg/*.t t/jp2/*.t t/png/*.t t/tiff/*.t t/wmf/*.t t/zlib/*.t
t/blobok
t/bzlib/read..ok
t/bzlib/write.ok
t/composite...ok
t/filter..ok
t/fpx/readok
t/fpx/write...ok
t/getattributeok
t/jbig/read...ok
t/jbig/write..ok
t/jp2/readok
t/jpeg/read...ok
t/jpeg/write..ok
t/montage.ok
t/png/read-16.ok
t/png/readok
t/png/write-16ok
t/png/write...ok
t/readok
t/setattributeok
t/tiff/read...ok
t/tiff/write..ok
t/wmf/readok
t/write...ok
t/zlib/read...ok
t/zlib/write..ok
All tests successful.
Files=26, Tests=343, 20 wallclock secs (13.97 cusr +  4.35 csys = 18.32 CPU)
#

perhaps you just haven't built perlmagick, or use some old libraries -
just a guess.

-- 
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 928 8233 
Fax: +44 (0)117 929 4423
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: build ImageMagick 6.4.4.1_1 from ports failed...

[Anton Shterenlikht]

On Wed, Oct 29, 2008 at 02:47:03PM +0200, Aggelidis Nikos wrote:
> On Wed, Oct 29, 2008 at 2:02 PM, Anton Shterenlikht <[EMAIL PROTECTED]> wrote:
> > In any case you can build and install without tests,
> > and then do 'make check' separately.
> >
> > I'm building IM on i386 7.0-stable and 8.0-current.
> > Will let you know how the tests go soon.
> >
> > Post also your /etc/make.conf
> 
> here it is:
> NO_OPENSSH = YES
> # added by use.perl 2008-10-28 20:44:42
> PERL_VER=5.8.8
> PERL_VERSION=5.8.8
> 
> i will try and build without the tests

not sure if it is related to your problems, but
I'm surprised you haven't got at least this in your /etc/make.conf

CFLAGS= -O -pipe
MAKE_SHELL=sh
BDECFLAGS=  -W -Wall -ansi -pedantic -Wbad-function-cast -Wcast-align \
-Wcast-qual -Wchar-subscripts -Winline \
-Wmissing-prototypes -Wnested-externs -Wpointer-arith \
-Wredundant-decls -Wshadow -Wstrict-prototypes -Wwrite-strings
COPTFLAGS= -O -pipe
INSTALL=install -C

-- 
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 928 8233 
Fax: +44 (0)117 929 4423
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: build ImageMagick 6.4.4.1_1 from ports failed...

[Jeremy Chadwick]

On Wed, Oct 29, 2008 at 02:49:36PM +0200, Aggelidis Nikos wrote:
> On Wed, Oct 29, 2008 at 2:02 PM, Anton Shterenlikht <[EMAIL PROTECTED]> wrote:
> > In any case you can build and install without tests,
> > and then do 'make check' separately.
> >
> > I'm building IM on i386 7.0-stable and 8.0-current.
> > Will let you know how the tests go soon.
> >
> > Post also your /etc/make.conf
> >
> 
> here it is:
> NO_OPENSSH = YES
> # added by use.perl 2008-10-28 20:44:42
> PERL_VER=5.8.8
> PERL_VERSION=5.8.8

Your "NO_OPENSSH = YES" line is broken, by the way.  You have a space
between the "H" and the "=".

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: build ImageMagick 6.4.4.1_1 from ports failed...

[Aggelidis Nikos]

On Wed, Oct 29, 2008 at 2:02 PM, Anton Shterenlikht <[EMAIL PROTECTED]> wrote:
> In any case you can build and install without tests,
> and then do 'make check' separately.
>
> I'm building IM on i386 7.0-stable and 8.0-current.
> Will let you know how the tests go soon.
>
> Post also your /etc/make.conf
>

here it is:
NO_OPENSSH = YES
# added by use.perl 2008-10-28 20:44:42
PERL_VER=5.8.8
PERL_VERSION=5.8.8

i will try and build without the tests
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: build ImageMagick 6.4.4.1_1 from ports failed...

[Anton Shterenlikht]

On Wed, Oct 29, 2008 at 01:52:08PM +0200, Aggelidis Nikos wrote:
> Here are the configurations options:
> 
> ===> The following configuration options are available for
> ImageMagick-6.4.4.1_1:
>  X11=on "X11 support"
>  IMAGEMAGICK_TESTS=on "Run bundled self-tests after build"
>  IMAGEMAGICK_OPENMP=off "OpenMP for SMP (needs threads)"
>  IMAGEMAGICK_PERL=on "Perl support"
>  IMAGEMAGICK_MODULES=off "Modules support (broken)"
>  IMAGEMAGICK_BZLIB=on "Bzlib support"
>  IMAGEMAGICK_16BIT_PIXEL=on "16bit pixel support"
>  IMAGEMAGICK_DJVU=off "DJVU format support (needs threads)"
>  IMAGEMAGICK_LCMS=on "LCMS support"
>  IMAGEMAGICK_HDRI=off "High Dynamic Range Images (HDRI)"
>  IMAGEMAGICK_TTF=on "Freetype support"
>  IMAGEMAGICK_FONTCONFIG=on "Fontconfig support"
>  IMAGEMAGICK_JPEG=on "JPG format support"
>  IMAGEMAGICK_OPENEXR=off "OpenEXR support (needs threads)"
>  IMAGEMAGICK_PNG=on "PNG format support"
>  IMAGEMAGICK_TIFF=on "TIFF format support"
>  IMAGEMAGICK_FPX=on "FPX format support"
>  IMAGEMAGICK_JBIG=on "JBIG format support"
>  IMAGEMAGICK_JPEG2000=on "JPEG2000 format support"
>  IMAGEMAGICK_DOT=off "GraphViz dot graphs support"
>  IMAGEMAGICK_WMF=off "WMF format support"
>  IMAGEMAGICK_SVG=off "SVG format support"
>  IMAGEMAGICK_PDF=on "PDF format support"
>  IMAGEMAGICK_GSLIB=off "libgs (Postscript SHLIB) support"
> ===> Use 'make config' to modify these settings
> 
> > what platform and FBSD version?
> 
> #uname -a: FreeBSD apollo 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb
> 24 19:59:52 UTC 2008
> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386
> 
> > did you build with perl support?
> yes
> 
> >
> > If I remember well, this is a known issue.  Change to the port's directory,
> > execute make config, and deselect IMAGEMAGICK_TESTS from the options dialog.
> > It should build and install fine.
> >
> oh i didn't know this, but Anton stated that
> > I've passed all tests on i386
> 
> So you think i should disable the tests and recompile?

In any case you can build and install without tests,
and then do 'make check' separately.

I'm building IM on i386 7.0-stable and 8.0-current.
Will let you know how the tests go soon.

Post also your /etc/make.conf

-- 
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 928 8233 
Fax: +44 (0)117 929 4423
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: build ImageMagick 6.4.4.1_1 from ports failed...

[Manolis Kiagias]

Aggelidis Nikos wrote:

Here are the configurations options:

===> The following configuration options are available for
ImageMagick-6.4.4.1_1:
 X11=on "X11 support"
 IMAGEMAGICK_TESTS=on "Run bundled self-tests after build"
 IMAGEMAGICK_OPENMP=off "OpenMP for SMP (needs threads)"
 IMAGEMAGICK_PERL=on "Perl support"
 IMAGEMAGICK_MODULES=off "Modules support (broken)"
 IMAGEMAGICK_BZLIB=on "Bzlib support"
 IMAGEMAGICK_16BIT_PIXEL=on "16bit pixel support"
 IMAGEMAGICK_DJVU=off "DJVU format support (needs threads)"
 IMAGEMAGICK_LCMS=on "LCMS support"
 IMAGEMAGICK_HDRI=off "High Dynamic Range Images (HDRI)"
 IMAGEMAGICK_TTF=on "Freetype support"
 IMAGEMAGICK_FONTCONFIG=on "Fontconfig support"
 IMAGEMAGICK_JPEG=on "JPG format support"
 IMAGEMAGICK_OPENEXR=off "OpenEXR support (needs threads)"
 IMAGEMAGICK_PNG=on "PNG format support"
 IMAGEMAGICK_TIFF=on "TIFF format support"
 IMAGEMAGICK_FPX=on "FPX format support"
 IMAGEMAGICK_JBIG=on "JBIG format support"
 IMAGEMAGICK_JPEG2000=on "JPEG2000 format support"
 IMAGEMAGICK_DOT=off "GraphViz dot graphs support"
 IMAGEMAGICK_WMF=off "WMF format support"
 IMAGEMAGICK_SVG=off "SVG format support"
 IMAGEMAGICK_PDF=on "PDF format support"
 IMAGEMAGICK_GSLIB=off "libgs (Postscript SHLIB) support"
===> Use 'make config' to modify these settings

  

what platform and FBSD version?



#uname -a: FreeBSD apollo 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb
24 19:59:52 UTC 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386

  

did you build with perl support?


yes

  

If I remember well, this is a known issue.  Change to the port's directory,
execute make config, and deselect IMAGEMAGICK_TESTS from the options dialog.
It should build and install fine.



oh i didn't know this, but Anton stated that
  

I've passed all tests on i386
    


So you think i should disable the tests and recompile?

thank you all for your help so far,
nikos
  


AFAIR, there was a discussion about this not so long ago, and compiling 
without the tests was a proposed solution. In fact, I just checked my 
system and I have ImageMagick installed without the tests in the config 
options.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: build ImageMagick 6.4.4.1_1 from ports failed...

[Aggelidis Nikos]

Here are the configurations options:

===> The following configuration options are available for
ImageMagick-6.4.4.1_1:
 X11=on "X11 support"
 IMAGEMAGICK_TESTS=on "Run bundled self-tests after build"
 IMAGEMAGICK_OPENMP=off "OpenMP for SMP (needs threads)"
 IMAGEMAGICK_PERL=on "Perl support"
 IMAGEMAGICK_MODULES=off "Modules support (broken)"
 IMAGEMAGICK_BZLIB=on "Bzlib support"
 IMAGEMAGICK_16BIT_PIXEL=on "16bit pixel support"
 IMAGEMAGICK_DJVU=off "DJVU format support (needs threads)"
 IMAGEMAGICK_LCMS=on "LCMS support"
 IMAGEMAGICK_HDRI=off "High Dynamic Range Images (HDRI)"
 IMAGEMAGICK_TTF=on "Freetype support"
 IMAGEMAGICK_FONTCONFIG=on "Fontconfig support"
 IMAGEMAGICK_JPEG=on "JPG format support"
 IMAGEMAGICK_OPENEXR=off "OpenEXR support (needs threads)"
 IMAGEMAGICK_PNG=on "PNG format support"
 IMAGEMAGICK_TIFF=on "TIFF format support"
 IMAGEMAGICK_FPX=on "FPX format support"
 IMAGEMAGICK_JBIG=on "JBIG format support"
 IMAGEMAGICK_JPEG2000=on "JPEG2000 format support"
 IMAGEMAGICK_DOT=off "GraphViz dot graphs support"
 IMAGEMAGICK_WMF=off "WMF format support"
 IMAGEMAGICK_SVG=off "SVG format support"
 IMAGEMAGICK_PDF=on "PDF format support"
 IMAGEMAGICK_GSLIB=off "libgs (Postscript SHLIB) support"
===> Use 'make config' to modify these settings

> what platform and FBSD version?

#uname -a: FreeBSD apollo 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb
24 19:59:52 UTC 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386

> did you build with perl support?
yes

>
> If I remember well, this is a known issue.  Change to the port's directory,
> execute make config, and deselect IMAGEMAGICK_TESTS from the options dialog.
> It should build and install fine.
>
oh i didn't know this, but Anton stated that
> I've passed all tests on i386

So you think i should disable the tests and recompile?

thank you all for your help so far,
nikos
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: build ImageMagick 6.4.4.1_1 from ports failed...

[Manolis Kiagias]

Aggelidis Nikos wrote:

hi to all the list,

i am trying to install ImageMagick 6.4.4.1_1 from the ports system.
The problem seems to be that i can't complete succesfully the tests of
imagemagick. In particular i fail in all the Magick++ tests

[snip]


  


If I remember well, this is a known issue.  Change to the port's 
directory, execute make config, and deselect IMAGEMAGICK_TESTS from the 
options dialog. It should build and install fine.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: build ImageMagick 6.4.4.1_1 from ports failed...

[Anton Shterenlikht]

On Wed, Oct 29, 2008 at 09:33:40AM +0200, Aggelidis Nikos wrote:
> hi to all the list,
> 
> i am trying to install ImageMagick 6.4.4.1_1 from the ports system.
> The problem seems to be that i can't complete succesfully the tests of
> imagemagick. In particular i fail in all the Magick++ tests
> 
> [snip]
> 
> FAIL: Magick++/tests/exceptions.sh
> FAIL: Magick++/tests/appendImages.sh
> FAIL: Magick++/tests/attributes.sh
> FAIL: Magick++/tests/averageImages.sh
> FAIL: Magick++/tests/coalesceImages.sh
> FAIL: Magick++/tests/coderInfo.sh
> FAIL: Magick++/tests/colorHistogram.sh
> FAIL: Magick++/tests/color.sh
> FAIL: Magick++/tests/montageImages.sh
> FAIL: Magick++/tests/morphImages.sh
> FAIL: Magick++/tests/readWriteBlob.sh
> FAIL: Magick++/tests/readWriteImages.sh
> FAIL: Magick++/demo/analyze.sh
> FAIL: Magick++/demo/button.sh
> FAIL: Magick++/demo/demo.sh
> FAIL: Magick++/demo/flip.sh
> FAIL: Magick++/demo/gravity.sh
> FAIL: Magick++/demo/piddle.sh
> FAIL: Magick++/demo/shapes.sh
> FAIL: Magick++/demo/zoom_bessel.sh
> FAIL: Magick++/demo/zoom_blackman.sh
> FAIL: Magick++/demo/zoom_box.sh
> FAIL: Magick++/demo/zoom_catrom.sh
> FAIL: Magick++/demo/zoom_cubic.sh
> FAIL: Magick++/demo/zoom_gaussian.sh
> FAIL: Magick++/demo/zoom_hamming.sh
> FAIL: Magick++/demo/zoom_hanning.sh
> FAIL: Magick++/demo/zoom_hermite.sh
> FAIL: Magick++/demo/zoom_lanczos.sh
> FAIL: Magick++/demo/zoom_mitchell.sh
> FAIL: Magick++/demo/zoom_point.sh
> FAIL: Magick++/demo/zoom_quadratic.sh
> FAIL: Magick++/demo/zoom_sample.sh
> FAIL: Magick++/demo/zoom_scale.sh
> FAIL: Magick++/demo/zoom_sinc.sh
> FAIL: Magick++/demo/zoom_triangle.sh
> 
> [snip]
> 
> ===
> 36 of 699 tests failed
> Please report to http://www.imagemagick.org
> ===
> *** Error code 1
> 
> Stop in /usr/ports/graphics/ImageMagick/work/ImageMagick-6.4.4.
> *** Error code 1
> 
> 
> 
> 
> What i've tried so far:
> 
> * i tried to install using
>portugrade -P -N ImageMagick and then by using
>cd /usr/ports/graphics/ImageMagick/ && make install clean
> * updated the ports
> * installed or updated to the last version all the tools listed from
> freshports.org as "Required To Build" or "Required To Run"
>   Required To Build: lang/perl5.8, devel/pkg-config,
> print/ghostscript8-nox11
>   Required To Run: lang/perl5.8, devel/pkg-config, 
> print/ghostscript8-nox11
> * finally i updated to  libtool-1.5.26 because in
> /usr/ports/graphics/ImageMagick/work/ImageMagick-6.4.4/Magick++/tests/attributes.sh
> in the comments is mentioned that libtool is needed...
> 
> Any ideas will be great! even if they are just directions for where to
> look from here...because i am out of ideas..

what platform and FBSD version?
did you build with perl support?
mail output of `make showconfig'.
YOu shouldn't need to build each port manually. If you upgrade ImageMagick
with portupgrade or portmaster, all dependencies would have been checked,
and all updates of ports on which IM depends would have been performed.

I've passed all tests on i386 and all but 2 tests on alpha.

-- 
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 928 8233 
Fax: +44 (0)117 929 4423
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

build ImageMagick 6.4.4.1_1 from ports failed...

[Aggelidis Nikos]

hi to all the list,

i am trying to install ImageMagick 6.4.4.1_1 from the ports system.
The problem seems to be that i can't complete succesfully the tests of
imagemagick. In particular i fail in all the Magick++ tests

[snip]

FAIL: Magick++/tests/exceptions.sh
FAIL: Magick++/tests/appendImages.sh
FAIL: Magick++/tests/attributes.sh
FAIL: Magick++/tests/averageImages.sh
FAIL: Magick++/tests/coalesceImages.sh
FAIL: Magick++/tests/coderInfo.sh
FAIL: Magick++/tests/colorHistogram.sh
FAIL: Magick++/tests/color.sh
FAIL: Magick++/tests/montageImages.sh
FAIL: Magick++/tests/morphImages.sh
FAIL: Magick++/tests/readWriteBlob.sh
FAIL: Magick++/tests/readWriteImages.sh
FAIL: Magick++/demo/analyze.sh
FAIL: Magick++/demo/button.sh
FAIL: Magick++/demo/demo.sh
FAIL: Magick++/demo/flip.sh
FAIL: Magick++/demo/gravity.sh
FAIL: Magick++/demo/piddle.sh
FAIL: Magick++/demo/shapes.sh
FAIL: Magick++/demo/zoom_bessel.sh
FAIL: Magick++/demo/zoom_blackman.sh
FAIL: Magick++/demo/zoom_box.sh
FAIL: Magick++/demo/zoom_catrom.sh
FAIL: Magick++/demo/zoom_cubic.sh
FAIL: Magick++/demo/zoom_gaussian.sh
FAIL: Magick++/demo/zoom_hamming.sh
FAIL: Magick++/demo/zoom_hanning.sh
FAIL: Magick++/demo/zoom_hermite.sh
FAIL: Magick++/demo/zoom_lanczos.sh
FAIL: Magick++/demo/zoom_mitchell.sh
FAIL: Magick++/demo/zoom_point.sh
FAIL: Magick++/demo/zoom_quadratic.sh
FAIL: Magick++/demo/zoom_sample.sh
FAIL: Magick++/demo/zoom_scale.sh
FAIL: Magick++/demo/zoom_sinc.sh
FAIL: Magick++/demo/zoom_triangle.sh

[snip]

===
36 of 699 tests failed
Please report to http://www.imagemagick.org
===
*** Error code 1

Stop in /usr/ports/graphics/ImageMagick/work/ImageMagick-6.4.4.
*** Error code 1




What i've tried so far:

* i tried to install using
   portugrade -P -N ImageMagick and then by using
   cd /usr/ports/graphics/ImageMagick/ && make install clean
* updated the ports
* installed or updated to the last version all the tools listed from
freshports.org as "Required To Build" or "Required To Run"
  Required To Build: lang/perl5.8, devel/pkg-config,
print/ghostscript8-nox11
  Required To Run: lang/perl5.8, devel/pkg-config, print/ghostscript8-nox11
* finally i updated to  libtool-1.5.26 because in
/usr/ports/graphics/ImageMagick/work/ImageMagick-6.4.4/Magick++/tests/attributes.sh
in the comments is mentioned that libtool is needed...

Any ideas will be great! even if they are just directions for where to
look from here...because i am out of ideas..

regards,
nikos
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Stop in /usr/ports/graphics/ImageMagick/work/ImageMagick-6.4.3/PerlMagick

[Dino Vliet]

Forwarded Message: Stop in 
/usr/ports/graphics/ImageMagick/work/ImageMagick-6.4.3/PerlMagick



Stop in 
/usr/ports/graphics/ImageMagick/work/ImageMagick-6.4.3/PerlMagick
Friday, September 12, 2008 8:47 AM





From: 

"Dino Vliet" <[EMAIL PROTECTED]>
 





To: 

freebsd-questions@freebsd.org, [EMAIL PROTECTED]


Hi folks,

on
my adm64 dual core system running freebsd I get the following error
when installing the port, /usr/porst/graphics/ImageMagick:

t/write...ok
t/x11/readXlib: connection to ":0.0" refused by server
Xlib: No protocol specified

t/x11/readok
t/x11/write...Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

t/x11/write...FAILED test 1
    Failed 1/2 tests, 50.00% okay
t/zlib/read...ok
t/zlib/write..ok
Failed Test   Stat Wstat Total Fail  Failed  List of Failed
---
t/x11/write.t    2    1  50.00%  1
Failed 1/27 test scripts, 96.30% okay. 1/345 subtests failed, 99.71% okay.
*** Error code 2

Stop in /usr/ports/graphics/ImageMagick/work/ImageMagick-6.4.3/PerlMagick.
*** Error code 1

Stop in /usr/ports/graphics/ImageMagick/work/ImageMagick-6.4.3.
*** Error code 1

Stop in /usr/ports/graphics/ImageMagick/work/ImageMagick-6.4.3.
*** Error code 1

Stop in /usr/ports/graphics/ImageMagick/work/ImageMagick-6.4.3.
*** Error code 1

Stop in /usr/ports/graphics/ImageMagick.
*** Error code 1

Stop in /usr/ports/multimedia/kino.
*** Error code 1

Stop in /usr/ports/multimedia/kino.

the application I'm trying to install at the end is Kino.

Hope anyone can help me out

Brds
Dino

***

Hi all,

Solved this.
I had to use google and found an issue with Xlib and where the selftest failed. 
I had to re-enable root logins for my shiny kde4.1 desktop and after that as 
root I rebuild this port and everything went smooth! Now I can finally use my 
dual core power to start manipulating those video files.

Thanks though for the help (no answer got me thinking, it should be something 
obvious:-)

Brgds
Dino




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Stop in /usr/ports/graphics/ImageMagick/work/ImageMagick-6.4.3/PerlMagick

[Dino Vliet]

Hi folks,

on my adm64 dual core system running freebsd I get the following error when 
installing the port, /usr/porst/graphics/ImageMagick:

t/write...ok
t/x11/readXlib: connection to ":0.0" refused by server
Xlib: No protocol specified

t/x11/readok
t/x11/write...Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

t/x11/write...FAILED test 1
    Failed 1/2 tests, 50.00% okay
t/zlib/read...ok
t/zlib/write..ok
Failed Test   Stat Wstat Total Fail  Failed  List of Failed
---
t/x11/write.t    2    1  50.00%  1
Failed 1/27 test scripts, 96.30% okay. 1/345 subtests failed, 99.71% okay.
*** Error code 2

Stop in /usr/ports/graphics/ImageMagick/work/ImageMagick-6.4.3/PerlMagick.
*** Error code 1

Stop in /usr/ports/graphics/ImageMagick/work/ImageMagick-6.4.3.
*** Error code 1

Stop in /usr/ports/graphics/ImageMagick/work/ImageMagick-6.4.3.
*** Error code 1

Stop in /usr/ports/graphics/ImageMagick/work/ImageMagick-6.4.3.
*** Error code 1

Stop in /usr/ports/graphics/ImageMagick.
*** Error code 1

Stop in /usr/ports/multimedia/kino.
*** Error code 1

Stop in /usr/ports/multimedia/kino.

the application I'm trying to install at the end is Kino.

Hope anyone can help me out

Brds
Dino




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

ports/ImageMagick -> Magick++ -> 2 tests fail on FBSD 6.3 alpha

[Anton Shterenlikht]

Two ImageMagick tests fail with core dumps  on my FBSD 6.3 alpha:

FAIL: Magick++/tests/exceptions.sh
FAIL: Magick++/tests/attributes.sh

They pass on my FBSD 7.0 i386.

exceptions.cpp actually warns:

%vi exceptions.cpp

[skip]

 22
 23   cout << "Checking for working exceptions (may crash) ... ";
 24

Is this to do with different c++ versions on FBSD 7 and 6?

many thanks
anton

-- 
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 928 8233 
Fax: +44 (0)117 929 4423
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

SOLVED: Re: ImageMagick 6.4.1.5 tests fail on FBSD-7.0 => perl: signal 11

[Anton Shterenlikht]

On Thu, Jun 19, 2008 at 03:59:31PM +0100, Anton Shterenlikht wrote:
> On Thu, Jun 19, 2008 at 09:41:01AM +0100, Anton Shterenlikht wrote:
> > On Wed, Jun 18, 2008 at 08:23:20PM +0100, Chris Whitehouse wrote:
> > > Anton Shterenlikht wrote:
> > > >
> > > >my ImageMagick configuration:
> > > >
> > > >
> > > ># cd /usr/ports/graphics/ImageMagick/
> > > ># make showconfig
> > > >===> The following configuration options are available for 
> > > >ImageMagick-6.4.1.5:
> > > > X11=on "X11 support"
> > > > IMAGEMAGICK_TESTS=on "Run bundled self-tests after build"
> > > > IMAGEMAGICK_OPENMP=off "Enable OpenMP for SMP"
> > > > IMAGEMAGICK_PERL=on "Perl support"
> > > > IMAGEMAGICK_MODULES=off "Modules support (broken)"
> > > > IMAGEMAGICK_BZLIB=on "Bzlib support"
> > > > IMAGEMAGICK_16BIT_PIXEL=on "16bit pixel support"
> > > > IMAGEMAGICK_DJVU=off "DJVU format support (needs threads)"
> > > > IMAGEMAGICK_LCMS=on "LCMS support"
> > > > IMAGEMAGICK_HDRI=off "High Dynamic Range Images (HDRI)"
> > > > IMAGEMAGICK_TTF=on "Freetype support"
> > > > IMAGEMAGICK_FONTCONFIG=on "Fontconfig support"
> > > > IMAGEMAGICK_JPEG=on "JPG format support"
> > > > IMAGEMAGICK_OPENEXR=off "OpenEXR support (needs threads)"
> > > > IMAGEMAGICK_PNG=on "PNG format support"
> > > > IMAGEMAGICK_TIFF=on "TIFF format support"
> > > > IMAGEMAGICK_FPX=on "FPX format support"
> > > > IMAGEMAGICK_JBIG=on "JBIG format support"
> > > > IMAGEMAGICK_JPEG2000=on "JPEG2000 format support"
> > > > IMAGEMAGICK_DOT=on "GraphViz dot graphs support"
> > > > IMAGEMAGICK_WMF=on "WMF format support"
> > > > IMAGEMAGICK_SVG=on "SVG format support"
> > > > IMAGEMAGICK_PDF=on "PDF format support"
> > > > IMAGEMAGICK_GSLIB=on "libgs (Postscript SHLIB) support"
> > > >===> Use 'make config' to modify these settings
> > > >#
> > > >
> > > >
> > > >#make check
> > > > [skip]
> > > >t/zlib/write.t  0   139 12 200.00%  1
> > > >Failed 26/26 test scripts, 0.00% okay. 343/343 subtests failed, 0.00% 
> > > >okay.

> 
> I just noticed that test failures are accompanied with the following
> in dmesg:
> 
> [skip]
> pid 79423 (perl5.8.8), uid 0: exited on signal 11 (core dumped)
> pid 79426 (perl5.8.8), uid 0: exited on signal 11 (core dumped)
> pid 79429 (perl5.8.8), uid 0: exited on signal 11 (core dumped)
> pid 79432 (perl5.8.8), uid 0: exited on signal 11 (core dumped)
> pid 79448 (perl5.8.8), uid 0: exited on signal 11 (core dumped)
> pid 79451 (perl5.8.8), uid 0: exited on signal 11 (core dumped)
> pid 79454 (perl5.8.8), uid 0: exited on signal 11 (core dumped)
> pid 79462 (perl5.8.8), uid 0: exited on signal 11 (core dumped)
> pid 79465 (perl5.8.8), uid 0: exited on signal 11 (core dumped)
> pid 79468 (perl5.8.8), uid 0: exited on signal 11 (core dumped)
> pid 79471 (perl5.8.8), uid 0: exited on signal 11 (core dumped)
> pid 79474 (perl5.8.8), uid 0: exited on signal 11 (core dumped)
> pid 79477 (perl5.8.8), uid 0: exited on signal 11 (core dumped)
> [skip]
> 
> a lot of them, perhaps one message for each failed test.
> Does this mean there's something wrong with my perl installation?

I rebuilt perl and passed all tests:

#make check

[skip]

t/zlib/write..ok
All tests successful.
Files=26, Tests=343, 138 wallclock secs (97.92 cusr + 14.59 csys = 112.51 CPU)
#

I think the tests broke because I went from FBSD 6.3 to 7.0.
Apparently perl rebuild is necessary in this case. I didn't 
do it straight away because I was overwhelmed by gettext upgrade.
Since perl does not depend on gettext, I didn't touch it.

However when I realised that only perlmagick tests were failing
(all 697 ImageMagick tests would always pass), and after I
noticed perl exiting on signal 11 with core dumps (see above),
I realised that perl might be the problem.

many thanks to all who replied.
anton

-- 
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 928 8233 
Fax: +44 (0)117 929 4423
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ImageMagick 6.4.1.5 tests fail on FBSD-7.0

[Chris Whitehouse]

Anton Shterenlikht wrote:

On Wed, Jun 18, 2008 at 08:23:20PM +0100, Chris Whitehouse wrote:

Anton Shterenlikht wrote:

I sent a query to ImageMagick port maintainers about this.

I'm getting errors while trying to upgrade to
ImageMagick 6.4.1.5 on FreeBSD 7.0-release.

Below are the error messages and my ImageMagick configuration.

Please advise
many thanks
anton


[skip]

PASS: utilities/tests/wave.sh
PASS: utilities/tests/montage.sh

All 697 tests passed

cd PerlMagick && make CC='cc' test
/bin/sh ../magick.sh PERL_DL_NONLAZY=1 /usr/local/bin/perl5.8.8 
"-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" 
t/*.t t/bzlib/*.t t/fpx/*.t t/jbig/*.t t/jpeg/*.t t/jp2/*.t t/png/*.t 
t/tiff/*.t t/wmf/*.t t/zlib/*.t

t/blobdubious




   Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED test 1
   Failed 1/1 tests, 0.00% okay
t/bzlib/read..dubious
   Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED test 1
   Failed 1/1 tests, 0.00% okay
t/bzlib/write.dubious
   Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED test 1
   Failed 1/1 tests, 0.00% okay
t/composite...dubious
   Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-18
   Failed 18/18 tests, 0.00% okay
t/filter..dubious
   Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-58
   Failed 58/58 tests, 0.00% okay
t/fpx/readdubious
   Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-5
   Failed 5/5 tests, 0.00% okay
t/fpx/write...dubious
   Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-4
   Failed 4/4 tests, 0.00% okay
t/getattributedubious
   Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-25
   Failed 25/25 tests, 0.00% okay
t/jbig/read...dubious
   Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED test 1
   Failed 1/1 tests, 0.00% okay
t/jbig/write..dubious
   Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED test 1
   Failed 1/1 tests, 0.00% okay
t/jp2/readdubious
   Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-3
   Failed 3/3 tests, 0.00% okay
t/jpeg/read...dubious
   Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-2
   Failed 2/2 tests, 0.00% okay
t/jpeg/write..dubious
   Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-2
   Failed 2/2 tests, 0.00% okay
t/montage.dubious
   Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-19
   Failed 19/19 tests, 0.00% okay
t/png/read-16.dubious
   Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-5
   Failed 5/5 tests, 0.00% okay
t/png/readdubious
   Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-6
   Failed 6/6 tests, 0.00% okay
t/png/write-16dubious
   Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-5
   Failed 5/5 tests, 0.00% okay
t/png/write...dubious
   Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-6
   Failed 6/6 tests, 0.00% okay
t/readdubious
   Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-47
   Failed 47/47 tests, 0.00% okay
t/setattributedubious
   Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-71
   Failed 71/71 tests, 0.00% okay
t/tiff/read...dubious
   Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-16
   Failed 16/16 tests, 0.00% okay
t/tiff/write..dubious
   Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-10
   Failed 10/10 tests, 0.00% okay
t/wmf/readdubious
   Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-2
   Failed 2/2 tests, 0.00% okay
t/write...dubious
   Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-32
   Failed 32/32 tests, 0.00% okay
t/zlib/read...dubious
   Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED test 1
   Failed 1/1 tests, 0.00% okay
t/zlib/write..dubious
   Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED test 1
   Failed 1/1 tests, 0.00% okay
Failed Test  Stat Wstat Total Fail  Failed  List of Failed
---
t/blob.t0   139 12 200.00%  1
t/bzlib/read.t  0   139 12 200.00%  1
t/bzlib/write.t 0   139 12 200.00%  1
t/composite.t   0   13918   36 200.00%  1-18
t/filter.t  0   13958  116 200.00%  1-58
t/fpx/read.t0   139 5   10 200.00%  1-5
t/fpx/write.t   0   139 48 200.00%  1-4
t/getattribute.t0   13925   50 200.00%  1-25
t/jbig/read.t   0   139 12 200.00%  1
t/jbig/write.t  0   139 12 200.00%  1
t/jp2/read.t 

Re: ImageMagick 6.4.1.5 tests fail on FBSD-7.0 => perl: signal 11

[Anton Shterenlikht]

On Thu, Jun 19, 2008 at 09:41:01AM +0100, Anton Shterenlikht wrote:
> On Wed, Jun 18, 2008 at 08:23:20PM +0100, Chris Whitehouse wrote:
> > Anton Shterenlikht wrote:
> > >I sent a query to ImageMagick port maintainers about this.
> > >
> > >I'm getting errors while trying to upgrade to
> > >ImageMagick 6.4.1.5 on FreeBSD 7.0-release.
> > >
> > >Below are the error messages and my ImageMagick configuration.
> > >
> > >Please advise
> > >many thanks
> > >anton
> > >
> > >
> > >[skip]
> > >
> > >PASS: utilities/tests/wave.sh
> > >PASS: utilities/tests/montage.sh
> > >
> > >All 697 tests passed
> > >
> > >cd PerlMagick && make CC='cc' test
> > >/bin/sh ../magick.sh PERL_DL_NONLAZY=1 /usr/local/bin/perl5.8.8 
> > >"-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" 
> > >t/*.t t/bzlib/*.t t/fpx/*.t t/jbig/*.t t/jpeg/*.t t/jp2/*.t t/png/*.t 
> > >t/tiff/*.t t/wmf/*.t t/zlib/*.t
> > >t/blobdubious
> > >Test returned status 0 (wstat 139, 0x8b)
> > >DIED. FAILED test 1
> > >Failed 1/1 tests, 0.00% okay
> > >t/bzlib/read..dubious
> > >Test returned status 0 (wstat 139, 0x8b)
> > >DIED. FAILED test 1
> > >Failed 1/1 tests, 0.00% okay
> > >t/bzlib/write.dubious
> > >Test returned status 0 (wstat 139, 0x8b)
> > >DIED. FAILED test 1
> > >Failed 1/1 tests, 0.00% okay
> > >t/composite...dubious
> > >Test returned status 0 (wstat 139, 0x8b)
> > >DIED. FAILED tests 1-18
> > >Failed 18/18 tests, 0.00% okay
> > >t/filter..dubious
> > >Test returned status 0 (wstat 139, 0x8b)
> > >DIED. FAILED tests 1-58
> > >Failed 58/58 tests, 0.00% okay
> > >t/fpx/readdubious
> > >Test returned status 0 (wstat 139, 0x8b)
> > >DIED. FAILED tests 1-5
> > >Failed 5/5 tests, 0.00% okay
> > >t/fpx/write...dubious
> > >Test returned status 0 (wstat 139, 0x8b)
> > >DIED. FAILED tests 1-4
> > >Failed 4/4 tests, 0.00% okay
> > >t/getattributedubious
> > >Test returned status 0 (wstat 139, 0x8b)
> > >DIED. FAILED tests 1-25
> > >Failed 25/25 tests, 0.00% okay
> > >t/jbig/read...dubious
> > >Test returned status 0 (wstat 139, 0x8b)
> > >DIED. FAILED test 1
> > >Failed 1/1 tests, 0.00% okay
> > >t/jbig/write..dubious
> > >Test returned status 0 (wstat 139, 0x8b)
> > >DIED. FAILED test 1
> > >Failed 1/1 tests, 0.00% okay
> > >t/jp2/readdubious
> > >Test returned status 0 (wstat 139, 0x8b)
> > >DIED. FAILED tests 1-3
> > >Failed 3/3 tests, 0.00% okay
> > >t/jpeg/read...dubious
> > >Test returned status 0 (wstat 139, 0x8b)
> > >DIED. FAILED tests 1-2
> > >Failed 2/2 tests, 0.00% okay
> > >t/jpeg/write..dubious
> > >Test returned status 0 (wstat 139, 0x8b)
> > >DIED. FAILED tests 1-2
> > >Failed 2/2 tests, 0.00% okay
> > >t/montage.dubious
> > >Test returned status 0 (wstat 139, 0x8b)
> > >DIED. FAILED tests 1-19
> > >Failed 19/19 tests, 0.00% okay
> > >t/png/read-16.dubious
> > >Test returned status 0 (wstat 139, 0x8b)
> > >DIED. FAILED tests 1-5
> > >Failed 5/5 tests, 0.00% okay
> > >t/png/readdubious
> > >Test returned status 0 (wstat 139, 0x8b)
> > >DIED. FAILED tests 1-6
> > >Failed 6/6 tests, 0.00% okay
> > >t/png/write-16dubious
> > >Test returned status 0 (wstat 139, 0x8b)
> > >DIED. FAILED tests 1-5
> > >Failed 5/5 tests, 0.00% okay
> > >t/png/write...dubious
> > >Test returned status 0 (wstat 139, 0x8b)
> > >DIED. FAILED tests 1-6
> > >Failed 6/6 tests, 0.00% okay
> > >t/readdubious
> > >Test returned status 0 (wstat 139, 0x8b)
> > >DIED. FAILED tests 1-47
> > >Failed 47/47 tests, 0.00% okay
> > >t/setattributedubious
> > >Test returned status 0 (wstat 139, 0x8b)
> > >DIE

Re: ImageMagick 6.4.1.5 tests fail on FBSD-7.0

[Anton Shterenlikht]

On Wed, Jun 18, 2008 at 08:23:20PM +0100, Chris Whitehouse wrote:
> Anton Shterenlikht wrote:
> >I sent a query to ImageMagick port maintainers about this.
> >
> >I'm getting errors while trying to upgrade to
> >ImageMagick 6.4.1.5 on FreeBSD 7.0-release.
> >
> >Below are the error messages and my ImageMagick configuration.
> >
> >Please advise
> >many thanks
> >anton
> >
> >
> >[skip]
> >
> >PASS: utilities/tests/wave.sh
> >PASS: utilities/tests/montage.sh
> >
> >All 697 tests passed
> >
> >cd PerlMagick && make CC='cc' test
> >/bin/sh ../magick.sh PERL_DL_NONLAZY=1 /usr/local/bin/perl5.8.8 
> >"-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" 
> >t/*.t t/bzlib/*.t t/fpx/*.t t/jbig/*.t t/jpeg/*.t t/jp2/*.t t/png/*.t 
> >t/tiff/*.t t/wmf/*.t t/zlib/*.t
> >t/blobdubious
> >Test returned status 0 (wstat 139, 0x8b)
> >DIED. FAILED test 1
> >Failed 1/1 tests, 0.00% okay
> >t/bzlib/read..dubious
> >Test returned status 0 (wstat 139, 0x8b)
> >DIED. FAILED test 1
> >Failed 1/1 tests, 0.00% okay
> >t/bzlib/write.dubious
> >Test returned status 0 (wstat 139, 0x8b)
> >DIED. FAILED test 1
> >Failed 1/1 tests, 0.00% okay
> >t/composite...dubious
> >Test returned status 0 (wstat 139, 0x8b)
> >DIED. FAILED tests 1-18
> >Failed 18/18 tests, 0.00% okay
> >t/filter..dubious
> >Test returned status 0 (wstat 139, 0x8b)
> >DIED. FAILED tests 1-58
> >Failed 58/58 tests, 0.00% okay
> >t/fpx/readdubious
> >Test returned status 0 (wstat 139, 0x8b)
> >DIED. FAILED tests 1-5
> >Failed 5/5 tests, 0.00% okay
> >t/fpx/write...dubious
> >Test returned status 0 (wstat 139, 0x8b)
> >DIED. FAILED tests 1-4
> >Failed 4/4 tests, 0.00% okay
> >t/getattributedubious
> >Test returned status 0 (wstat 139, 0x8b)
> >DIED. FAILED tests 1-25
> >Failed 25/25 tests, 0.00% okay
> >t/jbig/read...dubious
> >Test returned status 0 (wstat 139, 0x8b)
> >DIED. FAILED test 1
> >Failed 1/1 tests, 0.00% okay
> >t/jbig/write..dubious
> >Test returned status 0 (wstat 139, 0x8b)
> >DIED. FAILED test 1
> >Failed 1/1 tests, 0.00% okay
> >t/jp2/readdubious
> >Test returned status 0 (wstat 139, 0x8b)
> >DIED. FAILED tests 1-3
> >Failed 3/3 tests, 0.00% okay
> >t/jpeg/read...dubious
> >Test returned status 0 (wstat 139, 0x8b)
> >DIED. FAILED tests 1-2
> >Failed 2/2 tests, 0.00% okay
> >t/jpeg/write..dubious
> >Test returned status 0 (wstat 139, 0x8b)
> >DIED. FAILED tests 1-2
> >Failed 2/2 tests, 0.00% okay
> >t/montage.dubious
> >Test returned status 0 (wstat 139, 0x8b)
> >DIED. FAILED tests 1-19
> >Failed 19/19 tests, 0.00% okay
> >t/png/read-16.dubious
> >Test returned status 0 (wstat 139, 0x8b)
> >DIED. FAILED tests 1-5
> >Failed 5/5 tests, 0.00% okay
> >t/png/readdubious
> >Test returned status 0 (wstat 139, 0x8b)
> >DIED. FAILED tests 1-6
> >Failed 6/6 tests, 0.00% okay
> >t/png/write-16dubious
> >Test returned status 0 (wstat 139, 0x8b)
> >DIED. FAILED tests 1-5
> >Failed 5/5 tests, 0.00% okay
> >t/png/write...dubious
> >Test returned status 0 (wstat 139, 0x8b)
> >DIED. FAILED tests 1-6
> >Failed 6/6 tests, 0.00% okay
> >t/readdubious
> >Test returned status 0 (wstat 139, 0x8b)
> >DIED. FAILED tests 1-47
> >Failed 47/47 tests, 0.00% okay
> >t/setattributedubious
> >Test returned status 0 (wstat 139, 0x8b)
> >DIED. FAILED tests 1-71
> >Failed 71/71 tests, 0.00% okay
> >t/tiff/read...dubious
> >Test returned status 0 (wstat 139, 0x8b)
> >DIED. FAILED tests 1-16
> >Failed 16/16 tests, 0.00% okay
> >t/tiff/write..dubious
> >Test returned status 0 (wstat 139, 0x8b)
> >DIED. FAILED tests 1-10
> >Failed 10/10 tests, 0.00% okay
> >t/wmf/readdubious
> >Test returned status 0 (wstat 139, 0x8b)
> >DIED. FAILED tests 1-2
> >Failed 2/2 tests, 0.00% okay
>

Re: ImageMagick 6.4.1.5 tests fail on FBSD-7.0

[Yuri Pankov]

On 6/17/2008 1:52 PM, Anton Shterenlikht wrote:

I sent a query to ImageMagick port maintainers about this.

I'm getting errors while trying to upgrade to
ImageMagick 6.4.1.5 on FreeBSD 7.0-release.

Below are the error messages and my ImageMagick configuration.

Please advise
many thanks
anton


[skip]


Meanwhile you can disable tests using `make config -C 
/usr/ports/graphics/ImageMagick`



HTH,
Yuri
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ImageMagick 6.4.1.5 tests fail on FBSD-7.0

[Chris Whitehouse]

Anton Shterenlikht wrote:

I sent a query to ImageMagick port maintainers about this.

I'm getting errors while trying to upgrade to
ImageMagick 6.4.1.5 on FreeBSD 7.0-release.

Below are the error messages and my ImageMagick configuration.

Please advise
many thanks
anton


[skip]

PASS: utilities/tests/wave.sh
PASS: utilities/tests/montage.sh

All 697 tests passed

cd PerlMagick && make CC='cc' test
/bin/sh ../magick.sh PERL_DL_NONLAZY=1 /usr/local/bin/perl5.8.8 "-MExtUtils::Command::MM" 
"-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/bzlib/*.t t/fpx/*.t t/jbig/*.t 
t/jpeg/*.t t/jp2/*.t t/png/*.t t/tiff/*.t t/wmf/*.t t/zlib/*.t
t/blobdubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED test 1
Failed 1/1 tests, 0.00% okay
t/bzlib/read..dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED test 1
Failed 1/1 tests, 0.00% okay
t/bzlib/write.dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED test 1
Failed 1/1 tests, 0.00% okay
t/composite...dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-18
Failed 18/18 tests, 0.00% okay
t/filter..dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-58
Failed 58/58 tests, 0.00% okay
t/fpx/readdubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-5
Failed 5/5 tests, 0.00% okay
t/fpx/write...dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-4
Failed 4/4 tests, 0.00% okay
t/getattributedubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-25
Failed 25/25 tests, 0.00% okay
t/jbig/read...dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED test 1
Failed 1/1 tests, 0.00% okay
t/jbig/write..dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED test 1
Failed 1/1 tests, 0.00% okay
t/jp2/readdubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-3
Failed 3/3 tests, 0.00% okay
t/jpeg/read...dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-2
Failed 2/2 tests, 0.00% okay
t/jpeg/write..dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-2
Failed 2/2 tests, 0.00% okay
t/montage.dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-19
Failed 19/19 tests, 0.00% okay
t/png/read-16.dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-5
Failed 5/5 tests, 0.00% okay
t/png/readdubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-6
Failed 6/6 tests, 0.00% okay
t/png/write-16dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-5
Failed 5/5 tests, 0.00% okay
t/png/write...dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-6
Failed 6/6 tests, 0.00% okay
t/readdubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-47
Failed 47/47 tests, 0.00% okay
t/setattributedubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-71
Failed 71/71 tests, 0.00% okay
t/tiff/read...dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-16
Failed 16/16 tests, 0.00% okay
t/tiff/write..dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-10
Failed 10/10 tests, 0.00% okay
t/wmf/readdubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-2
Failed 2/2 tests, 0.00% okay
t/write...dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-32
Failed 32/32 tests, 0.00% okay
t/zlib/read...dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED test 1
Failed 1/1 tests, 0.00% okay
t/zlib/write..dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED test 1
Failed 1/1 tests, 0.00% okay
Failed Test  Stat Wstat Total Fail  Failed  List of Failed
---
t/blob.t0   139 12 200.00%  1
t/bzlib/read.t  0   139 12 200.00%  1
t/bzlib/write.t 0   139 12 200.00%  1
t/composite.t   0   13918   36 200.00%  1-18
t/filter.t  0   13958  116 200.00%  1-58
t/fpx/read.t0   139 5   10 200.00%  1-5
t/fpx/write.t   0   139 48 200.00%  1-4
t/getattribute.t0   13925   50 200.00%  1-25
t/jbig/read.t   0   139 12 200.00%  1
t/jbig/write.t  0   139 12 200.00%  1
t/jp2/read.t0   139 36 200.00%  1-3
t/jpeg/read.

ImageMagick 6.4.1.5 tests fail on FBSD-7.0

[Anton Shterenlikht]

I sent a query to ImageMagick port maintainers about this.

I'm getting errors while trying to upgrade to
ImageMagick 6.4.1.5 on FreeBSD 7.0-release.

Below are the error messages and my ImageMagick configuration.

Please advise
many thanks
anton


[skip]

PASS: utilities/tests/wave.sh
PASS: utilities/tests/montage.sh

All 697 tests passed

cd PerlMagick && make CC='cc' test
/bin/sh ../magick.sh PERL_DL_NONLAZY=1 /usr/local/bin/perl5.8.8 
"-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t 
t/bzlib/*.t t/fpx/*.t t/jbig/*.t t/jpeg/*.t t/jp2/*.t t/png/*.t t/tiff/*.t 
t/wmf/*.t t/zlib/*.t
t/blobdubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED test 1
Failed 1/1 tests, 0.00% okay
t/bzlib/read..dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED test 1
Failed 1/1 tests, 0.00% okay
t/bzlib/write.dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED test 1
Failed 1/1 tests, 0.00% okay
t/composite...dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-18
Failed 18/18 tests, 0.00% okay
t/filter..dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-58
Failed 58/58 tests, 0.00% okay
t/fpx/readdubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-5
Failed 5/5 tests, 0.00% okay
t/fpx/write...dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-4
Failed 4/4 tests, 0.00% okay
t/getattributedubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-25
Failed 25/25 tests, 0.00% okay
t/jbig/read...dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED test 1
Failed 1/1 tests, 0.00% okay
t/jbig/write..dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED test 1
Failed 1/1 tests, 0.00% okay
t/jp2/readdubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-3
Failed 3/3 tests, 0.00% okay
t/jpeg/read...dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-2
Failed 2/2 tests, 0.00% okay
t/jpeg/write..dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-2
Failed 2/2 tests, 0.00% okay
t/montage.dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-19
Failed 19/19 tests, 0.00% okay
t/png/read-16.dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-5
Failed 5/5 tests, 0.00% okay
t/png/readdubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-6
Failed 6/6 tests, 0.00% okay
t/png/write-16dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-5
Failed 5/5 tests, 0.00% okay
t/png/write...dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-6
Failed 6/6 tests, 0.00% okay
t/readdubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-47
Failed 47/47 tests, 0.00% okay
t/setattributedubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-71
Failed 71/71 tests, 0.00% okay
t/tiff/read...dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-16
Failed 16/16 tests, 0.00% okay
t/tiff/write..dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-10
Failed 10/10 tests, 0.00% okay
t/wmf/readdubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-2
Failed 2/2 tests, 0.00% okay
t/write...dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED tests 1-32
Failed 32/32 tests, 0.00% okay
t/zlib/read...dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED test 1
Failed 1/1 tests, 0.00% okay
t/zlib/write..dubious
Test returned status 0 (wstat 139, 0x8b)
DIED. FAILED test 1
Failed 1/1 tests, 0.00% okay
Failed Test  Stat Wstat Total Fail  Failed  List of Failed
---
t/blob.t0   139 12 200.00%  1
t/bzlib/read.t  0   139 12 200.00%  1
t/bzlib/write.t 0   139 12 200.00%  1
t/composite.t   0   13918   36 200.00%  1-18
t/filter.t  0   13958  116 200.00%  1-58
t/fpx/read.t0   139 5   10 200.00%  1-5
t/fpx/write.t   0   139 48 200.00%  1-4
t/getattribute.t0   13925   50 200.00%  1-25
t/jbig/read.t   0   139 12 200.00%  1
t/jbig/write.t  0   139 12 200.00%  1
t/jp2/read.t0   139 36 200.00%  1-3
t/jpeg/read.t   0   139 

Ports best practice (was Re: Imagemagick port seems broken....)

[Jonathan McKeown]

On Tuesday 13 May 2008 01:04, Johan  Dowdy wrote:
> Just as a best practice you might want to consider running a weekly cvsup
> out of cron.

I'm not sure I'd call this best practice in all cases, having taken over a 
network where every server OS install, and every port, used whatever had been 
the latest and greatest that day (at one stage I think I was running every 
release from 4.8 to 6.0, plus a couple of boxes running given snapshots of 
-STABLE).

I can do without the irritation of having to check, every time I log in to a 
different machine, whether the command I'm about to run or the config file 
I'm about to edit supports the option I'm hoping to use.

I now have most of the servers running the same OS release, and running the 
same version of each port, all installed from a central build server with 
locally-built packages where possible.

When something needs to be upgraded, we follow a documented procedure to make 
sure that there are no problems or regressions and that everything stays more 
or less in step.

Yes, it means our ports tree is often three months or so out of date. You'd be 
surprised how seldom that causes a problem. You'd be astonished how much 
easier it makes my life knowing every setup is the same.

Jonathan
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Imagemagick port seems broken - jp2.c patch fails

[Johan Dowdy]

Just as a best practice you might want to consider running a weekly cvsup
out of cron.
You should probably always run it before installing anything out of ports,
but if you have it as a weekly scheduled task, it will decrease the time it
takes to run when you ³need² to run it.

Of course portsnap also rocks the party. I¹m just old school and stuck in
cvsup land.

-J


On 5/12/08 1:06 AM, "Da Rock" <[EMAIL PROTECTED]> wrote:

> 
> 
> On Mon, 2008-05-12 at 08:03 +0100, Glyn Millington wrote:
>> > Da Rock <[EMAIL PROTECTED]> writes:
>> >
>>> > > On Mon, 2008-05-12 at 08:02 +0200, Roland Smith wrote:
>>>> > >> On Mon, May 12, 2008 at 09:46:31AM +1000, Da Rock wrote:
>>>>> > >> > I may be not thinking straight due to a head cold- in which case
just
>>>>> > >> > tell me so- but building Imagemagick-6.4.0.7 from ports is failing.
It
>>>> > >>
>>>> > >> Update your ports tree. The current version in ports is 6.4.1.0. There
>>>> > >> have been some problems with 6.4.0.7, see
>>>> > >> http://www.freshports.org/graphics/ImageMagick/
>>>> > >>
>>>> > >> Roland
>>> > >
>>> > > You'll have to excuse me- I'm not usually such a dunderhead- but how do
>>> > > I go about that? I ran portsnap update and it says the tree is up to
>>> > > date.
>> >
>> > Shouldn't it be
>> >
>> >
>> > portsnap fetch update
>> >  ^
>> >
>> > atb
>> >
>> > Glyn
>> >
> 
> I told you I wasn't with it. Of course that works now... I've updated
> AND installed imagemagick. I use portsnap fetch then portsnap update
> usually- but of course I forgot the first step in my foggy brain.
> 
> Thanks for your patience guys
> 
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> 


-- 
Johan Dowdy - CISSP
Senior Systems Administrator
nCircle Network Security
 
415.318.2880

"Any sufficiently advanced technology is indistinguishable from magic."
-- Arthur C. Clarke

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Imagemagick port seems broken - jp2.c patch fails

[Matthew Donovan]

I just tried to install imagemagick from ports myself and it installed fine 
maybe it's a 6.3 issue since I m on 7.0 or your ports is out of date 
considering here the imagemagick port installs ImageMagick-6.4.1.0

On Mon, May 12, 2008 at 11:53:18AM +1000, Da Rock wrote:
> 
> On Sun, 2008-05-11 at 17:20 -0700, Johan Dowdy wrote:
> > Did you cvsup before attempting the install?
> > 
> > -J
> > 
> 
> Do you mean update the ports tree? This is a relatively new install of
> 6.3 (last week or so) with a minimal distro and no ports tree installed
> at the time. I run portsnap manually after install nowadays so that the
> latest and greatest is installed from the start. I'll try updating, but
> pkg_version -v seems up to date so I doubt very much it'll make a diff.
> 
> 
> > - Original Message -
> > From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> > To: freebsd-questions@freebsd.org 
> > Sent: Sun May 11 16:46:31 2008
> > Subject: Imagemagick port seems broken - jp2.c patch fails
> > 
> > I may be not thinking straight due to a head cold- in which case just
> > tell me so- but building Imagemagick-6.4.0.7 from ports is failing. It
> > attempts to find Imagemagick folder in the work folder but cannot do so.
> > I ran ls but all it has is .extract.imagemagick._usr_local or the like
> > (the exact message is on another system atm).
> > 
> > All I want is to install lives, but this has killed that. Any ideas what
> > I can do? Or is this something to send to the ports list? Time is of the
> > essence here, so thats why I thought somebody here might be able to find
> > a workaround so I can continue for now and post to ports later.
> > 
> > Cheers
> > 
> > ___
> > freebsd-questions@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> > 
> > 
> 
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Imagemagick port seems broken - jp2.c patch fails

[Da Rock]

On Mon, 2008-05-12 at 08:03 +0100, Glyn Millington wrote:
> Da Rock <[EMAIL PROTECTED]> writes:
> 
> > On Mon, 2008-05-12 at 08:02 +0200, Roland Smith wrote:
> >> On Mon, May 12, 2008 at 09:46:31AM +1000, Da Rock wrote:
> >> > I may be not thinking straight due to a head cold- in which case just
> >> > tell me so- but building Imagemagick-6.4.0.7 from ports is failing. It
> >> 
> >> Update your ports tree. The current version in ports is 6.4.1.0. There
> >> have been some problems with 6.4.0.7, see
> >> http://www.freshports.org/graphics/ImageMagick/ 
> >> 
> >> Roland
> >
> > You'll have to excuse me- I'm not usually such a dunderhead- but how do
> > I go about that? I ran portsnap update and it says the tree is up to
> > date.
> 
> Shouldn't it be
> 
> 
> portsnap fetch update
>  ^
> 
> atb
> 
> Glyn
> 

I told you I wasn't with it. Of course that works now... I've updated
AND installed imagemagick. I use portsnap fetch then portsnap update
usually- but of course I forgot the first step in my foggy brain.

Thanks for your patience guys

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Imagemagick port seems broken - jp2.c patch fails

[Roland Smith]

On Mon, May 12, 2008 at 04:58:54PM +1000, Da Rock wrote:
> 
> On Mon, 2008-05-12 at 08:02 +0200, Roland Smith wrote:
> > On Mon, May 12, 2008 at 09:46:31AM +1000, Da Rock wrote:
> > > I may be not thinking straight due to a head cold- in which case just
> > > tell me so- but building Imagemagick-6.4.0.7 from ports is failing. It
> > 
> > Update your ports tree. The current version in ports is 6.4.1.0. There
> > have been some problems with 6.4.0.7, see
> > http://www.freshports.org/graphics/ImageMagick/ 
> > 
> > Roland
> 
> You'll have to excuse me- I'm not usually such a dunderhead- but how do
> I go about that? I ran portsnap update and it says the tree is up to
> date.

You have to get updates before you can apply them. So use:

portsnap fetch update

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)


pgphNvtGY0QrF.pgp
Description: PGP signature

Re: Imagemagick port seems broken - jp2.c patch fails

[Valentin Bud]

you must use

portsnap fetch update

from the man portsnap:
update   Update a ports tree extracted using the extract command.
  You must run this command to apply changes to your ports
  tree after downloading updates via the *fetch* or cron
com-
  mands.  Again, note that in the parts of the ports tree
  which are being updated, any local changes or additions
will
  be removed.

all the best V


On Mon, May 12, 2008 at 9:58 AM, Da Rock <[EMAIL PROTECTED]>
wrote:

>
> On Mon, 2008-05-12 at 08:02 +0200, Roland Smith wrote:
> > On Mon, May 12, 2008 at 09:46:31AM +1000, Da Rock wrote:
> > > I may be not thinking straight due to a head cold- in which case just
> > > tell me so- but building Imagemagick-6.4.0.7 from ports is failing. It
> >
> > Update your ports tree. The current version in ports is 6.4.1.0. There
> > have been some problems with 6.4.0.7, see
> > http://www.freshports.org/graphics/ImageMagick/
> >
> > Roland
>
> You'll have to excuse me- I'm not usually such a dunderhead- but how do
> I go about that? I ran portsnap update and it says the tree is up to
> date.
>
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> [EMAIL PROTECTED]"
>



-- 
Kind Regards,

Valentin Bud

www.syk.ro
www.spreadbsd.org/aff/86/1
www.spreadbsd.org/aff/86/2

valentin [dot] bud [at] gmail [dot] com
valentin [dot] bud [at] dep [dot] upt [dot] ro
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Imagemagick port seems broken - jp2.c patch fails

[Da Rock]

On Mon, 2008-05-12 at 08:02 +0200, Roland Smith wrote:
> On Mon, May 12, 2008 at 09:46:31AM +1000, Da Rock wrote:
> > I may be not thinking straight due to a head cold- in which case just
> > tell me so- but building Imagemagick-6.4.0.7 from ports is failing. It
> 
> Update your ports tree. The current version in ports is 6.4.1.0. There
> have been some problems with 6.4.0.7, see
> http://www.freshports.org/graphics/ImageMagick/ 
> 
> Roland

You'll have to excuse me- I'm not usually such a dunderhead- but how do
I go about that? I ran portsnap update and it says the tree is up to
date.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Imagemagick port seems broken - jp2.c patch fails

[Roland Smith]

On Mon, May 12, 2008 at 09:46:31AM +1000, Da Rock wrote:
> I may be not thinking straight due to a head cold- in which case just
> tell me so- but building Imagemagick-6.4.0.7 from ports is failing. It

Update your ports tree. The current version in ports is 6.4.1.0. There
have been some problems with 6.4.0.7, see
http://www.freshports.org/graphics/ImageMagick/ 

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)


pgpyeiMoEECa5.pgp
Description: PGP signature

Re: Imagemagick port seems broken - jp2.c patch fails

[Da Rock]

On Sun, 2008-05-11 at 23:50 -0400, Matthew Donovan wrote:
> I just tried to install imagemagick from ports myself and it installed fine 
> maybe it's a 6.3 issue since I m on 7.0 or your ports is out of date 
> considering here the imagemagick port installs ImageMagick-6.4.1.0
> 

Ok then, it must be a 6.3 issue. I ran portsnap update and the tree is
up to date as I thought. The error is a weird one- the patch looking for
a directory that isn't there, why would there be a Imagemagick directory
under the work directory? And where are all the source files for the
build which should be under the work directory? Instead just an empty
file named .extract_done.imagemagick._usr_local.

I've also looked under /usr/local but I can't find anything there
either.


> On Mon, May 12, 2008 at 11:53:18AM +1000, Da Rock wrote:
> > 
> > On Sun, 2008-05-11 at 17:20 -0700, Johan Dowdy wrote:
> > > Did you cvsup before attempting the install?
> > > 
> > > -J
> > > 
> > 
> > Do you mean update the ports tree? This is a relatively new install of
> > 6.3 (last week or so) with a minimal distro and no ports tree installed
> > at the time. I run portsnap manually after install nowadays so that the
> > latest and greatest is installed from the start. I'll try updating, but
> > pkg_version -v seems up to date so I doubt very much it'll make a diff.
> > 
> > 
> > > - Original Message -
> > > From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> > > To: freebsd-questions@freebsd.org 
> > > Sent: Sun May 11 16:46:31 2008
> > > Subject: Imagemagick port seems broken - jp2.c patch fails
> > > 
> > > I may be not thinking straight due to a head cold- in which case just
> > > tell me so- but building Imagemagick-6.4.0.7 from ports is failing. It
> > > attempts to find Imagemagick folder in the work folder but cannot do so.
> > > I ran ls but all it has is .extract.imagemagick._usr_local or the like
> > > (the exact message is on another system atm).
> > > 
> > > All I want is to install lives, but this has killed that. Any ideas what
> > > I can do? Or is this something to send to the ports list? Time is of the
> > > essence here, so thats why I thought somebody here might be able to find
> > > a workaround so I can continue for now and post to ports later.
> > > 
> > > Cheers
> > > 
> > > ___
> > > freebsd-questions@freebsd.org mailing list
> > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > > To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> > > 
> > > 
> > 
> > ___
> > freebsd-questions@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> > 
> 

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Imagemagick port seems broken - jp2.c patch fails

[Da Rock]

On Sun, 2008-05-11 at 17:20 -0700, Johan Dowdy wrote:
> Did you cvsup before attempting the install?
> 
> -J
> 

Do you mean update the ports tree? This is a relatively new install of
6.3 (last week or so) with a minimal distro and no ports tree installed
at the time. I run portsnap manually after install nowadays so that the
latest and greatest is installed from the start. I'll try updating, but
pkg_version -v seems up to date so I doubt very much it'll make a diff.


> - Original Message -
> From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> To: freebsd-questions@freebsd.org 
> Sent: Sun May 11 16:46:31 2008
> Subject: Imagemagick port seems broken - jp2.c patch fails
> 
> I may be not thinking straight due to a head cold- in which case just
> tell me so- but building Imagemagick-6.4.0.7 from ports is failing. It
> attempts to find Imagemagick folder in the work folder but cannot do so.
> I ran ls but all it has is .extract.imagemagick._usr_local or the like
> (the exact message is on another system atm).
> 
> All I want is to install lives, but this has killed that. Any ideas what
> I can do? Or is this something to send to the ports list? Time is of the
> essence here, so thats why I thought somebody here might be able to find
> a workaround so I can continue for now and post to ports later.
> 
> Cheers
> 
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> 
> 

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Imagemagick port seems broken - jp2.c patch fails

[Johan Dowdy]

Did you cvsup before attempting the install?

-J

- Original Message -
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
To: freebsd-questions@freebsd.org 
Sent: Sun May 11 16:46:31 2008
Subject: Imagemagick port seems broken - jp2.c patch fails

I may be not thinking straight due to a head cold- in which case just
tell me so- but building Imagemagick-6.4.0.7 from ports is failing. It
attempts to find Imagemagick folder in the work folder but cannot do so.
I ran ls but all it has is .extract.imagemagick._usr_local or the like
(the exact message is on another system atm).

All I want is to install lives, but this has killed that. Any ideas what
I can do? Or is this something to send to the ports list? Time is of the
essence here, so thats why I thought somebody here might be able to find
a workaround so I can continue for now and post to ports later.

Cheers

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Imagemagick port seems broken - jp2.c patch fails

[Da Rock]

I may be not thinking straight due to a head cold- in which case just
tell me so- but building Imagemagick-6.4.0.7 from ports is failing. It
attempts to find Imagemagick folder in the work folder but cannot do so.
I ran ls but all it has is .extract.imagemagick._usr_local or the like
(the exact message is on another system atm).

All I want is to install lives, but this has killed that. Any ideas what
I can do? Or is this something to send to the ports list? Time is of the
essence here, so thats why I thought somebody here might be able to find
a workaround so I can continue for now and post to ports later.

Cheers

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Distfile size mismatch for ImageMagick portupgrade

[Mike Clarke]

On Wednesday 30 April 2008, Lowell Gilbert wrote:

> The tarball was re-rolled.
> The port has now been updated accordingly.

Thanks. I've got the new version now

-- 
Mike Clarke
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Distfile size mismatch for ImageMagick portupgrade

[Lowell Gilbert]

Mike Clarke <[EMAIL PROTECTED]> writes:

> Upgrading ImageMagick from 6.3.6.9 to 6.4.0.11 fails after downloading 
> the distfile with "size mismatch: expected 5837175, actual 5836089".
>
> I don't see anything relevant in UPDATING or on the Freshports site. 
> I've run pkgdb -u and downloaded a fresh copy 
> of /usr/ports/graphics/ImageMagick but still get the problem.
>
> Is this a general problem or have I overlooked something?

The tarball was re-rolled. 
The port has now been updated accordingly.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Distfile size mismatch for ImageMagick portupgrade

[Mike Clarke]

Upgrading ImageMagick from 6.3.6.9 to 6.4.0.11 fails after downloading 
the distfile with "size mismatch: expected 5837175, actual 5836089".

I don't see anything relevant in UPDATING or on the Freshports site. 
I've run pkgdb -u and downloaded a fresh copy 
of /usr/ports/graphics/ImageMagick but still get the problem.

Is this a general problem or have I overlooked something?

-- 
Mike Clarke
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ImageMagick problem

[Matiss]

Thanks!

I guess I should just wait then, and compile from ports for now.
Thanks :)
  Quoting Lowell Gilbert : 
 The current state of the port:

http://portsmon.freebsd.org/portoverview.py?category=graphics&portname=ImageMagick
 

Links:
--
[1] mailto:[EMAIL PROTECTED]

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ImageMagick problem

[Lowell Gilbert]

Matiss <[EMAIL PROTECTED]> writes:

> So sorry, didn't noticed I don't have a subject in original mail.
> Hey all
>  Hope this is more or less right place to ask. 
>  What I noticed on my FreeBSD 6.2 installation, that 
>  pkg_add -r ImageMagick results in a file not found error.
>  DTG864# pkg_add -r ImageMagick
>  Error: FTP Unable to get
>
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/Latest/ImageMagick.tbz:
>  File unavailable (e.g., file not found, no access)
>  same with pkg_add -r ImageMagick-nox11.
>  and sure enough, indeed there is no ImageMagick.tbz on freebsd ftp
>  server for freebsd version 6. Browsed the net, but couldn't find any
>  info on this. 
>  Of course I could compile from ports, but that takes too much time.
>  So, any ideas, why there is no ImageMagick.tbz, and what shall one
>  do? :)

The current state of the port:
http://portsmon.freebsd.org/portoverview.py?category=graphics&portname=ImageMagick

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"