|
List Info
Thread: GNU Cross Compiler Support?
|
|
| GNU Cross Compiler Support? |
|
2007-01-15 10:18:20 |
I have another cross compiler problem.
We are running a cross compiler toolchain under
Cygwin/Windows. This
toolchain uses a cuistomized gcc compiler to generate code
for a linux
target.
When trying to build boost using this cross compiler, bjam
still detects
that it is running on cygwin and windows, and tries to build
DLLs
instead of linux shared libraries. Is there any chance to
configure bjam
to run under windows or cygwin but generate code for a
different target,
either by special command line options or even by compiling
a custom
version of bjam?
I have looked into jam some time ago but had to drop it
because it was
unable to differentiate between host and target
configuration (like
running under a windows host but generate code for Linux).
Seem I am
faling into the same trap again...
Any help is appreciated!
Norbert Unterberg
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
|
|
| Re: GNU Cross Compiler Support? |
|
2007-01-18 09:47:43 |
On Monday 15 January 2007 19:18, Norbert Unterberg wrote:
>
> I have another cross compiler problem.
>
> We are running a cross compiler toolchain under
Cygwin/Windows. This
> toolchain uses a cuistomized gcc compiler to generate
code for a linux
> target.
>
> When trying to build boost using this cross compiler,
bjam still detects
> that it is running on cygwin and windows, and tries to
build DLLs
> instead of linux shared libraries. Is there any chance
to configure bjam
> to run under windows or cygwin but generate code for a
different target,
> either by special command line options or even by
compiling a custom
> version of bjam?
Do you mean the extension is wrong, or that the build
process is wrong?
I've looked at the code in question and there are very few
platform-specific
differences.
> I have looked into jam some time ago but had to drop it
because it was
> unable to differentiate between host and target
configuration (like
> running under a windows host but generate code for
Linux). Seem I am
> faling into the same trap again...
We have internal mechanism to handle build-os != target-os,
but nobody
used it so far, so no wonder that gcc or shared library
might be still
looking at build os. Just report the particular issues you
run into
and I'll try to address them when I get back home on
Monday.
- Volodya
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
|
|
| Re: GNU Cross Compiler Support? |
|
2007-01-19 13:29:57 |
Norbert Unterberg schrieb:
> Volodya,
>
> Vladimir Prus schrieb:
>> On Monday 15 January 2007 19:18, Norbert Unterberg
wrote:
>>
>>> We are running a cross compiler toolchain under
Cygwin/Windows. This
>>> toolchain uses a cuistomized gcc compiler to
generate code for a linux
>>> target.
>>>
>> Do you mean the extension is wrong, or that the
build process is wrong?
>> I've looked at the code in question and there are
very few platform-specific
>> differences.
>
> The build does not succeed.
>
> I have downloaded and extracted boost, so I have a
boost_1_33_1 folder.
> I then downloaded boost-jam-3.1.13-1-ntx86 and copied
the bjam.exe into
> this folder.
Ok, some additional information that might help.
A collegue has downloaded the bjam sources and compiled them
under cygwin. When
using this self-made bjam to cross-build boost, bjam
produces the correct *.a
static libraries, but still produces dll files instead of
.so files as shared
libraries. And the files are really windows DLLs, you can
open them with the
dependency viewer and see that they reference the
cygwin.dll.
Unfortunately, I do not know the command line my collegue
used to build boost.
Maybe this is just because I do not know the correct bjam
switch?
Norbert
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
|
|
| Re: GNU Cross Compiler Support? |
|
2007-01-24 09:57:16 |
|
| Volodya,
> We have internal mechanism to handle build-os != target-os, but nobody
> used it so far, so no wonder that gcc or shared library might be still
> looking at build os. Just report the particular issues you run into
> and I'll try to address them when I get back home on Monday.
Any new information on this issue? Is there a command line switch to
force bjam to a particular target-os? I have searched the list archive
on gmane for "target-os" but only found some mailings about using a
feature inside of jam files. Can you give us some help?
Norbert
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
|
| Re: GNU Cross Compiler Support? |
|
2007-01-24 15:49:11 |
|
Vladimir Prus schrieb:
> On Wednesday 24 January 2007 18:57, Norbert Unterberg wrote:
>> Volodya,
>>
>>> We have internal mechanism to handle build-os != target-os, but nobody
>>> used it so far, so no wonder that gcc or shared library might be still
>>> looking at build os. Just report the particular issues you run into
>>> and I'll try to address them when I get back home on Monday.
>> Any new information on this issue? Is there a command line switch to
>> force bjam to a particular target-os? I have searched the list archive
>> on gmane for "target-os" but only found some mailings about using a
>> feature inside of jam files. Can you give us some help?
>
> Ah, to begin with, it turns out that you're using Boost.Build V1. I kinda assumed that you're
> using V2. I'd suggest to obtain CVS version of Boost (preferrably RC_1_34_0 branch),
> and try it. V1 is kinda unsupported at this time.
Thank you for taking the time to help me.
I am confused. All I wanted to do is to build the current official boost library
(which is 1.33.1 I guess). To do that, I downloaded boost 1.33.1 and boost-jam.
I do not know about boost.build. I thought that the boost archive contains
everything to build the boost libraries. Or is boost.build v2 included in
rc_1_34_0 so that you suggest using that version?
When will boost 1.34 be released? Is it stable to use it in a production
environment?
I am sorry, I thought I could download boost, compile it and start using it im
my project, without spending a week learning the internals of its build system...
To answer your question in your other mail, I did not build bjam, I used the
windows binary. This is because the getting starting guide suggests you just
need a running bjam executable, no matter which one, and bjam automatically
detects the build environment.
As I said, a colleague of mine did build bjam under cygwin and he managed to
build boost, but he did get cygwin DLL files instead of linux shared libraries.
That's why I keep asking for the magic switch  to tell bjam we have a LINUX
target created under a CYGWIN host.
We have cross-compiled another library, and all we did there was running
./configure -host x86-486-linux-gnu, and all went well. But what is the
corresponding option for bjam?
Norbert
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
|
| Re: GNU Cross Compiler Support? |
|
2007-01-25 12:05:52 |
|
| Vladimir Prus schrieb:
> On Wednesday 24 January 2007 18:57, Norbert Unterberg wrote:
>
> Ah, to begin with, it turns out that you're using Boost.Build V1. I kinda assumed that you're
> using V2. I'd suggest to obtain CVS version of Boost (preferrably RC_1_34_0 branch),
> and try it. V1 is kinda unsupported at this time.
Latest info on my progress:
I got the the CVS version of RC_1_34_0. I then compiled my own version of bjam
from those sources, running on cygwin.
I then edited the tools/build/v2/user-config.jam file and added something like
using gcc : : x86_486-g++ ;
(x86_486-g++ is the name of our our linux cross compiler running on cygwin)
Running bjam stage began compiling boost, but still with some problems:
* It still tried to create dll files instead of .so shared libraries
* Compilation failed with an error "bad parameter thread" or "parameter thread
not supported" or something like that (can't remember the exact wording).
So I guess boost.build2 is still using my host settings to compile the target
files, which is wrong in my case. Do you see any chance I can change that? I
have looked in some of the jam files but the jam language is just like chinese
to me :-(
A temporary solution might be to run the build system on some linux PC so that I
get the correct files, but if there is a way to use bjam for cross compiling I
would like to use that.
Norbert
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
|
[1-6]
|
|