headers
Rich Shepard | 1 Aug 2009 01:04
Favicon

Re: What Is .txz As Package Extension?

On Sat, 1 Aug 2009, markus reichelt wrote:

> Blame SuSE. They started the hype of using a new archiver, and sadly
> others joined the frenzy.

Markus,

   No reason to blame Novell/SuSE. After all, if gzip ain't broke, why break
ie? But, if Pat wants to change the packaging why not use .deb or .rpm?
Those are certainly well established and well supported.

> .txz is the new Slackware package archive extension. If you search
> this list's archive (or the official Changelog) you'll stumble upon
> it: LZMA, May 8th ...

   I didn't see that come across this mail list.

   So now I can expect another difficult upgrade because of major changes? Is
this going to break all the SlackBuild.org packages and all those I've
created myself. What a shame!

Thanks,

Rich
Permalink | Reply | 2 comments |
headers
Willy Sudiarto Raharjo | 1 Aug 2009 01:07
Picon
Gravatar

Re: What Is .txz As Package Extension?


>   No reason to blame Novell/SuSE. After all, if gzip ain't broke, why break
> ie? But, if Pat wants to change the packaging why not use .deb or .rpm?
> Those are certainly well established and well supported.

What's change is only the algorithm to compress the archive, not the formats

>   So now I can expect another difficult upgrade because of major changes? Is
> this going to break all the SlackBuild.org packages and all those I've
> created myself. What a shame!

pkgtool is still in tgz format, but it could work on tgz or newer txz
formats, so it's backward compatibility. But in order to be able to
work with txz, you must install/upgrade several packages first, which
should be installed by default on Slackware 13.0

--
Willy Sudiarto Raharjo
Registered Linux User : 336579
Web : http://www.informatix.or.id/willy
Blog : http://willysr.blogspot.com http://slackblogs.blogspot.com
Permalink | Reply | 1 comment |
headers
Rich Shepard | 1 Aug 2009 01:13
Favicon

Re: What Is .txz As Package Extension?

On Sat, 1 Aug 2009, Willy Sudiarto Raharjo wrote:

> What's change is only the algorithm to compress the archive, not the formats

   Ah, that's what I thought, but I wasn't sure.

> pkgtool is still in tgz format, but it could work on tgz or newer txz
> formats, so it's backward compatibility. But in order to be able to work
> with txz, you must install/upgrade several packages first, which should be
> installed by default on Slackware 13.0

   OK. Guess that I'll not install firefox-3.5.1 now, then. I could change
the script to use the gzip archiver but that might cause problems during the
distribution upgrade.

Thanks, Willy,

Rich
Permalink | Reply | 0 comments |
headers
Morten Juhl-Johansen Zölde-Fejér | 9 Aug 2009 09:43
Picon

Gmrun build errors

Dear all,
A request for an eye from those wiser than me.
I was building Gmrun on Slackware-current to use with Openbox, but I get
the errors indicated in this file:
http://syntaktisk.dk/files/gmrun_output
I am guessing I am missing something. Any pointers?

Yours,
Morten
Permalink | Reply | 5 comments |
headers
Laurence Darby | 9 Aug 2009 19:22
Favicon

Re: Gmrun build errors


Hi,

Morten Juhl-Johansen Zölde-Fejér wrote:

> Dear all,
> A request for an eye from those wiser than me.
> I was building Gmrun on Slackware-current to use with Openbox, but I get
> the errors indicated in this file:
> http://syntaktisk.dk/files/gmrun_output
> I am guessing I am missing something. Any pointers?

I saw a similar problem a few of days ago, looks like the newer
gcc's are being more strict.  The source code needed to be updated to have:

#include <cstring>

Hope that helps

Laurence
Permalink | Reply | 4 comments |
headers
Robby Workman | 9 Aug 2009 19:40

Re: Gmrun build errors

On Sun, 9 Aug 2009 18:22:52 +0100
Laurence Darby <ldarby <at> tuffmail.com> wrote:

> Morten Juhl-Johansen Zölde-Fejér wrote:
> 
> > Dear all,
> > A request for an eye from those wiser than me.
> > I was building Gmrun on Slackware-current to use with Openbox, but
> > I get the errors indicated in this file:
> > http://syntaktisk.dk/files/gmrun_output
> > I am guessing I am missing something. Any pointers?
> 
> 
> I saw a similar problem a few of days ago, looks like the newer
> gcc's are being more strict.  The source code needed to be updated to
> have:
> 
> #include <cstring>
> 
> Hope that helps

If it doesn't, then include string.h in gtkcompletionline.cc and
that should fix it.

For future reference, "man strlen" or "man strcmp" (using a few of
the missing declarations) will show you that string.h is the missing
include  :-)

-RW
(Continue reading)

Permalink | Reply | 3 comments |
headers
Morten Juhl-Johansen Zölde-Fejér | 10 Aug 2009 09:36
Picon

Re: Gmrun build errors


---- 8< ----  ---- 8< ----
> On Sun, 9 Aug 2009 18:22:52 +0100
> Laurence Darby <ldarby <at> tuffmail.com> wrote:
> Robby Workman wrote:
---- 8< ----  ---- 8< ----

Thank you both for your help. Gmrun is a brilliant tool with Openbox - I
would hate to have to do without a runbox on Openbox.

Yours,
M
__
http://www.syntaktisk.dk
Permalink | Reply | 0 comments |
headers
Morten Juhl-Johansen Zölde-Fejér | 10 Aug 2009 17:37
Picon

Re: Gmrun build errors

Again, thank you for your help. Well, I did as was suggested and am
rewarded by a new error message:

gmrun-0.9.2 $ ./configure && make
loading cache ./config.cache
checking for a BSD compatible install... (cached) /usr/bin/ginstall -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... (cached) yes
checking for working aclocal-1.4... missing
checking for working autoconf... found
checking for working automake-1.4... missing
checking for working autoheader... found
checking for working makeinfo... found
checking for strerror in -lcposix... (cached) no
checking for gcc... (cached) gcc
checking whether the C compiler (gcc  ) works... yes
checking whether the C compiler (gcc  ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ANSI C... (cached) none needed
checking for dirent.h that defines DIR... (cached) yes
checking for opendir in -ldir... (cached) no
checking how to run the C preprocessor... (cached) gcc -E
checking for ANSI C header files... (cached) yes
checking for c++... (cached) c++
checking whether the C++ compiler (c++  ) works... yes
checking whether the C++ compiler (c++  ) is a cross-compiler... no
checking whether we are using GNU C++... (cached) yes
checking whether c++ accepts -g... (cached) yes
checking for stlport libraries... (cached) no
(Continue reading)

Permalink | Reply | 1 comment |
headers
Robby Workman | 10 Aug 2009 18:08

Re: Gmrun build errors

On Mon, 10 Aug 2009 17:37:10 +0200
Morten Juhl-Johansen Zölde-Fejér <mjjzf <at> syntaktisk.dk> wrote:

> Again, thank you for your help. Well, I did as was suggested and am
> rewarded by a new error message:
> 
> gmrun-0.9.2 $ ./configure && make
> loading cache ./config.cache
> checking for a BSD compatible install... (cached) /usr/bin/ginstall -c
> checking whether build environment is sane... yes
> checking whether make sets ${MAKE}... (cached) yes
> checking for working aclocal-1.4... missing
> checking for working autoconf... found
> checking for working automake-1.4... missing
> checking for working autoheader... found
> checking for working makeinfo... found
> checking for strerror in -lcposix... (cached) no
> checking for gcc... (cached) gcc
> checking whether the C compiler (gcc  ) works... yes
> checking whether the C compiler (gcc  ) is a cross-compiler... no
> checking whether we are using GNU C... (cached) yes
> checking whether gcc accepts -g... (cached) yes
> checking for gcc option to accept ANSI C... (cached) none needed
> checking for dirent.h that defines DIR... (cached) yes
> checking for opendir in -ldir... (cached) no
> checking how to run the C preprocessor... (cached) gcc -E
> checking for ANSI C header files... (cached) yes
> checking for c++... (cached) c++
> checking whether the C++ compiler (c++  ) works... yes
> checking whether the C++ compiler (c++  ) is a cross-compiler... no
(Continue reading)

Permalink | Reply | 0 comments |
headers
Rich Shepard | 18 Aug 2009 03:13
Favicon

Problem Building Ekiga-3.2.4

   I'm trying to build ekiga-3.2.4 using the SlackBuild using the newest
ekiga.SlackBuild script which has a patch for gtk+2-2.12.12. It's failing
during the configure step:

checking for XV... configure: error: Package requirements (xv) were not met:

Package file '/usr/lib/pkgconfig/xextproto.pc' appears to be empty
Package 'xextproto' has no Name: field

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables XV_CFLAGS
and XV_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

   XV is installed as part of the -12.2 distribution, so I am uncertain what
I should do to resolve this issue. Why xextproto.pc is empty I've no idea,
and I don't know to what the environment variables ought to be set to avoid
calling pkg-config.

   A clue would be very helpful.

Rich
Permalink | Reply | 2 comments |

Gmane