All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/5] webkitgtk: fix compile error when len(TMPDIR) == 410
Date: Fri, 1 Dec 2017 09:46:00 +0800	[thread overview]
Message-ID: <8d0f0ec4-82a6-c63e-2fac-e012e9ee2ec5@windriver.com> (raw)
In-Reply-To: <bddd691d-b200-a99a-9909-99ab33da7adb@linux.intel.com>

Hi Alexander,

On 11/30/2017 07:34 PM, Alexander Kanavin wrote:
> On 11/30/2017 03:45 AM, Robert Yang wrote:
>> One of the gcc command line was too long (longer than 160,000 characters) when
>> len(TMPDIR) == 410, so there was an "Argument list too long" error:
>> $ bitbake webkitgtk
>> i586-poky-linux-g++: error trying to exec [snip] execv: Argument list too long
>>
>> The cmake doesn't support relative path, so we have to edit flags.make to fix
>> the problem:
>> - Replace -I${RECIPE_SYSROOT} with -I=
>> - Replace "-I${S}/path1/in/S -I ${S}/path2/in/S" with
>>    "-iprefix ${S} -iwithprefixbefore /path1/in/S -iwithprefixbefore /path2/in/S"
> 
> Where does flags.make come from? Can you fix the problem at the source, rather 
> than patch the file with a custom, unwieldy function after the fact?

The flags.make is generated by cmake, and as I said in the commit message:

"The cmake doesn't support relative path, so we have to edit flags.make to fix
the problem"

I'm not familiar with cmake, please let me know if there is a way to make
it generate a relative path in flags.make.

// Robert

> 
> Alex
> 


  reply	other threads:[~2017-12-01  1:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30  1:45 [PATCH 0/5] fix build when len(TMPDIR) == 410 Robert Yang
2017-11-30  1:45 ` [PATCH 1/5] go-native: fix PATH issue " Robert Yang
2017-11-30 11:33   ` Alexander Kanavin
2017-12-01  1:40     ` Robert Yang
2017-12-01  8:25       ` Alexander Kanavin
2017-11-30  1:45 ` [PATCH 2/5] go-native: fix import error " Robert Yang
2017-11-30  1:45 ` [PATCH 3/5] ninja: fix for llvm build " Robert Yang
2017-11-30  1:45 ` [PATCH 4/5] webkitgtk: fix compile error " Robert Yang
2017-11-30 11:34   ` Alexander Kanavin
2017-12-01  1:46     ` Robert Yang [this message]
2017-12-01  8:26       ` Alexander Kanavin
2017-12-01  9:49         ` Alexander Kanavin
2017-12-04  6:16           ` Robert Yang
2017-11-30  1:45 ` [PATCH 5/5] sqlite3: use 1024 for MAX_PATHNAM Robert Yang
2018-01-09  3:09 ` [PATCH 0/5] fix build when len(TMPDIR) == 410 Robert Yang
2018-01-19  1:52 ` Robert Yang
2018-02-02  3:34 ` Robert Yang
2018-03-06  1:51 ` Robert Yang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8d0f0ec4-82a6-c63e-2fac-e012e9ee2ec5@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=alexander.kanavin@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.