Re: mxe-build: undefined references

[Torsten]

On 27.03.2014 11:39, John D wrote:
> 
> 
> -----Original Message-----
> From: Torsten [mailto:address@hidden 
> Sent: Thursday, March 27, 2014 6:32 AM
> To: John D; octave maintainers mailing list
> Subject: Re: mxe-build: undefined references
> 
> On 22.03.2014 00:43, John D wrote:
>>
>>
>> -----Original Message-----
>> From: Torsten [mailto:address@hidden
>> Sent: Friday, March 21, 2014 2:13 PM
>> To: John D
>> Subject: Re: mxe-build: undefined references
>>
>> On 21.03.2014 18:55, John D wrote:
>>>
>>>
>>> -----Original Message-----
>>> From: Torsten [mailto:address@hidden
>>> Sent: Friday, March 21, 2014 1:22 PM
>>> To: John D; 'Michael Goffioul'
>>> Cc: 'Octave Maintainers List'
>>> Subject: Re: mxe-build: undefined references
>>>
>>> On 16.03.2014 18:32, John D wrote:
>>>> I'm doing a clean make on my system right now to verify it works 
>>>> still as a new build.
>>>> My octave gui-release was from change set ca1648b2e673 - set default 
>>>> toolkit when registering toolkits
>>>>
>>>
>>> Here still the same undefined references after a fresh bootsrap, 
>>> configure, make, make dist before using the archive for the mxe
>> cross-build.
>>>
>>> Torsten
>>>
>>>
>>> I cant remember now if you said what OS you are trying to compile on?
>>>
>>
>> Linux (Ubuntu)
>>
>>
>> --
>>
>> Out of interest, had you tried creating a 3.8.1 build using the make 
>> dist from the sources to generate the octave source tarball? Ie: can 
>> we prove that its an issue with the devel version, or whether an issue 
>> with make dist on your computer?
>>
> 
> Reverting src/octave.mk to its original version and then
>   make tar-dist
> successfully builds the stable version.
> 
> Torsten
> 
> --
> 
> How about checking out stable-octave at the 3.8.1 tag , creating the
> tarball, changing the checksum to match and then trying to build mxe-octave
> ?
> 

The mxe-built from the current stable branch can be finished
successfully, too. I will cross-check the gui-release branch again.

Torsten