Building JDK8 b106 with sysroot and isystem

[Jungwoo Ha]

Thanks. I revisited what I did earlier and checked what you guys mentioned
here.
I passed --with-tools-dir and --with-sys-root to specify the compiler and
the libc location.

As I described in my original email, the configure ignores sysroot and
extra_cflags when checking for C++ compiler
* configure:20253: checking whether the C compiler works
   Here ac_link is defined as "$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS
$LDFLAGS conftest.$ac_ext $LIBS >&5"
   There is no place that SYS_ROOT is added nor $with_extra_cflags.
   If I manually add -isystem and --sysroot= on the ac_link this part is
resolved.

I guess this should be somehow fixed, right?

Jungwoo



On Wed, Sep 18, 2013 at 2:55 AM, Magnus Ihse Bursie <
magnus.ihse.bursie at oracle.com> wrote:

> On 2013-09-17 20:01, Jungwoo Ha wrote:
>
>> Can you tell me what is the expected layout of devkit?
>> I'll put things together and will try.
>>
>
> --with-devkit=/foo is a shorthand for
> --with-tools-dir=/foo/bin --with-sys-root=/foo/<host_**alias>/libc
> or
> --with-tools-dir=/foo/bin --with-sys-root=/foo/<host>/**sys-root
> depending on wether /foo/<host_alias>/libc is an existing directory or not.
>
> <host> and <host_alias> are the name of the target platform as defined by
> configure, e.g. "x86_64-pc-linux-gnu" (host) or "x86-linux-gnu"
> (host_alias).
>
> I believe this is a common way to structure cross-compilation tools, which
> was the primary reason to include this shortcut.
>
> If this layout does not match your need, it is probably easier to just use
> --with-devit and --with-tools-dir separately. On the other hand, if you
> think that your layout is common, we welcome patches that adds a check for
> it in --with-devkit. After all, the idea with --with-devkit was to make
> cross-compilation easier.
>
> /Magnus
>