linux-kernel - Re: CONFIG_NLS=m resulting in undefined reference to utf16s_to

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110113075556.789ac3c3@jbarnes-vaio.home>
Date:	Thu, 13 Jan 2011 07:55:56 -0800
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Len Brown <lenb@...nel.org>
Cc:	Narendra_K@...l.com, linux-kernel@...r.kernel.org,
	linux-next@...r.kernel.org, sfr@...b.auug.org.au,
	Matt_Domsch@...l.com, Charles_Rose@...l.com,
	Surya_Prabhakar@...l.com
Subject: Re: CONFIG_NLS=m resulting in undefined reference to
 utf16s_to_utf8s causing build failure

On Wed, 12 Jan 2011 22:23:55 -0500 (EST)
Len Brown <lenb@...nel.org> wrote:
> > So there's no other ACPI code that depends on this function?  I'd hate
> > to make PCI depend on NLS, so assuming ACPI doesn't need it (in which
> > case the select or depend should be there), I guess it should be pulled
> > into a common file that will always be included.
> 
> No, nothing in the ACPI code uses utf16s_to_utf8s.
> 
> I don't know anything about NLS, but it appears to be
> something that file systems (befs, cifs, fat, hfs, isofs, jfs, etc)
> use to to support native languages.
> 
> BTW. I don't understand why pci-label.o appears twice above.
> It used to be just the 2nd one, that depends on CONFIG_DMI.

Ok, I'll drop this patch for now then since I haven't seen a fix yet
and need to get Linus the rest of the changes.

Thanks,
Jesse
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/