Hello
Thx for the fastest almost-full-featured web-browser in existence!
Just wondering if there's any development happening, particularly wrt
javascript.
thx!
Monday, 29 June 2015
Re: [gccsdk] Unable to load Shared library with GCC 4.7.4.1
Oops!, I forgot to change the subject heading to something meaningful.
On Mon, June 29, 2015 8:00 pm, Lee Noar <leenoar@sky.com> wrote:
>> I set an <appname>$LD$ENV variable for each application that uses the
>> library. It is usually just set to "LD_LIBRARY_PATH=DRW:" but can also
>> include path variables to any application specific shared libraries.
>
> It looks like I may have made a mistake in r6733 from about a year ago
> when dealing with LD_LIBRARY_PATH.
> If I email you a new dynamic linker, can you try it and see if it fixes
> your problem?
>
Yes that is a good idea.
Regards,
Pete Miller.
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
On Mon, June 29, 2015 8:00 pm, Lee Noar <leenoar@sky.com> wrote:
>> I set an <appname>$LD$ENV variable for each application that uses the
>> library. It is usually just set to "LD_LIBRARY_PATH=DRW:" but can also
>> include path variables to any application specific shared libraries.
>
> It looks like I may have made a mistake in r6733 from about a year ago
> when dealing with LD_LIBRARY_PATH.
> If I email you a new dynamic linker, can you try it and see if it fixes
> your problem?
>
Yes that is a good idea.
Regards,
Pete Miller.
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
Re: [gccsdk] gcc Digest, Vol 103, Issue 5
On Mon, June 29, 2015 8:00 pm, Lee Noar <leenoar@sky.com> wrote:
>> I set an <appname>$LD$ENV variable for each application that uses the
>> library. It is usually just set to "LD_LIBRARY_PATH=DRW:" but can also
>> include path variables to any application specific shared libraries.
>
> It looks like I may have made a mistake in r6733 from about a year ago
> when dealing with LD_LIBRARY_PATH.
> If I email you a new dynamic linker, can you try it and see if it fixes
> your problem?
>
Yes that is a good idea.
Regards,
Pete Miller.
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
>> I set an <appname>$LD$ENV variable for each application that uses the
>> library. It is usually just set to "LD_LIBRARY_PATH=DRW:" but can also
>> include path variables to any application specific shared libraries.
>
> It looks like I may have made a mistake in r6733 from about a year ago
> when dealing with LD_LIBRARY_PATH.
> If I email you a new dynamic linker, can you try it and see if it fixes
> your problem?
>
Yes that is a good idea.
Regards,
Pete Miller.
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
Re: [gccsdk] fontconfig build issue
On Mon, Jun 29, 2015 at 09:15:10PM +0100, Lee Noar wrote:
> John Ballance wrote:
> >p.s. I'm building quite a list of things where I have local patches to
> >the autobuilder scripts. Should theyy all come through you, or might it
> >be simpler if I put them in directly? (I guess I'm also asking whether
> >that could be arranged..)
>
> I think it's John Tytgat and Theo who have the power to give svn
> write access.
It's possible to allow write access, but it might be good if you posted
the patches here to begin with, just to make sure we're on the same page.
There are lots of moving parts to the autobuilder and (currently) we aren't
testing them all very regularly, so a little care is required in that
changing one thing to fix a problem here may cause issues for another
package over there. We can usually spot that by glancing over the code but
it might be something that might not be obvious if you aren't familiar with
some of the other packages.
As previously mentioned, just posting them to the list as attachments is
sufficient. If you want to get high tech (and don't mind dealing with
another version control system), git interfaces nicely with svn, handles
commits locally and will generate patch emails automatically.
Theo
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
> John Ballance wrote:
> >p.s. I'm building quite a list of things where I have local patches to
> >the autobuilder scripts. Should theyy all come through you, or might it
> >be simpler if I put them in directly? (I guess I'm also asking whether
> >that could be arranged..)
>
> I think it's John Tytgat and Theo who have the power to give svn
> write access.
It's possible to allow write access, but it might be good if you posted
the patches here to begin with, just to make sure we're on the same page.
There are lots of moving parts to the autobuilder and (currently) we aren't
testing them all very regularly, so a little care is required in that
changing one thing to fix a problem here may cause issues for another
package over there. We can usually spot that by glancing over the code but
it might be something that might not be obvious if you aren't familiar with
some of the other packages.
As previously mentioned, just posting them to the list as attachments is
sufficient. If you want to get high tech (and don't mind dealing with
another version control system), git interfaces nicely with svn, handles
commits locally and will generate patch emails automatically.
Theo
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
Re: [gccsdk] fontconfig build issue
On 29/06/15 20:26, John Ballance wrote:
> Hi
>
> On 29/06/2015 20:11, Lee Noar wrote:
>> On 29/06/15 19:05, John Ballance wrote:
>>> Hi Lee
[snip]
>>> Probably something simple that I'm missing, but the libfontconfig1
>>> directory
>>> doesn't exist in the package directory at this point.
>>
>> Are you building shared libraries? libfontconfig1 is the shared library
> I will need to build shared libraries, but at this stage not sure. I'll
> try again with the libfontconfig1 removed from the AB line
>
> .. build does complete, thanks
>
> shared libraries. ... I've missed this.. how do I globally turn on the
> build of shared libraries please?
In the directory where you build the packages, create a text file called:
build-setvars
containing the line:
RO_SHAREDLIBS=yes
So, for example, I have this:
autobuilder
|
autobuilt
| |
| build-setvars
|
cross
|
env
|
gcc4
where autobuilt is a directory I created myself to build the packages
in. I then do:
cd autobuilt
../autobuilder/build -d fontconfig
The autobuilder automatically reads the build-setvars file each time
it's invoked so shared libraries are always enabled.
> Thanks
> John
>
> p.s. I'm building quite a list of things where I have local patches to
> the autobuilder scripts. Should theyy all come through you, or might it
> be simpler if I put them in directly? (I guess I'm also asking whether
> that could be arranged..)
I think it's John Tytgat and Theo who have the power to give svn write
access.
Lee.
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
> Hi
>
> On 29/06/2015 20:11, Lee Noar wrote:
>> On 29/06/15 19:05, John Ballance wrote:
>>> Hi Lee
[snip]
>>> Probably something simple that I'm missing, but the libfontconfig1
>>> directory
>>> doesn't exist in the package directory at this point.
>>
>> Are you building shared libraries? libfontconfig1 is the shared library
> I will need to build shared libraries, but at this stage not sure. I'll
> try again with the libfontconfig1 removed from the AB line
>
> .. build does complete, thanks
>
> shared libraries. ... I've missed this.. how do I globally turn on the
> build of shared libraries please?
In the directory where you build the packages, create a text file called:
build-setvars
containing the line:
RO_SHAREDLIBS=yes
So, for example, I have this:
autobuilder
|
autobuilt
| |
| build-setvars
|
cross
|
env
|
gcc4
where autobuilt is a directory I created myself to build the packages
in. I then do:
cd autobuilt
../autobuilder/build -d fontconfig
The autobuilder automatically reads the build-setvars file each time
it's invoked so shared libraries are always enabled.
> Thanks
> John
>
> p.s. I'm building quite a list of things where I have local patches to
> the autobuilder scripts. Should theyy all come through you, or might it
> be simpler if I put them in directly? (I guess I'm also asking whether
> that could be arranged..)
I think it's John Tytgat and Theo who have the power to give svn write
access.
Lee.
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
Re: [gccsdk] fontconfig build issue
Hi
.. build does complete, thanks
shared libraries. ... I've missed this.. how do I globally turn on the build of shared libraries please?
Thanks
John
p.s. I'm building quite a list of things where I have local patches to the autobuilder scripts. Should theyy all come through you, or might it be simpler if I put them in directly? (I guess I'm also asking whether that could be arranged..)
On 29/06/2015 20:11, Lee Noar wrote:
On 29/06/15 19:05, John Ballance wrote:I will need to build shared libraries, but at this stage not sure. I'll try again with the libfontconfig1 removed from the AB line
Hi Lee
Thanks for the check. begs the Q of what it may be...
I did then try the --disable-docs which did bypass that issue, then
grumble in the riscpkg stage:
add-riscpkg: Adding files for the RISC OS Packaging Project
add-riskpkg: Using Debian description
add-riscpkg: Setting filetypes...
add-riskpkg: Finished
Autobuilder: Packaging files
Autobuilder: Packaging as fontconfig-config
-rw-rw-rw- 1 jb jb 88085 Jun 29 19:00
/home/jb/GCCSDK471/autobuilder/autobuilder_packages/Fonts/fontconfig-config_2.11.0-1.zip
Autobuilder: Packaging as fontconfig
-rw-rw-rw- 1 jb jb 5704386 Jun 29 19:00
/home/jb/GCCSDK471/autobuilder/autobuilder_packages/Fonts/fontconfig_2.11.0-1.zip
Autobuilder: Packaging as libfontconfig1-dev
-rw-rw-rw- 1 jb jb 860002 Jun 29 19:00
/home/jb/GCCSDK471/autobuilder/autobuilder_packages/Library/libfontconfig1-dev_2.11.0-1.zip
Autobuilder: Packaging as libfontconfig1
Autobuilder: package directory missing libfontconfig1
Package fontconfig: ***Failure***
Build for package "fontconfig" failed
Probably something simple that I'm missing, but the libfontconfig1 directory
doesn't exist in the package directory at this point.
Are you building shared libraries? libfontconfig1 is the shared library
.. build does complete, thanks
shared libraries. ... I've missed this.. how do I globally turn on the build of shared libraries please?
Thanks
John
p.s. I'm building quite a list of things where I have local patches to the autobuilder scripts. Should theyy all come through you, or might it be simpler if I put them in directly? (I guess I'm also asking whether that could be arranged..)
package and is only created if shared libraries are enabled. The
autobuilder expects to always find it though because it's mentioned at
the top of setvars in AB_PACKAGES. I guess I need to set AB_PACKAGES
here according to whether shared libraries are enabled or not.
IS there any AB type definition that brings in the native cc compiler,
not the arm one?
No I don't think so, because the autobuilder doesn't know which compiler
to use when. Sometimes the package authors will specifically support
cross compiling and allow you to set HOST_CC. Sometimes you have to
configure and build the package twice (in setvars) for native and
RISC OS to get native compiled tools.
In this case though all the html documentation files seem to be
present in doc/fontconfig-devel even with --disable-doc (in fact
the debian patch adds them), so I'll alter setvars to add this
option and fix AB_PACKAGES as above.
Lee.
--
Stop press! Just announced -
Most Trusted Broadband Provider in the 2014 Moneywise Customer Services Awards
Most Trusted Broadband Provider in the 2014 Moneywise Customer Services Awards
For full details of see https://www.utilitywarehouse.co.uk/reviews?exref=095761
Intrigued? Call me
John Ballance C.Eng MIET - jwb@macpcrepair.co.uk - 07976 295923
Re: [gccsdk] fontconfig build issue
On 29/06/15 19:05, John Ballance wrote:
> Hi Lee
>
> Thanks for the check. begs the Q of what it may be...
>
> I did then try the --disable-docs which did bypass that issue, then
> grumble in the riscpkg stage:
>
> add-riscpkg: Adding files for the RISC OS Packaging Project
> add-riskpkg: Using Debian description
> add-riscpkg: Setting filetypes...
> add-riskpkg: Finished
> Autobuilder: Packaging files
> Autobuilder: Packaging as fontconfig-config
> -rw-rw-rw- 1 jb jb 88085 Jun 29 19:00
> /home/jb/GCCSDK471/autobuilder/autobuilder_packages/Fonts/fontconfig-config_2.11.0-1.zip
> Autobuilder: Packaging as fontconfig
> -rw-rw-rw- 1 jb jb 5704386 Jun 29 19:00
> /home/jb/GCCSDK471/autobuilder/autobuilder_packages/Fonts/fontconfig_2.11.0-1.zip
> Autobuilder: Packaging as libfontconfig1-dev
> -rw-rw-rw- 1 jb jb 860002 Jun 29 19:00
> /home/jb/GCCSDK471/autobuilder/autobuilder_packages/Library/libfontconfig1-dev_2.11.0-1.zip
> Autobuilder: Packaging as libfontconfig1
> Autobuilder: package directory missing libfontconfig1
> Package fontconfig: ***Failure***
> Build for package "fontconfig" failed
>
>
> Probably something simple that I'm missing, but the libfontconfig1 directory
> doesn't exist in the package directory at this point.
Are you building shared libraries? libfontconfig1 is the shared library
package and is only created if shared libraries are enabled. The
autobuilder expects to always find it though because it's mentioned at
the top of setvars in AB_PACKAGES. I guess I need to set AB_PACKAGES
here according to whether shared libraries are enabled or not.
> IS there any AB type definition that brings in the native cc compiler,
> not the arm one?
No I don't think so, because the autobuilder doesn't know which compiler
to use when. Sometimes the package authors will specifically support
cross compiling and allow you to set HOST_CC. Sometimes you have to
configure and build the package twice (in setvars) for native and
RISC OS to get native compiled tools.
In this case though all the html documentation files seem to be
present in doc/fontconfig-devel even with --disable-doc (in fact
the debian patch adds them), so I'll alter setvars to add this
option and fix AB_PACKAGES as above.
Lee.
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
> Hi Lee
>
> Thanks for the check. begs the Q of what it may be...
>
> I did then try the --disable-docs which did bypass that issue, then
> grumble in the riscpkg stage:
>
> add-riscpkg: Adding files for the RISC OS Packaging Project
> add-riskpkg: Using Debian description
> add-riscpkg: Setting filetypes...
> add-riskpkg: Finished
> Autobuilder: Packaging files
> Autobuilder: Packaging as fontconfig-config
> -rw-rw-rw- 1 jb jb 88085 Jun 29 19:00
> /home/jb/GCCSDK471/autobuilder/autobuilder_packages/Fonts/fontconfig-config_2.11.0-1.zip
> Autobuilder: Packaging as fontconfig
> -rw-rw-rw- 1 jb jb 5704386 Jun 29 19:00
> /home/jb/GCCSDK471/autobuilder/autobuilder_packages/Fonts/fontconfig_2.11.0-1.zip
> Autobuilder: Packaging as libfontconfig1-dev
> -rw-rw-rw- 1 jb jb 860002 Jun 29 19:00
> /home/jb/GCCSDK471/autobuilder/autobuilder_packages/Library/libfontconfig1-dev_2.11.0-1.zip
> Autobuilder: Packaging as libfontconfig1
> Autobuilder: package directory missing libfontconfig1
> Package fontconfig: ***Failure***
> Build for package "fontconfig" failed
>
>
> Probably something simple that I'm missing, but the libfontconfig1 directory
> doesn't exist in the package directory at this point.
Are you building shared libraries? libfontconfig1 is the shared library
package and is only created if shared libraries are enabled. The
autobuilder expects to always find it though because it's mentioned at
the top of setvars in AB_PACKAGES. I guess I need to set AB_PACKAGES
here according to whether shared libraries are enabled or not.
> IS there any AB type definition that brings in the native cc compiler,
> not the arm one?
No I don't think so, because the autobuilder doesn't know which compiler
to use when. Sometimes the package authors will specifically support
cross compiling and allow you to set HOST_CC. Sometimes you have to
configure and build the package twice (in setvars) for native and
RISC OS to get native compiled tools.
In this case though all the html documentation files seem to be
present in doc/fontconfig-devel even with --disable-doc (in fact
the debian patch adds them), so I'll alter setvars to add this
option and fix AB_PACKAGES as above.
Lee.
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
Subscribe to:
Posts (Atom)