From: David Bolt on
On Tuesday 29 Dec 2009 01:42, while playing with a tin of spray paint,
Malcolm painted this mural:

> Hi
> In library linking? Might be that change they did on the as-needed in
> Factory?
>
> See this bug;
> https://bugzilla.novell.com/show_bug.cgi?id=533563

No, I used the workaround for that, and added a patch to handle some
missing headers, it almost builds. I forgot to check build logs after
the last checkin and so missed that it was failing on a directory that
wasn't owned by anything. I've updated the spec, again, and this time
it builds. Not sure I like the fix, but nothing else seems to provide
/usr/share/locale/sr(a)Latn or /usr/share/locale/sr(a)Latn/LC_MESSAGES so
pan might as well.


Regards,
David Bolt

--
Team Acorn: www.distributed.net OGR-NG @ ~100Mnodes RC5-72 @ ~1Mkeys/s
openSUSE 11.0 32b | | openSUSE 11.2 32b |
openSUSE 11.0 64b | openSUSE 11.1 64b | openSUSE 11.2 64b |
TOS 4.02 | openSUSE 11.1 PPC | RISC OS 4.02 | RISC OS 3.11
From: David Bolt on
On Tuesday 29 Dec 2009 10:46, while playing with a tin of spray paint,
central painted this mural:

<snip>

> log.cc:106: error: 'vsnprintf' was not declared in this scope
> log.cc: In static member function 'static void pan::Log::add_urgent_va
> (const char*, ...)':
> log.cc:118: error: 'vsnprintf' was not declared in this scope

> Which seems strange to me, as it ran perfectly under 11.0 (this is the
> same source), using houghi's method, but failing at the make stage.

It's failing due to missing headers. Gcc 4.4 is rather more strict with
respect to the headers and so where it would compile before,, now it
fails. To get past this, you need to patch several files to add the
line:

#include <cstdio>

with the other #include lines. The files you need to patch are:

pan-0.133/pan/general/log.cc
pan-0.133/pan/general/progress.cc
pan-0.133/pan/tasks/nntp.cc
pan-0.133/pan/tasks/nntp-pool.cc
pan-0.133/pan/usenet-utils/numbers.cc

> I'm
> well out of my comfort zone here, but would still like to get it sorted
> if I can...

If you're interested, send me a patch and I'll add it to my collection.


Regards,
David Bolt

--
Team Acorn: www.distributed.net OGR-NG @ ~100Mnodes RC5-72 @ ~1Mkeys/s
openSUSE 11.0 32b | | openSUSE 11.2 32b |
openSUSE 11.0 64b | openSUSE 11.1 64b | openSUSE 11.2 64b |
TOS 4.02 | openSUSE 11.1 PPC | RISC OS 4.02 | RISC OS 3.11
From: David Bolt on
On Tuesday 29 Dec 2009 13:00, while playing with a tin of spray paint,
central painted this mural:


> Right then, clearly I'm missing something, no doubt because I couldn't be
> bothered to start from page 1 many years ago :)
> ./configure and make seem to work fine after the above patches (I've
> searched the output for 'error', 'fail' etc, just to be sure.
>
> sudo checkinstall gives the 'message command not found' (I assume this is
> to do with paths?).
>
> if I su to work as root, checkinstall gives a raft of errors along the
> lines of:
> error: File not found: /usr/src/packages/BUILDROOT/pan-0.133-2.x86_64/usr
>
> followed by:
> RPM build errors:
> File not found: /usr/src/packages/BUILDROOT/pan-0.133-2.x86_64/usr
> etc etc, which is hardly surprising as there are no files in /usr/src/
> packages/BUILDROOT/

Interesting. I'd not have expected checkinstall to be using
/usr/src/packages/BUILDROOT as that's normally where rpmbuild would be
building packages. Having said that, the last time I used checkinstall
was as a learning tool to figure out how to write my own spec files and
do proper packaging, way back to when 8.0 was current.

> Which in turn makes me think I've done something wrong in configure /
> make. Should I be moving those somewhere first? Or looking for an error I
> havent seen? I'm running these in /home/user which is what I did in 11.0
> with configure/make/install. Maybe I need to uninstall the original pan
> first? (or just go back and RTFM right from the start...)

AFAIK, there's a spec file included in the sources[0]. It does need a
little tweaking to match the openSUSE packaging guidelines, and some
BuildRequires: adding, but it's not a lot of stuff to add and then you
could use rpmbuild to build the package properly. In the end, it makes
maintenance much easier than using a barely supported tool.

If you have a buildservice account, you can find the spec file and all
the patches I use here:

https://build.opensuse.org/package/show?package=pan&project=home%3Adavjam79


[0] Not that I use it for my builds. I wrote my own so the same package
will build properly on the major distros[1], and I've even included
SLES 11. Now all I need to do is sort out the build failures on
Mandriva 2010 and it'll be built for the full set.

[1] rpm based distros at least. I've only one package that I build for
Debian based distros, but that's in a sub-project of my main
buildservice home[2] since it's easier than disabling the various repos
for all the other packages.

[2] http://download.opensuse.org/repositories/home:/davjam79/

Regards,
David Bolt

--
Team Acorn: www.distributed.net OGR-NG @ ~100Mnodes RC5-72 @ ~1Mkeys/s
openSUSE 11.0 32b | | openSUSE 11.2 32b |
openSUSE 11.0 64b | openSUSE 11.1 64b | openSUSE 11.2 64b |
TOS 4.02 | openSUSE 11.1 PPC | RISC OS 4.02 | RISC OS 3.11
From: Malcolm on
On 29 Dec 2009 15:16:01 GMT
central <central77(a)fastmailNOSPAM.fm> wrote:

> On Tue, 29 Dec 2009 16:04:40 +0100, houghi wrote:
>
> > central wrote:
> >> Which in turn makes me think I've done something wrong in
> >> configure / make. Should I be moving those somewhere first? Or
> >> looking for an error I havent seen? I'm running these
> >> in /home/user which is what I did in 11.0 with
> >> configure/make/install. Maybe I need to uninstall the original pan
> >> first? (or just go back and RTFM right from the start...)
> >
> > Do as root `which checkinstall` and you will see the whole path to
> > use with sudo.
>
> /usr/sbin/checkinstall
>
>
> >
> > Also it asumes that a `make install` works. And you must be in the
> > directory where you would normally run `make install`
>
> see other post - it didnt :(
> >
> > I always make a seperate directory for each build I make e.g.
> > /home/houghi/dev/pan.1.2.3/
> >
> Thats pretty much what I had already done. Never mind, in Linux there
> is *always* more than one way to solve a problem, right?
Yes, openSUSE Build Service ;)
https://build.opensuse.org/

I also believe there is a new version of checkinstall out to overcome
11.2 issues (not working..)
See this mail list thread;
http://lists.opensuse.org/opensuse/2009-12/msg00334.html

--
Cheers Malcolm ��� (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 2.6.27.39-0.3-default
up 2 days 13:07, 3 users, load average: 0.60, 0.41, 0.35
GPU GeForce 8600 GTS Silent - CUDA Driver Version: 190.18

From: Malcolm on
On Tue, 29 Dec 2009 17:23:18 +0100
houghi <houghi(a)houghi.org.invalid> wrote:

> Malcolm wrote:
> > I also believe there is a new version of checkinstall out to
> > overcome 11.2 issues (not working..)
> > See this mail list thread;
> > http://lists.opensuse.org/opensuse/2009-12/msg00334.html
>
> never knew it was not working. The working version is apparently in
> the repo http://download.opensuse.org/repositories/devel:/tools/
> Untested by me.
>
> I think it is sily to have a program in the repor where they KNOW it
> is not working. Sometimes I think the only reason they keep some
> programs is so they can say "I am the maintainer of XYZ number of
> packages."
>
> houghi
Seems to be the nature of the OB(east)S..... it's so easy for one to
add repositories and then wonder why there are conflicts and problems.
I've seen novice users with in excess of 30 repositories active (sigh).

--
Cheers Malcolm ��� (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 2.6.27.39-0.3-default
up 2 days 14:08, 3 users, load average: 0.05, 0.07, 0.11
GPU GeForce 8600 GTS Silent - CUDA Driver Version: 190.18