From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <435488DB.2090406@domain.hid> Date: Tue, 18 Oct 2005 08:32:11 +0300 From: Heikki Lindholm MIME-Version: 1.0 Subject: Re: [Xenomai-help] compiling xenomai on x86_64 References: <4353F109.7000707@domain.hid> <4353F411.4000500@domain.hid> <4353F896.1040508@domain.hid> <435402B4.5060004@domain.hid> <435403C8.80400@domain.hid> <43540531.8050304@domain.hid> <435406E0.8020405@domain.hid> <435409AD.6060705@domain.hid> <43540BB5.9040401@domain.hid> <17236.13470.692381.730895@domain.hid> In-Reply-To: <17236.13470.692381.730895@domain.hid> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix Cc: xenomai@xenomai.org Gilles Chanteperdrix kirjoitti: > Philippe Gerum wrote: > > Probably grabbing more stuff from the kernel cflags into XENO_ARCH_FLAGS (e.g. > > -m[0-9]* to start with). Gilles, would this be ok? > > Probably, but last time I checked that, the ppc-compiled version of the > dummy program used at configuration time to extract the arch flags from > Kbuild was not work here, because of ahem, quoting issues. There are > some -m arguments we do not want (such as for example the -msoft-float > used in ppc kernel space). Hmm. Does this also mean that the compiler isn't taken from kernel config at all? I tried compiling Xeno on a ppc box the other day, where the kernel had already been compiled by gcc-3.4 on another host. The box also had gcc-3.4, but 3.3 as the default (old debian.) Xenomai config seemed to pick the wrong compiler, because modules complained at load time of 3.3 vs. 3.4 conflict. The kernel compile host's default was gcc-4.0, so it was also forced to use gcc-3.4. -- Heikki Lindholm