Re: [gentoo-user] Compilation error with StructureSynth

2017-11-01 Thread tuxic 
On 11/01 06:04, David Haller wrote:
> Hello,
> 
> On Wed, 01 Nov 2017, tu...@posteo.de wrote:
> [..]
> >(using zsh)
> >export PATCH_OPTS=-I; emerge structure-synth
> 
> Ah PATCH_OPTS. 'man epatch.eclass' just popped up on my reading list.
> 
> >which fails the same way...
> 
> 'minus' little 'Ludwig'... Not 'minus' big 'Isaac' ...
> 
> Read 'patch --help' please ;)
> 
> Please, do use a monospaced font for this list where iíìïl1|IÍÌÏLoø0OØ
> etc. are all distinct from each other. I recommend gnu-unifont which I
> use and where that is given even on a small low-dpi screen. It may not
> be as nice looking, but in the shell, discerning each char from the
> others is a "MUST" IMO. There's a reason the 'dotted' 0 came along in
> line-printers (IIRC).
> 
> But using that with PATCH_OPTS should work. Or just replace
> the patch with the un-xz'd .xz'd attachment I sent.
> 
> BTW: you do not need to "export" variables in your current shell to be
> "exported" to subprocesses. Adding them before the command suffices,
> as in:
> 
>   # PATCH_OPTS="-l" emerge media-gfx/structure-synth
> 
> HTH,
> -dnh
> 
> -- 
> Ugga Ugga ! Nognog! Dadadadada! [Woko° in dag°]
> 

Hi David,

I am using mutt here and vim to compose email...its a pure ASCII
thing. I looks like this

ABCDEFGHIJKLMN
12345678901023
.|-=+:
(I will attach a screenshot to this email)

export:
I know that. Its pure convenience...or lazyness in another context...
;)

Cheers
Meino

Re: [gentoo-user] Compilation error with StructureSynth

2017-11-01 Thread tuxic 
On 11/01 05:42, David Haller wrote:
> Hello,
> 
> On Wed, 01 Nov 2017, tu...@posteo.de wrote:
> [..]
> >nope...currently the cat is more dead than alive...
> >I looked at it!
> >
> >I did the following:
> >
> >vim 
> >:set ff
> >unix
> >:set ff=dos
> >:wq
> >repoman -v manifest (since file has changed)
> 
> Does vim really reencode lineendings there?
> 
> >emerge structure-synth.
> >
> >BADABOOM! (The fifth element)
> [..]
> 
> Please check the patch manually with something that _shows_ the
> lineendings, like mcedit. And the patch itself should probably not
> be _completely_ in CRLF (I guess). Please try with my xz'd version
> (decompressed), or with
> 
> patch -p1 -l < "${FILESDIR}/structure-synth-1.5.0-gl.patch"
> 
> instead of the 'epatch' line in the ebuild's src_prepare() function
> or recreate the patch by yourself ... The actual changes are rather
> trivial[1].
> 
> HTH,
> -dnh

Hi David,

vim shows lineending with :set list.

I xycat your compressed file directly into
/usr/local/portage//files/.
and the compilation runs through without problems.

No I have a running with no working graphical output.

I think I will give up...it is too much work to get this
old code successfully running ... for both of us.

Thanks a lot for youre help (exclamation mark) nonetheless, David!
Cheers
Meino




> 
> [1] well, what and what type to return in VoxelStepper.cpp was a bit
> of "look around" ... The empty QList maps from 0, but not from the
> bool "false". Speaking of that: the programmers of that software
> don't seem too avid on quality... errors like those (returning
> false for an empty QList) ... they bode of woe... I'd be looking
> for other software.
> 
> PS: And if you're looking for programmatical forms: have a look at
> Metafont! It does lack the 3rd dimension you're after I guess. 
> https://en.wikipedia.org/wiki/Metafont
> https://de.wikipedia.org/wiki/METAFONT Wow, once en and de have
> _both_ points well worth to read, and lacking in the other. Anyway,
> from metafont we get to
> https://de.wikipedia.org/wiki/MetaPost
> https://en.wikipedia.org/wiki/MetaPost
> https://en.wikipedia.org/wiki/PSTricks
> and probably more, have a look at the Software/See also links in
> those pages.
> 
> Why not postscript? Easy: with postscript, you need coordinates. 
> With metafont/-post you define equations (with e.g. sinus/cosinus)
> for to define points for drawing (Bezier?) paths and let the
> software solve them all, e.g. finding the intersection of two
> paths, so you can "draw" a third path veering off that
> intersection ... Oh, and that "pen" concept. See the example in
> https://en.wikipedia.org/wiki/Metafont#Example
> 
> -- 
> Yah. Spam, spam, spam, cuisson de cerf haché au sauce truffe, and spam.
> -- Richard Bos on french "hypermarkets"
>

Re: [gentoo-user] Compilation error with StructureSynth

2017-11-01 Thread David Haller 
Hello,

On Wed, 01 Nov 2017, tu...@posteo.de wrote:
[..]
>(using zsh)
>export PATCH_OPTS=-I; emerge structure-synth

Ah PATCH_OPTS. 'man epatch.eclass' just popped up on my reading list.

>which fails the same way...

'minus' little 'Ludwig'... Not 'minus' big 'Isaac' ...

Read 'patch --help' please ;)

Please, do use a monospaced font for this list where iíìïl1|IÍÌÏLoø0OØ
etc. are all distinct from each other. I recommend gnu-unifont which I
use and where that is given even on a small low-dpi screen. It may not
be as nice looking, but in the shell, discerning each char from the
others is a "MUST" IMO. There's a reason the 'dotted' 0 came along in
line-printers (IIRC).

But using that with PATCH_OPTS should work. Or just replace
the patch with the un-xz'd .xz'd attachment I sent.

BTW: you do not need to "export" variables in your current shell to be
"exported" to subprocesses. Adding them before the command suffices,
as in:

  # PATCH_OPTS="-l" emerge media-gfx/structure-synth

HTH,
-dnh

-- 
Ugga Ugga ! Nognog! Dadadadada! [Woko° in dag°]

Re: [gentoo-user] Compilation error with StructureSynth

2017-11-01 Thread David Haller 
Hello,

On Wed, 01 Nov 2017, tu...@posteo.de wrote:
[..]
>nope...currently the cat is more dead than alive...
>I looked at it!
>
>I did the following:
>
>vim 
>:set ff
>unix
>:set ff=dos
>:wq
>repoman -v manifest (since file has changed)

Does vim really reencode lineendings there?

>emerge structure-synth.
>
>BADABOOM! (The fifth element)
[..]

Please check the patch manually with something that _shows_ the
lineendings, like mcedit. And the patch itself should probably not
be _completely_ in CRLF (I guess). Please try with my xz'd version
(decompressed), or with

patch -p1 -l < "${FILESDIR}/structure-synth-1.5.0-gl.patch"

instead of the 'epatch' line in the ebuild's src_prepare() function
or recreate the patch by yourself ... The actual changes are rather
trivial[1].

HTH,
-dnh

[1] well, what and what type to return in VoxelStepper.cpp was a bit
of "look around" ... The empty QList maps from 0, but not from the
bool "false". Speaking of that: the programmers of that software
don't seem too avid on quality... errors like those (returning
false for an empty QList) ... they bode of woe... I'd be looking
for other software.

PS: And if you're looking for programmatical forms: have a look at
Metafont! It does lack the 3rd dimension you're after I guess. 
https://en.wikipedia.org/wiki/Metafont
https://de.wikipedia.org/wiki/METAFONT Wow, once en and de have
_both_ points well worth to read, and lacking in the other. Anyway,
from metafont we get to
https://de.wikipedia.org/wiki/MetaPost
https://en.wikipedia.org/wiki/MetaPost
https://en.wikipedia.org/wiki/PSTricks
and probably more, have a look at the Software/See also links in
those pages.

Why not postscript? Easy: with postscript, you need coordinates. 
With metafont/-post you define equations (with e.g. sinus/cosinus)
for to define points for drawing (Bezier?) paths and let the
software solve them all, e.g. finding the intersection of two
paths, so you can "draw" a third path veering off that
intersection ... Oh, and that "pen" concept. See the example in
https://en.wikipedia.org/wiki/Metafont#Example

-- 
Yah. Spam, spam, spam, cuisson de cerf haché au sauce truffe, and spam.
-- Richard Bos on french "hypermarkets"

Re: [gentoo-user] Compilation error with StructureSynth

2017-11-01 Thread tuxic 
On 11/01 04:44, tu...@posteo.de wrote:
> On 11/01 04:05, David Haller wrote:
> > Hello,
> > 
> > On Wed, 01 Nov 2017, tu...@posteo.de wrote:
> > [..]
> > >Thanks a lot for the extensive help, SIR! :)
> > 
> > Thanks.
> > 
> > [..]
> > >The patch itself was found (so the local thing works fine) and failed.
> > >
> > >The *.patch.out is attached to the email and after looking into it I
> > >think you will find the problem a hundred years faster than me since
> > >you created it. It seems some files are not where they are supposed to
> > >be.
> > 
> > Not quite. The "not founds" are normal for epatch/eapply trying
> > various '-p' levels... But see below in the patch.out (and nice that
> > you supplied that right away).
> > 
> > >There is a glitch in the matrix...they have changed something...I
> > >see Schroedingers cat twice.
> > >
> > >Ah! By the way: According to quantum physics the cite at the bottom of
> > >you previous email is wrong :
> > >"WANTED: Schroedingers Cat, dead or alive."
> > >must be
> > >"WANTED: Schroedingers Cat, dead and alive."
> > >Heisenberg would not accept this kind of uncertainty -- in
> > >principle... 
> > >;)
> > 
> > *g* You're right. But it's just a quote I picked up long time ago ;)
> > 
> > Anyway, here's the deal:
> > 
> > [..]
> > >PATCH COMMAND:  patch -p1 -g0 -E --no-backup-if-mismatch  --dry-run -f < 
> > >'/var/tmp/portage/media-gfx/structure-synth-1.5.0-r1/files/structure-synth-1.5.0-gl.patch'
> > >
> > >==
> > >checking file SyntopiaCore/GLEngine/Raytracer/Sampler.h
> > >Hunk #1 FAILED at 1 (different line endings).
> > >1 out of 1 hunk FAILED
> > >checking file SyntopiaCore/GLEngine/Raytracer/VoxelStepper.cpp
> > >Hunk #1 FAILED at 122 (different line endings).
> > >1 out of 1 hunk FAILED
> > >checking file SyntopiaCore/GLEngine/Sphere.h
> > >Hunk #1 FAILED at 1 (different line endings).
> > >1 out of 1 hunk FAILED
> > >
> > >patch program exited with status 1
> > >==
> > 
> > Because this failed, epatch goes on, confusing you with more a few
> > more 'not found' stuff outputs...
> > 
> > >PATCH COMMAND:  patch -p2 -g0 -E --no-backup-if-mismatch  --dry-run -f < 
> > >'/var/tmp/portage/media-gfx/structure-synth-1.5.0-r1/files/structure-synth-1.5.0-gl.patch'
> > >
> > >==
> > >can't find file to patch at input line 4
> > [..]
> > 
> > Thing is: the source-code of this package has CRLF line endings,
> > and, while I added the CRs to my patch, via mail and saving, you
> > probably saved them with "just" the LFs.
> > 
> > a) add the '-l' / '--ignore-whitespace' option to patch, don't know if
> >that works with epatch/eapply as e.g. 'epatch -l ${FILESDIR}/..', or
> > 
> > b) reencode the line-endings of the patch to match that of the
> >source-files. No idea if you can reencode the whole patch or just
> >the diff. So ... I'll reattach the patch xzipped, that should keep
> >your mail-client from changing the line-endings. xz -d that patch
> >then into the files subdir. That's probably the easiest way.
> > 
> > HTH,
> > -dnh
> > 
> > -- 
> > Chemie ist auch bloß spezialisierte Physik.
> >-- Jens Dittmar in drsst
> 
> Moin David,
> 
> ;)
> 
> nope...currently the cat is more dead than alive...
> I looked at it!
> 
> 
> I did the following:
> 
> vim 
> :set ff
> unix
> :set ff=dos
> :wq
> repoman -v manifest (since file has changed)
> 
> emerge structure-synth.
> 
> BADABOOM! (The fifth element)
> 
> See my theorie of uncertainity attached to this mail...
> 
> :)
> 
> Cheers
> Meino
> 
> 

Hi,

did the following after the failed CRLF-fix:

(using zsh)
export PATCH_OPTS=-I; emerge structure-synth

which fails the same way...

Cheers
Meino

Re: [gentoo-user] Compilation error with StructureSynth

2017-11-01 Thread tuxic 
On 11/01 04:05, David Haller wrote:
> Hello,
> 
> On Wed, 01 Nov 2017, tu...@posteo.de wrote:
> [..]
> >Thanks a lot for the extensive help, SIR! :)
> 
> Thanks.
> 
> [..]
> >The patch itself was found (so the local thing works fine) and failed.
> >
> >The *.patch.out is attached to the email and after looking into it I
> >think you will find the problem a hundred years faster than me since
> >you created it. It seems some files are not where they are supposed to
> >be.
> 
> Not quite. The "not founds" are normal for epatch/eapply trying
> various '-p' levels... But see below in the patch.out (and nice that
> you supplied that right away).
> 
> >There is a glitch in the matrix...they have changed something...I
> >see Schroedingers cat twice.
> >
> >Ah! By the way: According to quantum physics the cite at the bottom of
> >you previous email is wrong :
> >"WANTED: Schroedingers Cat, dead or alive."
> >must be
> >"WANTED: Schroedingers Cat, dead and alive."
> >Heisenberg would not accept this kind of uncertainty -- in
> >principle... 
> >;)
> 
> *g* You're right. But it's just a quote I picked up long time ago ;)
> 
> Anyway, here's the deal:
> 
> [..]
> >PATCH COMMAND:  patch -p1 -g0 -E --no-backup-if-mismatch  --dry-run -f < 
> >'/var/tmp/portage/media-gfx/structure-synth-1.5.0-r1/files/structure-synth-1.5.0-gl.patch'
> >
> >==
> >checking file SyntopiaCore/GLEngine/Raytracer/Sampler.h
> >Hunk #1 FAILED at 1 (different line endings).
> >1 out of 1 hunk FAILED
> >checking file SyntopiaCore/GLEngine/Raytracer/VoxelStepper.cpp
> >Hunk #1 FAILED at 122 (different line endings).
> >1 out of 1 hunk FAILED
> >checking file SyntopiaCore/GLEngine/Sphere.h
> >Hunk #1 FAILED at 1 (different line endings).
> >1 out of 1 hunk FAILED
> >
> >patch program exited with status 1
> >==
> 
> Because this failed, epatch goes on, confusing you with more a few
> more 'not found' stuff outputs...
> 
> >PATCH COMMAND:  patch -p2 -g0 -E --no-backup-if-mismatch  --dry-run -f < 
> >'/var/tmp/portage/media-gfx/structure-synth-1.5.0-r1/files/structure-synth-1.5.0-gl.patch'
> >
> >==
> >can't find file to patch at input line 4
> [..]
> 
> Thing is: the source-code of this package has CRLF line endings,
> and, while I added the CRs to my patch, via mail and saving, you
> probably saved them with "just" the LFs.
> 
> a) add the '-l' / '--ignore-whitespace' option to patch, don't know if
>that works with epatch/eapply as e.g. 'epatch -l ${FILESDIR}/..', or
> 
> b) reencode the line-endings of the patch to match that of the
>source-files. No idea if you can reencode the whole patch or just
>the diff. So ... I'll reattach the patch xzipped, that should keep
>your mail-client from changing the line-endings. xz -d that patch
>then into the files subdir. That's probably the easiest way.
> 
> HTH,
> -dnh
> 
> -- 
> Chemie ist auch bloß spezialisierte Physik.
>-- Jens Dittmar in drsst

Moin David,

;)

nope...currently the cat is more dead than alive...
I looked at it!


I did the following:

vim 
:set ff
unix
:set ff=dos
:wq
repoman -v manifest (since file has changed)

emerge structure-synth.

BADABOOM! (The fifth element)

See my theorie of uncertainity attached to this mail...

:)

Cheers
Meino


* structure-synth-1.5.0-gl.patch *
PWD: /var/tmp/portage/media-gfx/structure-synth-1.5.0-r1/work/Structure Synth 
Source Code
PATCH TOOL: patch -> /usr/bin/patch
VERSION INFO:
GNU patch 2.7.5
Copyright (C) 2003, 2009-2012 Free Software Foundation, Inc.
Copyright (C) 1988 Larry Wall

License GPLv3+: GNU GPL version 3 or later .
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Larry Wall and Paul Eggert

==

PATCH COMMAND:  patch -p0 -g0 -E --no-backup-if-mismatch  --dry-run -f < 
'/var/tmp/portage/media-gfx/structure-synth-1.5.0-r1/files/structure-synth-1.5.0-gl.patch'

==
(Stripping trailing CRs from patch; use --binary to disable.)
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--
|diff -x '*~' -purN a/SyntopiaCore/GLEngine/Raytracer/Sampler.h 
b/SyntopiaCore/GLEngine/Raytracer/Sampler.h
|--- a/SyntopiaCore/GLEngine/Raytracer/Sampler.h2010-11-04 
20:02:46.0 +0100
|+++ b/SyntopiaCore/GLEngine/Raytracer/Sampler.h2017-11-01 
04:42:46.320970684 +0100
--
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
(Stripping trailing CRs from patch; use --binary to disable.)
can't find file to patch at input line 14
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--
|diff -x '*~' -purN

Re: [gentoo-user] Compilation error with StructureSynth

2017-11-01 Thread David Haller 
Hello,

On Wed, 01 Nov 2017, tu...@posteo.de wrote:
[..]
>Thanks a lot for the extensive help, SIR! :)

Thanks.

[..]
>The patch itself was found (so the local thing works fine) and failed.
>
>The *.patch.out is attached to the email and after looking into it I
>think you will find the problem a hundred years faster than me since
>you created it. It seems some files are not where they are supposed to
>be.

Not quite. The "not founds" are normal for epatch/eapply trying
various '-p' levels... But see below in the patch.out (and nice that
you supplied that right away).

>There is a glitch in the matrix...they have changed something...I
>see Schroedingers cat twice.
>
>Ah! By the way: According to quantum physics the cite at the bottom of
>you previous email is wrong :
>"WANTED: Schroedingers Cat, dead or alive."
>must be
>"WANTED: Schroedingers Cat, dead and alive."
>Heisenberg would not accept this kind of uncertainty -- in
>principle... 
>;)

*g* You're right. But it's just a quote I picked up long time ago ;)

Anyway, here's the deal:

[..]
>PATCH COMMAND:  patch -p1 -g0 -E --no-backup-if-mismatch  --dry-run -f < 
>'/var/tmp/portage/media-gfx/structure-synth-1.5.0-r1/files/structure-synth-1.5.0-gl.patch'
>
>==
>checking file SyntopiaCore/GLEngine/Raytracer/Sampler.h
>Hunk #1 FAILED at 1 (different line endings).
>1 out of 1 hunk FAILED
>checking file SyntopiaCore/GLEngine/Raytracer/VoxelStepper.cpp
>Hunk #1 FAILED at 122 (different line endings).
>1 out of 1 hunk FAILED
>checking file SyntopiaCore/GLEngine/Sphere.h
>Hunk #1 FAILED at 1 (different line endings).
>1 out of 1 hunk FAILED
>
>patch program exited with status 1
>==

Because this failed, epatch goes on, confusing you with more a few
more 'not found' stuff outputs...

>PATCH COMMAND:  patch -p2 -g0 -E --no-backup-if-mismatch  --dry-run -f < 
>'/var/tmp/portage/media-gfx/structure-synth-1.5.0-r1/files/structure-synth-1.5.0-gl.patch'
>
>==
>can't find file to patch at input line 4
[..]

Thing is: the source-code of this package has CRLF line endings,
and, while I added the CRs to my patch, via mail and saving, you
probably saved them with "just" the LFs.

a) add the '-l' / '--ignore-whitespace' option to patch, don't know if
   that works with epatch/eapply as e.g. 'epatch -l ${FILESDIR}/..', or

b) reencode the line-endings of the patch to match that of the
   source-files. No idea if you can reencode the whole patch or just
   the diff. So ... I'll reattach the patch xzipped, that should keep
   your mail-client from changing the line-endings. xz -d that patch
   then into the files subdir. That's probably the easiest way.

HTH,
-dnh

-- 
Chemie ist auch bloß spezialisierte Physik.
   -- Jens Dittmar in drsst


structure-synth-1.5.0-gl.patch.xz
Description: structure-synth-1.5.0-gl.patch.xz

Re: [gentoo-user] Compilation error with StructureSynth

2017-11-01 Thread tuxic 
On 11/01 11:03, David Haller wrote:
> Hello Meino,
> 
> On Wed, 01 Nov 2017, tu...@posteo.de wrote:
> [..]
> >But it seems, that I am doing something wrong with the local
> >overlay...
> 
> I assumed you already have one. If not, drop this into your
> /etc/portage/repos.conf/ directory as e.g. local.conf:
> 
>  /etc/portage/repos.conf/local.conf 
> [local]
> location = /usr/local/portage
> masters = gentoo
> auto-sync = no
> priority = 99
> 
> 
> Or, if you have a _FILE_ /etc/portage/repos.conf, add the above
> snippet as a new section in there.
> 
> And create /usr/local/portage.
> 
> >I copied (as root)
> >
> >cp -a /usr/portage/media-gfx/structur-synth /usr/local/portage/media-gfx/.
> 
> Did you create /usr/local/portage/media-gfx/ before?
> 
> Clean up /usr/local/portage/media-gfx first, then use:
> 
> # mkdir -p /usr/local/portage/media-gfx/
> # cp -va /usr/portage/media-gfx/structure-synth \
> /usr/local/portage/media-gfx/
> 
> Depending on your umask, you might need to make stuff explicitly
> readable for or owned by the user "portage" (usually).
> 
> # chown -cR portage.portage /usr/local/portage/
> 
> Anyway, this should get you a structure like:
> 
> /usr/local/portage/media-gfx/structure-synth/
> /usr/local/portage/media-gfx/structure-synth/metadata.xml
> /usr/local/portage/media-gfx/structure-synth/structure-synth-1.5.0.ebuild
> /usr/local/portage/media-gfx/structure-synth/Manifest
> 
> Then:
> 
> # mkdir /usr/local/portage/media-gfx/structure-synth/files
> 
> drop my '.patch' into that ./files/ dir, drop my -r1.ebuild into
> /usr/local/portage/media-gfx/structure-synth/
> 
> and run:
> 
> # pushd /usr/local/portage/media-gfx/structure-synth/
> # repoman -v manifest
> # popd
> 
> (I forgot that step in my first mail)
> 
> It should look like this then:
> 
> /usr/local/portage/media-gfx/structure-synth/
> /usr/local/portage/media-gfx/structure-synth/structure-synth-1.5.0.ebuild
> /usr/local/portage/media-gfx/structure-synth/structure-synth-1.5.0-r1.ebuild
> /usr/local/portage/media-gfx/structure-synth/files
> /usr/local/portage/media-gfx/structure-synth/files/structure-synth-1.5.0-gl.patch
> /usr/local/portage/media-gfx/structure-synth/metadata.xml
> /usr/local/portage/media-gfx/structure-synth/Manifest
> 
> (actually, you could prune the structure-synth-1.5.0.ebuild file,
> update the manifest again if you do).
> 
> >then
> >
> >eix structure-synth
> >
> >* media-gfx/structure-synth
> > Available versions:  (~)1.5.0
> > Homepage:http://structuresynth.sourceforge.net/
> > Description: A program to generate 3D structures by specifying 
> > a design grammar
> >
> >so no *-r1 version visible.
> 
> Did you run 'eix-update'??? *nudge* *nudge*
> 
> Anyway: even without eix-update and eix not showing stuff,
> 
> # emerge --pretend --nodeps media-gfx/structure-synth
> 
> should show that it'd build media-gfx/structure-synth-1.5.0-r1::local
> 
> (unless I forgot something about initializing a local overlay, it's
> been a while).
> 
> >layman -l does not show up structure-synth
> 
> That lists overlays. Not packages inside them.
> 
> >Then I tried different permutations of "media-gfx" (w/o) and
> >structur-synth in combination with layman -a in desperation ;)
> >no success
> 
> layman and your local overlay have nothing to do with each other. 
> layman is "just" a tool to easily add/remove "external" public
> overlays. And eix-layman to add/remove them to/from your local
> 'eix'-DB and what is considered "local" ('eix' vs. 'eix -R').
> 
> [..]
> >So I think, that the layman engine is working correctly so far.
> >But the driver behind the steering wheels needs some instructions it
> >seems ;)
> >Where can I get my license?
> 
> In the handbook, IIRC :) I did read that about a local overlay in the
> official docs somewhere (and my local overlay is over 100 pkgs ;)
> 
> PS: I wonder how that ebuild got into the portage-tree ... Maybe some
> weird configs present or absent in the qt4/qmake stuff about opengl...
> 
> I found that 'QMAKE_LIBS_OPENGL="-lGL"' thingy I added (with the
> missing '-lGLU') to the ebuild in the qmake config files in
> /usr/share/qt4/... I hate qmake (and just about every other build
> system[1]).
> 
> Ask, if stuff is still unclear. And read up a bit again on overlays
> and layman ;)
> 
> HTH,
> -dnh
> 
> [1] had a problem recently with some stuff using scons. Needed
> 'strace' to find why it did not pick up some header or lib.
> *gah* As bad as the autotools or plain Makefiles may be, they're
> at least transparent and easy to grep around in and _local_ to
> the package.
> 
> -- 
>   Thank God I'm an atheist.
> 

Hello David,

OH MAN!

Thanks a lot for the extensive help, SIR! :)

Ok, it works now...and it doesn't...

The repository was found and compilation had started with the
*-r1 version of the wonderful beast.
(are you in 3D-printing, David?...?)

BUT:
* Failed Patch: structure-synth-1.5.0-gl.patch !
 *  (

Re: [gentoo-user] Compilation error with StructureSynth

2017-11-01 Thread David Haller 
Hello Meino,

On Wed, 01 Nov 2017, tu...@posteo.de wrote:
[..]
>But it seems, that I am doing something wrong with the local
>overlay...

I assumed you already have one. If not, drop this into your
/etc/portage/repos.conf/ directory as e.g. local.conf:

 /etc/portage/repos.conf/local.conf 
[local]
location = /usr/local/portage
masters = gentoo
auto-sync = no
priority = 99


Or, if you have a _FILE_ /etc/portage/repos.conf, add the above
snippet as a new section in there.

And create /usr/local/portage.

>I copied (as root)
>
>cp -a /usr/portage/media-gfx/structur-synth /usr/local/portage/media-gfx/.

Did you create /usr/local/portage/media-gfx/ before?

Clean up /usr/local/portage/media-gfx first, then use:

# mkdir -p /usr/local/portage/media-gfx/
# cp -va /usr/portage/media-gfx/structure-synth \
/usr/local/portage/media-gfx/

Depending on your umask, you might need to make stuff explicitly
readable for or owned by the user "portage" (usually).

# chown -cR portage.portage /usr/local/portage/

Anyway, this should get you a structure like:

/usr/local/portage/media-gfx/structure-synth/
/usr/local/portage/media-gfx/structure-synth/metadata.xml
/usr/local/portage/media-gfx/structure-synth/structure-synth-1.5.0.ebuild
/usr/local/portage/media-gfx/structure-synth/Manifest

Then:

# mkdir /usr/local/portage/media-gfx/structure-synth/files

drop my '.patch' into that ./files/ dir, drop my -r1.ebuild into
/usr/local/portage/media-gfx/structure-synth/

and run:

# pushd /usr/local/portage/media-gfx/structure-synth/
# repoman -v manifest
# popd

(I forgot that step in my first mail)

It should look like this then:

/usr/local/portage/media-gfx/structure-synth/
/usr/local/portage/media-gfx/structure-synth/structure-synth-1.5.0.ebuild
/usr/local/portage/media-gfx/structure-synth/structure-synth-1.5.0-r1.ebuild
/usr/local/portage/media-gfx/structure-synth/files
/usr/local/portage/media-gfx/structure-synth/files/structure-synth-1.5.0-gl.patch
/usr/local/portage/media-gfx/structure-synth/metadata.xml
/usr/local/portage/media-gfx/structure-synth/Manifest

(actually, you could prune the structure-synth-1.5.0.ebuild file,
update the manifest again if you do).

>then
>
>eix structure-synth
>
>* media-gfx/structure-synth
> Available versions:  (~)1.5.0
> Homepage:http://structuresynth.sourceforge.net/
> Description: A program to generate 3D structures by specifying a 
> design grammar
>
>so no *-r1 version visible.

Did you run 'eix-update'??? *nudge* *nudge*

Anyway: even without eix-update and eix not showing stuff,

# emerge --pretend --nodeps media-gfx/structure-synth

should show that it'd build media-gfx/structure-synth-1.5.0-r1::local

(unless I forgot something about initializing a local overlay, it's
been a while).

>layman -l does not show up structure-synth

That lists overlays. Not packages inside them.

>Then I tried different permutations of "media-gfx" (w/o) and
>structur-synth in combination with layman -a in desperation ;)
>no success

layman and your local overlay have nothing to do with each other. 
layman is "just" a tool to easily add/remove "external" public
overlays. And eix-layman to add/remove them to/from your local
'eix'-DB and what is considered "local" ('eix' vs. 'eix -R').

[..]
>So I think, that the layman engine is working correctly so far.
>But the driver behind the steering wheels needs some instructions it
>seems ;)
>Where can I get my license?

In the handbook, IIRC :) I did read that about a local overlay in the
official docs somewhere (and my local overlay is over 100 pkgs ;)

PS: I wonder how that ebuild got into the portage-tree ... Maybe some
weird configs present or absent in the qt4/qmake stuff about opengl...

I found that 'QMAKE_LIBS_OPENGL="-lGL"' thingy I added (with the
missing '-lGLU') to the ebuild in the qmake config files in
/usr/share/qt4/... I hate qmake (and just about every other build
system[1]).

Ask, if stuff is still unclear. And read up a bit again on overlays
and layman ;)

HTH,
-dnh

[1] had a problem recently with some stuff using scons. Needed
'strace' to find why it did not pick up some header or lib.
*gah* As bad as the autotools or plain Makefiles may be, they're
at least transparent and easy to grep around in and _local_ to
the package.

-- 
  Thank God I'm an atheist.

Re: [gentoo-user] Compilation error with StructureSynth

2017-11-01 Thread tuxic 
On 11/01 05:17, David Haller wrote:
> Hello,
> 
> On Wed, 01 Nov 2017, tu...@posteo.de wrote:
> >I am trying to compile this wonderful beast:
> >* media-gfx/structure-synth
> > Available versions:  (~)1.5.0
> > Homepage:http://structuresynth.sourceforge.net/
> > Description: A program to generate 3D structures by specifying 
> > a design grammar
> >
> >
> >and it gives me this:
> >
> >x86_64-pc-linux-gnu-g++ -c -march=native -O2 -pipe -Wall -W -D_REENTRANT 
> >-DQT_NO_DEBUG -DQT_SCRIPT_LIB -DQT_XML_LIB -DQT_OPENGL_LIB -DQT_GUI_LIB 
> >-DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++ -I. 
> >-I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui 
> >-I/usr/include/qt4/QtOpenGL -I/usr/include/qt4/QtXml 
> >-I/usr/include/qt4/QtScript -I/usr/include/qt4 -I. -IStructureSynth/GUI 
> >-ISyntopiaCore/GLEngine -ISyntopiaCore/Math -ISyntopiaCore/Misc 
> >-IStructureSynth/Parser -ISyntopiaCore/Exceptions 
> >-IStructureSynth/Model/Rendering -IStructureSynth/Model 
> >-IThirdPartyCode/MersenneTwister -ISyntopiaCore/Logging 
> >-IStructureSynth/JavaScriptSupport -ISyntopiaCore/GLEngine/Raytracer -I. -o 
> >JavaScriptParser.o StructureSynth/JavaScriptSupport/JavaScriptParser.cpp
> >In file included from StructureSynth/JavaScriptSupport/Debug.cpp:16:0:
> >StructureSynth/JavaScriptSupport/../../SyntopiaCore/GLEngine/Sphere.h:25:4: 
> >error: 'GLUquadric' does not name a type
> >GLUquadric* myQuad;
> >^
> 
> Copy the media-gfx/structure-synth subdir from the portage-tree to
> your local overlay and add the attached files as suggested by the
> filenames (create the files/ subdir in advance and put the patch there).
> 
> HTH,
> -dnh
> 
> -- 
> WANTED: Schroedingers Cat, dead or alive.

> # Copyright 1999-2013 Gentoo Foundation
> # Distributed under the terms of the GNU General Public License v2
> 
> EAPI=4
> 
> inherit eutils qt4-r2
> 
> MY_P="StructureSynth-Source-v${PV}"
> DESCRIPTION="A program to generate 3D structures by specifying a design 
> grammar"
> HOMEPAGE="http://structuresynth.sourceforge.net/;
> SRC_URI="mirror://sourceforge/structuresynth/${MY_P}.zip"
> 
> LICENSE="|| ( LGPL-2.1 GPL-3 )"
> SLOT="0"
> KEYWORDS="~amd64 ~x86"
> IUSE=""
> 
> RDEPEND="virtual/opengl
>   dev-qt/qtcore:4
>   dev-qt/qtgui:4
>   dev-qt/qtopengl:4
>   dev-qt/qtscript:4"
> DEPEND="${RDEPEND}
>   app-arch/unzip"
> 
> S="${WORKDIR}/Structure Synth Source Code"
> 
> src_prepare() {
>   epatch "${FILESDIR}/structure-synth-1.5.0-gl.patch"
> 
>   qmake -project -o ${PN}.pro -after "CONFIG+=opengl" \
>   -after "QT+=xml opengl script" \
>   QMAKE_LIBS_OPENGL="-lGLU -lGL" || die "qmake failed"
> }
> 
> src_install() {
>   dobin ${PN}
>   dodoc roadmap.txt changelog.txt bugs.txt
>   domenu ${PN}.desktop
>   newicon images/structuresynth.png ${PN}.png
> }


Hi David,

thanks a LOT for the patch !!! This is one of the quickestestest :)
patch I ever got for a compilation problem! :) Yeah!

But it seems, that I am doing something wrong with the local
overlay...

I copied (as root)

cp -a /usr/portage/media-gfx/structur-synth /usr/local/portage/media-gfx/.

then

eix structure-synth

* media-gfx/structure-synth
 Available versions:  (~)1.5.0
 Homepage:http://structuresynth.sourceforge.net/
 Description: A program to generate 3D structures by specifying a 
design grammar

so no *-r1 version visible.

layman -l does not show up structure-synth

Then I tried different permutations of "media-gfx" (w/o) and
structur-synth in combination with layman -a in desperation ;)
no success

Previously I successfully added the palemoon overlay and compiled it
and compilation failed due to some code problems (which fails, but this a long 
long and different story).

So I think, that the layman engine is working correctly so far.
But the driver behind the steering wheels needs some instructions it
seems ;)
Where can I get my license?

Cheers
Meino

Re: [gentoo-user] Compilation error with StructureSynth

2017-10-31 Thread David Haller 
Hello,

On Wed, 01 Nov 2017, tu...@posteo.de wrote:
>I am trying to compile this wonderful beast:
>* media-gfx/structure-synth
> Available versions:  (~)1.5.0
> Homepage:http://structuresynth.sourceforge.net/
> Description: A program to generate 3D structures by specifying a 
> design grammar
>
>
>and it gives me this:
>
>x86_64-pc-linux-gnu-g++ -c -march=native -O2 -pipe -Wall -W -D_REENTRANT 
>-DQT_NO_DEBUG -DQT_SCRIPT_LIB -DQT_XML_LIB -DQT_OPENGL_LIB -DQT_GUI_LIB 
>-DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++ -I. 
>-I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtOpenGL 
>-I/usr/include/qt4/QtXml -I/usr/include/qt4/QtScript -I/usr/include/qt4 -I. 
>-IStructureSynth/GUI -ISyntopiaCore/GLEngine -ISyntopiaCore/Math 
>-ISyntopiaCore/Misc -IStructureSynth/Parser -ISyntopiaCore/Exceptions 
>-IStructureSynth/Model/Rendering -IStructureSynth/Model 
>-IThirdPartyCode/MersenneTwister -ISyntopiaCore/Logging 
>-IStructureSynth/JavaScriptSupport -ISyntopiaCore/GLEngine/Raytracer -I. -o 
>JavaScriptParser.o StructureSynth/JavaScriptSupport/JavaScriptParser.cpp
>In file included from StructureSynth/JavaScriptSupport/Debug.cpp:16:0:
>StructureSynth/JavaScriptSupport/../../SyntopiaCore/GLEngine/Sphere.h:25:4: 
>error: 'GLUquadric' does not name a type
>GLUquadric* myQuad;
>^

Copy the media-gfx/structure-synth subdir from the portage-tree to
your local overlay and add the attached files as suggested by the
filenames (create the files/ subdir in advance and put the patch there).

HTH,
-dnh

-- 
WANTED: Schroedingers Cat, dead or alive.# Copyright 1999-2013 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2

EAPI=4

inherit eutils qt4-r2

MY_P="StructureSynth-Source-v${PV}"
DESCRIPTION="A program to generate 3D structures by specifying a design grammar"
HOMEPAGE="http://structuresynth.sourceforge.net/;
SRC_URI="mirror://sourceforge/structuresynth/${MY_P}.zip"

LICENSE="|| ( LGPL-2.1 GPL-3 )"
SLOT="0"
KEYWORDS="~amd64 ~x86"
IUSE=""

RDEPEND="virtual/opengl
dev-qt/qtcore:4
dev-qt/qtgui:4
dev-qt/qtopengl:4
dev-qt/qtscript:4"
DEPEND="${RDEPEND}
app-arch/unzip"

S="${WORKDIR}/Structure Synth Source Code"

src_prepare() {
epatch "${FILESDIR}/structure-synth-1.5.0-gl.patch"

qmake -project -o ${PN}.pro -after "CONFIG+=opengl" \
-after "QT+=xml opengl script" \
QMAKE_LIBS_OPENGL="-lGLU -lGL" || die "qmake failed"
}

src_install() {
dobin ${PN}
dodoc roadmap.txt changelog.txt bugs.txt
domenu ${PN}.desktop
newicon images/structuresynth.png ${PN}.png
}
diff -x '*~' -purN a/SyntopiaCore/GLEngine/Raytracer/Sampler.h b/SyntopiaCore/GLEngine/Raytracer/Sampler.h
--- a/SyntopiaCore/GLEngine/Raytracer/Sampler.h	2010-11-04 20:02:46.0 +0100
+++ b/SyntopiaCore/GLEngine/Raytracer/Sampler.h	2017-11-01 04:42:46.320970684 +0100
@@ -1,5 +1,6 @@
 #pragma once
 
+#include 
 #include "SyntopiaCore/Math/Random.h"
 #include "SyntopiaCore/Math/Vector3.h"
 
diff -x '*~' -purN a/SyntopiaCore/GLEngine/Raytracer/VoxelStepper.cpp b/SyntopiaCore/GLEngine/Raytracer/VoxelStepper.cpp
--- a/SyntopiaCore/GLEngine/Raytracer/VoxelStepper.cpp	2010-09-08 21:25:30.0 +0200
+++ b/SyntopiaCore/GLEngine/Raytracer/VoxelStepper.cpp	2017-11-01 04:46:51.052969311 +0100
@@ -122,7 +122,7 @@ namespace SyntopiaCore {
 		currentT = p;
 
 		// We do not intersect grid.
-		if (!found) return false;
+		if (!found) return 0;
 }
 
 stepX = (dir.x() > 0) ? 1 : -1;
diff -x '*~' -purN a/SyntopiaCore/GLEngine/Sphere.h b/SyntopiaCore/GLEngine/Sphere.h
--- a/SyntopiaCore/GLEngine/Sphere.h	2010-08-11 15:12:22.0 +0200
+++ b/SyntopiaCore/GLEngine/Sphere.h	2017-11-01 04:42:55.864970632 +0100
@@ -1,5 +1,6 @@
 #pragma once
 
+#include 
 #include "SyntopiaCore/Math/Vector3.h"
 #include "Object3D.h"